From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Thu, 31 Jul 2014 16:54:46 -0600 Subject: [U-Boot] Driver Model and DTS Parsing In-Reply-To: References: <538DF8BF.4080500@wwwdotorg.org> <539A2A42.80903@wwwdotorg.org> <53D91387.2040706@wwwdotorg.org> <53D94E31.7040008@wwwdotorg.org> Message-ID: <53DAC936.3050801@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 07/31/2014 03:58 PM, Simon Glass wrote: > On 31 July 2014 10:56, Simon Glass wrote: ... >> Firstly we need to establish that GPIOs have names and that these should be >> supported in U-Boot. Without agreement on this point we might not get much >> further. > > Can I please press you on this point, as it is important to establish > this first. Oh, you were talking about agreeing with me? I thought this was more of a general comment, since you'd indicated earlier that amending the gpio to handle names was outside the scope of this patchset, and GPIO names are basically only relevant if the user-interface exposes/handles the names. Well sure, GPIOs obviously have various sets of (controller-relative) names and IDs. There certainly aren't any "global" or "absolute" names though, unless you include the controller name/ID (or something derived from it) as part of the GPIO's name/ID (either numerically via controller base IDs or textually by e.g. prefixing GPIO names with the controller name). It would be good for any user-visible command/script to be able to handle either numeric IDs (either in an absolute space or preferably relative to a specified controller) or names.