From: Hans Hu <hanshu-oc@zhaoxin.com>
To: <andi.shyti@kernel.org>, <wsa@kernel.org>, <linux-i2c@vger.kernel.org>
Cc: <cobechen@zhaoxin.com>, <TonyWWang@zhaoxin.com>
Subject: [PATCH v2 0/2] i2c: add support for Zhaoxin I2C controller
Date: Mon, 14 Aug 2023 16:40:17 +0800 [thread overview]
Message-ID: <cover.1691999569.git.hanshu-oc@zhaoxin.com> (raw)
Hi Andi, Wolfram,
The Zhaoxin I2C controller uses the same I2C IP as Wonder Media.
Both Zhaoxin and Wonder Media's I2C IP are come from VIA I2C IP.
Therefore, some codes of i2c-wmt.c can be re-used by i2c-zhaoxin.c.
As suggested earlier, created two files, named i2c-viai2c-common.{c,h}.
They contains the macro definitions, functions declaration and data
structure used by both i2c-zhaoxin.c and i2c-wmt.c.
v1->v2:
1. Fixed a compilation error for header file references.
2. use I2C platform device's name to define the irq's name.
Hans Hu (2):
i2c: wmt: split out i2c-viai2c-common.{c,h}
i2c: add support for Zhaoxin I2C controller
MAINTAINERS | 7 +
drivers/i2c/busses/Kconfig | 15 +
drivers/i2c/busses/Makefile | 2 +
drivers/i2c/busses/i2c-viai2c-common.c | 239 +++++++++++++++
drivers/i2c/busses/i2c-viai2c-common.h | 76 +++++
drivers/i2c/busses/i2c-wmt.c | 402 ++-----------------------
drivers/i2c/busses/i2c-zhaoxin.c | 274 +++++++++++++++++
7 files changed, 644 insertions(+), 371 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-zhaoxin.c
--
2.34.1
next reply other threads:[~2023-08-14 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 8:40 Hans Hu [this message]
2023-08-14 8:40 ` [PATCH v2 1/2] i2c: wmt: split out i2c-viai2c-common.{c,h} Hans Hu
2023-08-25 20:02 ` Wolfram Sang
2023-08-28 2:42 ` Hans Hu
2023-08-28 6:00 ` Wolfram Sang
2023-08-28 7:25 ` Hans Hu
2023-08-28 7:37 ` Wolfram Sang
2023-08-14 8:40 ` [PATCH v2 2/2] i2c: add support for Zhaoxin I2C controller Hans Hu
2023-08-25 20:04 ` Wolfram Sang
2023-08-28 2:50 ` Hans Hu
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=cover.1691999569.git.hanshu-oc@zhaoxin.com \
--to=hanshu-oc@zhaoxin.com \
--cc=TonyWWang@zhaoxin.com \
--cc=andi.shyti@kernel.org \
--cc=cobechen@zhaoxin.com \
--cc=linux-i2c@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