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 0/7] Another set of exynos7870 devicetree fixes
Date: Sun, 28 Sep 2025 22:13:51 +0530	[thread overview]
Message-ID: <20250928-exynos7870-dt-fixes-v1-0-a40e77a73f16@disroot.org> (raw)

Applying this patchset will introduce the following:
* All ${x}-names properties will now follow the corresponding ${x}
  properties.
* bus-width of mmc0 node of all exynos7870 devices will be explicitly
  defined.

Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
---
Kaustabh Chakraborty (7):
      arm64: dts: exynos7870: relocate ${x}-names property after ${x}
      arm64: dts: exynos7870-a2corelte: relocate ${x}-names property after ${x}
      arm64: dts: exynos7870-j6lte: relocate ${x}-names property after ${x}
      arm64: dts: exynos7870-on7xelte: relocate ${x}-names property after ${x}
      arm64: dts: exynos7870-a2corelte: add bus-width to mmc0 node
      arm64: dts: exynos7870-j6lte: add bus-width to mmc0 node
      arm64: dts: exynos7870-on7xelte: add bus-width to mmc0 node

 .../arm64/boot/dts/exynos/exynos7870-a2corelte.dts |  21 ++--
 arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts    |  21 ++--
 arch/arm64/boot/dts/exynos/exynos7870-on7xelte.dts |  21 ++--
 arch/arm64/boot/dts/exynos/exynos7870.dtsi         | 108 ++++++++++-----------
 4 files changed, 87 insertions(+), 84 deletions(-)
---
base-commit: 262858079afde6d367ce3db183c74d8a43a0e83f
change-id: 20250820-exynos7870-dt-fixes-b4ad027cef67

Best regards,
-- 
Kaustabh Chakraborty <kauschluss@disroot.org>


             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 Kaustabh Chakraborty [this message]
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 ` [PATCH 5/7] arm64: dts: exynos7870-a2corelte: add bus-width to mmc0 node Kaustabh Chakraborty
2025-10-13  0:25   ` (subset) " 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-0-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).