From: Keith Busch <keith.busch@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Sinan Kaya <okaya@codeaurora.org>,
linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 2/2] pci: Add ignore indicator quirk for devices
Date: Tue, 23 Aug 2016 16:44:21 -0400 [thread overview]
Message-ID: <20160823204421.GA10993@localhost.localdomain> (raw)
In-Reply-To: <20160823195221.GA3725@localhost>
On Tue, Aug 23, 2016 at 02:52:21PM -0500, Bjorn Helgaas wrote:
> Everybody probably knows this, but the problem is not with LED control
> per se. The problem is multiple writers to the Slot Control register.
> Each write to Slot Control is a "command", and software is responsible
> for waiting for one command to complete before writing another (see
> PCIe r3.0, sec 6.7.3.2).
>
> It's no problem to make pciehp keep its mitts off the LEDs; the
> problem is if ledmon writes Slot Control for the indicators, and
> pciehp writes Slot Control for some other reason at about the same
> time.
>
> Sinan has a very interesting idea... Maybe we can work with that.
> Hmm, it looks like if we have an attention indicator, we already put
> an "attention" file in sysfs (see attention_write_file()). That
> should eventually call into pciehp_set_attention_status(), where we
> currently only support off/on/blink states.
>
> What if you made a quirk that replaced pciehp_set_attention_status()
> with a special version that supported the extra states you need and
> made ledmon use that sysfs file instead of writing Slot Control
> directly? Would everything just work?
I'm on board with this idea. I'll get some testing started and send a
new version if/when successful.
next prev parent reply other threads:[~2016-08-23 20:44 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
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 [this message]
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=20160823204421.GA10993@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=okaya@codeaurora.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).