From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v1 1/1] iio: accel: bmc150: use fwnode_irq_get_byname()
Date: Sat, 24 Aug 2024 10:48:32 +0100 [thread overview]
Message-ID: <20240824104832.68575484@jic23-huawei> (raw)
In-Reply-To: <20240823230056.745872-1-andy.shevchenko@gmail.com>
On Sat, 24 Aug 2024 02:00:56 +0300
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> Use the generic fwnode_irq_get_byname() in place of of_irq_get_byname()
> to get the IRQ number from the interrupt pin.
>
> Signed-off-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Applied
> ---
> drivers/iio/accel/bmc150-accel-core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/accel/bmc150-accel-core.c b/drivers/iio/accel/bmc150-accel-core.c
> index 03121d020470..14ce03c70ab5 100644
> --- a/drivers/iio/accel/bmc150-accel-core.c
> +++ b/drivers/iio/accel/bmc150-accel-core.c
> @@ -10,9 +10,9 @@
> #include <linux/delay.h>
> #include <linux/slab.h>
> #include <linux/acpi.h>
> -#include <linux/of_irq.h>
> #include <linux/pm.h>
> #include <linux/pm_runtime.h>
> +#include <linux/property.h>
> #include <linux/iio/iio.h>
> #include <linux/iio/sysfs.h>
> #include <linux/iio/buffer.h>
> @@ -514,7 +514,7 @@ static void bmc150_accel_interrupts_setup(struct iio_dev *indio_dev,
> */
> irq_info = bmc150_accel_interrupts_int1;
> if (data->type == BOSCH_BMC156 ||
> - irq == of_irq_get_byname(dev->of_node, "INT2"))
> + irq == fwnode_irq_get_byname(dev_fwnode(dev), "INT2"))
> irq_info = bmc150_accel_interrupts_int2;
>
> for (i = 0; i < BMC150_ACCEL_INTERRUPTS; i++)
prev parent reply other threads:[~2024-08-24 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 23:00 [PATCH v1 1/1] iio: accel: bmc150: use fwnode_irq_get_byname() Andy Shevchenko
2024-08-24 9:48 ` Jonathan Cameron [this message]
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=20240824104832.68575484@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=hdegoede@redhat.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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