All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Michael Walle <mwalle@kernel.org>
Cc: Pratyush Yadav <pratyush@kernel.org>,
	 Takahiro Kuwano <takahiro.kuwano@infineon.com>,
	 Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	 Tudor Ambarus <tudor.ambarus@linaro.org>,
	 linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] mtd: spi-nor: Rework flash parameter initialization
Date: Thu, 02 Jul 2026 17:17:55 +0200	[thread overview]
Message-ID: <87jyrdpgik.fsf@bootlin.com> (raw)
In-Reply-To: <20260601125438.3481722-1-mwalle@kernel.org> (Michael Walle's message of "Mon, 1 Jun 2026 14:52:42 +0200")

Hello,

> This might have the consequence that all the flashes now get a
> RDSFPD opcode which might be an unknown opcode. But that was already
> the case for any flashes which were unknown to the linux kernel. So
> far, there was not a single complaint.
>
> See patch 3 for more information. If feedback is positive, this is
> intended to be applied to the spi-nor tree after the next merge
> window, so it will sit around in -next for quite some time and get
> some testing.

Tested-by: Miquel Raynal <miquel.raynal@bootlin.com>

Tested with a Winbond W25Q02JVFIM.

If you can also give a try to my QER rework I would be interested to
gather feedback on it and ideally also try to merge this kind of rework
early in the cycle. ;)

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Michael Walle <mwalle@kernel.org>
Cc: Pratyush Yadav <pratyush@kernel.org>,
	 Takahiro Kuwano <takahiro.kuwano@infineon.com>,
	 Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	 Tudor Ambarus <tudor.ambarus@linaro.org>,
	 linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] mtd: spi-nor: Rework flash parameter initialization
Date: Thu, 02 Jul 2026 17:17:55 +0200	[thread overview]
Message-ID: <87jyrdpgik.fsf@bootlin.com> (raw)
In-Reply-To: <20260601125438.3481722-1-mwalle@kernel.org> (Michael Walle's message of "Mon, 1 Jun 2026 14:52:42 +0200")

Hello,

> This might have the consequence that all the flashes now get a
> RDSFPD opcode which might be an unknown opcode. But that was already
> the case for any flashes which were unknown to the linux kernel. So
> far, there was not a single complaint.
>
> See patch 3 for more information. If feedback is positive, this is
> intended to be applied to the spi-nor tree after the next merge
> window, so it will sit around in -next for quite some time and get
> some testing.

Tested-by: Miquel Raynal <miquel.raynal@bootlin.com>

Tested with a Winbond W25Q02JVFIM.

If you can also give a try to my QER rework I would be interested to
gather feedback on it and ideally also try to merge this kind of rework
early in the cycle. ;)

Thanks,
Miquèl

  parent reply	other threads:[~2026-07-02 15:18 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01 12:52 [RFC PATCH 0/3] mtd: spi-nor: Rework flash parameter initialization Michael Walle
2026-06-01 12:52 ` Michael Walle
2026-06-01 12:52 ` [RFC PATCH 1/3] mtd: spi-nor: spansion: s25fl256s0: remove SKIP_SFDP flag Michael Walle
2026-06-01 12:52   ` Michael Walle
2026-06-02  9:57   ` Miquel Raynal
2026-06-02  9:57     ` Miquel Raynal
2026-06-02 11:01     ` Michael Walle
2026-06-02 11:01       ` Michael Walle
2026-06-05  8:05   ` Takahiro.Kuwano
2026-06-05  8:05     ` Takahiro.Kuwano
2026-06-05 13:05   ` Tudor Ambarus
2026-06-05 13:05     ` Tudor Ambarus
2026-06-01 12:52 ` [RFC PATCH 2/3] mtd: spi-nor: don't clear the SNOR_F_4B_OPCODES flag on failure Michael Walle
2026-06-01 12:52   ` Michael Walle
2026-06-02  9:58   ` Miquel Raynal
2026-06-02  9:58     ` Miquel Raynal
2026-06-05  8:15   ` Takahiro.Kuwano
2026-06-05  8:15     ` Takahiro.Kuwano
2026-06-05 13:05   ` Tudor Ambarus
2026-06-05 13:05     ` Tudor Ambarus
2026-06-01 12:52 ` [RFC PATCH 3/3] mtd: spi-nor: rework flash parameter initialization Michael Walle
2026-06-01 12:52   ` Michael Walle
2026-06-05 13:17   ` Tudor Ambarus
2026-06-05 13:17     ` Tudor Ambarus
2026-06-02 10:03 ` [RFC PATCH 0/3] mtd: spi-nor: Rework " Miquel Raynal
2026-06-02 10:03   ` Miquel Raynal
2026-06-03  0:13   ` Takahiro.Kuwano
2026-06-03  0:13     ` Takahiro.Kuwano
2026-06-05  8:50     ` Takahiro.Kuwano
2026-06-05  8:50       ` Takahiro.Kuwano
2026-07-02  2:39 ` Cheng Ming Lin
2026-07-02  2:39   ` Cheng Ming Lin
2026-07-02 15:17 ` Miquel Raynal [this message]
2026-07-02 15:17   ` Miquel Raynal
2026-07-07  6:35   ` Michael Walle
2026-07-07  6:35     ` Michael Walle
2026-07-06  6:24 ` Miquel Raynal
2026-07-06  6:24   ` Miquel Raynal
2026-07-06  7:33   ` Michael Walle
2026-07-06  7:33     ` Michael Walle
2026-07-06 13:45     ` Miquel Raynal
2026-07-06 13:45       ` Miquel Raynal
2026-07-06 14:16       ` Miquel Raynal
2026-07-06 14:16         ` Miquel Raynal

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=87jyrdpgik.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mwalle@kernel.org \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=takahiro.kuwano@infineon.com \
    --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 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.