From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Saravana Kannan <saravanak@google.com>
Cc: Puranjay Mohan <puranjay12@gmail.com>,
gregkh@linuxfoundation.org, rafael@kernel.org,
heikki.krogerus@linux.intel.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, lars@metafoo.de,
Michael.Hennerich@analog.com, jic23@kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v2 0/2] device property: Adding fwnode_irq_get_byname()
Date: Wed, 10 Nov 2021 10:32:05 +0200 [thread overview]
Message-ID: <YYuDhTlMIn9qxlvo@smile.fi.intel.com> (raw)
In-Reply-To: <CAGETcx9-WoAa8VbEPSthseYNz=L-gnoXLcHFtHrD_+yhQXmJnA@mail.gmail.com>
On Tue, Nov 09, 2021 at 02:42:35PM -0800, Saravana Kannan wrote:
> On Tue, Nov 9, 2021 at 12:09 PM Puranjay Mohan <puranjay12@gmail.com> wrote:
> >
> > The first patch in this series adds the fwnode_irq_get_byname() which is
> > the generic version of the of_irq_get_byname(). It is used to get the
> > IRQ number from name of the interrupt.
> >
> > The second patch in this series uses the fwnode_irq_get_byname()
> > function in the IIO driver of the ADXL355 accelerometer. The driver has
> > been tested after applying this patch on a Raspberry PI. The ADXL355 was
> > connected to the Raspberry Pi using I2C and fwnode_irq_get_byname() was
> > used to get the IRQ number for the "DRDY" interrupt. Earlier this driver
> > was using of_irq_get_byname() to get this IRQ number.
>
> Why do we need these changes though? Is there a non-OF device this
> driver would ever probe?
Strange question, TBH. All discrete component drivers are subject to
be enumerated on any type of the systems. So, of course the answer
to it "Definitely yes".
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-11-10 8:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 20:08 [PATCH v2 0/2] device property: Adding fwnode_irq_get_byname() Puranjay Mohan
2021-11-09 20:08 ` [PATCH v2 1/2] device property: Add fwnode_irq_get_byname() Puranjay Mohan
2021-11-10 8:53 ` Andy Shevchenko
2021-11-10 17:04 ` Puranjay Mohan
2021-11-10 17:27 ` Andy Shevchenko
2021-11-09 20:08 ` [PATCH v2 2/2] iio: accel: adxl355: use fwnode_irq_get_byname() Puranjay Mohan
2022-02-01 16:25 ` Andy Shevchenko
2022-02-27 12:41 ` Jonathan Cameron
2022-04-10 17:13 ` Jonathan Cameron
2022-04-11 10:17 ` Andy Shevchenko
2021-11-09 22:42 ` [PATCH v2 0/2] device property: Adding fwnode_irq_get_byname() Saravana Kannan
2021-11-10 8:32 ` Andy Shevchenko [this message]
2021-11-10 8:32 ` Andy Shevchenko
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=YYuDhTlMIn9qxlvo@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jic23@kernel.org \
--cc=kuba@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=puranjay12@gmail.com \
--cc=rafael@kernel.org \
--cc=saravanak@google.com \
/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