linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philip Elcan <pelcan@codeaurora.org>
To: Adrian Hunter <adrian.hunter@intel.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, Timur Tabi <timur@codeaurora.org>,
	Jon Masters <jcm@redhat.org>,
	Mark Langsdorf <mlangsdo@redhat.com>
Subject: Re: [PATCH] mmc: sdhci-acpi: set non-removable in ACPI table
Date: Fri, 04 Dec 2015 10:40:32 -0500	[thread overview]
Message-ID: <5661B3F0.2010000@codeaurora.org> (raw)
In-Reply-To: <56604E57.9000201@intel.com>


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.

>
>> mark it as non-removable if GPIO card detection is
>> already setup.
>>
>> Signed-off-by: Philip Elcan <pelcan@codeaurora.org>
>> ---
>>

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2015-12-04 15:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-03 13:48 [PATCH] mmc: sdhci-acpi: set non-removable in ACPI table Philip Elcan
2015-12-03 14:14 ` Adrian Hunter
2015-12-04 15:40   ` Philip Elcan [this message]
2015-12-07  8:30     ` Adrian Hunter
2015-12-10 20:57       ` Philip Elcan
2015-12-11  8:17         ` Adrian Hunter
2015-12-11 22:53           ` Rafael J. Wysocki
     [not found]             ` <567087F3.7030308@codeaurora.org>
2015-12-16  1:17               ` Rafael J. Wysocki

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=5661B3F0.2010000@codeaurora.org \
    --to=pelcan@codeaurora.org \
    --cc=adrian.hunter@intel.com \
    --cc=jcm@redhat.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mlangsdo@redhat.com \
    --cc=timur@codeaurora.org \
    --cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).