From: Alexandre Courbot <acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 2/2] ARM: tegra: roth: enable input on mmc clock pins
Date: Tue, 24 Jun 2014 14:44:06 +0900 [thread overview]
Message-ID: <53A91026.7040506@nvidia.com> (raw)
In-Reply-To: <53A87979.6000104-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On 06/24/2014 04:01 AM, Stephen Warren wrote:
> On 06/23/2014 01:32 AM, Alexandre Courbot wrote:
>> Input had been disabled by mistake on these pins, leading to issues with
>> SDIO devices like the Wifi module not being probed or random errors
>> occuring on the SD card.
>
> I thought the host controller always drove the clock, so there should be
> no need for the pin's input path to be enabled. Perhaps it depends on
> the transfer mode (e.g. UHS)?
That's what I thought too, so I went against what was done downstream
and disabled input mode. Eventually noticed various issues with MMC
devices, reverted to the downstream settings and noticed my problems
were solved by this single change.
>
> If this fix is valid, perhaps Jetson TK1's sdmmc3_clk and Venice2's
> sdmmc1_clk need the same fix, although we'll need to file bugs against
> their pinmux spreadsheets first if that's the case.
>
Are we having MMC issues with Jetson? I haven't noticed anything
recently, and I have been using both eMMC and SD card.
Anyway, at least for SHIELD, this change seems to be valid.
next prev parent reply other threads:[~2014-06-24 5:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 7:32 [PATCH 0/2] ARM: tegra: roth: pinmux fixes Alexandre Courbot
2014-06-23 7:32 ` [PATCH 1/2] ARM: tegra: roth: fix unsupported pinmux properties Alexandre Courbot
[not found] ` <1403508779-25896-1-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-06-23 7:32 ` [PATCH 2/2] ARM: tegra: roth: enable input on mmc clock pins Alexandre Courbot
[not found] ` <1403508779-25896-3-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-06-23 19:01 ` Stephen Warren
[not found] ` <53A87979.6000104-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-06-24 5:44 ` Alexandre Courbot [this message]
2014-06-24 15:53 ` Stephen Warren
2014-06-23 18:46 ` [PATCH 0/2] ARM: tegra: roth: pinmux fixes Stephen Warren
2014-06-24 3:57 ` Alexandre Courbot
2014-06-27 22:08 ` Stephen Warren
2014-06-29 4:27 ` Alexandre Courbot
[not found] ` <CAAVeFuKjfmuo0JjRnhhfbuo-Ed-QqVciAQ3g6ESCmzxhOvv0JA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-30 15:46 ` Stephen Warren
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=53A91026.7040506@nvidia.com \
--to=acourbot-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).