| Message ID | 20161125075614.GB14431@verge.net.au (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On Fri, Nov 25, 2016 at 8:56 AM, Simon Horman <horms+renesas@verge.net.au> wrote: > Simply document new compatibility strings as the driver is already > activated using a fallback compatibility string. > > These compat strings are in keeping with those for all other > Renesas ARM based SoCs with sh_mmcif enabled in mainline. > > Signed-off-by: Simon Horman <horms+renesas@verge.net.au> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be> Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 25 November 2016 at 08:56, Simon Horman <horms+renesas@verge.net.au> wrote: > Simply document new compatibility strings as the driver is already > activated using a fallback compatibility string. > > These compat strings are in keeping with those for all other > Renesas ARM based SoCs with sh_mmcif enabled in mainline. > > Signed-off-by: Simon Horman <horms+renesas@verge.net.au> Thanks, applied for next! Kind regards Uffe > --- > Reposted with r8a7778 instead of r8a7779 in subject > > I have also posted patches to use these new compat strings > to bring the DT files of the SoCs in question in-line with those > for other Renesas ARM based SoCs with sh_mmcif enabled in mainline. > --- > Documentation/devicetree/bindings/mmc/renesas,mmcif.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mmc/renesas,mmcif.txt b/Documentation/devicetree/bindings/mmc/renesas,mmcif.txt > index ff611fa66871..e4ba92aa035e 100644 > --- a/Documentation/devicetree/bindings/mmc/renesas,mmcif.txt > +++ b/Documentation/devicetree/bindings/mmc/renesas,mmcif.txt > @@ -8,11 +8,14 @@ Required properties: > > - compatible: should be "renesas,mmcif-<soctype>", "renesas,sh-mmcif" as a > fallback. Examples with <soctype> are: > + - "renesas,mmcif-r8a73a4" for the MMCIF found in r8a73a4 SoCs > - "renesas,mmcif-r8a7740" for the MMCIF found in r8a7740 SoCs > + - "renesas,mmcif-r8a7778" for the MMCIF found in r8a7778 SoCs > - "renesas,mmcif-r8a7790" for the MMCIF found in r8a7790 SoCs > - "renesas,mmcif-r8a7791" for the MMCIF found in r8a7791 SoCs > - "renesas,mmcif-r8a7793" for the MMCIF found in r8a7793 SoCs > - "renesas,mmcif-r8a7794" for the MMCIF found in r8a7794 SoCs > + - "renesas,mmcif-sh73a0" for the MMCIF found in sh73a0 SoCs > > - clocks: reference to the functional clock > > -- > 2.7.0.rc3.207.g0ac5344 > -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/devicetree/bindings/mmc/renesas,mmcif.txt b/Documentation/devicetree/bindings/mmc/renesas,mmcif.txt index ff611fa66871..e4ba92aa035e 100644 --- a/Documentation/devicetree/bindings/mmc/renesas,mmcif.txt +++ b/Documentation/devicetree/bindings/mmc/renesas,mmcif.txt @@ -8,11 +8,14 @@ Required properties: - compatible: should be "renesas,mmcif-<soctype>", "renesas,sh-mmcif" as a fallback. Examples with <soctype> are: + - "renesas,mmcif-r8a73a4" for the MMCIF found in r8a73a4 SoCs - "renesas,mmcif-r8a7740" for the MMCIF found in r8a7740 SoCs + - "renesas,mmcif-r8a7778" for the MMCIF found in r8a7778 SoCs - "renesas,mmcif-r8a7790" for the MMCIF found in r8a7790 SoCs - "renesas,mmcif-r8a7791" for the MMCIF found in r8a7791 SoCs - "renesas,mmcif-r8a7793" for the MMCIF found in r8a7793 SoCs - "renesas,mmcif-r8a7794" for the MMCIF found in r8a7794 SoCs + - "renesas,mmcif-sh73a0" for the MMCIF found in sh73a0 SoCs - clocks: reference to the functional clock
Simply document new compatibility strings as the driver is already activated using a fallback compatibility string. These compat strings are in keeping with those for all other Renesas ARM based SoCs with sh_mmcif enabled in mainline. Signed-off-by: Simon Horman <horms+renesas@verge.net.au> --- Reposted with r8a7778 instead of r8a7779 in subject I have also posted patches to use these new compat strings to bring the DT files of the SoCs in question in-line with those for other Renesas ARM based SoCs with sh_mmcif enabled in mainline. --- Documentation/devicetree/bindings/mmc/renesas,mmcif.txt | 3 +++ 1 file changed, 3 insertions(+)