Re: [U-Boot] [RFC PATCH v2 13/13] tegra: Convert tegra GPIO driver to use driver model

2014-05-21 Thread Simon Glass
Hi Stephen, On 13 May 2014 09:30, Stephen Warren wrote: > On 05/09/2014 11:28 AM, Simon Glass wrote: >> This is an implementation of GPIOs for Tegra that uses driver model. It has >> been tested on trimslice and also using the new iotrace feature. >> >> The implementation uses a top-level GPIO de

Re: [U-Boot] [RFC PATCH v2 13/13] tegra: Convert tegra GPIO driver to use driver model

2014-05-13 Thread Stephen Warren
On 05/09/2014 11:28 AM, Simon Glass wrote: > This is an implementation of GPIOs for Tegra that uses driver model. It has > been tested on trimslice and also using the new iotrace feature. > > The implementation uses a top-level GPIO device (which has no actual GPIOS). > Under this all the banks ar

[U-Boot] [RFC PATCH v2 13/13] tegra: Convert tegra GPIO driver to use driver model

2014-05-09 Thread Simon Glass
This is an implementation of GPIOs for Tegra that uses driver model. It has been tested on trimslice and also using the new iotrace feature. The implementation uses a top-level GPIO device (which has no actual GPIOS). Under this all the banks are created as separate GPIO devices. The GPIOs are na

Re: [U-Boot] [RFC PATCH v2 13/13] tegra: Convert tegra GPIO driver to use driver model

2014-05-06 Thread Simon Glass
Hi Stephen, On 6 May 2014 14:37, Stephen Warren wrote: > On 05/06/2014 02:28 PM, Simon Glass wrote: > ... > > The GPIO uclass does sequentially number GPIOs, but be aware that on > > platforms with multiple GPIO controllers (e.g. an I2C GPIO extender) you > > might hit a problem where the tegra

Re: [U-Boot] [RFC PATCH v2 13/13] tegra: Convert tegra GPIO driver to use driver model

2014-05-06 Thread Stephen Warren
On 05/06/2014 02:28 PM, Simon Glass wrote: ... > The GPIO uclass does sequentially number GPIOs, but be aware that on > platforms with multiple GPIO controllers (e.g. an I2C GPIO extender) you > might hit a problem where the tegra GPIOs are not first, so might start > at 8 or 16, for example. Howev

Re: [U-Boot] [RFC PATCH v2 13/13] tegra: Convert tegra GPIO driver to use driver model

2014-05-06 Thread Simon Glass
HI Stephen, On 6 May 2014 11:34, Stephen Warren wrote: > On 05/05/2014 05:00 PM, Simon Glass wrote: > > Hi Stephen, > > > > On 5 May 2014 16:07, Stephen Warren > > wrote: > > > > On 05/05/2014 03:30 PM, Simon Glass wrote: > > ... > > > I think you have

Re: [U-Boot] [RFC PATCH v2 13/13] tegra: Convert tegra GPIO driver to use driver model

2014-05-06 Thread Stephen Warren
On 05/05/2014 05:00 PM, Simon Glass wrote: > Hi Stephen, > > On 5 May 2014 16:07, Stephen Warren > wrote: > > On 05/05/2014 03:30 PM, Simon Glass wrote: > ... > > I think you have it backwards...the current implementation has a > > single level of hi

Re: [U-Boot] [RFC PATCH v2 13/13] tegra: Convert tegra GPIO driver to use driver model

2014-05-05 Thread Simon Glass
Hi Stephen, On 5 May 2014 16:07, Stephen Warren wrote: > On 05/05/2014 03:30 PM, Simon Glass wrote: > ... > > I think you have it backwards...the current implementation has a > > single level of hierarchy. Each driver handles one bank (or 'port' in > > the case of Tegra). What you are talking ab

Re: [U-Boot] [RFC PATCH v2 13/13] tegra: Convert tegra GPIO driver to use driver model

2014-05-05 Thread Stephen Warren
On 05/05/2014 03:30 PM, Simon Glass wrote: ... > I think you have it backwards...the current implementation has a > single level of hierarchy. Each driver handles one bank (or 'port' in > the case of Tegra). What you are talking about is having a single > driver handle multiple banks, thus requirin

Re: [U-Boot] [RFC PATCH v2 13/13] tegra: Convert tegra GPIO driver to use driver model

2014-05-05 Thread Simon Glass
HI Stephen, On 5 May 2014 15:14, Stephen Warren wrote: > On 05/05/2014 01:53 PM, Simon Glass wrote: >> Hi Stephen, >> >> On 5 May 2014 11:29, Stephen Warren wrote: >>> On 05/05/2014 10:09 AM, Simon Glass wrote: This is an implementation of GPIOs for Tegra that uses driver model. It has

Re: [U-Boot] [RFC PATCH v2 13/13] tegra: Convert tegra GPIO driver to use driver model

2014-05-05 Thread Stephen Warren
On 05/05/2014 01:53 PM, Simon Glass wrote: > Hi Stephen, > > On 5 May 2014 11:29, Stephen Warren wrote: >> On 05/05/2014 10:09 AM, Simon Glass wrote: >>> This is an implementation of GPIOs for Tegra that uses driver model. It has >>> been tested on trimslice and also using the new iotrace feature

Re: [U-Boot] [RFC PATCH v2 13/13] tegra: Convert tegra GPIO driver to use driver model

2014-05-05 Thread Simon Glass
Hi Stephen, On 5 May 2014 11:29, Stephen Warren wrote: > On 05/05/2014 10:09 AM, Simon Glass wrote: >> This is an implementation of GPIOs for Tegra that uses driver model. It has >> been tested on trimslice and also using the new iotrace feature. >> >> The implementation uses a top-level GPIO dev

Re: [U-Boot] [RFC PATCH v2 13/13] tegra: Convert tegra GPIO driver to use driver model

2014-05-05 Thread Stephen Warren
On 05/05/2014 10:09 AM, Simon Glass wrote: > This is an implementation of GPIOs for Tegra that uses driver model. It has > been tested on trimslice and also using the new iotrace feature. > > The implementation uses a top-level GPIO device (which has no actual GPIOS). > Under this all the banks ar

[U-Boot] [RFC PATCH v2 13/13] tegra: Convert tegra GPIO driver to use driver model

2014-05-05 Thread Simon Glass
This is an implementation of GPIOs for Tegra that uses driver model. It has been tested on trimslice and also using the new iotrace feature. The implementation uses a top-level GPIO device (which has no actual GPIOS). Under this all the banks are created as separate GPIO devices. The GPIOs are na