Hi Eugeniu > In the context of M3N-ULCB (RTP0RC77965SKBX010SA00) board bring-up, it's > rather pointless to add a new "renesas,m3nulcb" compatible string. Any > SoC-level differences between the two variants of ULCB (M3 and M3-N) > should be successfully covered by making use of existing > "renesas,r8a7796" and "renesas,r8a77965" compatibles. > > Prior to adding M3-N Starter Kit to the list, rename: > - "renesas,h3ulcb" => "renesas,ulcb" > - "renesas,m3ulcb" => "renesas,ulcb" I'm not sure detail, but does it mean, both H3/M3 board can boot/work with "renesas,ulcb" compatible if we had such driver/soc ? > diff --git a/Documentation/devicetree/bindings/arm/shmobile.txt b/Documentation/devicetree/bindings/arm/shmobile.txt > index d8cf740132c6..f391dba10574 100644 > --- a/Documentation/devicetree/bindings/arm/shmobile.txt > +++ b/Documentation/devicetree/bindings/arm/shmobile.txt > @@ -81,7 +81,7 @@ Boards: > compatible = "renesas,gose", "renesas,r8a7793" > - H3ULCB (R-Car Starter Kit Premier, RTP0RC7795SKBX0010SA00 (H3 ES1.1)) > H3ULCB (R-Car Starter Kit Premier, RTP0RC77951SKBX010SA00 (H3 ES2.0)) > - compatible = "renesas,h3ulcb", "renesas,r8a7795" > + compatible = "renesas,ulcb", "renesas,r8a7795" > - Henninger > compatible = "renesas,henninger", "renesas,r8a7791" > - iWave Systems RZ/G1C Single Board Computer (iW-RainboW-G23S) > @@ -105,7 +105,7 @@ Boards: > - Lager (RTP0RC7790SEB00010S) > compatible = "renesas,lager", "renesas,r8a7790" > - M3ULCB (R-Car Starter Kit Pro, RTP0RC7796SKBX0010SA09 (M3 ES1.0)) > - compatible = "renesas,m3ulcb", "renesas,r8a7796" > + compatible = "renesas,ulcb", "renesas,r8a7796" > - Marzen (R0P7779A00010S) > compatible = "renesas,marzen", "renesas,r8a7779" > - Porter (M2-LCDP) My opinion is that if you want to exchange compatible name, related all driver/document should be exchanged in same patch. For example, above "h3ulcb" case, patch subject indicates "rename h3ulcb" or something, and it include [03/14][04/14][05/14][06/14]. Same for m3
