Re: [PATCH v2 3/7] gpiolib: Introduce ->add_pin_ranges() callback

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Nov 13, 2019 at 10:46:24AM +0100, Linus Walleij wrote:
> On Tue, Nov 5, 2019 at 9:36 PM Andy Shevchenko
> <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote:
> 
> > When IRQ chip is being added by GPIO library, the ACPI based platform expects
> > GPIO <-> pin mapping ranges to be initialized in order to correctly initialize
> > ACPI event mechanism on affected platforms. Unfortunately this step is missed.
> >
> > Introduce ->add_pin_ranges() callback to fill the above mentioned gap.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
> 
> Reviewed-by: Linus Walleij <linus.walleij@xxxxxxxxxx>

Thank you.

> I also think DT drivers can benefit from this.
> I expect this in a big pull request :)

You mean GPIO library one? Pin control is the other one and it seems that part
of Intel pin control (despite Lynxpoint case) will be split between v5.5 and
v5.6 due to this very patch as dependency.

-- 
With Best Regards,
Andy Shevchenko





[Index of Archives]     [Linux SPI]     [Linux Kernel]     [Linux ARM (vger)]     [Linux ARM MSM]     [Linux Omap]     [Linux Arm]     [Linux Tegra]     [Fedora ARM]     [Linux for Samsung SOC]     [eCos]     [Linux Fastboot]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [Linux MIPS]     [Yosemite Campsites]

  Powered by Linux