From: Durai Manickam KR <durai.manickamkr@microchip.com>
To: <linux-i3c@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <alexandre.belloni@bootlin.com>,
<Frank.Li@nxp.com>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <balamanikandan.gunasundar@microchip.com>,
<nicolas.ferre@microchip.com>
Cc: Durai Manickam KR <durai.manickamkr@microchip.com>
Subject: [PATCH 0/4] Add Microchip I3C controller
Date: Tue, 9 Sep 2025 16:43:29 +0530 [thread overview]
Message-ID: <20250909111333.170016-1-durai.manickamkr@microchip.com> (raw)
Add support for microchip SAMA7D65 I3C HCI master only IP. This
hardware is an instance of the MIPI I3C HCI Controller implementing
version 1.0 specification. This driver adds platform-specific
support for SAMA7D65 SoC.
I3C in master mode supports up to 12.5MHz, SDR mode data transfer in
mixed bus mode (I2C and I3C target devices on same i3c bus). It also
supports IBI mechanism.
Features tested and supported :
Standard CCC commands.
I3C SDR mode private transfers in PIO mode.
I2C transfers in PIO mode.
Pure bus mode and mixed bus mode.
Testing done:
With this patch we are able to fully configure the lsm6dso I3C slave
device. Unlike I2C, I hope there is no linux utility to check the
various transactions supported in the host controller. These features
will be added later on this driver after testing (probably with I3C
analyser KIT).
Durai Manickam KR (4):
clk: at91: sama7d65: add peripheral clock for I3C
i3c: master: add Microchip SAMA7D65 I3C HCI master driver
ARM: configs: at91: sama7: Add SAMA7D65 I3C HCI master
ARM: dts: microchip: add I3C controller
arch/arm/boot/dts/microchip/sama7d65.dtsi | 12 +
arch/arm/configs/sama7_defconfig | 2 +
drivers/clk/at91/sama7d65.c | 5 +-
drivers/i3c/master/Kconfig | 14 +
drivers/i3c/master/Makefile | 1 +
drivers/i3c/master/sama7d65-i3c-hci-master.c | 2705 ++++++++++++++++++
6 files changed, 2737 insertions(+), 2 deletions(-)
create mode 100644 drivers/i3c/master/sama7d65-i3c-hci-master.c
--
2.34.1
next reply other threads:[~2025-09-09 11:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 11:13 Durai Manickam KR [this message]
2025-09-09 11:13 ` [PATCH 1/4] clk: at91: sama7d65: add peripheral clock for I3C Durai Manickam KR
2025-09-09 11:19 ` Durai.ManickamKR
2025-09-09 11:13 ` [PATCH 2/4] i3c: master: add Microchip SAMA7D65 I3C HCI master driver Durai Manickam KR
2025-09-09 21:18 ` Frank Li
2025-09-10 6:12 ` Durai.ManickamKR
2025-09-10 6:53 ` Wolfram Sang
2025-09-10 9:01 ` Jarkko Nikula
2025-09-18 6:40 ` Durai.ManickamKR
2025-09-10 16:16 ` Frank Li
2025-09-10 5:57 ` kernel test robot
2025-09-10 6:19 ` Durai.ManickamKR
2025-09-09 11:13 ` [PATCH 3/4] ARM: configs: at91: sama7: Add SAMA7D65 I3C HCI master Durai Manickam KR
2025-09-09 11:13 ` [PATCH 4/4] ARM: dts: microchip: add I3C controller Durai Manickam KR
2025-09-09 19:46 ` [PATCH 0/4] Add Microchip " Conor Dooley
2025-09-10 6:14 ` Durai.ManickamKR
2025-09-10 17:54 ` Conor Dooley
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=20250909111333.170016-1-durai.manickamkr@microchip.com \
--to=durai.manickamkr@microchip.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=balamanikandan.gunasundar@microchip.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--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
all inboxes | Powered by JetHome®