Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sander Vanheule <sander@svanheule.net>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Chris Packham <chris.packham@alliedtelesis.co.nz>,
	devicetree@vger.kernel.org, linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Sander Vanheule <sander@svanheule.net>
Subject: [PATCH 0/9] mips: dts: Split Realtek devicetrees
Date: Sun, 19 Jan 2025 19:34:15 +0100	[thread overview]
Message-ID: <20250119183424.259353-1-sander@svanheule.net> (raw)

This patch series intends to clean up the base includes, shared between
hardware devicetrees. To get rid of some dtbs_check warnings, some cpu
clock prorerties are also modified.

To indicate why the split-up is required, the series concludes with
adding some CPU peripherals to rtl838x.dtsi, which are then used to add
a gpio-restart for the Cisco SG220-26P.

Sander Vanheule (9):
  mips: dts: realtek: Decouple RTL930x base DTSI
  mips: dts: realtek: Clean up CPU clocks
  mips: dts: realtek: Add address to SoC node name
  mips: dts: realtek: Fold rtl83xx into rtl838x
  mips: dts: realtek: Add SoC IRQ node for RTL838x
  mips: dts: realtek: Correct uart interrupt-parent
  mips: dts: realtek: Replace uart clock property
  mips: dts: realtek: Add RTL838x SoC peripherals
  mips: dts: realtek: Add restart to Cisco SG220-26P

 arch/mips/boot/dts/realtek/cisco_sg220-26.dts |  10 +-
 arch/mips/boot/dts/realtek/rtl838x.dtsi       | 111 +++++++++++++-
 arch/mips/boot/dts/realtek/rtl83xx.dtsi       |  59 --------
 arch/mips/boot/dts/realtek/rtl930x.dtsi       | 136 +++++++++++-------
 4 files changed, 202 insertions(+), 114 deletions(-)
 delete mode 100644 arch/mips/boot/dts/realtek/rtl83xx.dtsi

-- 
2.48.1


             reply	other threads:[~2025-01-19 18:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-19 18:34 Sander Vanheule [this message]
2025-01-19 18:34 ` [PATCH 1/9] mips: dts: realtek: Decouple RTL930x base DTSI Sander Vanheule
2025-01-20  1:20   ` Chris Packham
2025-01-19 18:34 ` [PATCH 2/9] mips: dts: realtek: Clean up CPU clocks Sander Vanheule
2025-01-20  1:21   ` Chris Packham
2025-01-19 18:34 ` [PATCH 3/9] mips: dts: realtek: Add address to SoC node name Sander Vanheule
2025-01-20  1:22   ` Chris Packham
2025-01-19 18:34 ` [PATCH 4/9] mips: dts: realtek: Fold rtl83xx into rtl838x Sander Vanheule
2025-01-20  1:23   ` Chris Packham
2025-01-19 18:34 ` [PATCH 5/9] mips: dts: realtek: Add SoC IRQ node for RTL838x Sander Vanheule
2025-01-19 18:34 ` [PATCH 6/9] mips: dts: realtek: Correct uart interrupt-parent Sander Vanheule
2025-01-19 18:34 ` [PATCH 7/9] mips: dts: realtek: Replace uart clock property Sander Vanheule
2025-01-19 18:34 ` [PATCH 8/9] mips: dts: realtek: Add RTL838x SoC peripherals Sander Vanheule
2025-01-19 18:34 ` [PATCH 9/9] mips: dts: realtek: Add restart to Cisco SG220-26P Sander Vanheule
2025-02-21 15:27 ` [PATCH 0/9] mips: dts: Split Realtek devicetrees Thomas Bogendoerfer
2025-02-22 10:57   ` Sander Vanheule

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=20250119183424.259353-1-sander@svanheule.net \
    --to=sander@svanheule.net \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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