Re: [PATCH v2 0/2] Report platform enforced SPI flash write protection

From: "Michael Walle" <mwalle@kernel.org>
To: "Mika Westerberg" <mika.westerberg@linux.intel.com>
Cc: <tjakobsen84@protonmail.com>,
	"Pratyush Yadav" <pratyush@kernel.org>,
	"Takahiro Kuwano" <takahiro.kuwano@infineon.com>,
	"Miquel Raynal" <miquel.raynal@bootlin.com>,
	"Richard Weinberger" <richard@nod.at>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Mark Brown" <broonie@kernel.org>,
	<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
	<linux-spi@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] Report platform enforced SPI flash write protection
Date: Mon, 31 Aug 2026 15:00:36 +0200	[thread overview]
Message-ID: <DL35CFJ3BXZ1.2RE00JYDZKXXU@kernel.org> (raw)
In-Reply-To: <20260831125526.GJ124825@black.igk.intel.com>

[-- Attachment #1.1: Type: text/plain, Size: 809 bytes --]

Hi,

On Mon Aug 31, 2026 at 2:55 PM CEST, Mika Westerberg wrote:
> Hi,
>
> On Mon, Aug 31, 2026 at 02:37:59PM +0200, Michael Walle wrote:
>> Hi,
>> 
>> On Mon Aug 31, 2026 at 2:05 PM CEST, Tobias Jakobsen via B4 Relay wrote:
>> > Patch 2 adds the only user, spi-intel, which already computes protected
>> > range state at probe but has had no way to expose it since the SPI MEM
>> > conversion removed its visibility of the MTD device.
>> 
>> Where was it removed, though?
>
> After the SPI MEM conversion the driver is a regular SPI driver so it can
> only use spi_new_device() to add and configure the SPI-NOR chip (via
> platform data, struct flash_platform_data). Prior this it was creating the
> MTD device itself.

Yeah, but it never exposed the _is_locked() op, right?

-michael

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]

[-- Attachment #2: Type: text/plain, Size: 144 bytes --]

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