From: Heiko Stuebner <heiko@sntech.de>
To: "Matwey V. Kornilov" <matwey@sai.msu.ru>
Cc: Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:ARM/Rockchip SoC support"
<linux-rockchip@lists.infradead.org>,
Rob Herring <robh+dt@kernel.org>,
Akash Gajjar <akash@openedev.com>,
matwey.kornilov@gmail.com,
Ezequiel Garcia <ezequiel@collabora.com>,
"moderated list:ARM/Rockchip SoC support"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] arm64: dts: rockchip: Enable PCIe for Radxa Rock Pi 4 board
Date: Mon, 18 Nov 2019 01:46:36 +0100 [thread overview]
Message-ID: <1784520.t1z2W423De@phil> (raw)
In-Reply-To: <20191117101545.6406-1-matwey@sai.msu.ru>
Hi Matwey,
Am Sonntag, 17. November 2019, 11:15:37 CET schrieb Matwey V. Kornilov:
> Radxa Rock Pi 4 is equipped with M.2 PCIe slot,
> so enable PCIe for the board.
>
> The changes has been tested with Intel SSD 660p series device.
>
> 01:00.0 Class 0108: Device 8086:f1a8 (rev 03)
>
> Signed-off-by: Matwey V. Kornilov <matwey@sai.msu.ru>
applied the patch, but you could do a follow-up that mimics
https://lore.kernel.org/linux-arm-kernel/20191117140728.917-1-linux.amoon@gmail.com/
aka find out from the schematics where the 0.9 and 1.8 supplies come from.
Thanks
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: "Matwey V. Kornilov" <matwey@sai.msu.ru>
Cc: Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:ARM/Rockchip SoC support"
<linux-rockchip@lists.infradead.org>,
Rob Herring <robh+dt@kernel.org>,
Akash Gajjar <akash@openedev.com>,
matwey.kornilov@gmail.com,
Ezequiel Garcia <ezequiel@collabora.com>,
"moderated list:ARM/Rockchip SoC support"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] arm64: dts: rockchip: Enable PCIe for Radxa Rock Pi 4 board
Date: Mon, 18 Nov 2019 01:46:36 +0100 [thread overview]
Message-ID: <1784520.t1z2W423De@phil> (raw)
In-Reply-To: <20191117101545.6406-1-matwey@sai.msu.ru>
Hi Matwey,
Am Sonntag, 17. November 2019, 11:15:37 CET schrieb Matwey V. Kornilov:
> Radxa Rock Pi 4 is equipped with M.2 PCIe slot,
> so enable PCIe for the board.
>
> The changes has been tested with Intel SSD 660p series device.
>
> 01:00.0 Class 0108: Device 8086:f1a8 (rev 03)
>
> Signed-off-by: Matwey V. Kornilov <matwey@sai.msu.ru>
applied the patch, but you could do a follow-up that mimics
https://lore.kernel.org/linux-arm-kernel/20191117140728.917-1-linux.amoon@gmail.com/
aka find out from the schematics where the 0.9 and 1.8 supplies come from.
Thanks
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: "Matwey V. Kornilov" <matwey@sai.msu.ru>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Ezequiel Garcia <ezequiel@collabora.com>,
Akash Gajjar <akash@openedev.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:ARM/Rockchip SoC support"
<linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Rockchip SoC support"
<linux-rockchip@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
matwey.kornilov@gmail.com
Subject: Re: [PATCH v2] arm64: dts: rockchip: Enable PCIe for Radxa Rock Pi 4 board
Date: Mon, 18 Nov 2019 01:46:36 +0100 [thread overview]
Message-ID: <1784520.t1z2W423De@phil> (raw)
In-Reply-To: <20191117101545.6406-1-matwey@sai.msu.ru>
Hi Matwey,
Am Sonntag, 17. November 2019, 11:15:37 CET schrieb Matwey V. Kornilov:
> Radxa Rock Pi 4 is equipped with M.2 PCIe slot,
> so enable PCIe for the board.
>
> The changes has been tested with Intel SSD 660p series device.
>
> 01:00.0 Class 0108: Device 8086:f1a8 (rev 03)
>
> Signed-off-by: Matwey V. Kornilov <matwey@sai.msu.ru>
applied the patch, but you could do a follow-up that mimics
https://lore.kernel.org/linux-arm-kernel/20191117140728.917-1-linux.amoon@gmail.com/
aka find out from the schematics where the 0.9 and 1.8 supplies come from.
Thanks
Heiko
next prev parent reply other threads:[~2019-11-18 0:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 10:15 [PATCH v2] arm64: dts: rockchip: Enable PCIe for Radxa Rock Pi 4 board Matwey V. Kornilov
2019-11-17 10:15 ` Matwey V. Kornilov
2019-11-17 10:15 ` Matwey V. Kornilov
2019-11-18 0:46 ` Heiko Stuebner [this message]
2019-11-18 0:46 ` Heiko Stuebner
2019-11-18 0:46 ` Heiko Stuebner
2019-11-18 18:40 ` Matwey V. Kornilov
2019-11-18 18:40 ` Matwey V. Kornilov
2019-11-19 0:44 ` Tom Cubie
2019-11-19 0:44 ` Tom Cubie
[not found] ` <CAFjve-AT6c-yweF0mOPea-caG3n43nZzVPcwef-qp+n35JN9ig-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-11-20 16:12 ` [PATCH] arm64: dts: rockchip: Add regulators for " Matwey V. Kornilov
2019-11-20 16:12 ` Matwey V. Kornilov
2019-11-20 16:12 ` Matwey V. Kornilov
2019-12-13 10:08 ` Heiko Stuebner
2019-12-13 10:08 ` Heiko Stuebner
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=1784520.t1z2W423De@phil \
--to=heiko@sntech.de \
--cc=akash@openedev.com \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matwey.kornilov@gmail.com \
--cc=matwey@sai.msu.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.