On Thu, Jan 09, 2020 at 08:53:28AM +0100, Linus Walleij wrote: > When IRQ chip is instantiated via GPIO library flow, the few functions, > in particular the ACPI event registration mechanism, on some of ACPI based > platforms expect that the pin ranges are initialized to that point. > > Add GPIO <-> pin mapping ranges via callback in the GPIO library flow. > > Cc: Hans de Goede <hdegoede@xxxxxxxxxx> > Signed-off-by: Linus Walleij <linus.walleij@xxxxxxxxxx> Acked-by: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
Re: [PATCH 1/2] pinctrl: intel: Add GPIO <-> pin mapping ranges via callback
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH 1/2] pinctrl: intel: Add GPIO <-> pin mapping ranges via callback
- From: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
- Date: Thu, 9 Jan 2020 12:21:45 +0200
- In-reply-to: <20200109075329.398347-1-linus.walleij@linaro.org>
- Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
- References: <20200109075329.398347-1-linus.walleij@linaro.org>
- References:
- [PATCH 1/2] pinctrl: intel: Add GPIO <-> pin mapping ranges via callback
- From: Linus Walleij
- [PATCH 1/2] pinctrl: intel: Add GPIO <-> pin mapping ranges via callback
- Prev by Date: Re: [PATCH v3] pinctrl: baytrail: Replace WARN with dev_info_once when setting direct-irq pin to output
- Next by Date: Re: [PATCH 2/2] pinctrl: intel: Pass irqchip when adding gpiochip
- Previous by thread: Re: [PATCH 2/2] pinctrl: intel: Pass irqchip when adding gpiochip
- Next by thread: Re: [PATCH 1/2] pinctrl: intel: Add GPIO <-> pin mapping ranges via callback
- Index(es):
 |