From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergei Shtylyov Subject: Re: [PATCH mmc/next] mmc: sh_mmcif: Document r8a73a4, r8a7779 and sh73a0 DT bindings Date: Thu, 24 Nov 2016 21:50:38 +0300 Message-ID: References: <1480011435-22125-1-git-send-email-horms+renesas@verge.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1480011435-22125-1-git-send-email-horms+renesas@verge.net.au> Sender: linux-mmc-owner@vger.kernel.org To: Simon Horman , Ulf Hansson Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org, Magnus Damm , linux-renesas-soc@vger.kernel.org List-Id: devicetree@vger.kernel.org Hello. On 11/24/2016 09:17 PM, Simon Horman 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 > --- > I plan to follow-up with 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-", "renesas,sh-mmcif" as a > fallback. Examples with 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 7779 in the subject, 7778 here. [...] MBR, Sergei