On Tue, Nov 15, 2016 at 12:36 PM, Laxman Dewangan wrote:
> [Me]
>> It would be more natural to add a function pinctrl_is_gpio(unsigned gpio)
>> to call back to the pin controller, then that can be called from
>> the generic or driver-specific debug print callback.
>
>
> We have two type of IPs, GP
On Tuesday 15 November 2016 02:33 PM, Linus Walleij wrote:
On Fri, Nov 11, 2016 at 1:17 PM, Laxman Dewangan wrote:
Yeah but since pinctrl and pinmux has its own debugfs files why is this
necessary? I understand it is convenient but only for debugging
right? They the inconvenience of using pin
On Fri, Nov 11, 2016 at 1:17 PM, Laxman Dewangan wrote:
>> Yeah but since pinctrl and pinmux has its own debugfs files why is this
>> necessary? I understand it is convenient but only for debugging
>> right? They the inconvenience of using pinctrls debugfs files should
>> be bearable.
>
> Yes, it
On Saturday 05 November 2016 03:50 AM, Linus Walleij wrote:
On Wed, Nov 2, 2016 at 1:17 PM, Laxman Dewangan wrote:
Many of devices/SoCs supports the GPIO and special IO function
from their pins. On such cases, there is always configuration
bits to select the mode of pin as GPIO or as the spec
On Wed, Nov 2, 2016 at 1:17 PM, Laxman Dewangan wrote:
> Many of devices/SoCs supports the GPIO and special IO function
> from their pins. On such cases, there is always configuration
> bits to select the mode of pin as GPIO or as the special IO mode.
> The functional modes are selected by pinmux
5 matches
Mail list logo