* Re: gpiolib and pinmux interaction
[not found] ` <2218697f-8cb2-e20c-b8c9-c0386257aebf@linux.intel.com>
@ 2019-07-30 16:54 ` Fried, Ramon
2019-07-30 17:50 ` Fried, Ramon
0 siblings, 1 reply; 2+ messages in thread
From: Fried, Ramon @ 2019-07-30 16:54 UTC (permalink / raw)
To: Stefan Wahren, Linus Walleij; +Cc: open list:GPIO SUBSYSTEM
On 3/18/2019 13:41, Ramon Fried wrote:
> On 3/18/19 11:21 AM, Stefan Wahren wrote:
>> Hi Ramon,
>>
>> Am 17.03.19 um 10:09 schrieb Ramon Fried:
>>> Hi Linus, Stefan,
>>>
>>> Great patch, If you need help testing it on other HW tell me.
>> yes, please. I didn't get what kind of hardware you are using.
> Hi.
>
> custom mips based SOC with sta2x11 gpio driver & proprietary pin muxing ip allowing every pin to be muxed as gpio.
>
>> Regards
>> Stefan
Hey Linus, Stefan,
I'm not sure where are we standing with the patch.
I didn't find it merged, so I just took it and tested it. (It took my a
while, hehe)
It's working, but not as I would expect, instead of marking the gpio as
used,
it adds [kernel] flag. Which is OK, but I think it's clearer to also
make the "used" column. (see below)
What do you think ?
Thanks,
Ramon.
See below:
# gpioinfo
gpiochip1 - 23 lines:
line 0: unnamed unused input active-high
line 1: unnamed unused input active-high
line 2: unnamed unused input active-high
line 3: unnamed unused input active-high
line 4: unnamed unused input active-high
line 5: unnamed unused input active-high
line 6: unnamed unused input active-high
line 7: unnamed unused input active-high
line 8: unnamed unused input active-high [kernel]
line 9: unnamed unused input active-high [kernel]
line 10: unnamed unused input active-high [kernel]
line 11: unnamed unused input active-high [kernel]
line 12: unnamed unused input active-high
line 13: unnamed unused input active-high
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: gpiolib and pinmux interaction
2019-07-30 16:54 ` gpiolib and pinmux interaction Fried, Ramon
@ 2019-07-30 17:50 ` Fried, Ramon
0 siblings, 0 replies; 2+ messages in thread
From: Fried, Ramon @ 2019-07-30 17:50 UTC (permalink / raw)
To: Stefan Wahren, Linus Walleij, brgl; +Cc: open list:GPIO SUBSYSTEM
On 7/30/2019 19:54, Fried, Ramon wrote:
>
> On 3/18/2019 13:41, Ramon Fried wrote:
>> On 3/18/19 11:21 AM, Stefan Wahren wrote:
>>> Hi Ramon,
>>>
>>> Am 17.03.19 um 10:09 schrieb Ramon Fried:
>>>> Hi Linus, Stefan,
>>>>
>>>> Great patch, If you need help testing it on other HW tell me.
>>> yes, please. I didn't get what kind of hardware you are using.
>> Hi.
>>
>> custom mips based SOC with sta2x11 gpio driver & proprietary pin
>> muxing ip allowing every pin to be muxed as gpio.
>>
>>> Regards
>>> Stefan
>
> Hey Linus, Stefan,
>
> I'm not sure where are we standing with the patch.
> I didn't find it merged, so I just took it and tested it. (It took my
> a while, hehe)
> It's working, but not as I would expect, instead of marking the gpio
> as used,
> it adds [kernel] flag. Which is OK, but I think it's clearer to also
> make the "used" column. (see below)
>
> What do you think ?
>
> Thanks,
>
> Ramon.
>
> See below:
>
> # gpioinfo
> gpiochip1 - 23 lines:
> line 0: unnamed unused input active-high
> line 1: unnamed unused input active-high
> line 2: unnamed unused input active-high
> line 3: unnamed unused input active-high
> line 4: unnamed unused input active-high
> line 5: unnamed unused input active-high
> line 6: unnamed unused input active-high
> line 7: unnamed unused input active-high
> line 8: unnamed unused input active-high [kernel]
> line 9: unnamed unused input active-high [kernel]
> line 10: unnamed unused input active-high [kernel]
> line 11: unnamed unused input active-high [kernel]
> line 12: unnamed unused input active-high
> line 13: unnamed unused input active-high
>
Adding Bartosz.
Turns out I was running and old version of libgpiod, in current version
it's printed "[used] instead of [kernel].
The patch from Stefan is perfectly fine from my standpoint, but the
output of gpioinfo can be improved,
I'll post a patch to LIBGPIOD.
Thanks.
Ramon
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-07-30 17:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <d031ce76-252a-9388-17fa-8a52f81f22f1@linux.intel.com>
[not found] ` <CACRpkdZUA33i+OVMH2KeKaBF368oGi9nW_GLawr+x9t=Gc67Ug@mail.gmail.com>
[not found] ` <bab378aa-8fb2-849c-9b73-3ed55ef9643e@linux.intel.com>
[not found] ` <2a08855b-9df2-e536-60c3-07770a9162b1@i2se.com>
[not found] ` <2218697f-8cb2-e20c-b8c9-c0386257aebf@linux.intel.com>
2019-07-30 16:54 ` gpiolib and pinmux interaction Fried, Ramon
2019-07-30 17:50 ` Fried, Ramon
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.