I've created a new device driver that is responsible for controlling a
GPIO expander. This driver contains gpio_chip code, pinmux/pinconf,
code, pwm, and irq handlers.
I'm not certain what I should name this driver. `pinctrl-*`, `gpio-*`,
or something else?
I'm also not sure where this driver
On Mon, Aug 8, 2022 at 4:57 PM Andy Shevchenko
wrote:
> On Sun, Aug 7, 2022 at 4:57 PM Ian Pilcher wrote:
> >
> > I am trying to figure out how to use gpiod_get(), or one of its
> > variants, to get the descriptor (struct gpio_desc *) for a specific
> > GPIO. Getting a reference to the GPIO
On Sun, Aug 7, 2022 at 4:57 PM Ian Pilcher wrote:
>
> I am trying to figure out how to use gpiod_get(), or one of its
> variants, to get the descriptor (struct gpio_desc *) for a specific
> GPIO. Getting a reference to the GPIO chip (struct gpio_chip *) is
> straightforward, and it provides a
On 8/7/22 22:05, Adverg Ebashinskii wrote:
What is the right things to do if a patch got ignored? Is it appropriate
to request a feedback by explicitly replying to the thread or ignoring
the patch automatically means that it was rejected? If it's possible to
request a feedback how long should
On Sun, Aug 07, 2022 at 11:05:39PM +0300, Adverg Ebashinskii wrote:
> What is the right things to do if a patch got ignored? Is it appropriate to
> request a feedback by explicitly replying to the thread or ignoring the patch
> automatically means that it was rejected? If it's possible to request
