From: Petr Malat <firstname.lastname@example.org>
To: Pratyush Yadav <email@example.com>
Miquel Raynal <firstname.lastname@example.org>,
Richard Weinberger <email@example.com>,
Vignesh Raghavendra <firstname.lastname@example.org>,
Rob Herring <email@example.com>,
Tudor Ambarus <firstname.lastname@example.org>
Subject: Re: [PATCH] spi-nor: sfdp: Allow configuring unknown flashes using SFDP
Date: Fri, 21 May 2021 13:53:50 +0200 [thread overview]
Message-ID: <20210521115350.GA7908@ntb.petris.klfree.czf> (raw)
On Fri, May 21, 2021 at 03:25:05PM +0530, Pratyush Yadav wrote:
> On 20/05/21 06:07PM, Petr Malat wrote:
> > This change allows adding a support for flashes with correct SFDP
> > without recompilation of the kernel by setting sfdp-compatible property
> > in their node. Alternatively, sfdp_compatible module option can be used
> > to list JEDEC IDs of flashes, whose SFDP can be trusted. Star "*" can
> > be used to match all JEDEC IDs.
> I have skimmed through the patch. Before I look at it more closely, I
> want to understand the use case for this patch. Why would you not want
> to recompile the kernel when adding support for new hardware? Do you
> want the ability to support flashes on devices that have already been
> deployed in the field? Is it something that comes up frequently?
In my case the kernel is loaded from a USB mass storage device, which
can be preproduced and on stock (with the kernel already on it). With
my patch I can change the flash vendor without the need of updating
the image on already existing USB mass storage devices.
The patch is also useful for people who use distribution kernel as they
will not have to wait until (and if) the distribution updates it.
> Then comes the question of how do you get the flash to probe if it is
> not present in device tree? And if you are able to update the device
> tree then you should also be able to update the kernel.
If one sets sfdp-compatible flag in the device tree and replaces one
flash with another, he doesn't need to update the device tree. It
extends what is already possible now - if I make "jedec,spi-nor" node
and the JEDEC ID is known to the driver I can replace the flash with
a different one whose JEDEC ID is known as well and it will work
without touching the device tree.
> Have you tested this with any flash? If so, with which one?
I have tested it with n25q128a11 by removing it from the driver.
> > Signed-off-by: Petr Malat <email@example.com>
> > ---
> > .../devicetree/bindings/mtd/jedec,spi-nor.txt | 3 +
> This file has been converted to yaml since at least 5.12-rc1. Please
> update your kernel sources and rebase your patches.
OK, I will rebase.
Linux MTD discussion mailing list
next prev parent reply other threads:[~2021-05-21 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 16:07 [PATCH] spi-nor: sfdp: Allow configuring unknown flashes using SFDP Petr Malat
2021-05-21 9:55 ` Pratyush Yadav
2021-05-21 11:53 ` Petr Malat [this message]
2021-05-27 13:52 ` Vignesh Raghavendra
2021-05-27 13:54 ` Pratyush Yadav
2021-05-27 15:45 ` Petr Malat
2021-05-28 11:56 ` Vignesh Raghavendra
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.