From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] spl: fix SPI config dependencies
Date: Sat, 26 Oct 2019 00:01:43 +0200 [thread overview]
Message-ID: <20191026000143.7809dd1d@jawa> (raw)
In-Reply-To: <20191025142209.3838-1-simon.k.r.goldschmidt@gmail.com>
On Fri, 25 Oct 2019 16:22:09 +0200
Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com> wrote:
> As SPL_SPI_FLASH_SUPPORT cannot work without SPL_SPI_SUPPORT, fix
> dependencies to prevent enabling SPI flash support without basic SPI
> support.
>
> Signed-off-by: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
> ---
>
> Changes in v2:
> - move SYS_SPI_U_BOOT_OFFS out of the SPL_SPI_FLASH_SUPPORT guard
> since that broke sunxi SPL (which uses non-DM spi)
>
> common/spl/Kconfig | 21 +++++++++++----------
> 1 file changed, 11 insertions(+), 10 deletions(-)
>
> diff --git a/common/spl/Kconfig b/common/spl/Kconfig
> index 86d7edfee1..b8d234eb5e 100644
> --- a/common/spl/Kconfig
> +++ b/common/spl/Kconfig
> @@ -1014,8 +1014,19 @@ config SPL_SERIAL_SUPPORT
> unless there are space reasons not to. Even then, consider
> enabling SPL_USE_TINY_PRINTF which is a small printf()
> version.
> +config SPL_SPI_SUPPORT
> + bool "Support SPI drivers"
> + help
> + Enable support for using SPI in SPL. This is used for
> connecting
> + to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT
> for
> + more details on that. The SPI driver provides the
> transport for
> + data between the SPI flash and the CPU. This option can be
> used to
> + enable SPI drivers that are needed for other purposes
> also, such
> + as a SPI PMIC.
> +
> config SPL_SPI_FLASH_SUPPORT
> bool "Support SPI flash drivers"
> + depends on SPL_SPI_SUPPORT
> help
> Enable support for using SPI flash in SPL, and loading
> U-Boot from SPI flash. SPI flash (Serial Peripheral Bus flash) is
> named after @@ -1060,16 +1071,6 @@ config SYS_SPI_U_BOOT_OFFS
> Address within SPI-Flash from where the u-boot payload is
> fetched from.
>
> -config SPL_SPI_SUPPORT
> - bool "Support SPI drivers"
> - help
> - Enable support for using SPI in SPL. This is used for
> connecting
> - to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT
> for
> - more details on that. The SPI driver provides the
> transport for
> - data between the SPI flash and the CPU. This option can be
> used to
> - enable SPI drivers that are needed for other purposes
> also, such
> - as a SPI PMIC.
> -
> config SPL_THERMAL
> bool "Driver support for thermal devices"
> help
Reviewed-by: Lukasz Majewski <lukma@denx.de>
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191026/626cd001/attachment.sig>
next prev parent reply other threads:[~2019-10-25 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 14:22 [U-Boot] [PATCH v2] spl: fix SPI config dependencies Simon Goldschmidt
2019-10-25 22:01 ` Lukasz Majewski [this message]
2019-11-08 15:32 ` Tom Rini
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=20191026000143.7809dd1d@jawa \
--to=lukma@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