From: Frank Wunderlich <linux@fw-web.de>
To: linux-mediatek@lists.infradead.org
Cc: Frank Wunderlich <frank-w@public-files.de>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [RFC v3 00/11] Add BananaPi R3
Date: Sun, 6 Nov 2022 09:50:23 +0100 [thread overview]
Message-ID: <20221106085034.12582-1-linux@fw-web.de> (raw)
From: Frank Wunderlich <frank-w@public-files.de>
This Series adds some Nodes to mt7986 devicetree and the BananaPi R3
i included sams series for mt7986 DTS with small changes
https://patchwork.kernel.org/project/linux-mediatek/cover/20220427124741.18245-1-sam.shih@mediatek.com/
this series need these Patches:
i2c-support:
https://patchwork.kernel.org/project/linux-mediatek/cover/20221009101631.82380-1-linux@fw-web.de/
mmc bindings:
https://patchwork.kernel.org/project/linux-mediatek/list/?series=688675
update pinctrl-bindings:
https://patchwork.kernel.org/project/linux-mediatek/list/?series=692462
hwrng and pinctrl (uart splitting) are already applied to next
i had run full dtbs-check but i end up with some strange warnings in
ethernet-node that should not come up as phy-handle and sfp/managed
properties are already defined.
phy-handle made optional
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/net/mediatek,net.yaml#n265
property sfp/managed (which is included for mac subnode in yaml above):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/net/ethernet-controller.yaml#n137
changes:
v3:
- changed mmc pull-ups
- added patch for board binding (sent separately before)
- added pcie node in mt7986 (not yet again in r3)
- added dt overlays
Frank Wunderlich (5):
arm64: dts: mt7986: add i2c node
dt-bindings: arm64: dts: mediatek: add compatible for bananapi r3
arm64: dts: mt7986: add Bananapi R3
arm64: dts: mt7986: add PCIe nodes to BananaPi-R3
arm64: dts: mt7986: add BPI-R3 nand/nor overlays
Sam Shih (6):
arm64: dts: mt7986: harmonize device node order
arm64: dts: mt7986: add spi related device nodes
arm64: dts: mt7986: add usb related device nodes
arm64: dts: mt7986: add crypto related device nodes
arm64: dts: mt7986: add mmc related device nodes
arm64: dts: mt7986: add pcie related device nodes
.../devicetree/bindings/arm/mediatek.yaml | 1 +
arch/arm64/boot/dts/mediatek/Makefile | 4 +
.../mediatek/mt7986a-bananapi-bpi-r3-emmc.dts | 31 ++
.../mediatek/mt7986a-bananapi-bpi-r3-nand.dts | 53 ++
.../mediatek/mt7986a-bananapi-bpi-r3-nor.dts | 67 +++
.../mediatek/mt7986a-bananapi-bpi-r3-sd.dts | 25 +
.../dts/mediatek/mt7986a-bananapi-bpi-r3.dtsi | 458 ++++++++++++++++++
arch/arm64/boot/dts/mediatek/mt7986a-rfb.dts | 264 ++++++++--
arch/arm64/boot/dts/mediatek/mt7986a.dtsi | 179 +++++++
arch/arm64/boot/dts/mediatek/mt7986b-rfb.dts | 83 +++-
10 files changed, 1110 insertions(+), 55 deletions(-)
create mode 100644 arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3-emmc.dts
create mode 100644 arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3-nand.dts
create mode 100644 arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3-nor.dts
create mode 100644 arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3-sd.dts
create mode 100644 arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dtsi
--
2.34.1
next reply other threads:[~2022-11-06 8:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 8:50 Frank Wunderlich [this message]
2022-11-06 8:50 ` [RFC v3 01/11] arm64: dts: mt7986: harmonize device node order Frank Wunderlich
2022-11-11 8:55 ` Matthias Brugger
2022-11-11 9:05 ` Matthias Brugger
2022-11-06 8:50 ` [RFC v3 02/11] arm64: dts: mt7986: add spi related device nodes Frank Wunderlich
2022-11-11 8:54 ` Matthias Brugger
2022-11-06 8:50 ` [RFC v3 03/11] arm64: dts: mt7986: add usb " Frank Wunderlich
2022-11-11 8:52 ` Matthias Brugger
2022-11-06 8:50 ` [RFC v3 04/11] arm64: dts: mt7986: add crypto " Frank Wunderlich
2022-11-11 8:56 ` Matthias Brugger
2022-11-06 8:50 ` [RFC v3 05/11] arm64: dts: mt7986: add mmc " Frank Wunderlich
2022-11-11 8:58 ` Matthias Brugger
2022-11-11 12:45 ` Aw: " Frank Wunderlich
2022-11-06 8:50 ` [RFC v3 06/11] arm64: dts: mt7986: add i2c node Frank Wunderlich
2022-11-11 9:06 ` Matthias Brugger
2022-11-06 8:50 ` [RFC v3 07/11] arm64: dts: mt7986: add pcie related device nodes Frank Wunderlich
2022-11-06 8:50 ` [RFC v3 08/11] dt-bindings: arm64: dts: mediatek: add compatible for bananapi r3 Frank Wunderlich
2022-11-06 8:50 ` [RFC v3 09/11] arm64: dts: mt7986: add Bananapi R3 Frank Wunderlich
2022-11-06 8:50 ` [RFC v3 10/11] arm64: dts: mt7986: add PCIe nodes to BananaPi-R3 Frank Wunderlich
2022-11-06 8:50 ` [RFC v3 11/11] arm64: dts: mt7986: add BPI-R3 nand/nor overlays Frank Wunderlich
2022-11-11 9:16 ` Matthias Brugger
2022-11-15 16:50 ` Aw: " Frank Wunderlich
2022-11-18 21:23 ` Rob Herring
2022-11-10 17:03 ` Aw: [RFC v3 00/11] Add BananaPi R3 Frank Wunderlich
2022-11-11 9:17 ` Matthias Brugger
2022-11-11 12:37 ` Aw: " Frank Wunderlich
2022-11-13 22:28 ` Matthias Brugger
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=20221106085034.12582-1-linux@fw-web.de \
--to=linux@fw-web.de \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@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).