linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	Thorsten Einsbein <thorsten.eisbein@head-acoustics.de>,
	Balaji T K <balajitk@ti.com>
Subject: Re: [PATCH] mmc: omap_hsmmc: Add small delay after enabling power
Date: Fri, 12 Sep 2014 09:26:54 +0200	[thread overview]
Message-ID: <5412A03E.8060307@denx.de> (raw)
In-Reply-To: <CAPDyKFp9JKb=XOo5m7YQEQFbF4Rtn_DKP2ia3jCBMhRa6aJVZQ@mail.gmail.com>

On 11.09.2014 16:15, Ulf Hansson wrote:
> On 11 September 2014 16:11, Stefan Roese <sr@denx.de> wrote:
>> From: Thorsten Einsbein <thorsten.eisbein@head-acoustics.de>
>>
>> On the TAO3530 (OMAP3530 based) we noticed that some SD cards are not
>> detected reliably upon bootup (timeout). Especially the SanDisk Ultra
>> 8GiB seems to be problematic here. The SanDisk Extreme also has this
>> problem on this platform, but not that often. A Samsung 8 GiB type 6
>> doesn't show this problem at all.
>>
>> This patch now adds a short delay after enabling the power on the slot.
>> With this delay all cards are detected reliably.
>
> Is this delay related to regulator ramp up/down time? Then I think it
> maybe should be a part of the regulator code/DT.

Thanks for this feedback. Yes, adding "regulator-enable-ramp-delay" to 
the regulator(s) solves this issue too. I wasn't aware of that one.

The patch can be dropped.

Thanks,
Stefan


      reply	other threads:[~2014-09-12  7:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 14:11 [PATCH] mmc: omap_hsmmc: Add small delay after enabling power Stefan Roese
2014-09-11 14:15 ` Ulf Hansson
2014-09-12  7:26   ` Stefan Roese [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=5412A03E.8060307@denx.de \
    --to=sr@denx.de \
    --cc=balajitk@ti.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=thorsten.eisbein@head-acoustics.de \
    --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).