From mboxrd@z Thu Jan 1 00:00:00 1970 From: Segher Boessenkool Subject: Re: DT case sensitivity Date: Fri, 24 Aug 2018 11:52:42 -0500 Message-ID: <20180824165242.GW24439@gate.crashing.org> References: <3335cff2cc999c1dda58d75949ab3d12185fca79.camel@kernel.crashing.org> <18175413a0148f7859ab36ed9715dce7a598f318.camel@kernel.crashing.org> <20180823123650.GT24439@gate.crashing.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linuxppc-dev-bounces+glppe-linuxppc-embedded-2=m.gmane.org@lists.ozlabs.org Sender: "Linuxppc-dev" To: Rob Herring Cc: devicetree@vger.kernel.org, Kumar Gala , Frank Rowand , Stephen Rothwell , devicetree-spec@vger.kernel.org, Grant Likely , linuxppc-dev , David Gibson List-Id: devicetree@vger.kernel.org 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