All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <p.yadav@ti.com>
To: Marek Vasut <marex@denx.de>
Cc: <u-boot@lists.denx.de>, Jagan Teki <jagan@amarulasolutions.com>,
	Vignesh R <vigneshr@ti.com>
Subject: Re: [PATCH] mtd: sf: Set SF parameters as env variables
Date: Fri, 24 Sep 2021 00:23:18 +0530	[thread overview]
Message-ID: <20210923185316.se55powofpm37mg3@ti.com> (raw)
In-Reply-To: <20210914032849.273625-1-marex@denx.de>

On 14/09/21 05:28AM, Marek Vasut wrote:
> Set the SF page size, erase block size and total size as an environment
> variable after "sf probe". This lets us discern boards with multiple
> distinct SPI flash options and also e.g. set mtdparts accordingly.

I don't quite follow the rationale for making these environment 
variables. Wouldn't you be better off finding this info out via mtd or 
sf command?

> 
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Jagan Teki <jagan@amarulasolutions.com>
> Cc: Vignesh R <vigneshr@ti.com>
> ---
>  drivers/mtd/spi/spi-nor-core.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/mtd/spi/spi-nor-core.c b/drivers/mtd/spi/spi-nor-core.c
> index d5d905fa5a1..448653b9931 100644
> --- a/drivers/mtd/spi/spi-nor-core.c
> +++ b/drivers/mtd/spi/spi-nor-core.c
> @@ -15,6 +15,7 @@
>  #include <dm.h>
>  #include <dm/device_compat.h>
>  #include <dm/devres.h>
> +#include <env.h>
>  #include <linux/bitops.h>
>  #include <linux/err.h>
>  #include <linux/errno.h>
> @@ -3829,8 +3830,11 @@ int spi_nor_scan(struct spi_nor *nor)
>  #ifndef CONFIG_SPL_BUILD
>  	printf("SF: Detected %s with page size ", nor->name);
>  	print_size(nor->page_size, ", erase size ");
> +	env_set_hex("sf_pagesize", nor->page_size);
>  	print_size(nor->erase_size, ", total ");
> +	env_set_hex("sf_erasesize", nor->erase_size);
>  	print_size(nor->size, "");
> +	env_set_hex("sf_size", nor->size);
>  	puts("\n");
>  #endif
>  
> -- 
> 2.33.0
> 

-- 
Regards,
Pratyush Yadav
Texas Instruments Inc.

  reply	other threads:[~2021-09-23 18:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14  3:28 [PATCH] mtd: sf: Set SF parameters as env variables Marek Vasut
2021-09-23 18:53 ` Pratyush Yadav [this message]
2021-09-23 20:00   ` Marek Vasut
2021-10-07 12:40     ` Pratyush Yadav
2021-10-07 12:46       ` Marek Vasut
2021-11-28 21:56         ` Marek Vasut
2021-12-02  9:14           ` Pratyush Yadav
2021-12-02 16:41       ` Sean Anderson
2021-12-02  5:47 ` Jagan Teki
2021-12-02  5:49   ` Marek Vasut
2021-12-02  5:57     ` Jagan Teki
2021-12-02  6:03       ` Marek Vasut

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=20210923185316.se55powofpm37mg3@ti.com \
    --to=p.yadav@ti.com \
    --cc=jagan@amarulasolutions.com \
    --cc=marex@denx.de \
    --cc=u-boot@lists.denx.de \
    --cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.