[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YyC4zq2YEmzQMkBL@smile.fi.intel.com>
Date: Tue, 13 Sep 2022 20:07:26 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Kent Gibson <warthog618@...il.com>
Cc: Bartosz Golaszewski <brgl@...ev.pl>,
Linus Walleij <linus.walleij@...aro.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] gpiolib: cdev: export the consumer's PID
On Wed, Sep 14, 2022 at 12:17:39AM +0800, Kent Gibson wrote:
> On Tue, Sep 13, 2022 at 05:58:32PM +0200, Bartosz Golaszewski wrote:
> > On Tue, Sep 13, 2022 at 4:55 PM Kent Gibson <warthog618@...il.com> wrote:
...
> > We'd need of course first expose that info like:
> >
> > gpio chip:gpiochip2 lines:0,3,4,7
> >
> > Does that make sense?
>
> Makes sense to me, though I don't claim to know anything about fdinfo
> field formatting.
>
> e.g. I also see fdinfo fields like this:
>
> eventfd-count: 0
> eventfd-id: 1
>
> so
>
> gpio-chip: gpiochip2
> gpio-lines: 0,3,4,7
>
> might be ok too.
Always think about two or more GPIO chips in the same process with 1 or more
lines requested from each of them.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists