From: ryan_chen <ryan_chen@aspeedtech.com>
To: <BMC-SW@aspeedtech.com>, Rob Herring <robh+dt@kernel.org>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
Philipp Zabel <p.zabel@pengutronix.de>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] Add ASPEED AST2600 I2C new controller driver
Date: Wed, 23 Mar 2022 08:40:07 +0800 [thread overview]
Message-ID: <20220323004009.943298-1-ryan_chen@aspeedtech.com> (raw)
This series add AST2600 i2c new register mode driver. The
i2c new register mode have new clock divider option for
more flexibale generation. And also have separate i2c
master and slave register set for control.
ryan_chen (2):
dt-bindings: i2c-new: Add bindings for AST2600 i2C new controller
i2c:aspeed:support ast2600 i2c new register mode driver
.../bindings/i2c/aspeed,i2c-new.yaml | 78 +
drivers/i2c/busses/Kconfig | 11 +
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/aspeed-i2c-new-global.c | 91 +
drivers/i2c/busses/aspeed-i2c-new-global.h | 19 +
drivers/i2c/busses/i2c-new-aspeed.c | 1698 +++++++++++++++++
6 files changed, 1898 insertions(+)
create mode 100644 Documentation/devicetree/bindings/i2c/aspeed,i2c-new.yaml
create mode 100644 drivers/i2c/busses/aspeed-i2c-new-global.c
create mode 100644 drivers/i2c/busses/aspeed-i2c-new-global.h
create mode 100644 drivers/i2c/busses/i2c-new-aspeed.c
--
2.25.1
next reply other threads:[~2022-03-23 0:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 0:40 ryan_chen [this message]
2022-03-23 0:40 ` [PATCH 1/2] dt-bindings: i2c-new: Add bindings for AST2600 i2C new controller ryan_chen
2022-03-23 0:40 ` [PATCH 2/2] i2c:aspeed:support ast2600 i2c new register mode driver ryan_chen
2022-03-23 4:07 ` kernel test robot
2022-03-23 12:37 ` Andrew Lunn
2022-03-25 5:19 ` Ryan Chen
2022-03-24 8:56 ` kernel test robot
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=20220323004009.943298-1-ryan_chen@aspeedtech.com \
--to=ryan_chen@aspeedtech.com \
--cc=BMC-SW@aspeedtech.com \
--cc=andrew@aj.id.au \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@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).