[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3f8bd4e2-02ed-44c1-8925-5c16a98d90cc@linux.dev>
Date: Fri, 17 Jan 2025 11:50:41 -0500
From: Sean Anderson <sean.anderson@...ux.dev>
To: Mark Brown <broonie@...nel.org>
Cc: Michal Simek <michal.simek@....com>, linux-spi@...r.kernel.org,
linux-kernel@...r.kernel.org, Jinjie Ruan <ruanjinjie@...wei.com>,
linux-arm-kernel@...ts.infradead.org,
Amit Kumar Mahapatra <amit.kumar-mahapatra@....com>,
Miquel Raynal <miquel.raynal@...tlin.com>, Conor Dooley
<conor+dt@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Rob Herring <robh@...nel.org>, devicetree@...r.kernel.org
Subject: Re: [PATCH 0/5] spi: zynqmp-gqspi: Improve error recovery by
resetting
On 1/17/25 11:48, Mark Brown wrote:
> On Fri, Jan 17, 2025 at 11:17:35AM -0500, Sean Anderson wrote:
>> On 1/17/25 08:21, Mark Brown wrote:
>
>> > If you're hitting a timeout that tends to indicate there's already a
>> > serious stability problem...
>
>> This was mostly hit when I was hacking on the driver. But of course
>> there are probably still bugs lurking in this driver, so I think it is
>> good to handle the exceptional conditions in a more-robust way.
>
> I'm not saying it's a bad idea, but your changelog is written in a way
> that makes it sound like timeouts are normal.
I've updated my cover letter for v2 to include the above blurb. Hopefully
that clears things up.
--Sean
Powered by blists - more mailing lists