From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: wsa@the-dreams.de, mika.westerberg@linux.intel.com,
jarkko.nikula@linux.intel.com, linux-i2c@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
benjamin.tissoires@redhat.com, jbroadus@gmail.com,
patches@opensource.cirrus.com
Subject: Re: [PATCH v5 2/7] i2c: acpi: Use available IRQ helper functions
Date: Thu, 20 Jun 2019 16:11:15 +0100 [thread overview]
Message-ID: <20190620151115.GA54126@ediswmail.ad.cirrus.com> (raw)
In-Reply-To: <20190620145221.GC9224@smile.fi.intel.com>
On Thu, Jun 20, 2019 at 05:52:21PM +0300, Andy Shevchenko wrote:
> On Thu, Jun 20, 2019 at 02:34:15PM +0100, Charles Keepax wrote:
> > Use the available IRQ helper functions, most of the functions have
> > additional helpful side affects like configuring the trigger type of the
> > IRQ.
> >
> > Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
>
> Some last minute observations / questions.
>
> > + struct resource r;
> > +
> > + if (*irq <= 0 && acpi_dev_resource_interrupt(ares, 0, &r))
> > + *irq = i2c_dev_irq_from_resources(&r, 1);
> > +
> > + return 1; /* No need to add resource to the list */
>
> If we don't add it to the list, do we still need to manage the empty
> resource_list below?
>
I think you are right looking closely I think we can skip this. I
might update the comment here to make it clear the list needs
freed if this is changed though.
> > /* Then fill IRQ number if any */
> > INIT_LIST_HEAD(&resource_list);
> > - ret = acpi_dev_get_resources(adev, &resource_list, NULL, NULL);
> > + ret = acpi_dev_get_resources(adev, &resource_list,
> > + i2c_acpi_add_resource, &irq);
> > if (ret < 0)
> > return -EINVAL;
> >
> > - resource_list_for_each_entry(entry, &resource_list) {
> > - if (resource_type(entry->res) == IORESOURCE_IRQ) {
> > - info->irq = entry->res->start;
> > - break;
> > - }
> > - }
>
> > + if (irq > 0)
> > + info->irq = irq;
>
> Hmm... can't we just assign it directly inside the _add_resource() call back as
> original code did?
>
Again I think you are correct here, my thinking had been to
preserve the original functionality of only overwriting the value
in info->irq if we found one. But it looks like all callers don't
pass anything meaningful in this field so changing that behaviour
shouldn't matter.
Thanks,
Charles
next prev parent reply other threads:[~2019-06-20 15:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 13:34 [PATCH v5 0/7] I2C IRQ Probe Improvements Charles Keepax
2019-06-20 13:34 ` [PATCH v5 1/7] i2c: core: Allow whole core to use i2c_dev_irq_from_resources Charles Keepax
2019-06-20 13:34 ` [PATCH v5 2/7] i2c: acpi: Use available IRQ helper functions Charles Keepax
2019-06-20 14:52 ` Andy Shevchenko
2019-06-20 15:11 ` Charles Keepax [this message]
2019-06-20 13:34 ` [PATCH v5 3/7] i2c: acpi: Factor out getting the IRQ from ACPI Charles Keepax
2019-06-20 14:54 ` Andy Shevchenko
2019-06-20 13:34 ` [PATCH v5 4/7] i2c: core: Make i2c_acpi_get_irq available to the rest of the I2C core Charles Keepax
2019-06-20 14:59 ` Andy Shevchenko
2019-06-20 15:12 ` Charles Keepax
2019-06-20 13:34 ` [PATCH v5 5/7] i2c: core: Move ACPI IRQ handling to probe time Charles Keepax
2019-06-20 13:34 ` [PATCH v5 6/7] i2c: core: Move ACPI gpio IRQ handling into i2c_acpi_get_irq Charles Keepax
2019-06-20 13:34 ` [PATCH v5 7/7] i2c: core: Tidy up handling of init_irq Charles Keepax
2019-06-20 15:00 ` [PATCH v5 0/7] I2C IRQ Probe Improvements 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=20190620151115.GA54126@ediswmail.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jbroadus@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=patches@opensource.cirrus.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).