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 3/4] ARM: configs: at91: sama7: add sama7d65 i3c-hci
Date: Thu, 18 Sep 2025 15:24:28 +0530 [thread overview]
Message-ID: <20250918095429.232710-4-durai.manickamkr@microchip.com> (raw)
In-Reply-To: <20250918095429.232710-1-durai.manickamkr@microchip.com>
Enable the configs needed for I3C framework and microchip
sama7d65 i3c-hci driver.
Signed-off-by: Durai Manickam KR <durai.manickamkr@microchip.com>
---
arch/arm/configs/sama7_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/sama7_defconfig b/arch/arm/configs/sama7_defconfig
index e14720a9a5ac..6a7455d5b7f5 100644
--- a/arch/arm/configs/sama7_defconfig
+++ b/arch/arm/configs/sama7_defconfig
@@ -115,6 +115,8 @@ CONFIG_HW_RANDOM=y
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_AT91=y
+CONFIG_I3C=y
+CONFIG_MIPI_I3C_HCI=y
CONFIG_SPI=y
CONFIG_SPI_ATMEL=y
CONFIG_SPI_ATMEL_QUADSPI=y
--
2.34.1
next prev parent reply other threads:[~2025-09-18 9:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 9:54 [PATCH 0/4] Add microchip sama7d65 SoC I3C support Durai Manickam KR
2025-09-18 9:54 ` [PATCH 1/4] clk: at91: sama7d65: add peripheral clock for I3C Durai Manickam KR
2025-09-18 9:54 ` [PATCH 2/4] i3c: mipi-i3c-hci: add microchip sama7d65 SoC Durai Manickam KR
2025-09-18 16:27 ` Frank Li
2025-09-25 13:23 ` Jarkko Nikula
2025-09-18 9:54 ` Durai Manickam KR [this message]
2025-09-18 9:54 ` [PATCH 4/4] ARM: dts: microchip: add I3C controller Durai Manickam KR
2025-09-18 15:44 ` Frank Li
2025-09-18 15:48 ` Conor Dooley
2025-09-18 14:50 ` [PATCH 0/4] Add microchip sama7d65 SoC I3C support Rob Herring (Arm)
2025-09-18 15:11 ` 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=20250918095429.232710-4-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