Re: [U-Boot] Driver Model and DTS Parsing

Hi Stephen, On 4 August 2014 11:38, Stephen Warren wrote: > On 08/04/2014 04:22 AM, Simon Glass wrote: >> >> Hi Stephen, >> >> On 31 July 2014 12:04, Stephen Warren wrote: >>> >>> On 07/31/2014 03:56 AM, Simon Glass wrote: Hi Stephen, On 30 July 2014 20:57, Stephen Warre

Re: [U-Boot] Driver Model and DTS Parsing

On 08/04/2014 04:22 AM, Simon Glass wrote: Hi Stephen, On 31 July 2014 12:04, Stephen Warren wrote: On 07/31/2014 03:56 AM, Simon Glass wrote: Hi Stephen, On 30 July 2014 20:57, Stephen Warren mailto:swar...@wwwdotorg.org>> wrote: On 07/30/2014 10:09 AM, Simon Glass wrote: H

Re: [U-Boot] Driver Model and DTS Parsing

Hi Stephen, On 31 July 2014 12:04, Stephen Warren wrote: > On 07/31/2014 03:56 AM, Simon Glass wrote: >> >> Hi Stephen, >> >> On 30 July 2014 20:57, Stephen Warren > > wrote: >> >> On 07/30/2014 10:09 AM, Simon Glass wrote: >> >> Hi Stephen, >> >>

Re: [U-Boot] Driver Model and DTS Parsing

>>> 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 agree

Re: [U-Boot] Driver Model and DTS Parsing

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

Re: [U-Boot] Driver Model and DTS Parsing

Hi Stephen, On 31 July 2014 10:56, Simon Glass wrote: > Hi Stephen, > > On 30 July 2014 20:57, Stephen Warren wrote: >> >> On 07/30/2014 10:09 AM, Simon Glass wrote: >>> >>> Hi Stephen, >>> >>> On 30 July 2014 16:47, Stephen Warren wrote: On 07/30/2014 09:26 AM, Simon Glass wrote: >>>

Re: [U-Boot] Driver Model and DTS Parsing

On 07/31/2014 03:56 AM, Simon Glass wrote: Hi Stephen, On 30 July 2014 20:57, Stephen Warren mailto:swar...@wwwdotorg.org>> wrote: On 07/30/2014 10:09 AM, Simon Glass wrote: Hi Stephen, On 30 July 2014 16:47, Stephen Warren mailto:swar...@wwwdotorg.org>> wrote:

Re: [U-Boot] Driver Model and DTS Parsing

Hi Stephen, On 30 July 2014 20:57, Stephen Warren wrote: > On 07/30/2014 10:09 AM, Simon Glass wrote: > >> Hi Stephen, >> >> On 30 July 2014 16:47, Stephen Warren wrote: >> >>> On 07/30/2014 09:26 AM, Simon Glass wrote: >>> Hi Stephen, On 12 June 2014 23:31, Stephen Warren

Re: [U-Boot] Driver Model and DTS Parsing

On 07/30/2014 10:09 AM, Simon Glass wrote: Hi Stephen, On 30 July 2014 16:47, Stephen Warren wrote: On 07/30/2014 09:26 AM, Simon Glass wrote: Hi Stephen, On 12 June 2014 23:31, Stephen Warren wrote: On 06/11/2014 10:55 PM, Simon Glass wrote: ... Tegra doesn't have much in the device t

Re: [U-Boot] Driver Model and DTS Parsing

Hi Stephen, On 30 July 2014 16:47, Stephen Warren wrote: > On 07/30/2014 09:26 AM, Simon Glass wrote: >> >> Hi Stephen, >> >> On 12 June 2014 23:31, Stephen Warren wrote: >>> >>> On 06/11/2014 10:55 PM, Simon Glass wrote: >>> ... Tegra doesn't have much in the device tree for GPIOs - i

Re: [U-Boot] Driver Model and DTS Parsing

On 07/30/2014 09:26 AM, Simon Glass wrote: Hi Stephen, On 12 June 2014 23:31, Stephen Warren wrote: On 06/11/2014 10:55 PM, Simon Glass wrote: ... Tegra doesn't have much in the device tree for GPIOs - it seems to be all hard-coded in the software. So I ended up with the code you saw which ju

Re: [U-Boot] Driver Model and DTS Parsing

Hi Stephen, On 12 June 2014 23:31, Stephen Warren wrote: > On 06/11/2014 10:55 PM, Simon Glass wrote: > ... >> Tegra doesn't have much in the device tree for GPIOs - it seems to be >> all hard-coded in the software. So I ended up with the code you saw >> which just iterates over a known number of

Re: [U-Boot] Driver Model and DTS Parsing

On 06/11/2014 10:55 PM, Simon Glass wrote: ... > Tegra doesn't have much in the device tree for GPIOs - it seems to be > all hard-coded in the software. So I ended up with the code you saw > which just iterates over a known number of banks, creating a device > for each. That still sounds wrong. Te

Re: [U-Boot] Driver Model and DTS Parsing

Hi Stephen, On 3 June 2014 12:33, Stephen Warren wrote: > On 06/03/2014 10:04 AM, Simon Glass wrote: >> +Stephen > > I don't think there's anything actionable for me in this email, although > I guess I'll chime in on a couple of points: > > I agree that the current way U-Boot parses DT is complet

Re: [U-Boot] Driver Model and DTS Parsing

On 06/03/2014 10:04 AM, Simon Glass wrote: > +Stephen I don't think there's anything actionable for me in this email, although I guess I'll chime in on a couple of points: I agree that the current way U-Boot parses DT is completely inadequate. The only way to parse it is to take a top-down recurs

Re: [U-Boot] Driver Model and DTS Parsing

+Stephen Hi Jon, On 3 June 2014 07:39, Jon Loeliger wrote: > On Mon, Jun 2, 2014 at 8:26 PM, Simon Glass wrote: > > > > Driver model works by looking up compatible strings in the top-level > > nodes and binding a driver for each one it finds. > > I get that. > > I'm saying that isn't sufficien

Re: [U-Boot] Driver Model and DTS Parsing

On Mon, Jun 2, 2014 at 8:26 PM, Simon Glass wrote: > > Driver model works by looking up compatible strings in the top-level > nodes and binding a driver for each one it finds. I get that. I'm saying that isn't sufficient. > The exynos pinctrl device tree binding does not have a compatible > str

Re: [U-Boot] Driver Model and DTS Parsing

Hi Jon, On 30 May 2014 08:49, Jon Loeliger wrote: > Folks, > > I'd like to discuss the new Driver Model's parsing of the DTS file > for the purposes of instancing and binding devices as I was not > able to get the existing code to work anything like I was expecting. > > The current code only find

[U-Boot] Driver Model and DTS Parsing

Folks, I'd like to discuss the new Driver Model's parsing of the DTS file for the purposes of instancing and binding devices as I was not able to get the existing code to work anything like I was expecting. The current code only finds and binds the top-level nodes of the DTS file. This leads to