From: "Milan P. Stanić" <mps@arvanta.net>
To: Shengyu Qu <wiagn233@outlook.com>
Cc: xypron.glpk@gmx.de, chanho61.park@samsung.com,
ycliang@andestech.com, yanhong.wang@starfivetech.com,
u-boot@lists.denx.de
Subject: Re: [PATCH v1 2/2] doc: board: starfive: Add more info about supported driver
Date: Wed, 23 Aug 2023 22:39:09 +0200 [thread overview]
Message-ID: <20230823203909.GB21828@m1> (raw)
In-Reply-To: <TY3P286MB26115DF6D963C38835BCBE30981FA@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM>
On Tue, 2023-08-22 at 22:33, Shengyu Qu wrote:
> Since PLDA PCIE driver is added and VL805 support is enabled in
> defconfig for Starfive Visionfive 2, modify the document to keep
> consistent.
>
> Signed-off-by: Shengyu Qu <wiagn233@outlook.com>
Tested-by: Milan P. Stanić <mps@arvanta.net>
> ---
> doc/board/starfive/visionfive2.rst | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/doc/board/starfive/visionfive2.rst b/doc/board/starfive/visionfive2.rst
> index 941899a0a4..460f23aec3 100644
> --- a/doc/board/starfive/visionfive2.rst
> +++ b/doc/board/starfive/visionfive2.rst
> @@ -20,6 +20,8 @@ The support for following drivers are already enabled:
> 3. StarFive JH7110 reset Driver.
> 4. Cadence QSPI controller Driver.
> 5. MMC SPI Driver for MMC/SD support.
> +6. PLDA PCIE controller driver.
> +7. On-board VL805 PCIE-USB controller driver.
>
> Booting from MMC using U-Boot SPL
> ---------------------------------
> --
> 2.42.0
>
next prev parent reply other threads:[~2023-08-23 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230822143357.2818-1-wiagn233@outlook.com>
2023-08-22 14:33 ` [PATCH v1 1/2] configs: starfive: Enable PCIE auto enum and NVME/USB stuff for Starfive Visionfive 2 Shengyu Qu
2023-08-23 20:38 ` Milan P. Stanić
2023-09-05 5:58 ` Dennis Gilmore
2023-08-22 14:33 ` [PATCH v1 2/2] doc: board: starfive: Add more info about supported driver Shengyu Qu
2023-08-23 20:39 ` Milan P. Stanić [this message]
2023-09-05 5:58 ` Dennis Gilmore
2023-09-05 6:46 ` Heinrich Schuchardt
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=20230823203909.GB21828@m1 \
--to=mps@arvanta.net \
--cc=chanho61.park@samsung.com \
--cc=u-boot@lists.denx.de \
--cc=wiagn233@outlook.com \
--cc=xypron.glpk@gmx.de \
--cc=yanhong.wang@starfivetech.com \
--cc=ycliang@andestech.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