From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 02/11] pci-rcar-gen2: add initial device tree documentation
Date: Wed, 05 Feb 2014 12:17:23 +0000 [thread overview]
Message-ID: <52F22BD3.8040107@codethink.co.uk> (raw)
In-Reply-To: <1391595554-20640-3-git-send-email-ben.dooks@codethink.co.uk>
On 05/02/14 12:04, Magnus Damm wrote:
> On Wed, Feb 5, 2014 at 7:19 PM, Ben Dooks <ben.dooks@codethink.co.uk> wrote:
>> Add initial documentation for the pci-rcar-gen2 driver device tree bindings.
>> This is not yet complete and needs work on the sub-nodes for the PCI bus.
>>
>> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
>> ---
>> Cc: linux-sh@vger.kernel.org
>> Cc: devicetree@vger.kernel.org
>> Cc: horms+renesas@verge.net.au
>> ---
>> .../devicetree/bindings/pci/renessas,pci-r8a7790.txt | 12 ++++++++++++
>> 1 file changed, 12 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/pci/renessas,pci-r8a7790.txt
>
> Hi Ben,
>
> Thanks for this. Regarding DT bindings, I agree about using the SoC as
> suffix in the compatible string since this is in line with what we do
> for other device drivers. I much prefer that over "gen2" or something
> else that may or may not apply to newer SoCs.
Great, let's get this lot reviewed and hopefully we can get this sorted
before the 3.15-rc1.
> As you probably know, the pci-rcar-gen2.c driver is intended to be
> used both on r8a7790 and r8a7791. Regarding this binding document, is
> it possible to make it one file for the driver instead of r8a7790
> specific? That would match what we do for DT binding documentation for
> other device drivers.
Thanks, should I change this to be renesas,pci-rcar-gen2.txt then?
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2014-02-05 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 10:19 [PATCH 02/11] pci-rcar-gen2: add initial device tree documentation Ben Dooks
2014-02-05 12:04 ` Magnus Damm
2014-02-05 12:17 ` Ben Dooks [this message]
2014-02-05 12:22 ` Magnus Damm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52F22BD3.8040107@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-sh@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).