On 21 August 2017 at 14:25, Biju Das <biju.das@xxxxxxxxxxxxxx> wrote: > Add support for r8a7743/5 SoC. Renesas RZ/G1[ME] (R8A7743/5) SDHI > is identical to the R-Car Gen2 family. > > Signed-off-by: Biju Das <biju.das@xxxxxxxxxxxxxx> Thanks, applied for next! Kind regards Uffe > --- > v1->v2 > - Modified the listing SoC's description related to SoC > with 1 Clock and 2 Clocks > v2->v3 > - Fixed the trailing double quote. > - Updated listing SoC's description. > > This patch is compiled and tested against linux next tag > next-20170817. > > Documentation/devicetree/bindings/mmc/tmio_mmc.txt | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/Documentation/devicetree/bindings/mmc/tmio_mmc.txt b/Documentation/devicetree/bindings/mmc/tmio_mmc.txt > index 4fd8b7a..54ef642 100644 > --- a/Documentation/devicetree/bindings/mmc/tmio_mmc.txt > +++ b/Documentation/devicetree/bindings/mmc/tmio_mmc.txt > @@ -15,6 +15,8 @@ Required properties: > "renesas,sdhi-r7s72100" - SDHI IP on R7S72100 SoC > "renesas,sdhi-r8a73a4" - SDHI IP on R8A73A4 SoC > "renesas,sdhi-r8a7740" - SDHI IP on R8A7740 SoC > + "renesas,sdhi-r8a7743" - SDHI IP on R8A7743 SoC > + "renesas,sdhi-r8a7745" - SDHI IP on R8A7745 SoC > "renesas,sdhi-r8a7778" - SDHI IP on R8A7778 SoC > "renesas,sdhi-r8a7779" - SDHI IP on R8A7779 SoC > "renesas,sdhi-r8a7790" - SDHI IP on R8A7790 SoC > @@ -33,10 +35,8 @@ Required properties: > If 2 clocks are specified by the hardware, you must name them as > "core" and "cd". If the controller only has 1 clock, naming is not > required. > - Below is the number clocks for each supported SoC: > - 1: SH73A0, R8A73A4, R8A7740, R8A7778, R8A7779, R8A7790 > - R8A7791, R8A7792, R8A7793, R8A7794, R8A7795, R8A7796 > - 2: R7S72100 > + Devices which have more than 1 clock are listed below: > + 2: R7S72100 > > Optional properties: > - toshiba,mmc-wrprotect-disable: write-protect detection is unavailable > -- > 1.9.1 > -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
