From: Segher Boessenkool <segher@kernel.crashing.org>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, Kumar Gala <kumar.gala@linaro.org>,
Frank Rowand <frowand.list@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
devicetree-spec@vger.kernel.org,
Grant Likely <grant.likely@arm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: DT case sensitivity
Date: Fri, 24 Aug 2018 11:52:42 -0500 [thread overview]
Message-ID: <20180824165242.GW24439@gate.crashing.org> (raw)
In-Reply-To: <CAL_Jsq+VnhT_4H4yECWsuXnmpQRnSHNRXAohRYds1LxcRjUHkw@mail.gmail.com>
On Fri, Aug 24, 2018 at 10:14:01AM -0500, Rob Herring wrote:
> Another question: Is there ever a case where the node name in the path
> aka 'driver-name' doesn't match the 'name' property? I think this
> generally can't happen on FDT as the 'name' property is generated when
> we unflatten it though I suppose one could craft an FDT with name
> properties.
In Open Firmware, it *is* the "name" property :-)
> There's also various places in the kernel that check for a NULL name
> which doesn't seem like it could happen either other than the root
> node.
In Open Firmware the root node is required to have a "name" property, too.
There are systems that violate that rule (as with most rules...)
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Rob Herring <robh@kernel.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Kumar Gala <kumar.gala@linaro.org>,
devicetree@vger.kernel.org, devicetree-spec@vger.kernel.org,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Grant Likely <grant.likely@arm.com>,
Frank Rowand <frowand.list@gmail.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: DT case sensitivity
Date: Fri, 24 Aug 2018 11:52:42 -0500 [thread overview]
Message-ID: <20180824165242.GW24439@gate.crashing.org> (raw)
In-Reply-To: <CAL_Jsq+VnhT_4H4yECWsuXnmpQRnSHNRXAohRYds1LxcRjUHkw@mail.gmail.com>
On Fri, Aug 24, 2018 at 10:14:01AM -0500, Rob Herring wrote:
> Another question: Is there ever a case where the node name in the path
> aka 'driver-name' doesn't match the 'name' property? I think this
> generally can't happen on FDT as the 'name' property is generated when
> we unflatten it though I suppose one could craft an FDT with name
> properties.
In Open Firmware, it *is* the "name" property :-)
> There's also various places in the kernel that check for a NULL name
> which doesn't seem like it could happen either other than the root
> node.
In Open Firmware the root node is required to have a "name" property, too.
There are systems that violate that rule (as with most rules...)
Segher
next prev parent reply other threads:[~2018-08-24 16:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 0:47 DT case sensitivity Rob Herring
2018-08-23 1:03 ` Benjamin Herrenschmidt
2018-08-23 1:26 ` Rob Herring
2018-08-23 1:26 ` Rob Herring
2018-08-23 1:29 ` Benjamin Herrenschmidt
2018-08-23 1:29 ` Benjamin Herrenschmidt
2018-08-23 9:02 ` Grant Likely
2018-08-23 9:02 ` Grant Likely
2018-08-23 11:43 ` Rob Herring
2018-08-23 11:43 ` Rob Herring
2018-08-23 11:47 ` Benjamin Herrenschmidt
2018-08-23 11:47 ` Benjamin Herrenschmidt
2018-08-23 11:56 ` Grant Likely
2018-08-23 11:56 ` Grant Likely
2018-08-23 12:08 ` Rob Herring
2018-08-23 12:08 ` Rob Herring
2018-08-23 12:48 ` Grant Likely
2018-08-23 12:48 ` Grant Likely
2018-08-23 12:36 ` Segher Boessenkool
2018-08-23 12:36 ` Segher Boessenkool
2018-08-24 15:14 ` Rob Herring
2018-08-24 15:14 ` Rob Herring
2018-08-24 16:52 ` Segher Boessenkool [this message]
2018-08-24 16:52 ` Segher Boessenkool
2018-08-23 12:19 ` Segher Boessenkool
2018-08-23 12:19 ` Segher Boessenkool
2018-08-23 21:49 ` Benjamin Herrenschmidt
2018-08-23 21:49 ` Benjamin Herrenschmidt
2018-08-24 5:39 ` Michael Ellerman
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=20180824165242.GW24439@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=grant.likely@arm.com \
--cc=kumar.gala@linaro.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
/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 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.