From: Antonio Ospite <ao2@ao2.it>
To: i2c@lm-sensors.org
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Wolfram Sang <wsa@the-dreams.de>,
Octavian Purdila <octavian.purdila@intel.com>,
Robert Dolca <robert.dolca@intel.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2 1/3] gpio / ACPI: Add support for retrieving GpioInt resources from a device
Date: Tue, 12 May 2015 14:49:01 +0200 [thread overview]
Message-ID: <20150512144901.49a1894b51edc0113ae35375@ao2.it> (raw)
In-Reply-To: <1430908148-201129-2-git-send-email-mika.westerberg@linux.intel.com>
On Wed, 6 May 2015 13:29:06 +0300
Mika Westerberg <mika.westerberg@linux.intel.com> wrote:
> ACPI specification knows two types of GPIOs: GpioIo and GpioInt. The latter
> is used to describe that a given device interrupt line is connected to a
> specific GPIO pin. Typical ACPI _CRS entry for such device looks like
> below:
>
> Name (_CRS, ResourceTemplate ()
> {
> I2cSerialBus (0x004A, ControllerInitiated, 0x00061A80,
> AddressingMode7Bit, "\\_SB.PCI0.I2C6",
> 0x00, ResourceConsumer)
> GpioIo (Exclusive, PullDefault, 0x0000, 0x0000,
> IoRestrictionOutputOnly, "\\_SB.GPO0",
> 0x00, ResourceConsumer)
> {
> 0x004B
> }
> GpioInt (Level, ActiveLow, Shared, PullDefault, 0x0000,
> "\\_SB.GPO0", 0x00, ResourceConsumer)
> {
> 0x004C
> }
> })
>
> Currently drivers need to request a GPIO corresponding to the right GpioInt
> and then translate that to Linux IRQ number. This adds unnecessary lines of
> boiler-plate code.
>
> We can ease this a bit by introducing acpi_dev_gpio_irq_get() analogous to
> of_irq_get(). This function translates given GpioInt resource under the
> device in question to the suitable Linux IRQ number.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Antonio Ospite <ao2@ao2.it>
Thanks a lot Mika, this is very useful, my touchscreen now works without
adding a struct acpi_gpio_mapping and the related boilerplate code to
the goodix driver.
Thanks again,
Antonio
> ---
> drivers/gpio/gpiolib-acpi.c | 29 +++++++++++++++++++++++++++++
> include/linux/acpi.h | 7 +++++++
> 2 files changed, 36 insertions(+)
>
> diff --git a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.c
> index d2303d50f561..bff29bb0a3fe 100644
> --- a/drivers/gpio/gpiolib-acpi.c
> +++ b/drivers/gpio/gpiolib-acpi.c
> @@ -514,6 +514,35 @@ struct gpio_desc *acpi_get_gpiod_by_index(struct acpi_device *adev,
> return lookup.desc ? lookup.desc : ERR_PTR(-ENOENT);
> }
>
> +/**
> + * acpi_dev_gpio_irq_get() - Find GpioInt and translate it to Linux IRQ number
> + * @adev: pointer to a ACPI device to get IRQ from
> + * @index: index of GpioInt resource (starting from %0)
> + *
> + * If the device has one or more GpioInt resources, this function can be
> + * used to translate from the GPIO offset in the resource to the Linux IRQ
> + * number.
> + *
> + * Return: Linux IRQ number (>%0) on success, negative errno on failure.
The percent in the comment here is supposed to be and equal sign, isn't
it?
> + */
> +int acpi_dev_gpio_irq_get(struct acpi_device *adev, int index)
> +{
> + int idx, i;
> +
> + for (i = 0, idx = 0; idx <= index; i++) {
> + struct acpi_gpio_info info;
> + struct gpio_desc *desc;
> +
> + desc = acpi_get_gpiod_by_index(adev, NULL, i, &info);
> + if (IS_ERR(desc))
> + break;
> + if (info.gpioint && idx++ == index)
> + return gpiod_to_irq(desc);
> + }
> + return -ENOENT;
> +}
> +EXPORT_SYMBOL_GPL(acpi_dev_gpio_irq_get);
> +
> static acpi_status
> acpi_gpio_adr_space_handler(u32 function, acpi_physical_address address,
> u32 bits, u64 *value, void *handler_context,
> diff --git a/include/linux/acpi.h b/include/linux/acpi.h
> index e4da5e35e29c..f57c440642cd 100644
> --- a/include/linux/acpi.h
> +++ b/include/linux/acpi.h
> @@ -721,6 +721,8 @@ static inline void acpi_dev_remove_driver_gpios(struct acpi_device *adev)
> if (adev)
> adev->driver_gpios = NULL;
> }
> +
> +int acpi_dev_gpio_irq_get(struct acpi_device *adev, int index);
> #else
> static inline int acpi_dev_add_driver_gpios(struct acpi_device *adev,
> const struct acpi_gpio_mapping *gpios)
> @@ -728,6 +730,11 @@ static inline int acpi_dev_add_driver_gpios(struct acpi_device *adev,
> return -ENXIO;
> }
> static inline void acpi_dev_remove_driver_gpios(struct acpi_device *adev) {}
> +
> +static inline int acpi_dev_gpio_irq_get(struct acpi_device *adev, int index)
> +{
> + return -ENXIO;
> +}
> #endif
>
> /* Device properties */
> --
> 2.1.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Antonio Ospite
http://ao2.it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
next prev parent reply other threads:[~2015-05-12 12:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 10:29 [PATCH v2 0/3] ACPI: Translate Linux IRQ number directly from GpioInt Mika Westerberg
2015-05-06 10:29 ` [PATCH v2 1/3] gpio / ACPI: Add support for retrieving GpioInt resources from a device Mika Westerberg
2015-05-11 9:56 ` Linus Walleij
2015-05-12 12:49 ` Antonio Ospite [this message]
2015-05-06 10:29 ` [PATCH v2 2/3] i2c / ACPI: Use 0 to indicate that device does not have interrupt assigned Mika Westerberg
2015-05-11 9:58 ` Linus Walleij
2015-05-12 13:09 ` wsa
[not found] ` <1430908148-201129-3-git-send-email-mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-05-13 8:24 ` Linus Walleij
2015-05-06 10:29 ` [PATCH v2 3/3] i2c / ACPI: Assign IRQ for devices that have GpioInt automatically Mika Westerberg
2015-05-11 9:59 ` Linus Walleij
2015-05-12 13:09 ` wsa
[not found] ` <1430908148-201129-4-git-send-email-mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-05-13 8:25 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150512144901.49a1894b51edc0113ae35375@ao2.it \
--to=ao2@ao2.it \
--cc=gnurou@gmail.com \
--cc=i2c@lm-sensors.org \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=octavian.purdila@intel.com \
--cc=rjw@rjwysocki.net \
--cc=robert.dolca@intel.com \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).