From: Bjorn Helgaas <helgaas@kernel.org>
To: Keith Busch <keith.busch@intel.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 2/2] pci: Add ignore indicator quirk for devices
Date: Mon, 15 Aug 2016 22:03:45 -0500 [thread overview]
Message-ID: <20160816030345.GA14894@localhost> (raw)
In-Reply-To: <20160815223503.GD18083@localhost.localdomain>
On Mon, Aug 15, 2016 at 06:35:03PM -0400, Keith Busch wrote:
> On Mon, Aug 15, 2016 at 02:50:58PM -0500, Bjorn Helgaas wrote:
> > What? This is August 15, not April 1. That makes no sense
> > whatsoever.
>
> Yes, I agree, and not advocating this was a good idea. I'm just the
> messenger in this case.
>
> That said, it looks like this can fall under the intended usage for
> the quirk framework if we can consider this a work-around for standard
> non-compliance. Or are your thoughts that we've gone too far if it's
> not a true erratum?
Well, I don't want to add random quirks for everybody who decides to
make their own non-standard hardware. The reason we have the PCI
specs is for interoperability, and this is not it.
The whole purpose of capability bits is for the hardware to tell the
OS that it has certain *capabilities* that work in certain ways. It's
idiotic to set a capability bit that says "I have this indicator" when
it doesn't work the way it's supposed to. The hardware should just
NOT SET THE BIT. How hard is that? I can't conceive of the reasoning
that concluded this was useful.
I don't care if you want to make the LEDs do something else, but for
Pete's sake, don't claim they work according to spec when they don't.
I assume there will be more broken devices like this in the future.
How long will we be adding quirks? Do you have a plan to resolve this
the correct way eventually?
I still don't know what it means that the devices "do the wrong
thing." Do the LEDs not work? Do the LEDs work according to the PCIe
spec, but the patterns don't match the International Blinken Lights
spec? Does the hotplug controller lock up?
Sigh.
next prev parent reply other threads:[~2016-08-16 3:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 20:19 [PATCH 1/2] pci: add option to ignore slot capabilities Keith Busch
2016-08-08 20:19 ` [PATCH 2/2] pci: Add ignore indicator quirk for devices Keith Busch
2016-08-15 17:40 ` Bjorn Helgaas
2016-08-15 19:23 ` Keith Busch
2016-08-15 19:50 ` Bjorn Helgaas
2016-08-15 22:35 ` Keith Busch
2016-08-16 3:03 ` Bjorn Helgaas [this message]
2016-08-17 21:37 ` Bjorn Helgaas
2016-08-17 23:09 ` Keith Busch
2016-08-18 19:56 ` Bjorn Helgaas
2016-08-18 22:46 ` Keith Busch
2016-08-22 16:55 ` Bjorn Helgaas
2016-08-22 21:15 ` Keith Busch
2016-08-23 13:39 ` Bjorn Helgaas
2016-08-23 17:10 ` Keith Busch
2016-08-23 17:14 ` Sinan Kaya
2016-08-23 19:23 ` Keith Busch
2016-08-23 19:52 ` Bjorn Helgaas
2016-08-23 20:44 ` Keith Busch
2016-08-23 20:02 ` Bjorn Helgaas
2016-08-24 17:33 ` Keith Busch
2016-08-13 0:03 ` [PATCH 1/2] pci: add option to ignore slot capabilities Sean O. Stalley
2016-08-13 0:58 ` 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=20160816030345.GA14894@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=keith.busch@intel.com \
--cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).