public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] arm: mvebu: clearfog: support multiple SATA boot
Date: Mon, 23 Mar 2020 11:23:02 +0100	[thread overview]
Message-ID: <8f417dad-4e60-91c6-540d-cdb08703c758@denx.de> (raw)
In-Reply-To: <20200129035945.37765-2-mrjoel@lixil.net>

Added Josua to Cc.

On 29.01.20 04:59, Joel Johnson wrote:
> Enabled distro bootcmd support for additional SATA ports if enabled.
> 
> Signed-off-by: Joel Johnson <mrjoel@lixil.net>
> 
> ---
> 
> 
> This patch builds on and requires the separate patch series adding
> configurable SATA support ("arm: mvebu: clearfog: Add SATA mode flags").
> 
> ---
>   include/configs/clearfog.h | 31 ++++++++++++++++++++++++++++---
>   1 file changed, 28 insertions(+), 3 deletions(-)
> 
> diff --git a/include/configs/clearfog.h b/include/configs/clearfog.h
> index a452f4b009..0bf7e9d950 100644
> --- a/include/configs/clearfog.h
> +++ b/include/configs/clearfog.h
> @@ -111,15 +111,40 @@
>   #endif
>   
>   #ifdef CONFIG_SCSI
> -#define BOOT_TARGET_DEVICES_SCSI(func) func(SCSI, scsi, 0)
> +#define BOOT_TARGET_DEVICES_SCSI_M2SATA(func) func(SCSI, scsi, 0)
> +
> +/*
> + * Either one or both mPCIe slots may be configured as mSATA interfaces. The
> + * SCSI bus ids are assigned based on sequence of hardware present, not always
> + * tied to hardware slot ids. As such, use second SCSI bus if either slot is
> + * set for SATA, and only use third SCSI bus if both slots are SATA enabled.
> + */
> +#if defined (CONFIG_CLEARFOG_CON2_SATA) || defined (CONFIG_CLEARFOG_CON3_SATA)
> +#define BOOT_TARGET_DEVICES_SCSI_CLEARFOG2(func) func(SCSI, scsi, 1)
> +#else
> +#define BOOT_TARGET_DEVICES_SCSI_CLEARFOG2(func)
> +#endif
> +
> +#if defined (CONFIG_CLEARFOG_CON2_SATA) && defined (CONFIG_CLEARFOG_CON3_SATA)
> +#define BOOT_TARGET_DEVICES_SCSI_CLEARFOG3(func) func(SCSI, scsi, 2)
>   #else
> -#define BOOT_TARGET_DEVICES_SCSI(func)
> +#define BOOT_TARGET_DEVICES_SCSI_CLEARFOG3(func)
>   #endif
>   
> +#else
> +#define BOOT_TARGET_DEVICES_SCSI_M2SATA(func)
> +#endif /* CONFIG_SCSI */
> +
> +/*
> + * The SCSI buses are attempted in increasing bus order, there is no current
> + * mechanism to alter the default bus priority order for booting.
> + */
>   #define BOOT_TARGET_DEVICES(func) \
>   	BOOT_TARGET_DEVICES_MMC(func) \
>   	BOOT_TARGET_DEVICES_USB(func) \
> -	BOOT_TARGET_DEVICES_SCSI(func) \
> +	BOOT_TARGET_DEVICES_SCSI_M2SATA(func) \
> +	BOOT_TARGET_DEVICES_SCSI_CLEARFOG2(func) \
> +	BOOT_TARGET_DEVICES_SCSI_CLEARFOG3(func) \
>   	func(PXE, pxe, na) \
>   	func(DHCP, dhcp, na)
>   
> 

Josua, Baruch, any comments from you on this one?

Thanks,
Stefan

  reply	other threads:[~2020-03-23 10:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29  3:59 [PATCH 1/2] arm: mvebu: clearfog: add SCSI to distro bootcmd Joel Johnson
2020-01-29  3:59 ` [PATCH 2/2] arm: mvebu: clearfog: support multiple SATA boot Joel Johnson
2020-03-23 10:23   ` Stefan Roese [this message]
2020-03-22 18:53 ` [PATCH 1/2] arm: mvebu: clearfog: add SCSI to distro bootcmd Joel Johnson
2020-03-23 10:27   ` Stefan Roese
2020-03-23 15:38     ` Joel Johnson
2020-03-23 10:20 ` Stefan Roese
2020-04-16  4:09   ` Joel Johnson
2020-04-16  6:13     ` Stefan Roese
2020-04-17  7:08       ` Joel Johnson

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=8f417dad-4e60-91c6-540d-cdb08703c758@denx.de \
    --to=sr@denx.de \
    --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