public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Kurt Miller <kurt@intricatesoftware.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 2/2] rockchip: Enable PCIe and NVMe on ROCKPro64
Date: Thu, 28 May 2020 14:42:12 -0400	[thread overview]
Message-ID: <1590691332.9708.27.camel@intricatesoftware.com> (raw)
In-Reply-To: <20200525090057.6076-2-kettenis@openbsd.org>

On Mon, 2020-05-25 at 11:00 +0200, Mark Kettenis wrote:
> Enable CONFIG_PCI and CONFIG_NVME and related configs for the
> ROCKPro64 board.
> 
> Signed-off-by: Mark Kettenis <kettenis@openbsd.org>

Tested by: Kurt Miller <kurt@intricatesoftware.com>

Model: Pine64 RockPro64 v2.1

=> pci
Scanning PCI devices on bus 0
BusDevFun??VendorId???DeviceId???Device Class???????Sub-Class
_____________________________________________________________
00.00.00???0x1d87?????0x0100?????Bridge device???????????0x04
=> pci 1
Scanning PCI devices on bus 1
BusDevFun??VendorId???DeviceId???Device Class???????Sub-Class
_____________________________________________________________
01.00.00???0x1b4b?????0x9128?????Mass storage controller 0x06

> ---
> Changes in v2:
> - Extend commit message
> 
> ?configs/rockpro64-rk3399_defconfig | 4 ++++
> ?1 file changed, 4 insertions(+)
> 
> diff --git a/configs/rockpro64-rk3399_defconfig b/configs/rockpro64-rk3399_defconfig
> index 95037a191d..b472167283 100644
> --- a/configs/rockpro64-rk3399_defconfig
> +++ b/configs/rockpro64-rk3399_defconfig
> @@ -19,6 +19,7 @@ CONFIG_CMD_BOOTZ=y
> ?CONFIG_CMD_GPT=y
> ?CONFIG_CMD_MMC=y
> ?CONFIG_CMD_USB=y
> +CONFIG_CMD_PCI=y
> ?# CONFIG_CMD_SETEXPR is not set
> ?CONFIG_CMD_TIME=y
> ?CONFIG_SPL_OF_CONTROL=y
> @@ -38,10 +39,13 @@ CONFIG_SPI_FLASH_GIGADEVICE=y
> ?CONFIG_DM_ETH=y
> ?CONFIG_ETH_DESIGNWARE=y
> ?CONFIG_GMAC_ROCKCHIP=y
> +CONFIG_NVME=y
> +CONFIG_PCI=y
> ?CONFIG_PMIC_RK8XX=y
> ?CONFIG_REGULATOR_PWM=y
> ?CONFIG_REGULATOR_RK8XX=y
> ?CONFIG_PWM_ROCKCHIP=y
> +CONFIG_DM_RESET=y
> ?CONFIG_RAM_RK3399_LPDDR4=y
> ?CONFIG_BAUDRATE=115200
> ?CONFIG_DEBUG_UART_SHIFT=2

  reply	other threads:[~2020-05-28 18:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  9:00 [PATCH v2 1/2] rockchip: Enable PCIe/M.2 and NVMe on Firefly RK3399 Mark Kettenis
2020-05-25  9:00 ` [PATCH v2 2/2] rockchip: Enable PCIe and NVMe on ROCKPro64 Mark Kettenis
2020-05-28 18:42   ` Kurt Miller [this message]
2020-06-01  1:01   ` Kever Yang
2020-06-01  1:01 ` [PATCH v2 1/2] rockchip: Enable PCIe/M.2 and NVMe on Firefly RK3399 Kever Yang
2020-06-01  1:15 ` Kever Yang
2020-06-07 12:06   ` Mark Kettenis

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=1590691332.9708.27.camel@intricatesoftware.com \
    --to=kurt@intricatesoftware.com \
    --cc=u-boot@lists.denx.de \
    /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