From: Tony Lindgren <tony@atomide.com>
To: Balaji T K <balajitk@ti.com>
Cc: Stefan Roese <stefan.roese@gmail.com>,
Sebastian Reichel <sre@ring0.de>,
Michael Trimarchi <michael@amarulasolutions.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux MMC List <linux-mmc@vger.kernel.org>,
'Chris Ball' <chris@printf.net>
Subject: Re: SD card timeout problems on Nokia N900 (omap_hsmmc on OMAP3)
Date: Wed, 26 Feb 2014 09:03:23 -0800 [thread overview]
Message-ID: <20140226170323.GB11654@atomide.com> (raw)
In-Reply-To: <530DA97E.7090406@ti.com>
* Balaji T K <balajitk@ti.com> [140226 00:48]:
> On Wednesday 26 February 2014 12:25 PM, Stefan Roese wrote:
> >Hi Sebastian,
> >
> >On 26.02.2014 07:02, Michael Trimarchi wrote:
> >>Hi Sebastian
> >>
> >>On Wed, Feb 26, 2014 at 12:47 AM, Sebastian Reichel <sre@ring0.de> wrote:
> >>>Hi,
> >>>
> >>>I have problems with the SD-card initialization on my Nokia N900
> >>>using a 3.14-rc1 based kernel in DT boot mode. The bug is can be
> >>>circumvented by changing the kernel slightly (e.g. remove some DT
> >>>nodes or mark them as disabled). So the SD card's timeout problems
> >>>seem to derive from kernel timing problems. I'm pretty sure, that
> >>>the problems are not originating from a broken SD card, since
>
> Can you provide removed/Disabled dt nodes, it might give some clue ?
>
> >>>
> >>> 1. The SD card worked quite good before and still does depending
> >>> on unrelated DTS changes (=> loading less drivers).
> >>> 2. The SD card works flawlessly on my notebook using a USB adapter
> >>> 3. Another SD card showed the same problem
> >>>
> >>>I tried to git bisect the problem, but I just get shown some
> >>>unrelated driver additions.
> >>>
> >>>Anyways, this is the error I get during boot:
> >>>
> >>>[ 3.896820] mmc0: mmc_rescan_try_freq: trying to init card at 400000 Hz
> >>>...
> >>>[ 5.956237] mmc0: error -110 whilst initialising SD card
> >>>
> >>
> >>Are you sure that some subsystem that you deactivate don't change
> >>pin muxing setting? Can you check in the broken system if the pins of the sdcard
> >>are correctly muxed? Does it happen even if you change the sdcard?
> >
> >Did you try to add this patch series:
> >
> >http://www.spinics.net/lists/linux-omap/msg103264.html
> >
> >Without it I'm also having problems with MMC detection on some OMAP3 based boards.
> >
> >Balaji, what is the status of this patch series? Are there any chances that it will be included in v3.14?
> >
>
> Due to dependencies between regulator, mmc, omap def config, devicetree changes,
> I am hoping either Chris or Tony pick the whole series for 3.15
Best that Chris takes it all, I just acked the only patch that did not have
my ack yet.
> Couple of tested-by will surely help.
Yeah please ack in the thread above if you did not already.
Regards,
Tony
prev parent reply other threads:[~2014-02-26 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 23:47 SD card timeout problems on Nokia N900 (omap_hsmmc on OMAP3) Sebastian Reichel
2014-02-26 6:02 ` Michael Trimarchi
2014-02-26 6:55 ` Stefan Roese
2014-02-26 8:44 ` Balaji T K
2014-02-26 17:03 ` Tony Lindgren [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=20140226170323.GB11654@atomide.com \
--to=tony@atomide.com \
--cc=balajitk@ti.com \
--cc=chris@printf.net \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=michael@amarulasolutions.com \
--cc=sre@ring0.de \
--cc=stefan.roese@gmail.com \
/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).