Re: [PATCH] gpiolib: Avoid side effects in gpio_is_visible()
From: Kent Gibson
Date: Tue May 16 2023 - 21:21:47 EST
On Wed, May 17, 2023 at 01:07:25AM +0000, Chris Packham wrote:
>
> On 17/05/23 12:47, Kent Gibson wrote:
> > On Tue, May 16, 2023 at 11:50:42PM +0000, Chris Packham wrote:
> >> Hi Kent,
> >>
> >>
> > Given appropriate line names, that is already something you can do with
> > the libgpiod v2 tools. Something like:
> >
> > `for x in gpiochip*; do gpioset -c x tx-dis=1; done`
> Would that deal with the fact the GPIO lines are port1-tx-dis,
> port2-tx-dis, ... port96-tx-dis?
That is assuming the lines are all given the same name - "tx-dis".
If the line names are all distinct, and you can generate the list, then
you could provide that list to gpioset instead.
e.g.
`gpioset port1-tx-dis=1 port2-tx-dis=1 ....`
and it will work out which lines are on which chips.
Cheers,
Kent.