From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 13D7E3CE48F for ; Mon, 6 Jul 2026 07:33:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783323228; cv=none; b=QTiwQmJQDo2vNBu/5uB/A2zfY301H7rQI9F2hKG721m8KwNZMvlVNzDUdJMiz2f3OVcl5zI+KcbX2jKpU1gA+m4gfL52rwqxIlvy6GP//a6WHAr2BOlTpDntIyByxxLjpcSh2xDWYVtLT/TL6sDAuVvpBNxXaOvjCOGRht5DYWk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783323228; c=relaxed/simple; bh=Da/crD/c42EcGPW155zbOb6uONCuevcgyOgrjHlYVSA=; h=Mime-Version:Content-Type:Date:Message-Id:From:To:Subject:Cc: References:In-Reply-To; b=QZwcqzuzuMuZuk8p0Dh4qsbh2YnK2x8ZLN9meK0eap0fDasODrRZCXR5ls2y/m+RGV1CNDpvu6C1a5yl+WQEogit+LEgaGNPxRSP2cs8hAxoQvJjPAxdDXNVkxch/JSNKXD6F1MJWSfIdrWNdY5U0wu72a+9tVCSNRXzlSZloVk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=NCgOjEL2; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="NCgOjEL2" Received: by smtp.kernel.org (Postfix) with UTF8SMTPSA id 86F5A1F000E9; Mon, 6 Jul 2026 07:33:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1783323223; bh=1ukOqhUIyhqwzYEErT0FIxxuwMebK40CW0OY3I/ZcfY=; h=Date:From:To:Subject:Cc:References:In-Reply-To; b=NCgOjEL2AaoP1dShSVmWQDDm23Jds8hNFrLSMge/9cpmsa+O2KZyhgV3bJj1moMDz wT+s8tPFk//MOg2yBsRki+mX35QM3jOfWWkWLZnm7MOF6HEUTS5wsltO6nfDJfn1eI /0gPF5Y3brfw39VqppdS/nj7ZYaGFkcLpoXE/Qu7uHsR6vpgR8hg3LJbM3hgj9wcBe 6xeHF8zNBm5TW6T7stZSQ2ZNTbLPz2oj4HClLr9ZjkXQcVCzgZkAM+KfL8H9bO2480 7+/0I/yCUl3eu79muIiiAj3dhDn+pHA95q6haQkq6q1c4XRFDPQ8mamc0ZjdVH3qmJ udy7xHLtF8QFw== Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Type: multipart/signed; boundary=36999bf6262f04d5582998dd6acb24b4eca9920076ee79a221b98ace3f0a; micalg=pgp-sha384; protocol="application/pgp-signature" Date: Mon, 06 Jul 2026 09:33:38 +0200 Message-Id: From: "Michael Walle" To: "Miquel Raynal" , "Pratyush Yadav" , "Takahiro Kuwano" , "Richard Weinberger" , "Vignesh Raghavendra" , "Tudor Ambarus" Subject: Re: [RFC PATCH 0/3] mtd: spi-nor: Rework flash parameter initialization Cc: , X-Mailer: aerc 0.20.0 References: <20260601125438.3481722-1-mwalle@kernel.org> <178331904816.868671.4599503585231715805.b4-ty@bootlin.com> In-Reply-To: <178331904816.868671.4599503585231715805.b4-ty@bootlin.com> --36999bf6262f04d5582998dd6acb24b4eca9920076ee79a221b98ace3f0a Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 On Mon Jul 6, 2026 at 8:24 AM CEST, Miquel Raynal wrote: > On Mon, 01 Jun 2026 14:52:42 +0200, Michael Walle wrote: >> Try to simplify the flash initialization and get rid of the legacy >> handling. As default, all the flags of the in-kernel database are >> taken and amended with the SFDP data. >>=20 >> 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. >>=20 >> [...] > > Applied to mtd/fixes, thanks! > > [1/3] mtd: spi-nor: spansion: s25fl256s0: remove SKIP_SFDP flag > (no commit info) > [2/3] mtd: spi-nor: don't clear the SNOR_F_4B_OPCODES flag on failure > (no commit info) > [3/3] mtd: spi-nor: rework flash parameter initialization > (no commit info) > > Patche(s) should be available on mtd/linux.git and will be > part of the next PR (provided that no robot complains by then). Did you see, that there was a v1 of this series? There wasn't many changes for these three patches. Just what Tudor mentioned that the unsupported RDSFDP opcode should be mentioned in the commit message, too. Apart from that, the series now includes fixes that Sashiko found, that is, the rollback in case of a failed SFDP parsing is broken. I can also rebase that on top of these three patches. -michael --36999bf6262f04d5582998dd6acb24b4eca9920076ee79a221b98ace3f0a Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iKgEABMJADAWIQTIVZIcOo5wfU/AngkSJzzuPgIf+AUCaktaUxIcbXdhbGxlQGtl cm5lbC5vcmcACgkQEic87j4CH/hjSQF/WHZ+eUDa7zpaqSEal9vD7Tc3gtkuz3/V 8bxySWZd+JSuc3Mi9DjnGIQzVrVUtUZCAX9TsmwU0BluqCa8RnhLB22NJWhZQqec Tc2yxtsvdKAfiBEoCOK+I2z6gp5KeIwoiqM= =+69i -----END PGP SIGNATURE----- --36999bf6262f04d5582998dd6acb24b4eca9920076ee79a221b98ace3f0a--