From: Akhil R <akhilrajeev@nvidia.com>
To: <wsa@kernel.org>, <sumit.semwal@linaro.org>,
<christian.koenig@amd.com>, <gregkh@linuxfoundation.org>,
<rafael@kernel.org>, <andy.shevchenko@gmail.com>,
<digetx@gmail.com>, <ldewangan@nvidia.com>,
<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-tegra@vger.kernel.org>
Cc: Akhil R <akhilrajeev@nvidia.com>
Subject: [PATCH 0/2] Enable named interrupt smbus-alert for ACPI as well
Date: Thu, 16 Dec 2021 18:43:20 +0530 [thread overview]
Message-ID: <1639660402-31207-1-git-send-email-akhilrajeev@nvidia.com> (raw)
I2C - SMBus core drivers use named interrupts to support smbus_alert.
As named interrupts are not available for ACPI based systems, it was
required to change the i2c bus controller driver if to use smbus alert.
These patches provide option for named interrupts in ACPI and make the
implementation similar to DT. This will enable use of interrupt named
'smbus-alert' in ACPI as well which will be taken during i2c adapter
register.
Akhil R (2):
device property: Add device_irq_get_byname
i2c: smbus: Use device_ functions instead of of_
drivers/base/property.c | 35 +++++++++++++++++++++++++++++++++++
drivers/i2c/i2c-core-base.c | 2 +-
drivers/i2c/i2c-core-smbus.c | 10 +++++-----
drivers/i2c/i2c-smbus.c | 2 +-
include/linux/i2c-smbus.h | 6 +++---
include/linux/property.h | 3 +++
6 files changed, 48 insertions(+), 10 deletions(-)
--
2.7.4
next reply other threads:[~2021-12-16 13:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 13:13 Akhil R [this message]
2021-12-16 13:13 ` [PATCH 1/2] device property: Add device_irq_get_byname Akhil R
2021-12-16 14:38 ` Andy Shevchenko
2022-01-04 10:06 ` Akhil R
2021-12-16 13:13 ` [PATCH 2/2] i2c: smbus: Use device_ functions instead of of_ Akhil R
2021-12-16 14:59 ` Andy Shevchenko
2021-12-16 16:08 ` Akhil R
2021-12-16 20:18 ` Andy Shevchenko
2021-12-17 5:31 ` Akhil R
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=1639660402-31207-1-git-send-email-akhilrajeev@nvidia.com \
--to=akhilrajeev@nvidia.com \
--cc=andy.shevchenko@gmail.com \
--cc=christian.koenig@amd.com \
--cc=digetx@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=thierry.reding@gmail.com \
--cc=wsa@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;
as well as URLs for NNTP newsgroup(s).