From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754100Ab3GBRJm (ORCPT ); Tue, 2 Jul 2013 13:09:42 -0400 Received: from mail-oa0-f50.google.com ([209.85.219.50]:55450 "EHLO mail-oa0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753337Ab3GBRJj (ORCPT ); Tue, 2 Jul 2013 13:09:39 -0400 MIME-Version: 1.0 In-Reply-To: <20130702104406.4473EE0090@blue.fi.intel.com> References: <1372177330-28013-1-git-send-email-mika.westerberg@linux.intel.com> <1372177330-28013-6-git-send-email-mika.westerberg@linux.intel.com> <20130702104406.4473EE0090@blue.fi.intel.com> From: Bjorn Helgaas Date: Tue, 2 Jul 2013 11:09:19 -0600 Message-ID: Subject: Re: [PATCH 5/6] PCI: acpiphp: look _RMV method a bit deeper in the hierarhcy To: "Kirill A. Shutemov" Cc: Mika Westerberg , Greg Kroah-Hartman , "Rafael J. Wysocki" , Jesse Barnes , Yinghai Lu , "Ronciak, John" , "Penner, Miles J" , Bruce Allan , Heikki Krogerus , "linux-kernel@vger.kernel.org" , "linux-pci@vger.kernel.org" , "x86@kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 2, 2013 at 4:44 AM, Kirill A. Shutemov wrote: > Mika Westerberg wrote: >> The acpiphp driver finds out whether the device is hotpluggable by checking >> whether it has _RMV method behind it (and if it returns 1). However, at >> least Acer Aspire S5 with Thunderbolt host router has this method placed >> behind device called EPUP (endpoint upstream port?) and not directly behind >> the root port as can be seen from the ASL code below: >> >> Device (RP05) >> { >> ... >> Device (HRUP) >> { >> Name (_ADR, Zero) >> Name (_PRW, Package (0x02) >> { >> 0x09, >> 0x04 >> }) >> Device (HRDN) >> { >> Name (_ADR, 0x00040000) >> Name (_PRW, Package (0x02) >> { >> 0x09, >> 0x04 >> }) >> Device (EPUP) >> { >> Name (_ADR, Zero) >> Method (_RMV, 0, NotSerialized) >> { >> Return (One) >> } >> } >> } >> } >> >> If we want to support such machines we must look for the _RMV method a bit >> deeper in the hierarchy. Fix this by changing pcihp_is_ejectable() to check >> few more devices down from the root port. > > We found that this approach is broken. We've got false positive: host > bridge itself was detected as hotplugable slot %) I think it's not > acceptable. > > Mika has tried few more approaches, but we haven't found anything better > then hardcoded path like in original workaround patch[1]. It's not generic > at all, but safe from false positives. > > Any thoughts? > > [1] http://article.gmane.org/gmane.linux.kernel.pci/19102 The changelog of this patch ([1]) says "Correct ACPI PCI hotplug implementation should have _RMV method in a PCI slot (device under pci bridge). In Acer Aspire S5 case we have it deeper in hierarchy ..." This is exactly what I mean about acpiphp being brittle because of the assumptions it makes about the ACPI namespace. Is there actually something in the spec that requires the _RMV method to be where pcihp_is_ejectable() expects it? I'm not 100% dead-set against merging the workaround with hard-coded path, but I still don't think it's a good idea. It "fixes" it for one particular machine, but there will likely be other machines that require similar fixes in the future. It makes it harder for somebody to clean up the design later, because that person won't have an Aspire S5 to test. It makes it less likely that somebody *will* clean it up later, because "everything is already working." That's why my preference (given infinite resources) would be to rework acpiphp now, while people are interested and can test it. I'm sure this would be a major redesign of acpiphp and its interaction with pciehp, but I think it's something we're going to have to do at some point. Bjorn