From: Ben Zong-You Xie via B4 Relay <devnull+ben717.andestech.com@kernel.org>
To: Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Ben Zong-You Xie <ben717@andestech.com>,
Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH v4 0/4] i2c: add support for Andes platform
Date: Mon, 30 Mar 2026 15:30:30 +0800 [thread overview]
Message-ID: <20260330-atciic100-v4-0-d40822f63e4e@andestech.com> (raw)
This patch series adds I2C support to Andes platform, such as AE350 and
QiLai SoC.
Signed-off-by: Ben Zong-You Xie <ben717@andestech.com>
---
Changes in v4:
- Rebased on andi.shyti/i2c/i2c-host-next.
- (1/4)
- Added Conor's acked by tag.
- Link to v3: https://patch.msgid.link/20260128-atciic100-v3-0-8c002fcc2bb4@andestech.com
Changes in v3:
- (1/4)
- Rewrote the commit message to provide a detailed hardware
description and explain the relationship between the ATCIIC100 IP,
the AE350 platform, and the QiLai SoC. (Krzysztof)
- Link to v2: https://patch.msgid.link/20260122-atciic100-v2-0-7559136d07cf@andestech.com
Changes in v2:
- ATCIIC100 is the hardware name for the Andes I2C controller and was used
throughout v1. However, since Device Tree bindings should reflect the hardware
identity and driver/config naming typically follows the i2c-<soc/platform>
convention, this version replaces occurrences of "atciic100" with more
appropriate names, such as "i2c-andes" or "andes_i2c," to align with upstream
standards.
- Updated cover letter title and the description.
- Rebased on andi.shyti/i2c/i2c-host-next.
- (1/4)
- Updated the title and the description of the patch.
- Specified what the hardware is, and modify the title and compatibles. (Krzysztof)
- Corrected device register size.
- (2/4)
- Updated the title and the description of the patch.
- Replaced the readl/writel operations with regmap APIs.
- Replaced all occurrences of atciic100 with proper names.
- Used module_platform_driver() to initialize. (Andi)
- Moved CONFIG_I2C_ANDES (CONFIG_I2C_ATCIIC100 in v1) to the
"Embedded system I2C/SMBus host controller drivers" section.
- Made CONFIG_I2C_ANDES depend on ARCH_ANDES
- (3/4) (new)
- Added an entry to the MAINTAINERS file.
- (4/4) (new)
- Added the I2C node to QiLai DTS.
- Link to v1: https://patch.msgid.link/20250207021923.2912373-1-ben717@andestech.com
---
Ben Zong-You Xie (4):
dt-bindings: i2c: add support for AE350 I2C controller
i2c: add Andes I2C driver support
MAINTAINERS: add an entry for Andes I2C driver
riscv: dts: andes: qilai: add I2C controller
.../bindings/i2c/andestech,ae350-i2c.yaml | 45 +++
MAINTAINERS | 6 +
arch/riscv/boot/dts/andes/qilai.dtsi | 7 +
drivers/i2c/busses/Kconfig | 10 +
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/i2c-andes.c | 341 +++++++++++++++++++++
6 files changed, 410 insertions(+)
---
base-commit: 46ec065d8610c5e8d11a8b205a6b7bd3c40d46b8
change-id: 20260120-atciic100-da3ec68f7bb4
Best regards,
--
Ben Zong-You Xie <ben717@andestech.com>
next reply other threads:[~2026-03-30 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 7:30 Ben Zong-You Xie via B4 Relay [this message]
2026-03-30 7:30 ` [PATCH v4 1/4] dt-bindings: i2c: add support for AE350 I2C controller Ben Zong-You Xie via B4 Relay
2026-03-30 7:30 ` [PATCH v4 2/4] i2c: add Andes I2C driver support Ben Zong-You Xie via B4 Relay
2026-03-30 7:30 ` [PATCH v4 3/4] MAINTAINERS: add an entry for Andes I2C driver Ben Zong-You Xie via B4 Relay
2026-03-30 7:30 ` [PATCH v4 4/4] riscv: dts: andes: qilai: add I2C controller Ben Zong-You Xie via B4 Relay
2026-04-24 2:36 ` [PATCH v4 0/4] i2c: add support for Andes platform Ben Zong-You Xie
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=20260330-atciic100-v4-0-d40822f63e4e@andestech.com \
--to=devnull+ben717.andestech.com@kernel.org \
--cc=alex@ghiti.fr \
--cc=andi.shyti@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ben717@andestech.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@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