diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2016-12-14 14:52:05 +0100 |
|---|---|---|
| committer | Lee Jones <lee.jones@linaro.org> | 2017-02-13 09:29:40 +0000 |
| commit | 0a5454c901aea0fef99f5ef7910c69c501817ae1 (patch) | |
| tree | 0d7f9985229006a006ecad0056dad82e8f1664a9 /include/linux/mfd | |
| parent | 34a23327697d558a582e356573d7d36773996fbb (diff) | |
| download | linux-0a5454c901aea0fef99f5ef7910c69c501817ae1.tar.gz linux-0a5454c901aea0fef99f5ef7910c69c501817ae1.tar.bz2 linux-0a5454c901aea0fef99f5ef7910c69c501817ae1.zip | |
mfd: axp20x: Use IRQF_TRIGGER_LOW on the axp288
The interrupt line of the entire family of axp2xx pmics is active-low,
for devicetree enumerated irqs, this is dealt with in the devicetree.
ACPI irq resources have a flag field for this too, I tried using this
on my CUBE iwork8 Air tablet, but it does not contain the right data.
The dstd shows the irq listed as either ActiveLow or ActiveHigh,
depending on the OSID variable, which seems to be set by the
"OS IMAGE ID" in the BIOS/EFI setup screen.
Since the acpi-resource info is no good, simply pass in IRQF_TRIGGER_LOW
on the axp288.
Together with the other axp288 fixes in this series, this fixes the axp288
irq contineously triggering.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Acked-by: Chen-Yu Tsai <wens@csie.org>
Signed-off-by: Lee Jones <lee.jones@linaro.org>
Diffstat (limited to 'include/linux/mfd')
| -rw-r--r-- | include/linux/mfd/axp20x.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/mfd/axp20x.h b/include/linux/mfd/axp20x.h index 39f1da18c917..6d5dd3f96d33 100644 --- a/include/linux/mfd/axp20x.h +++ b/include/linux/mfd/axp20x.h @@ -523,6 +523,7 @@ enum axp809_irqs { struct axp20x_dev { struct device *dev; int irq; + unsigned long irq_flags; struct regmap *regmap; struct regmap_irq_chip_data *regmap_irqc; long variant; |