U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: alice.guo@oss.nxp.com
Cc: u-boot@lists.denx.de, sbabic@denx.de, festevam@gmail.com,
	uboot-imx@nxp.com, marek.vasut+renesas@mailbox.org,
	peng.fan@nxp.com, fedor.ross@ifm.com, ye.li@nxp.com,
	seanga2@gmail.com, Alice Guo <alice.guo@nxp.com>
Subject: Re: [PATCH v1] imx: Kconfig: make IMX8_ROMAPI configurable
Date: Sun, 6 Oct 2024 15:23:32 -0600	[thread overview]
Message-ID: <20241006212332.GQ4737@bill-the-cat> (raw)
In-Reply-To: <20241005233116.2781053-1-alice.guo@oss.nxp.com>

[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]

On Sun, Oct 06, 2024 at 07:31:16AM +0800, alice.guo@oss.nxp.com wrote:

> From: Peng Fan <peng.fan@nxp.com>
> 
> Make CONFIG_IMX8_ROMAPI could be configured in defconfig.
> 
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> Signed-off-by: Alice Guo <alice.guo@nxp.com>
> Reviewed-by: Ye Li <ye.li@nxp.com>
> ---
>  arch/arm/mach-imx/Kconfig | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm/mach-imx/Kconfig b/arch/arm/mach-imx/Kconfig
> index 134e42028c..9d3aafd2f8 100644
> --- a/arch/arm/mach-imx/Kconfig
> +++ b/arch/arm/mach-imx/Kconfig
> @@ -179,7 +179,8 @@ config DDRMC_VF610_CALIBRATION
>  	  the ddrmc_cr_setting on relevant board file.
>  
>  config IMX8_ROMAPI
> -	def_bool y
> +	bool "Enable i.MX ROMAPI"
> +	default y
>  	depends on IMX8MN || IMX8MP || IMX8ULP || IMX9

Since there's no help here, is this truly configurable, or is this
something that should be select'd based on the SoC and presumably some
of the newer IMX9 parts cannot use this?

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2024-10-06 21:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-05 23:31 [PATCH v1] imx: Kconfig: make IMX8_ROMAPI configurable alice.guo
2024-10-06 21:23 ` Tom Rini [this message]
2024-10-06 22:28   ` Marek Vasut
2024-10-06 22:50     ` Tom Rini
2024-10-07 11:46       ` Peng Fan
2024-10-07 14:17         ` Tom Rini
2024-10-08  8:54           ` Peng Fan
2024-10-08 13:41             ` Tom Rini
2024-10-08 15:32               ` Peng Fan
2024-10-07 11:23     ` Peng Fan
2024-10-07 11:32       ` Marek Vasut
2024-10-07 11:48 ` Fabio Estevam

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=20241006212332.GQ4737@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=alice.guo@nxp.com \
    --cc=alice.guo@oss.nxp.com \
    --cc=fedor.ross@ifm.com \
    --cc=festevam@gmail.com \
    --cc=marek.vasut+renesas@mailbox.org \
    --cc=peng.fan@nxp.com \
    --cc=sbabic@denx.de \
    --cc=seanga2@gmail.com \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-imx@nxp.com \
    --cc=ye.li@nxp.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