linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Frank Wunderlich <linux@fw-web.de>
To: linux-mediatek@lists.infradead.org
Cc: Frank Wunderlich <frank-w@public-files.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] support PCIe on mt7986/BPI-R3 (DTS)
Date: Thu, 27 Oct 2022 08:01:40 +0200	[thread overview]
Message-ID: <20221027060142.6354-1-linux@fw-web.de> (raw)

From: Frank Wunderlich <frank-w@public-files.de>

After PCIe binding got reviewed here the last 2 PCIe Patches for adding
DTS nodes to mt7986 and bpi-r3.

based on:

rework mtk pcie-gen3 bindings and support mt7986
https://patchwork.kernel.org/project/linux-mediatek/list/?series=688557

Add BananaPi R3
https://patchwork.kernel.org/project/linux-mediatek/list/?series=688984

Frank Wunderlich (1):
  arm64: dts: mt7986: add pcie node to BananaPi-R3

Sam Shih (1):
  arm64: dts: mt7986: add pcie related device nodes

 .../dts/mediatek/mt7986a-bananapi-bpi-r3.dtsi | 17 ++++++
 arch/arm64/boot/dts/mediatek/mt7986a-rfb.dts  | 16 ++++++
 arch/arm64/boot/dts/mediatek/mt7986a.dtsi     | 52 +++++++++++++++++++
 3 files changed, 85 insertions(+)

-- 
2.34.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2022-10-27  6:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27  6:01 Frank Wunderlich [this message]
2022-10-27  6:01 ` [PATCH v1 1/2] arm64: dts: mt7986: add pcie related device nodes Frank Wunderlich
2022-10-27  6:01 ` [PATCH v1 2/2] arm64: dts: mt7986: add PCIe nodes to BananaPi-R3 Frank Wunderlich

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=20221027060142.6354-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).