From: Mark Brown <broonie@kernel.org>
To: "Krzysztof Hałasa" <khalasa@piap.pl>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Schwierzeck <daniel.schwierzeck@gmail.com>,
Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: MIPS Lantiq VRX268 general Linux SPI timeout
Date: Tue, 12 May 2026 10:27:15 +0900 [thread overview]
Message-ID: <agKB85O1LM5kF_J6@sirena.co.uk> (raw)
In-Reply-To: <m3bjemm0ds.fsf@t19.piap.pl>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
On Mon, May 11, 2026 at 05:28:15PM +0200, Krzysztof Hałasa wrote:
> Now what should we do with this?
> a) should we increase the 200 ms timeout? Would it still fail eventually?
> b) should the timeout be configurable, maybe by the platform code?
> c) some other way?
If raising the timeout resolves the issue just raise the timeout, this
is not something that should ever happen in production and is just there
to ensure we don't completely deadlock on catastrophic errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-05-12 1:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 15:28 MIPS Lantiq VRX268 general Linux SPI timeout Krzysztof Hałasa
2026-05-12 1:27 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=agKB85O1LM5kF_J6@sirena.co.uk \
--to=broonie@kernel.org \
--cc=daniel.schwierzeck@gmail.com \
--cc=hauke@hauke-m.de \
--cc=khalasa@piap.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox