[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240314054145.GM112498@black.fi.intel.com>
Date: Thu, 14 Mar 2024 07:41:45 +0200
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Florian Fainelli <florian.fainelli@...adcom.com>
Cc: linux-spi@...r.kernel.org, Michael Walle <mwalle@...nel.org>,
Pratyush Yadav <pratyush@...nel.org>,
Mark Brown <broonie@...nel.org>, Michael Walle <michael@...le.cc>,
"Chia-Lin Kao (AceLan)" <acelan.kao@...onical.com>,
Miquel Raynal <miquel.raynal@...tlin.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] spi: Fix error code checking in spi_mem_exec_op()
On Wed, Mar 13, 2024 at 12:45:30PM -0700, Florian Fainelli wrote:
> After commit cff49d58f57e ("spi: Unify error codes by replacing -ENOTSUPP with
> -EOPNOTSUPP"), our SPI NOR flashes would stop probing with the following
> visible in the kernel log:
>
> [ 2.196300] brcmstb_qspi f0440920.qspi: using bspi-mspi mode
> [ 2.210295] spi-nor: probe of spi1.0 failed with error -95
>
> It turns out that the check in spi_mem_exec_op() was changed to check
> for -ENOTSUPP (old error code) or -EOPNOTSUPP (new error code), but this
> means that for drivers that were converted, the second condition is now
> true, and we stop falling through like we used to. Fix the error to
> check for neither error being neither -ENOTSUPP *nor* -EOPNOTSUPP.
>
> Fixes: cff49d58f57e ("spi: Unify error codes by replacing -ENOTSUPP with -EOPNOTSUPP")
> Reviewed-by: Michael Walle <mwalle@...nel.org>
> Reviewed-by: Pratyush Yadav <pratyush@...nel.org>
Reviewed-by: Mika Westerberg <mika.westerberg@...ux.intel.com>
Powered by blists - more mailing lists