devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Raphael Gallais-Pou <rgallaispou@gmail.com>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	 Patrice Chotard <patrice.chotard@foss.st.com>,
	 Russell King <linux@armlinux.org.uk>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org,
	Alain Volmat <avolmat@me.com>,
	 Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: [PATCH v2 0/3] STi device-tree cleanup
Date: Mon, 14 Jul 2025 15:49:13 +0200	[thread overview]
Message-ID: <20250714-sti-rework-v2-0-f4274920858b@gmail.com> (raw)

This serie aims to cleanup and rework the STi device-tree.

STiH415/STIh416 SoCs are not supported anymore and B2120 boards are
internal boards.  Update the documentation and drop the related DT
files.

Patch [2/3] has already been sent by Alain several months ago, but got
no response [1].

[1] https://lore.kernel.org/all/20230416185939.18497-1-avolmat@me.com

Signed-off-by: Raphael Gallais-Pou <rgallaispou@gmail.com>
---
Changes in v2:
- Fix typo in cover letter s/[4/6]/[2/3]
- Reorder patchset to be bisectable as Krzysztof mentioned
- Add Krzysztof's Acked-by where relevant
- Link to v1: https://lore.kernel.org/r/20250713-sti-rework-v1-0-6716a09e538d@gmail.com

---
Alain Volmat (1):
      ARM: sti: removal of stih415/stih416 related entries

Raphael Gallais-Pou (2):
      ARM: sti: drop B2120 board support
      dt-bindings: arm: sti: drop B2120 board support

 Documentation/devicetree/bindings/arm/sti.yaml |   4 -
 arch/arm/boot/dts/st/Makefile                  |   2 -
 arch/arm/boot/dts/st/stih407-b2120.dts         |  27 ----
 arch/arm/boot/dts/st/stih407.dtsi              | 145 -----------------
 arch/arm/boot/dts/st/stih410-b2120.dts         |  66 --------
 arch/arm/boot/dts/st/stihxxx-b2120.dtsi        | 206 -------------------------
 arch/arm/mach-sti/Kconfig                      |  20 +--
 arch/arm/mach-sti/board-dt.c                   |   2 -
 8 files changed, 1 insertion(+), 471 deletions(-)
---
base-commit: a6cfa4c8833944f8912c1fa7f95795753f6376ea
change-id: 20250401-sti-rework-b009551a362c

Best regards,
-- 
Raphael Gallais-Pou <rgallaispou@gmail.com>


             reply	other threads:[~2025-07-14 13:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-14 13:49 Raphael Gallais-Pou [this message]
2025-07-14 13:49 ` [PATCH v2 1/3] ARM: sti: drop B2120 board support Raphael Gallais-Pou
2025-07-28  9:25   ` Patrice CHOTARD
2025-08-18 14:02     ` Patrice CHOTARD
2025-07-14 13:49 ` [PATCH v2 2/3] ARM: sti: removal of stih415/stih416 related entries Raphael Gallais-Pou
2025-07-28  9:25   ` Patrice CHOTARD
2025-08-18 14:02     ` Patrice CHOTARD
2025-07-14 13:49 ` [PATCH v2 3/3] dt-bindings: arm: sti: drop B2120 board support Raphael Gallais-Pou
2025-07-28  9:26   ` Patrice CHOTARD
2025-08-18 14:02     ` Patrice CHOTARD

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=20250714-sti-rework-v2-0-f4274920858b@gmail.com \
    --to=rgallaispou@gmail.com \
    --cc=avolmat@me.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=patrice.chotard@foss.st.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;
as well as URLs for NNTP newsgroup(s).