From: Yicong Yang <yangyicong@hisilicon.com>
To: <jarkko.nikula@linux.intel.com>,
<andriy.shevchenko@linux.intel.com>,
<mika.westerberg@linux.intel.com>, <wsa@kernel.org>,
<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <yangyicong@hisilicon.com>, <prime.zeng@hisilicon.com>,
<linuxarm@huawei.com>
Subject: [PATCH 0/2] Add I2C bus recovery support on Kunpeng 920/930
Date: Tue, 25 Jan 2022 20:49:28 +0800 [thread overview]
Message-ID: <20220125124930.50369-1-yangyicong@hisilicon.com> (raw)
This series adds the I2C bus recovery support on Kunpeng 920/930.
We're using HiSilicon I2C controller on Kunpeng 930 and Designware
I2C controller on Kunpeng 920. For both platform, the SCL/SDA pins
are multiplexed with GPIOs. Both driver use generic GPIO recovery
method and we need to switch the pin mutiplexing before/after the
recovery process. We use ACPI method to help on the pin mux switching
which is also introduced in this series.
Yicong Yang (2):
i2c: hisi: Add generic GPIO bus recovery support
i2c: designware: Add ACPI assisted recovery support
drivers/i2c/busses/i2c-designware-core.h | 2 +
drivers/i2c/busses/i2c-designware-master.c | 84 ++++++++++++++++++++-
drivers/i2c/busses/i2c-designware-platdrv.c | 6 +-
drivers/i2c/busses/i2c-hisi.c | 78 +++++++++++++++++++
4 files changed, 164 insertions(+), 6 deletions(-)
--
2.24.0
next reply other threads:[~2022-01-25 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 12:49 Yicong Yang [this message]
2022-01-25 12:49 ` [PATCH 1/2] i2c: hisi: Add generic GPIO bus recovery support Yicong Yang
2022-02-07 11:17 ` Andy Shevchenko
2022-02-07 11:20 ` Andy Shevchenko
2022-02-08 2:15 ` Yicong Yang
2022-02-09 12:12 ` Andy Shevchenko
2022-01-25 12:49 ` [PATCH 2/2] i2c: designware: Add ACPI assisted " Yicong Yang
2022-02-07 7:37 ` [PATCH 0/2] Add I2C bus recovery support on Kunpeng 920/930 Yicong Yang
2022-02-07 11:21 ` 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=20220125124930.50369-1-yangyicong@hisilicon.com \
--to=yangyicong@hisilicon.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mika.westerberg@linux.intel.com \
--cc=prime.zeng@hisilicon.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
all inboxes | Powered by JetHome®