From: Jan Glauber <jan.glauber-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org> To: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> Cc: Boris Brezillon <boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>, Richard Weinberger <richard-/L3Ra7n9ekc@public.gmane.org>, David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>, Brian Norris <computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, Marek Vasut <marek.vasut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, Cyrille Pitchen <cyrille.pitchen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>, "linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" <linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>, Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>, "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> Subject: Re: [RFC PATCH 1/2] dt-bindings: mtd: Add Cavium SOCs NAND bindings Date: Mon, 3 Apr 2017 18:18:49 +0200 [thread overview] Message-ID: <20170403161849.GA2845@hardcore> (raw) In-Reply-To: <CAL_JsqJ2VgF_Lp-vpdn6VL71K4z6Mu7DWYSaLZ_N0U+jaTuPsQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> On Mon, Apr 03, 2017 at 09:47:05AM -0500, Rob Herring wrote: > On Mon, Apr 3, 2017 at 9:38 AM, Jan Glauber > <jan.glauber-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org> wrote: > > On Mon, Apr 03, 2017 at 08:29:37AM -0500, Rob Herring wrote: > >> On Mon, Mar 27, 2017 at 06:05:23PM +0200, Jan Glauber wrote: > >> > Add device tree binding description for Cavium SOC nand flash controller. > >> > > >> > CC: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> > >> > CC: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org> > >> > CC: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org > >> > > >> > Signed-off-by: Jan Glauber <jglauber-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org> > >> > --- > >> > .../devicetree/bindings/mtd/cavium_nand.txt | 32 ++++++++++++++++++++++ > >> > 1 file changed, 32 insertions(+) > >> > create mode 100644 Documentation/devicetree/bindings/mtd/cavium_nand.txt > >> > > >> > diff --git a/Documentation/devicetree/bindings/mtd/cavium_nand.txt b/Documentation/devicetree/bindings/mtd/cavium_nand.txt > >> > new file mode 100644 > >> > index 0000000..4698d1f > >> > --- /dev/null > >> > +++ b/Documentation/devicetree/bindings/mtd/cavium_nand.txt > >> > @@ -0,0 +1,32 @@ > >> > +* Cavium NAND controller > >> > + > >> > +Required properties: > >> > + > >> > +- compatible: should be "cavium,cn8xxx-nand" > >> > >> Don't use wildcards in compatible strings. For PCI devices, this should > >> be based on the PCI vendor and device IDs. > >> > > > > Is there a syntax for compatible PCI devices? I'm afraid I've not seen > > this yet, can you give an example? > > www.o3one.org/hwdocs/openfirmware/pci_supplement_2_1.pdf Thanks, I probably should have read this before... So it will be something like: compatible = "pci177d,a04f" A bit unreadable, but it solves the wildcard issue. > > Most of Cavium's devices are PCI devices, we just added the compatible > > as convenience and usually it is not parsed. > > Linux doesn't parse it, but it's still required in the binding. OK. --Jan > Rob -- 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
WARNING: multiple messages have this Message-ID (diff)
From: Jan Glauber <jan.glauber@caviumnetworks.com> To: Rob Herring <robh@kernel.org> Cc: Boris Brezillon <boris.brezillon@free-electrons.com>, Richard Weinberger <richard@nod.at>, David Woodhouse <dwmw2@infradead.org>, Brian Norris <computersforpeace@gmail.com>, Marek Vasut <marek.vasut@gmail.com>, Cyrille Pitchen <cyrille.pitchen@atmel.com>, "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>, Mark Rutland <mark.rutland@arm.com>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org> Subject: Re: [RFC PATCH 1/2] dt-bindings: mtd: Add Cavium SOCs NAND bindings Date: Mon, 3 Apr 2017 18:18:49 +0200 [thread overview] Message-ID: <20170403161849.GA2845@hardcore> (raw) In-Reply-To: <CAL_JsqJ2VgF_Lp-vpdn6VL71K4z6Mu7DWYSaLZ_N0U+jaTuPsQ@mail.gmail.com> On Mon, Apr 03, 2017 at 09:47:05AM -0500, Rob Herring wrote: > On Mon, Apr 3, 2017 at 9:38 AM, Jan Glauber > <jan.glauber@caviumnetworks.com> wrote: > > On Mon, Apr 03, 2017 at 08:29:37AM -0500, Rob Herring wrote: > >> On Mon, Mar 27, 2017 at 06:05:23PM +0200, Jan Glauber wrote: > >> > Add device tree binding description for Cavium SOC nand flash controller. > >> > > >> > CC: Rob Herring <robh+dt@kernel.org> > >> > CC: Mark Rutland <mark.rutland@arm.com> > >> > CC: devicetree@vger.kernel.org > >> > > >> > Signed-off-by: Jan Glauber <jglauber@cavium.com> > >> > --- > >> > .../devicetree/bindings/mtd/cavium_nand.txt | 32 ++++++++++++++++++++++ > >> > 1 file changed, 32 insertions(+) > >> > create mode 100644 Documentation/devicetree/bindings/mtd/cavium_nand.txt > >> > > >> > diff --git a/Documentation/devicetree/bindings/mtd/cavium_nand.txt b/Documentation/devicetree/bindings/mtd/cavium_nand.txt > >> > new file mode 100644 > >> > index 0000000..4698d1f > >> > --- /dev/null > >> > +++ b/Documentation/devicetree/bindings/mtd/cavium_nand.txt > >> > @@ -0,0 +1,32 @@ > >> > +* Cavium NAND controller > >> > + > >> > +Required properties: > >> > + > >> > +- compatible: should be "cavium,cn8xxx-nand" > >> > >> Don't use wildcards in compatible strings. For PCI devices, this should > >> be based on the PCI vendor and device IDs. > >> > > > > Is there a syntax for compatible PCI devices? I'm afraid I've not seen > > this yet, can you give an example? > > www.o3one.org/hwdocs/openfirmware/pci_supplement_2_1.pdf Thanks, I probably should have read this before... So it will be something like: compatible = "pci177d,a04f" A bit unreadable, but it solves the wildcard issue. > > Most of Cavium's devices are PCI devices, we just added the compatible > > as convenience and usually it is not parsed. > > Linux doesn't parse it, but it's still required in the binding. OK. --Jan > Rob
next prev parent reply other threads:[~2017-04-03 16:18 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-03-27 16:05 [RFC PATCH 0/2] Cavium NAND flash driver Jan Glauber [not found] ` <20170327160524.29019-1-jglauber-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org> 2017-03-27 16:05 ` [RFC PATCH 1/2] dt-bindings: mtd: Add Cavium SOCs NAND bindings Jan Glauber 2017-03-27 16:05 ` Jan Glauber [not found] ` <20170327160524.29019-2-jglauber-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org> 2017-03-28 20:20 ` Boris Brezillon 2017-03-28 20:20 ` Boris Brezillon 2017-03-28 21:30 ` Jan Glauber 2017-03-28 21:30 ` Jan Glauber 2017-04-03 13:29 ` Rob Herring 2017-04-03 13:29 ` Rob Herring 2017-04-03 14:38 ` Jan Glauber 2017-04-03 14:38 ` Jan Glauber 2017-04-03 14:47 ` Rob Herring 2017-04-03 14:47 ` Rob Herring [not found] ` <CAL_JsqJ2VgF_Lp-vpdn6VL71K4z6Mu7DWYSaLZ_N0U+jaTuPsQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2017-04-03 16:18 ` Jan Glauber [this message] 2017-04-03 16:18 ` Jan Glauber 2017-03-27 16:05 ` [RFC PATCH 2/2] nand: cavium: Nand flash controller for Cavium ARM64 SOCs Jan Glauber 2017-03-29 9:29 ` Boris Brezillon 2017-03-29 10:02 ` Jan Glauber 2017-03-29 13:59 ` Boris Brezillon 2017-04-25 11:26 ` Jan Glauber 2017-04-30 13:01 ` Boris Brezillon 2017-05-15 12:33 ` Boris Brezillon 2017-05-15 12:35 ` Boris Brezillon 2017-05-19 7:51 ` Boris Brezillon 2017-05-22 11:35 ` Jan Glauber 2017-05-22 11:53 ` Boris Brezillon 2017-05-22 11:44 ` Boris Brezillon 2017-07-20 20:25 ` [RFC PATCH 0/2] Cavium NAND flash driver Karl Beldan
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=20170403161849.GA2845@hardcore \ --to=jan.glauber-m3mlkvoiwjvv6pq1l3v1odbpr1lh4cv8@public.gmane.org \ --cc=boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \ --cc=computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \ --cc=cyrille.pitchen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org \ --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \ --cc=linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=marek.vasut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \ --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \ --cc=richard-/L3Ra7n9ekc@public.gmane.org \ --cc=robh-DgEjT+Ai2ygdnm+yROfE0A@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.