devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kaustabh Chakraborty <kauschluss@disroot.org>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	 linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Kaustabh Chakraborty <kauschluss@disroot.org>
Subject: [PATCH 5/7] arm64: dts: exynos7870-a2corelte: add bus-width to mmc0 node
Date: Sun, 28 Sep 2025 22:13:56 +0530	[thread overview]
Message-ID: <20250928-exynos7870-dt-fixes-v1-5-a40e77a73f16@disroot.org> (raw)
In-Reply-To: <20250928-exynos7870-dt-fixes-v1-0-a40e77a73f16@disroot.org>

Add the bus-width property in &mmc0 node. The Exynos DWMMC driver
assumes bus width to be 8 if not present in devicetree, so at least with
respect to the Linux kernel, this doesn't introduce any functional
changes. But other drivers referring to it may not. Either way, without
the bus-width property the hardware description remains incomplete.

Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
---
 arch/arm64/boot/dts/exynos/exynos7870-a2corelte.dts | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm64/boot/dts/exynos/exynos7870-a2corelte.dts b/arch/arm64/boot/dts/exynos/exynos7870-a2corelte.dts
index f8a7610abeb77cab9f38aaf48d441d99ec61ab5f..1193f0f7dcc171762fefccee23c2c294a41c46c9 100644
--- a/arch/arm64/boot/dts/exynos/exynos7870-a2corelte.dts
+++ b/arch/arm64/boot/dts/exynos/exynos7870-a2corelte.dts
@@ -447,6 +447,7 @@ &mmc0 {
 	vmmc-supply = <&vdd_ldo26>;
 	vqmmc-supply = <&vdd_ldo27>;
 
+	bus-width = <8>;
 	fifo-depth = <64>;
 	samsung,dw-mshc-ciu-div = <3>;
 	samsung,dw-mshc-sdr-timing = <0 4>;

-- 
2.51.0


  parent reply	other threads:[~2025-09-28 16:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-28 16:43 [PATCH 0/7] Another set of exynos7870 devicetree fixes Kaustabh Chakraborty
2025-09-28 16:43 ` [PATCH 1/7] arm64: dts: exynos7870: relocate ${x}-names property after ${x} Kaustabh Chakraborty
2025-09-28 21:56   ` Krzysztof Kozlowski
2025-09-29 10:01     ` Kaustabh Chakraborty
2025-10-07  1:22       ` Krzysztof Kozlowski
2025-10-13  8:24         ` Kaustabh Chakraborty
2025-09-28 16:43 ` [PATCH 2/7] arm64: dts: exynos7870-a2corelte: " Kaustabh Chakraborty
2025-09-28 16:43 ` [PATCH 3/7] arm64: dts: exynos7870-j6lte: " Kaustabh Chakraborty
2025-09-28 16:43 ` [PATCH 4/7] arm64: dts: exynos7870-on7xelte: " Kaustabh Chakraborty
2025-09-28 16:43 ` Kaustabh Chakraborty [this message]
2025-10-13  0:25   ` (subset) [PATCH 5/7] arm64: dts: exynos7870-a2corelte: add bus-width to mmc0 node Krzysztof Kozlowski
2025-09-28 16:43 ` [PATCH 6/7] arm64: dts: exynos7870-j6lte: " Kaustabh Chakraborty
2025-10-13  0:25   ` (subset) " Krzysztof Kozlowski
2025-09-28 16:43 ` [PATCH 7/7] arm64: dts: exynos7870-on7xelte: " Kaustabh Chakraborty
2025-10-13  0:26   ` (subset) " Krzysztof Kozlowski

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=20250928-exynos7870-dt-fixes-v1-5-a40e77a73f16@disroot.org \
    --to=kauschluss@disroot.org \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.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;
as well as URLs for NNTP newsgroup(s).