From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: wsa@the-dreams.de, jarkko.nikula@linux.intel.com,
andriy.shevchenko@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 v8 2/6] i2c: acpi: Use available IRQ helper functions
Date: Thu, 27 Jun 2019 14:26:31 +0300 [thread overview]
Message-ID: <20190627112631.GC2640@lahna.fi.intel.com> (raw)
In-Reply-To: <20190627092411.26123-3-ckeepax@opensource.cirrus.com>
On Thu, Jun 27, 2019 at 10:24:07AM +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: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2019-06-27 11:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 9:24 [PATCH v8 0/6] I2C IRQ Probe Improvements Charles Keepax
2019-06-27 9:24 ` [PATCH v8 1/6] i2c: core: Allow whole core to use i2c_dev_irq_from_resources Charles Keepax
2019-06-27 9:24 ` [PATCH v8 2/6] i2c: acpi: Use available IRQ helper functions Charles Keepax
2019-06-27 11:26 ` Mika Westerberg [this message]
2019-06-27 9:24 ` [PATCH v8 3/6] i2c: acpi: Factor out getting the IRQ from ACPI Charles Keepax
2019-06-27 11:27 ` Mika Westerberg
2019-06-27 9:24 ` [PATCH v8 4/6] i2c: core: Move ACPI IRQ handling to probe time Charles Keepax
2019-06-27 11:29 ` Mika Westerberg
2019-06-27 9:24 ` [PATCH v8 5/6] i2c: core: Move ACPI gpio IRQ handling into i2c_acpi_get_irq Charles Keepax
2019-06-27 11:30 ` Mika Westerberg
2019-06-27 9:24 ` [PATCH v8 6/6] i2c: core: Tidy up handling of init_irq Charles Keepax
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=20190627112631.GC2640@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=ckeepax@opensource.cirrus.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=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).