Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933069Ab3CTQjs (ORCPT ); Wed, 20 Mar 2013 12:39:48 -0400 Received: from cantor2.suse.de ([195.135.220.15]:46329 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751980Ab3CTQjr (ORCPT ); Wed, 20 Mar 2013 12:39:47 -0400 Date: Wed, 20 Mar 2013 17:39:45 +0100 Message-ID: From: Takashi Iwai To: Randy Dunlap Cc: Bjorn Helgaas , Oliver Neukum , Michal Marek , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] pciehp: Add pciehp_surprise module option In-Reply-To: <5149E4CE.2060104@infradead.org> References: <5149E4CE.2060104@infradead.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/24.2 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2735 Lines: 60 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 > > --- > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/