mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: Pierre Ossman <drzeus-list@drzeus.cx>,
	Alex Chiang <achiang@hp.com>, LKML <linux-kernel@vger.kernel.org>,
	linux-pci@vger.kernel.org,
	Kristen Accardi <kristen.c.accardi@intel.com>
Subject: Re: post 2.6.26 requires pciehp_slot_with_bus
Date: Tue, 29 Jul 2008 08:14:32 -0700	[thread overview]
Message-ID: <200807290814.33098.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <488E83E9.6030108@jp.fujitsu.com>

On Monday, July 28, 2008 7:43 pm Kenji Kaneshige wrote:
> > Your systems don't have _RMV methods for the hotpluggable PCIe slots in
> > the DSDT?  That's a shame; the Windows docs I found on PCIe hotplug
> > seemed to indicate that _RMV and _OSC (under Vista) were used to detect
> > whether a given slot was hot pluggable (I just googled for "windows pcie
> > hotplug" or something) so I was hoping that would be a reliable method...
> >  Any other ideas?  I'll go see if I can dig up some ExpressCard info.
>
> My systems don't have _RMV methods for the hot pluggable PCIe slots in the
> DSDT, but I don't think that's a shame. I suppose that the document you are
> referring describes how Windows handles ExpressCard slots. In my
> understanding, Hot Plug Surprise bit in the Slot Capabilities register is
> set to 1b on ExpressCard slots, and I believe that ACPI _RVM method is for
> the device that only supports surprise-style removal. I think this is why
> your system implements _RMV method for slots.

Yeah, that may be.  The document wasn't very clear; I was hoping that 
something simple would be available.

> On the other hand, hot pluggable slots on my servers are *not* ExpressCard
> slots, and all of them have Power Controller instead of surprise-style
> removal (Hot Plug Surprise bit in the Slot Capabilities register is set to
> 0b). So I believe there is no reason to implement _RMV methods for the hot
> pluggable PCIe slots on my systems.
>
> Here is an idea. How about using _RMV method to determine whether a given
> slot is actually hot pluggable when Hot Plug Surprise bit in the Slot
> Capabilities register is set to 1b on the slot? This is based on a little
> rough assumption that all PCIe slots that support surprise-style removal
> have _RMV method, though. Does this work for you?

It's worth a try.  We need *some* sort of better method to detect hot 
pluggable slots...

Thanks,
Jesse

  reply	other threads:[~2008-07-29 15:14 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24 11:47 Pierre Ossman
2008-07-24 12:38 ` Kenji Kaneshige
2008-07-24 20:39   ` Pierre Ossman
2008-07-24 21:07     ` Jesse Barnes
2008-07-24 21:51       ` Pierre Ossman
2008-07-24 22:06         ` Jesse Barnes
2008-07-24 22:29           ` Alex Chiang
2008-07-24 22:49             ` Pierre Ossman
2008-07-24 23:08               ` Alex Chiang
2008-07-24 23:29                 ` Pierre Ossman
2008-07-25  3:29                   ` Matthew Wilcox
2008-07-25  4:42                     ` Alex Chiang
2008-07-25  5:38                       ` Kenji Kaneshige
2008-07-25 11:18                         ` Matthew Wilcox
2008-07-28 18:05                       ` Greg KH
2008-07-25  4:57                     ` Kenji Kaneshige
2008-07-30  2:38                       ` Alex Chiang
2008-07-30  2:42                         ` [PATCH 1/2] pciehp: Rename duplicate slot name N as N-1, N-2, N-M Alex Chiang
2008-07-31 10:32                           ` Kenji Kaneshige
2008-07-30  2:44                         ` [PATCH 2/2] shpchp: " Alex Chiang
2008-07-31 10:32                           ` Kenji Kaneshige
2008-07-31 10:31                         ` post 2.6.26 requires pciehp_slot_with_bus Kenji Kaneshige
2008-07-31 15:47                           ` Alex Chiang
2008-08-01  8:43                             ` Kenji Kaneshige
2008-07-25  8:53                     ` Kenji Kaneshige
2008-07-25 11:40                       ` Matthew Wilcox
2008-07-28  7:21                         ` Kenji Kaneshige
2008-07-25  4:50                   ` Kenji Kaneshige
2008-07-25 22:18                     ` Jesse Barnes
2008-07-26  1:16                       ` Matthew Wilcox
2008-07-28  8:58                         ` Kenji Kaneshige
2008-07-28  8:44                       ` Kenji Kaneshige
2008-07-28 16:16                         ` Jesse Barnes
2008-07-29  2:43                           ` Kenji Kaneshige
2008-07-29 15:14                             ` Jesse Barnes [this message]
2008-07-30  2:44                               ` Kenji Kaneshige
2008-07-28 16:57                         ` Matthew Wilcox

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=200807290814.33098.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=achiang@hp.com \
    --cc=drzeus-list@drzeus.cx \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --cc=kristen.c.accardi@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome