Linus Walleij writes:
> On Sat, Apr 2, 2016 at 8:56 PM, Robert Jarzmik wrote:
>
>> Pincontrol is not yet ready for all PXA platforms.
>> For example, a legacy platform, if PINCTRL was activated, will fail its
>> calls to gpio_request() or
Linus Walleij writes:
> On Sat, Apr 2, 2016 at 8:56 PM, Robert Jarzmik wrote:
>
>> Pincontrol is not yet ready for all PXA platforms.
>> For example, a legacy platform, if PINCTRL was activated, will fail its
>> calls to gpio_request() or gpio_direction_output(), as the pinctrl
>> driver might
On Sat, Apr 2, 2016 at 8:56 PM, Robert Jarzmik wrote:
> Pincontrol is not yet ready for all PXA platforms.
> For example, a legacy platform, if PINCTRL was activated, will fail its
> calls to gpio_request() or gpio_direction_output(), as the pinctrl
> driver might not be
On Sat, Apr 2, 2016 at 8:56 PM, Robert Jarzmik wrote:
> Pincontrol is not yet ready for all PXA platforms.
> For example, a legacy platform, if PINCTRL was activated, will fail its
> calls to gpio_request() or gpio_direction_output(), as the pinctrl
> driver might not be available, such as for
Pincontrol is not yet ready for all PXA platforms.
For example, a legacy platform, if PINCTRL was activated, will fail its
calls to gpio_request() or gpio_direction_output(), as the pinctrl
driver might not be available, such as for pxa25x and pxa3xx.
As a step forward, activate pincontrol for
Pincontrol is not yet ready for all PXA platforms.
For example, a legacy platform, if PINCTRL was activated, will fail its
calls to gpio_request() or gpio_direction_output(), as the pinctrl
driver might not be available, such as for pxa25x and pxa3xx.
As a step forward, activate pincontrol for
6 matches
Mail list logo