From: "Marek Behún" <marek.behun@nic.cz>
To: Patrick Delaunay <patrick.delaunay@foss.st.com>,
Marek Vasut <marex@denx.de>, Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, "Pali Rohár" <pali@kernel.org>,
"Jagan Teki" <jagan@amarulasolutions.com>,
"Christophe KERELLO" <christophe.kerello@foss.st.com>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Priyanka Jain" <priyanka.jain@nxp.com>,
"Patrice Chotard" <patrice.chotard@foss.st.com>,
"Heiko Schocher" <hs@denx.de>, "Simon Glass" <sjg@chromium.org>,
"Vignesh R" <vigneshr@ti.com>,
"U-Boot STM32" <uboot-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH v4 0/2] mtd: spi: nor: force mtd name to "nor%d"
Date: Wed, 22 Sep 2021 19:29:25 +0200 [thread overview]
Message-ID: <20210922192925.723abcba@thinkpad> (raw)
In-Reply-To: <20210922162909.1857566-1-patrick.delaunay@foss.st.com>
(Adding also Tom.)
Hi Patrick, Marek,
I find this either not complete or not needed:
- either you need mtd names to be of this format so that old MTDPARTS
config definitions do not need to be changed, i.e. something like
CONFIG_MTDPARTS_DEFAULT="nor0:1M(u-boot),0x1000@0xfff000(env)"
does not work currently, and you want to make it work.
I find your solution here incomplete because MTDPARTS can also be
used to be passed to Linux as mtdparts parameter, but there is no
guarantee that the "norN" numbering you are creating in U-Boot will
be the same as the one in kernel.
- or it is not needed, because you can remove MTDPARTS definition from
the board config entirely and move the information into device tree.
In fact this was the main idea behind making the series
Support SPI NORs and OF partitions in `mtd list`
The SPI-NOR MTDs after this series can have conflicting names,
because you can still choose between them via OF path with the `mtd`
command.
Tom and I were of the opinion that MTDPARTS should be deprecated and
removed in favor of OF. Marek Vasut says that this is not possible
for every board, and so needs to stay.
BTW, I find it a little weird for Marek to defend old API which should
be converted to DT, when in discussion about DM USB / Nokia N900
USB TTY console [1] he was defending the opinion that we should be
heading to DT in U-Boot.
[1]
https://patchwork.ozlabs.org/project/uboot/patch/20210618145724.2558-1-pali@kernel.org/
On Wed, 22 Sep 2021 18:29:06 +0200
Patrick Delaunay <patrick.delaunay@foss.st.com> wrote:
> This serie is a V4 for [1].
>
> Now the SPI nor are named "norN" with N after the CFI nor device:
> "nor0" to "norM" => N= M+1.
>
> See also an other proposal from Marek (not working after test)
> "mtd: spi-nor: Fix SF MTDIDS when registering multiple MTDs with
> DM enabled"
>
> http://patchwork.ozlabs.org/project/uboot/list/?series=262362
>
> The first patch of the serie fixed the compilation issues around
> 'cfi_flash_num_flash_banks' found in CI:
>
> https://source.denx.de/u-boot/custodians/u-boot-stm/-/pipelines/9138
>
> [1] Series: mtd: spi: nor: force mtd name to "nor%d"
> http://patchwork.ozlabs.org/project/uboot/list/?series=262632&state=*
> http://patchwork.ozlabs.org/project/uboot/list/?series=262017&state=*
> http://patchwork.ozlabs.org/project/uboot/list/?series=262013&state=*
>
> Patrick
>
>
> Changes in v4:
> - introduce macro MTD_NAME_SIZE for mtd_name size and use MTD_DEV_TYPE
> to retrieved the "nor" string.
>
> Changes in v3:
> - NEW: solve compilation issue when CONFIG_SYS_MAX_FLASH_BANKS is used
> - start index after the last CFI device, use CONFIG_SYS_MAX_FLASH_BANKS
>
> Changes in v2:
> - correct commit message
>
> Patrick Delaunay (2):
> mtd: cfi_flash: use cfi_flash_num_flash_banks only when supported
> mtd: spi: nor: force mtd name to "nor%d"
>
> drivers/mtd/spi/spi-nor-core.c | 17 ++++++++++++++---
> include/dm/device.h | 3 ++-
> include/linux/mtd/spi-nor.h | 2 ++
> include/mtd.h | 4 ++++
> include/mtd/cfi_flash.h | 8 +++++++-
> 5 files changed, 29 insertions(+), 5 deletions(-)
>
next prev parent reply other threads:[~2021-09-22 17:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 16:29 [PATCH v4 0/2] mtd: spi: nor: force mtd name to "nor%d" Patrick Delaunay
2021-09-22 16:29 ` [PATCH v4 1/2] mtd: cfi_flash: use cfi_flash_num_flash_banks only when supported Patrick Delaunay
2021-09-28 18:45 ` Tom Rini
2021-09-22 16:29 ` [PATCH v4 2/2] mtd: spi: nor: force mtd name to "nor%d" Patrick Delaunay
2021-09-28 18:45 ` Tom Rini
2021-09-22 17:29 ` Marek Behún [this message]
2021-09-22 18:24 ` [PATCH v4 0/2] " Marek Vasut
2021-09-22 18:42 ` Tom Rini
2021-09-22 19:08 ` Marek Behún
2021-09-22 19:12 ` Marek Vasut
2021-09-22 19:05 ` Marek Behún
2021-09-22 19:23 ` Tom Rini
2021-09-22 19:39 ` Marek Vasut
2021-09-22 19:24 ` Marek Vasut
2021-09-22 19:41 ` Tom Rini
2021-09-22 19:42 ` Tom Rini
2021-09-22 19:46 ` Tom Rini
2021-09-22 19:56 ` Marek Vasut
2021-09-22 20:00 ` Tom Rini
2021-09-23 1:32 ` Marek Vasut
2021-09-23 9:04 ` Patrick DELAUNAY
2021-09-24 18:22 ` Tom Rini
2021-09-24 19:25 ` Marek Behún
2021-09-24 20:09 ` Marek Vasut
2021-09-25 0:12 ` Marek Behún
2021-09-25 3:06 ` 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=20210922192925.723abcba@thinkpad \
--to=marek.behun@nic.cz \
--cc=christophe.kerello@foss.st.com \
--cc=hs@denx.de \
--cc=jagan@amarulasolutions.com \
--cc=marex@denx.de \
--cc=miquel.raynal@bootlin.com \
--cc=pali@kernel.org \
--cc=patrice.chotard@foss.st.com \
--cc=patrick.delaunay@foss.st.com \
--cc=priyanka.jain@nxp.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-stm32@st-md-mailman.stormreply.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox