From: Mark Lord <lkml@rtr.ca>
To: kristen.c.accardi@intel.com
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Theodore Ts'o" <tytso@mit.edu>,
greg@kroah.com, pcihpd-discuss@lists.sourceforge.net
Subject: [PATCH 0/3] Fix two PEIe hotplug issues
Date: Wed, 17 Oct 2007 22:57:33 -0400 [thread overview]
Message-ID: <4716CB9D.6080503@rtr.ca> (raw)
Fix PCIe Hotplug so that it works with ExpressCard slots on Dell notebooks
(and others?) in conjunction with the modparam of pciehp_force=1.
The PCIe Hotplug driver has two issues when used on Dell notebooks
which lack ACPI BIOS support for PCIe hotplug:
1. The driver does not recognise cards that were inserted
prior to the driver being modprobe'd.
2. The driver stops functioning after a suspend/resume (RAM) cycle,
and needs to be rmmod'd and modprobe'd to get it working again.
This patch series addresses those issues, resulting in a completely
functional PCIe Hotplug driver for Dell notebooks, and possibly others
as well which may lack ACPI BIOS support for this.
Note that pciehp_force=1 is (still) required.
There are three patches in this series:
01_pciehp_handle_preinserted_card.patch
-- fixes problem number 1 (above).
02_pciehp_split_pcie_init.patch
-- preparation for the resume patch.
03_pciehp_resume_reinit_hardware.patch
-- fixes problem number 2 (above).
diffstat summary for the three patches combined:
drivers/pci/hotplug/pciehp.h | 3
drivers/pci/hotplug/pciehp_core.c | 23 +++
drivers/pci/hotplug/pciehp_ctrl.c | 2
drivers/pci/hotplug/pciehp_hpc.c | 185 +++++++++++++++-------------
4 files changed, 130 insertions(+), 83 deletions(-)
Cheers
--
Mark Lord <mlord@pobox.com>
next reply other threads:[~2007-10-18 2:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 2:57 Mark Lord [this message]
2007-10-18 2:59 ` [PATCH 1/3] pciehp_handle_preinserted_card Mark Lord
2007-10-18 3:00 ` [PATCH 2/3] pciehp_split_pcie_init Mark Lord
2007-10-18 3:02 ` [PATCH 3/3] pciehp_resume_reinit_hardware Mark Lord
2007-10-18 3:03 ` [PATCH 1/3] pciehp_handle_preinserted_card Mark Lord
2007-10-18 3:04 ` [PATCH 2/3] pciehp_split_pcie_init Mark Lord
2007-10-18 3:05 ` [PATCH 0/3] Fix two PEIe hotplug issues Mark Lord
2007-10-18 3:09 ` Mark Lord
2007-10-18 16:13 ` Kristen Carlson Accardi
2007-10-18 17:06 ` Mark Lord
2007-10-18 17:06 ` Kristen Carlson Accardi
2007-10-18 17:49 ` Theodore Tso
2007-10-18 17:56 ` Kristen Carlson Accardi
2007-10-18 21:11 ` Mark Lord
2007-10-18 21:26 ` Mark Lord
2007-10-18 3:32 ` [PATCH 1/3] pciehp: hotplug: deal with pre-inserted ExpressCards Mark Lord
2007-10-18 3:33 ` [PATCH 2/3] pciehp: hotplug: split out hardware init from pcie_init() Mark Lord
2007-10-18 3:34 ` [PATCH 3/3] pciehp: hotplug: reinit hotplug h/w on resume from suspend Mark Lord
2007-10-18 11:15 ` [Pcihpd-discuss] [PATCH 1/3] pciehp: hotplug: deal with pre-inserted ExpressCards Kenji Kaneshige
2007-10-18 13:31 ` Mark Lord
2007-10-19 2:38 ` Kenji Kaneshige
2007-10-19 3:09 ` Mark Lord
2007-10-19 3:27 ` Kenji Kaneshige
2007-11-18 0:27 ` [PATCH] Fix PCIe double initialization bug Mark Lord
2007-11-18 12:23 ` Rafael J. Wysocki
2007-11-18 14:20 ` Mark Lord
2007-11-18 14:37 ` Mark Lord
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=4716CB9D.6080503@rtr.ca \
--to=lkml@rtr.ca \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=tytso@mit.edu \
/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