From: Kever Yang <kever.yang@rock-chips.com>
To: Vagrant Cascadian <vagrant@debian.org>, u-boot@lists.denx.de
Cc: Alex Bee <knaerzche@gmail.com>,
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH 1/2] rockchip: Enable SCSI in distro bootcmd for rk3399.
Date: Sat, 9 Apr 2022 10:30:11 +0800 [thread overview]
Message-ID: <bb569090-ea2e-844d-aa92-c341be8a1c80@rock-chips.com> (raw)
In-Reply-To: <20220406204204.60328-2-vagrant@debian.org>
On 2022/4/7 04:42, Vagrant Cascadian wrote:
> Include SCSI in the list of boot targets if CONFIG_CMD_SCSI is
> enabled.
>
> Signed-off-by: Vagrant Cascadian <vagrant@debian.org>
Reviewed-by: Kever Yang <kever.yang@rock-chips.com>
Thanks,
- Kever
> ---
>
> include/configs/rockchip-common.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/include/configs/rockchip-common.h b/include/configs/rockchip-common.h
> index ba7061a287..0c08776ae2 100644
> --- a/include/configs/rockchip-common.h
> +++ b/include/configs/rockchip-common.h
> @@ -29,6 +29,12 @@
> #define BOOT_TARGET_NVME(func)
> #endif
>
> +#if CONFIG_IS_ENABLED(CMD_SCSI)
> + #define BOOT_TARGET_SCSI(func) func(SCSI, scsi, 0)
> +#else
> + #define BOOT_TARGET_SCSI(func)
> +#endif
> +
> #if CONFIG_IS_ENABLED(CMD_USB)
> #define BOOT_TARGET_USB(func) func(USB, usb, 0)
> #else
> @@ -57,6 +63,7 @@
> #define BOOT_TARGET_DEVICES(func) \
> BOOT_TARGET_MMC(func) \
> BOOT_TARGET_NVME(func) \
> + BOOT_TARGET_SCSI(func) \
> BOOT_TARGET_USB(func) \
> BOOT_TARGET_PXE(func) \
> BOOT_TARGET_DHCP(func) \
next prev parent reply other threads:[~2022-04-09 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 20:42 [PATCH 0/2] Enable booting from SCSI on rockpro64-rk3399 Vagrant Cascadian
2022-04-06 20:42 ` [PATCH 1/2] rockchip: Enable SCSI in distro bootcmd for rk3399 Vagrant Cascadian
2022-04-09 2:30 ` Kever Yang [this message]
2022-04-06 20:42 ` [PATCH 2/2] rockchip: Enable AHCI/SCSI/SATA on rockpro64-rk3399 Vagrant Cascadian
2022-04-09 2:30 ` Kever Yang
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=bb569090-ea2e-844d-aa92-c341be8a1c80@rock-chips.com \
--to=kever.yang@rock-chips.com \
--cc=knaerzche@gmail.com \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=vagrant@debian.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