On Fri, Aug 17, 2018 at 4:48 PM wrote:
>
> From: Justin Chen
>
> Sometimes we have empty banks within the GPIO block. This commit allows
> proper handling of 0 width GPIO banks. We handle 0 width GPIO banks by
> incrementing the bank and number of GPIOs, but not initializing them.
> This will mea
On Sat, Aug 18, 2018 at 1:47 AM wrote:
> From: Justin Chen
>
> Sometimes we have empty banks within the GPIO block. This commit allows
> proper handling of 0 width GPIO banks. We handle 0 width GPIO banks by
> incrementing the bank and number of GPIOs, but not initializing them.
> This will mean
On 08/17/2018 05:52 PM, Andrew Lunn wrote:
> On Fri, Aug 17, 2018 at 04:47:39PM -0700, justinpo...@gmail.com wrote:
>> From: Justin Chen
>>
>> Sometimes we have empty banks within the GPIO block. This commit allows
>> proper handling of 0 width GPIO banks.
>
> Hi Justin
>
> This is coming from D
On Fri, Aug 17, 2018 at 04:47:39PM -0700, justinpo...@gmail.com wrote:
> From: Justin Chen
>
> Sometimes we have empty banks within the GPIO block. This commit allows
> proper handling of 0 width GPIO banks.
Hi Justin
This is coming from DT? Why do you put 0 width banks in DT in the
first place
On 08/17/2018 04:47 PM, justinpo...@gmail.com wrote:
> From: Justin Chen
>
> Sometimes we have empty banks within the GPIO block. This commit allows
> proper handling of 0 width GPIO banks. We handle 0 width GPIO banks by
> incrementing the bank and number of GPIOs, but not initializing them.
> T
From: Justin Chen
Sometimes we have empty banks within the GPIO block. This commit allows
proper handling of 0 width GPIO banks. We handle 0 width GPIO banks by
incrementing the bank and number of GPIOs, but not initializing them.
This will mean a call into the non-existent GPIOs will return an e
6 matches
Mail list logo