[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5669E72C.4090701@codeaurora.org>
Date: Thu, 10 Dec 2015 15:57:16 -0500
From: Philip Elcan <pelcan@...eaurora.org>
To: Adrian Hunter <adrian.hunter@...el.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org
CC: linux-arm-msm@...r.kernel.org, Timur Tabi <timur@...eaurora.org>,
Jon Masters <jcm@...hat.org>,
Mark Langsdorf <mlangsdo@...hat.com>, harba@...eaurora.org
Subject: Re: [PATCH] mmc: sdhci-acpi: set non-removable in ACPI table
On 12/07/2015 03:30 AM, Adrian Hunter wrote:
> On 04/12/15 17:40, Philip Elcan wrote:
>> On 12/03/2015 09:14 AM, Adrian Hunter wrote:
>>> On 03/12/15 15:48, Philip Elcan wrote:
>>>> This allows setting an SDHC controller as non-removable
>>>> by using the _RMV method in the ACPI table. It doesn't
>>> Is that _RMV on the host controller? Shouldn't it be on the card i.e. child
>>> device node?
>> Yes, this is on the host controller. The ACPI table only describes the
>> host controller, not the child nodes.
>>
> If you look at Intel devices, the _RMV is on the child e.g.
>
> Device (SDHA)
> {
> Name (_HID, "80860F14") // _HID: Hardware ID
> Name (_CID, "PNP0D40") // _CID: Compatible ID
> Name (_DDN, "Intel(R) eMMC Controller - 80860F14") // _DDN: DOS Device Name
> ...
> Device (EMMD)
> {
> ...
> Method (_RMV, 0, NotSerialized) // _RMV: Removal Status
> {
> Return (Zero)
> }
> }
> }
>
> I am not an ACPI expert but that seems like the correct place for it.
My understanding is that in ACPI you don't generally create child devices on buses that are discoverable.
>
>>>> mark it as non-removable if GPIO card detection is
>>>> already setup.
>>>>
>>>> Signed-off-by: Philip Elcan <pelcan@...eaurora.org>
>>>> ---
>>>>
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists