mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Oliver Neukum <oneukum@suse.de>, Michal Marek <mmarek@suse.cz>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pciehp: Add pciehp_surprise module option
Date: Wed, 20 Mar 2013 17:39:45 +0100	[thread overview]
Message-ID: <s5hobeegh4e.wl%tiwai@suse.de> (raw)
In-Reply-To: <5149E4CE.2060104@infradead.org>

At Wed, 20 Mar 2013 09:33:18 -0700,
Randy Dunlap wrote:
> 
> On 03/20/13 07:02, Takashi Iwai wrote:
> > We encountered a problem that on some HP machines the Realtek PCI-e
> > card reader device appears only when you inserted a card before the
> > cold boot.  While debugging, it turned out that the device is actually
> > handled via PCI-e hotplug in some level.  The device sends a presence
> > change notification, and pciehp receives it, but it's ignored because
> > of lack of the hotplug surprise (PCI_EXP_SLTCAP_HPS) capability bit.
> > Once when this check passes, everything starts working -- the device
> > appears upon plugging the card properly.
> > 
> > There are a few other bug reports indicating the similar problems
> > (e.g. on recent Dell laptops), and I guess the culprit is same.
> > 
> > This patch adds a new module option, pciehp_surprise, to pciehp as a
> > workaround.  When pciehp_surprise=1 is given, pciehp handles the
> > presence change as the device on/off as if PCI_EXP_SLTCAP_HPS is set.
> > Unless it's set explicitly, there is no impact on the existing
> > behavior.
> > 
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > ---
> >  drivers/pci/hotplug/pciehp.h      | 3 ++-
> >  drivers/pci/hotplug/pciehp_core.c | 3 +++
> >  2 files changed, 5 insertions(+), 1 deletion(-)
> > 
> 
> > diff --git a/drivers/pci/hotplug/pciehp_core.c b/drivers/pci/hotplug/pciehp_core.c
> > index 7d72c5e..c3a574e 100644
> > --- a/drivers/pci/hotplug/pciehp_core.c
> > +++ b/drivers/pci/hotplug/pciehp_core.c
> > @@ -55,10 +56,12 @@ module_param(pciehp_debug, bool, 0644);
> >  module_param(pciehp_poll_mode, bool, 0644);
> >  module_param(pciehp_poll_time, int, 0644);
> >  module_param(pciehp_force, bool, 0644);
> > +module_param(pciehp_surprise, bool, 0644);
> >  MODULE_PARM_DESC(pciehp_debug, "Debugging mode enabled or not");
> >  MODULE_PARM_DESC(pciehp_poll_mode, "Using polling mechanism for hot-plug events or not");
> >  MODULE_PARM_DESC(pciehp_poll_time, "Polling mechanism frequency, in seconds");
> >  MODULE_PARM_DESC(pciehp_force, "Force pciehp, even if OSHP is missing");
> > +MODULE_PARM_DESC(pciehp_surprise, "Force to set hotplug-surprise capability");
> 
> 
> It appears that all of the pciehp options need to be documented,
> preferably in Documentation/kernel-parameters.txt .

Yeah, makes sense.

Off-topic: it would have been nicer if pciehp_ prefix was removed at
the first place, too.  But it's too late and we need to live with it.


Takashi

  reply	other threads:[~2013-03-20 16:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20 14:02 Takashi Iwai
2013-03-20 16:33 ` Randy Dunlap
2013-03-20 16:39   ` Takashi Iwai [this message]
2013-03-20 17:52 ` Matthew Garrett
2013-03-20 19:11   ` Takashi Iwai
2013-03-20 19:12     ` Matthew Garrett
2013-03-20 19:23       ` Takashi Iwai
2013-03-20 19:26         ` Matthew Garrett
2013-03-20 18:09 ` Alex Williamson
2013-03-20 19:08   ` Takashi Iwai
2013-03-22 16:15     ` Michal Marek
2013-03-22 16:16       ` Matthew Garrett
2013-03-22 16:35         ` Michal Marek
2013-03-22 16:20       ` Alex Williamson
2013-03-27 16:11         ` Oliver Neukum
2013-03-27 16:19           ` Michal Marek
2013-03-20 18:41 ` Martin Mokrejs
2013-03-20 18:56   ` Martin Mokrejs
2013-03-20 19:20   ` Takashi Iwai
2013-06-07  0:04     ` Martin Mokrejs
2013-03-25 16:58 ` Bjorn Helgaas
2013-04-10 16:34   ` Takashi Iwai
2013-04-10 17:19     ` Bjorn Helgaas
2013-04-11 13:40       ` Takashi Iwai

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=s5hobeegh4e.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=oneukum@suse.de \
    --cc=rdunlap@infradead.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

Powered by JetHome