From: Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>
To: Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>
Cc: Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
Grant Likely
<grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>,
Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Ian Campbell <ijc-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Device Tree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux ARM
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [RESEND Patch 2/2] DT: bindings: add missing Marvell Kirkwood SoC documentation
Date: Thu, 6 Mar 2014 13:44:11 +0100 [thread overview]
Message-ID: <20140306124411.GH4780@lunn.ch> (raw)
In-Reply-To: <20140306122300.GW1872-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
On Thu, Mar 06, 2014 at 07:23:00AM -0500, Jason Cooper wrote:
> On Wed, Mar 05, 2014 at 10:21:14PM +0100, Andrew Lunn wrote:
> > Marvell Dove SoC binding was not documented, yet. Add the
>
> s/Dove/Kirkwood/
Doh. I cut/paste from the Dove file.
> > documentation including the supported SoCs and boards.
> >
> > Signed-off-by: Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>
> > ---
> > .../devicetree/bindings/arm/marvell,kirkwood.txt | 97 ++++++++++++++++++++++
> > 1 file changed, 97 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/arm/marvell,kirkwood.txt
> >
> > diff --git a/Documentation/devicetree/bindings/arm/marvell,kirkwood.txt b/Documentation/devicetree/bindings/arm/marvell,kirkwood.txt
> > new file mode 100644
> > index 000000000000..925ecbf6e7b7
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/arm/marvell,kirkwood.txt
> > @@ -0,0 +1,97 @@
> > +Marvell Kirkwood SoC Family Device Tree Bindings
> > +------------------------------------------------
> > +
> > +Boards with a SoC of the Marvell Kirkwook family, eg 88f6281
>
> s/Kirkwook/Kirkwood/
I really need to add Kirkwood to my dictionary.
> > +
> > +* Required root node properties:
> > +compatible: must contain "marvell,kirkwood"
> > +
> > +In addition, the above compatible shall be extended with the specific
> > +SoC. Currently known SoC compatibles are:
> > +
> > +"marvell,kirkwood-88f6192"
> > +"marvell,kirkwood-88f6281"
> > +"marvell,kirkwood-88f6282"
> > +"marvell,kirkwood-88f6283"
> > +"marvell,kirkwood-88f6702"
> > +"marvell,kirkwood-98DX4122"
> > +
> > +And in addition, the compatible shall be extended with the specific
> > +board. Currently known boards are:
>
> This is more a question for Grant and the other DT maintainers: Do we
> really need this?
checkpatch.pl says yes, we need this. It gives warnings for every
unknown compatible string. I would say it is up to Grant and the other
DT maintainers to decide if checkpatch.pl is wrong.
Andrew
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-03-06 12:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 21:21 [RESEND Patch 0/2] DT vendor/soc updates Andrew Lunn
[not found] ` <1394054474-4310-1-git-send-email-andrew-g2DYL2Zd6BY@public.gmane.org>
2014-03-05 21:21 ` [RESEND Patch 1/2] DT: Vendor: Add prefixes used by Kirkwood devices Andrew Lunn
[not found] ` <1394054474-4310-2-git-send-email-andrew-g2DYL2Zd6BY@public.gmane.org>
2014-03-06 12:21 ` Arnaud Ebalard
[not found] ` <8738ivy0uo.fsf-LkuqDEemtHBg9hUCZPvPmw@public.gmane.org>
2014-03-06 12:25 ` Jason Cooper
2014-03-06 12:39 ` Andrew Lunn
2014-03-05 21:21 ` [RESEND Patch 2/2] DT: bindings: add missing Marvell Kirkwood SoC documentation Andrew Lunn
[not found] ` <1394054474-4310-3-git-send-email-andrew-g2DYL2Zd6BY@public.gmane.org>
2014-03-06 12:23 ` Jason Cooper
[not found] ` <20140306122300.GW1872-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2014-03-06 12:44 ` Andrew Lunn [this message]
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=20140306124411.GH4780@lunn.ch \
--to=andrew-g2dyl2zd6by@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=ijc-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
--cc=jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).