From: Neil Armstrong <narmstrong@baylibre.com>
To: khilman@baylibre.com
Cc: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] arm64: dts: meson-axg-s400: enable PCIe
Date: Fri, 20 Nov 2020 16:33:18 +0100 [thread overview]
Message-ID: <0b5405d7-4df3-c82b-8d73-a591fd343ba1@baylibre.com> (raw)
In-Reply-To: <20201007100631.192348-1-narmstrong@baylibre.com>
On 07/10/2020 12:06, Neil Armstrong wrote:
> This adds the nodes for the :
> - AXG PCIe PHY, using the shared analog PCIe/MIPI DSI PHY
> - 2x AXG PCIe controllers
>
> And enables the PCIe M.2 Key E slots on the S400 board.
>
> Dependencies:
> - Patch 1: Analog PCIe/MIPI DSI PHY update [1] MIPI-DSI nodes [2]
> - Patch 2: None
>
> [1] https://lkml.kernel.org/r/20200915130339.11079-1-narmstrong@baylibre.com
> [2] https://lkml.kernel.org/r/20200907083300.14412-3-narmstrong@baylibre.com
>
> Neil Armstrong (2):
> arm64: dts: meson-axg: add PCIe nodes
> arm64: dts: meson-axg-s400: enable PCIe M.2 Key E slots
>
> .../arm64/boot/dts/amlogic/meson-axg-s400.dts | 10 +++
> arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 61 +++++++++++++++++++
> 2 files changed, 71 insertions(+)
>
Was depending on USB DT patches, resent with USb DT patches in 20201120153229.3920123-1-narmstrong@baylibre.com
Neil
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2020-11-20 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 10:06 Neil Armstrong
2020-10-07 10:06 ` [PATCH 1/2] arm64: dts: meson-axg: add PCIe nodes Neil Armstrong
2020-10-07 10:06 ` [PATCH 2/2] arm64: dts: meson-axg-s400: enable PCIe M.2 Key E slots Neil Armstrong
2020-11-20 15:33 ` Neil Armstrong [this message]
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=0b5405d7-4df3-c82b-8d73-a591fd343ba1@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®