From: Kishon Vijay Abraham I <kishon@ti.com>
To: Tero Kristo <t-kristo@ti.com>, Nishanth Menon <nm@ti.com>,
Rob Herring <robh+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: [PATCH v2 0/2] Add DT to get PCIe working in J721E SoC
Date: Mon, 14 Sep 2020 20:51:13 +0530 [thread overview]
Message-ID: <20200914152115.1788-1-kishon@ti.com> (raw)
Now that J721E PCIe support is merged (including the YAML bindings),
add PCIe device tree nodes to get PCIe working in J721E SoC both in
RC mode and EP mode.
Series has been rebased to:
git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux ti-k3-dts-next
Changes from v1:
1) Renamed all syscon dt-nodes to "syscon" instead of pcieX-ctrl.
2) Add TI specific compatible for "syscon" DT nodes
3) Add information about appending "ranges" property to access all PCIe
instances in commit log.
Kishon Vijay Abraham I (2):
arm64: dts: ti: k3-j721e-main: Add PCIe device tree nodes
arm64: dts: ti: k3-j721e-common-proc-board: Configure the PCIe
instances
.../dts/ti/k3-j721e-common-proc-board.dts | 80 ++++++
arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 232 +++++++++++++++++-
arch/arm64/boot/dts/ti/k3-j721e.dtsi | 5 +-
3 files changed, 315 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2020-09-14 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 15:21 Kishon Vijay Abraham I [this message]
2020-09-14 15:21 ` [PATCH v2 1/2] arm64: dts: ti: k3-j721e-main: Add PCIe device tree nodes Kishon Vijay Abraham I
2020-09-14 15:21 ` [PATCH v2 2/2] arm64: dts: ti: k3-j721e-common-proc-board: Configure the PCIe instances Kishon Vijay Abraham I
2020-09-14 16:10 ` [PATCH v2 0/2] Add DT to get PCIe working in J721E SoC Nishanth Menon
2020-09-15 12:40 ` Kishon Vijay Abraham I
2020-09-16 12:35 ` Nishanth Menon
2020-09-16 12:35 ` Nishanth Menon
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=20200914152115.1788-1-kishon@ti.com \
--to=kishon@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
/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