From: Christian Marangi <ansuelsmth@gmail.com>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: Michael Walle <mwalle@kernel.org>,
Pratyush Yadav <pratyush@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
David Bauer <mail@david-bauer.net>
Subject: Re: [PATCH v2] mtd: spi-nor: Add support for BoHong bh25q128as
Date: Tue, 27 Feb 2024 10:33:19 +0100 [thread overview]
Message-ID: <65ddac61.5d0a0220.a0c6e.35bf@mx.google.com> (raw)
In-Reply-To: <4d117770-6e0c-412f-ac1a-d9ba84b5b4ba@linaro.org>
On Mon, Feb 26, 2024 at 10:53:34AM +0200, Tudor Ambarus wrote:
>
>
> On 26.02.2024 10:51, Michael Walle wrote:
> > Hi,
> >
> > On Sat Feb 24, 2024 at 12:18 PM CET, Christian Marangi wrote:
> >> The user just tested this and It seems there is a problem in JEDEC id?
> >>
> >> [ 0.726451] spi spi0.0: setup: ignoring unsupported mode bits a00
> >
> > What SPI controller is used in this case?
> >
> >> [ 0.732850] spi-nor spi0.0: unrecognized JEDEC id bytes: 68 40 18 68 40 18
> >> [ 0.739725] spi-nor: probe of spi0.0 failed with error -2
> >
> > And what kernel version is this? This should only happen if the SFDP
> > header is wrong, but according to your dump, it is correct.
> >
>
> I assume the test was done on an older kernel, where the identification
> of the flash based on SFDP is not yet available.
The test has been done on 5.15 and 6.1. The support for this was
introduced later? Can you point me to the commits so I can backport
them?
--
Ansuel
next prev parent reply other threads:[~2024-02-27 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 20:03 [PATCH v2] mtd: spi-nor: Add support for BoHong bh25q128as Christian Marangi
2024-02-20 20:15 ` Michael Walle
2024-02-22 9:19 ` Tudor Ambarus
2024-02-24 11:18 ` Christian Marangi
2024-02-26 8:51 ` Michael Walle
2024-02-26 8:53 ` Tudor Ambarus
2024-02-27 9:33 ` Christian Marangi [this message]
2024-02-27 10:08 ` Tudor Ambarus
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=65ddac61.5d0a0220.a0c6e.35bf@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mail@david-bauer.net \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=tudor.ambarus@linaro.org \
--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