[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <YqmrIsOEsFoKTwEK@lahna>
Date: Wed, 15 Jun 2022 12:49:22 +0300
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: "Oleksandr Ocheretnyi -X (oocheret - GLOBALLOGIC INC at Cisco)"
<oocheret@...co.com>
Cc: "tudor.ambarus@...rochip.com" <tudor.ambarus@...rochip.com>,
"miquel.raynal@...tlin.com" <miquel.raynal@...tlin.com>,
"p.yadav@...com" <p.yadav@...com>,
"michael@...le.cc" <michael@...le.cc>,
"richard@....at" <richard@....at>,
"vigneshr@...com" <vigneshr@...com>,
"broonie@...nel.org" <broonie@...nel.org>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
"linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
"mauro.lima@...ypsium.com" <mauro.lima@...ypsium.com>,
"lee.jones@...aro.org" <lee.jones@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"xe-linux-external(mailer list)" <xe-linux-external@...co.com>
Subject: Re: [PATCH] mtd: spi-nor: handle unsupported FSR opcodes properly
Hi,
On Tue, Jun 14, 2022 at 05:56:54PM +0000, Oleksandr Ocheretnyi -X (oocheret - GLOBALLOGIC INC at Cisco) wrote:
> Hello Mika,
>
> in my case (I work with memory chip n25q128a13 for recent kernels) I'm
> getting return value -ENOTSUPP from spi_mem_exec_op() call in the
> micron_st_nor_read_fsr() method
> [[1]https://elixir.bootlin.com/linux/v5.19-rc2/source/drivers/spi/spi-m
> em.c#L326]. So I decided to provide the same errorcode to
> intel_spi_hw_cycle() method because older kernel versions throw the
> error there. It is fine to use -EOPNOTSUPP return value instead.
>
> I suspect we need to cover both cases to check -ENOTSUPP as well as
> -EOPNOTSUPP to let the driver work properly.
>
> if (ret == -ENOTSUPP || ret == -EOPNOTSUPP)
I think we should follow the same in the Intel driver and return
-ENOTSUPP too.
Powered by blists - more mailing lists