devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: E Shattow <e@freeshell.de>
To: Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	devicetree@vger.kernel.org, E Shattow <e@freeshell.de>,
	Icenowy Zheng <uwu@icenowy.me>, Rob Herring <robh@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Subject: [PATCH v3 0/2] riscv: dts: starfive: Add OrangePi RV board
Date: Sun, 23 Nov 2025 14:50:43 -0800	[thread overview]
Message-ID: <20251123225059.49665-1-e@freeshell.de> (raw)

Icenowy is busy and so with their permission I have applied v2 review
feedback. Additionally I revise the commit messages. This should now be in
good shape for -next

- E

Changes since v2:
- enable active high mmc1 card detect gpio
- drop delete-node from mmc0 reset pins following commit fa939a287224
  ("dts: starfive: jh7110-common: split out mmc0 reset pins from common 
  into boards")
- sort phy0 properties rx before tx
- revise commit description of SoC peripherals as list
- revise commit description of compatible binding

Changes in v2:
- Property order change mentioned in the review of v1.
- Added Wi-Fi (along with the always on VCC3V3_PCIE regulator, which is
  used to power up WIFI_3V3). The OOB IRQ is still not possible to use
  because of some incompatibility between StarFive pinctrl driver and
  brcmfmac.
- Removed the LED because it's in common DTSI.

Icenowy Zheng (2):
  dt-bindings: riscv: starfive: add xunlong,orangepi-rv
  riscv: dts: starfive: add Orange Pi RV

 .../devicetree/bindings/riscv/starfive.yaml   |  1 +
 arch/riscv/boot/dts/starfive/Makefile         |  1 +
 .../boot/dts/starfive/jh7110-orangepi-rv.dts  | 76 +++++++++++++++++++
 3 files changed, 78 insertions(+)
 create mode 100644 arch/riscv/boot/dts/starfive/jh7110-orangepi-rv.dts


base-commit: 1088d49b626487777913079bef0db3adef4bfb4a
-- 
2.50.0


             reply	other threads:[~2025-11-23 22:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-23 22:50 E Shattow [this message]
2025-11-23 22:50 ` [PATCH v3 1/2] dt-bindings: riscv: starfive: add xunlong,orangepi-rv E Shattow
2025-11-24  7:28   ` Krzysztof Kozlowski
2025-11-24 13:22     ` Conor Dooley
2025-11-24 21:59       ` E Shattow
2025-11-25  7:28         ` Krzysztof Kozlowski
2025-11-25  7:33           ` Icenowy Zheng
2025-11-25  7:48             ` Krzysztof Kozlowski
2025-11-25  8:01               ` Icenowy Zheng
2025-11-25 13:07                 ` E Shattow
2025-11-25 19:14                   ` Conor Dooley
2025-11-26 20:34                     ` E Shattow
2025-11-26  8:23                   ` Krzysztof Kozlowski
2025-11-23 22:50 ` [PATCH v3 2/2] riscv: dts: starfive: add Orange Pi RV E Shattow
2025-11-24 11:07   ` Conor Dooley
2025-11-24 11:08     ` Icenowy Zheng
2025-11-24 13:21       ` Conor Dooley
2025-11-24 21:56         ` E Shattow
2025-11-25 22:24 ` [PATCH v3 0/2] riscv: dts: starfive: Add OrangePi RV board Conor Dooley
2025-11-26 13:48   ` Emil Renner Berthing

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=20251123225059.49665-1-e@freeshell.de \
    --to=e@freeshell.de \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.org \
    --cc=uwu@icenowy.me \
    /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).