linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Chen-Yu Tsai <wens@kernel.org>
To: Jernej Skrabec <jernej.skrabec@gmail.com>,
	Samuel Holland <samuel@sholland.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>
Cc: Chen-Yu Tsai <wens@csie.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-sunxi@lists.linux.dev, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] riscv: allwinner: ClockworkPi and DevTerm devicetrees
Date: Sat, 22 Jun 2024 23:07:28 +0800	[thread overview]
Message-ID: <20240622150731.1105901-1-wens@kernel.org> (raw)

From: Chen-Yu Tsai <wens@csie.org>

Hi folks,

Here are a couple patches that were originally sent by Samuel, but later
dropped due to the system LDO regulator bindings not getting merged. The
regulator bindings were recently resent and landed [1], so now is the time
to get the rest of the stragglers in.

Patch 1 and 3 were originally part of Samuel's D1 device tree submission [2].

Patch 2 was part of the system LDO series [3].

These have been rebased onto v6.10-rc1 and have been compile tested
only.

I plan to land these in the coming week for 6.11.


Regards
ChenYu


[1] https://lore.kernel.org/linux-sunxi/171532213496.2045034.2645456500780291742.b4-ty@kernel.org/
[2] https://lore.kernel.org/linux-sunxi/20221231233851.24923-1-samuel@sholland.org/
[3] https://lore.kernel.org/linux-sunxi/20221208084127.17443-1-samuel@sholland.org/

Chen-Yu Tsai (1):
  riscv: dts: allwinner: d1s-t113: Add system LDOs

Samuel Holland (2):
  dt-bindings: sram: sunxi-sram: Add regulators child
  riscv: dts: allwinner: Add ClockworkPi and DevTerm devicetrees

 .../allwinner,sun4i-a10-system-control.yaml   |  28 ++
 arch/riscv/boot/dts/allwinner/Makefile        |   2 +
 .../allwinner/sun20i-d1-clockworkpi-v3.14.dts | 252 ++++++++++++++++++
 .../dts/allwinner/sun20i-d1-devterm-v3.14.dts |  36 +++
 .../boot/dts/allwinner/sunxi-d1s-t113.dtsi    |  11 +
 5 files changed, 329 insertions(+)
 create mode 100644 arch/riscv/boot/dts/allwinner/sun20i-d1-clockworkpi-v3.14.dts
 create mode 100644 arch/riscv/boot/dts/allwinner/sun20i-d1-devterm-v3.14.dts

-- 
2.39.2



             reply	other threads:[~2024-06-22 15:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-22 15:07 Chen-Yu Tsai [this message]
2024-06-22 15:07 ` [PATCH 1/3] dt-bindings: sram: sunxi-sram: Add regulators child Chen-Yu Tsai
2024-06-22 16:35   ` Rob Herring (Arm)
2024-06-22 16:46     ` Chen-Yu Tsai
2024-06-23 14:28       ` Conor Dooley
2024-06-22 15:07 ` [PATCH 2/3] riscv: dts: allwinner: d1s-t113: Add system LDOs Chen-Yu Tsai
2024-06-22 15:07 ` [PATCH 3/3] riscv: dts: allwinner: Add ClockworkPi and DevTerm devicetrees Chen-Yu Tsai
2024-06-30 15:06 ` (subset) [PATCH 0/3] riscv: allwinner: " Chen-Yu Tsai
2024-06-30 15:09 ` Chen-Yu Tsai

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=20240622150731.1105901-1-wens@kernel.org \
    --to=wens@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=devicetree@vger.kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=samuel@sholland.org \
    --cc=wens@csie.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).