From: Keith Busch <kbusch@kernel.org>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Keith Busch <kbusch@meta.com>,
bhelgaas@google.com, linux-pci@vger.kernel.org,
ilpo.jarvinen@linux.intel.com, lukas@wunner.de
Subject: Re: [PATCHv2] pci: allow user specifiy a reset poll timeout
Date: Wed, 11 Jun 2025 11:17:43 -0600 [thread overview]
Message-ID: <aEm6Nx6bSDvyouEy@kbusch-mbp> (raw)
In-Reply-To: <reekyt4dm7uszybipm25xfxlksn5bm2cdpubx5idovxenpg44z@qcqs44xlevea>
On Wed, Jun 11, 2025 at 10:41:33PM +0530, Manivannan Sadhasivam wrote:
> On Wed, Jun 11, 2025 at 10:40:10AM -0600, Keith Busch wrote:
> >
> > No. I'm dealing with new devices being actively developed, with new ones
> > coming out every year, so a quirk list would just be never ending
> > maintenance pain point.
>
> Sounds like you have a lot of devices behaving this way. So can't you quirk them
> based on VID and CLASS?
What I mean by active development is that the timeout continues to be a
moving target. A quirk only gives me a fixed value, but I need a
modifiable one without having to recompile the kernel.
next prev parent reply other threads:[~2025-06-11 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 16:54 [PATCHv2] pci: allow user specifiy a reset poll timeout Keith Busch
2025-04-15 0:11 ` Keith Busch
2025-06-11 16:28 ` Manivannan Sadhasivam
2025-06-11 16:40 ` Keith Busch
2025-06-11 17:11 ` Manivannan Sadhasivam
2025-06-11 17:17 ` Keith Busch [this message]
2025-06-12 8:06 ` Ilpo Järvinen
2025-06-23 17:51 ` Keith Busch
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=aEm6Nx6bSDvyouEy@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kbusch@meta.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mani@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