From: Scott Branden <sbranden@broadcom.com>
To: Fabio Estevam <festevam@gmail.com>, Ulf Hansson <ulf.hansson@linaro.org>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: 04e079cf6b24c794 to stable
Date: Tue, 28 Apr 2015 14:15:19 -0700 [thread overview]
Message-ID: <553FF867.9080507@broadcom.com> (raw)
In-Reply-To: <CAOMZO5DnfYs7O6AvshfKWrQ_Op6NZwg4R=Z2wzwXMG=_go1Lvg@mail.gmail.com>
Hi Fabio,
Yes, you can apply the change to stable.
Regards,
Scott
On 15-04-28 12:49 PM, Fabio Estevam wrote:
> On Tue, Apr 28, 2015 at 12:46 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> Hi Ulf and Scott,
>>
>> Should the commit below be applied to stable?
>>
>> commit 04e079cf6b24c794bbc52b04b370f84cb728540e
>> Author: Scott Branden <sbranden@broadcom.com>
>> Date: Tue Mar 10 11:35:10 2015 -0700
>>
>> mmc: sdhci: fix card presence logic in sdhci_request function
>>
>> The sdhci_request function should consider a non-removable device
>> always present.
>> Call the correct logic already available in sdhci_do_get_cd function.
>>
>> This fixes some logic paths where MMC requests are being made to
>> non-removable devices that do not have the card detect pin connected
>> on the hardware as it is non-removable.
>>
>> Signed-off-by: Scott Branden <sbranden@broadcom.com>
>> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
>>
>> The reason I am asking is that we were seeing issues on mx6 boards
>> running 4.0 kernel branch + 8d86e4fcccf61bafe5 ("mmc: sdhci-esdhc-imx:
>> Call mmc_of_parse()"), which is 4.1-rc1 material.
>>
>> Otavio suggested me to apply 04e079cf6b24 in our tree and after that
>> the SD card detection goes away.
>
> Sorry, I meant "and after that the SD card detection problem goes away"
>
prev parent reply other threads:[~2015-04-28 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 15:46 04e079cf6b24c794 to stable Fabio Estevam
2015-04-28 19:49 ` Fabio Estevam
2015-04-28 21:15 ` Scott Branden [this message]
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=553FF867.9080507@broadcom.com \
--to=sbranden@broadcom.com \
--cc=festevam@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=otavio@ossystems.com.br \
--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