From: Andi Shyti <andi.shyti@kernel.org>
To: Wolfram Sang <wsa@kernel.org>
Cc: linux-i2c <linux-i2c@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Hans Hu <HansHu-oc@zhaoxin.com>
Subject: [GIT PULL] i2c-host changes for v6.9 - part 2 (i2c zhaoxin)
Date: Sun, 10 Mar 2024 12:32:45 +0100 [thread overview]
Message-ID: <sxe4w2iwfkaoowaqssz2lbig7tlnoasseod5atval23saqigee@tzz7qwy4fhaq> (raw)
Hi Wolfram,
after Linus pulled the commit from Christophe, which was causing
conflicts with the I2C Zhaoxin controller, I'm sending you the
second part of pull request for v6.9, which includes only the six
patches from Hans that add support.
This series is in i2c/i2c-host-next. I haven't created a new
branch since it has already been tested here for several days
here.
If time permits, there are two series from Theo and Mukesh queued
in i2c/i2c-host.
Thanks,
Andi
The following changes since commit b3b00cea6378475f972eb49c068062627ff3a14d:
Merge branch 'i2c/i2c-host' into i2c/i2c-host-next (2024-03-08 23:30:28 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux.git tags/i2c-host-6.9-pt.2-zhaoxin
for you to fetch changes up to 391ead8dc4e49b6de96ffdd1f6b1d89fa2282e40:
i2c: add zhaoxin i2c controller driver (2024-03-08 23:30:50 +0100)
----------------------------------------------------------------
Added support for the Zhaoxin I2C controller. This required
extensive code refactoring in the wmt driver, mainly targeting
the extraction of the common IP from the viai2c, which will be
used by both wmt and Zhaoxin.
----------------------------------------------------------------
Hans Hu (6):
i2c: wmt: create wmt_i2c_init for general init
i2c: wmt: split out common files
i2c: wmt: rename something
i2c: wmt: fix a bug when thread blocked
i2c: wmt: add platform type VIAI2C_PLAT_WMT
i2c: add zhaoxin i2c controller driver
MAINTAINERS | 10 +++-
drivers/i2c/busses/Kconfig | 10 ++++
drivers/i2c/busses/Makefile | 3 ++
drivers/i2c/busses/i2c-viai2c-common.c | 250 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
drivers/i2c/busses/i2c-viai2c-common.h | 85 +++++++++++++++++++++++++++++++++
drivers/i2c/busses/i2c-viai2c-wmt.c | 148 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
drivers/i2c/busses/i2c-viai2c-zhaoxin.c | 299 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
drivers/i2c/busses/i2c-wmt.c | 421 -------------------------------------------------------------------------------------------------------------------------------------------------------------------
8 files changed, 804 insertions(+), 422 deletions(-)
create mode 100644 drivers/i2c/busses/i2c-viai2c-common.c
create mode 100644 drivers/i2c/busses/i2c-viai2c-common.h
create mode 100644 drivers/i2c/busses/i2c-viai2c-wmt.c
create mode 100644 drivers/i2c/busses/i2c-viai2c-zhaoxin.c
delete mode 100644 drivers/i2c/busses/i2c-wmt.c
next reply other threads:[~2024-03-10 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 11:32 Andi Shyti [this message]
2024-03-11 14:30 ` [GIT PULL] i2c-host changes for v6.9 - part 2 (i2c zhaoxin) Andi Shyti
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=sxe4w2iwfkaoowaqssz2lbig7tlnoasseod5atval23saqigee@tzz7qwy4fhaq \
--to=andi.shyti@kernel.org \
--cc=HansHu-oc@zhaoxin.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).