From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
Raghuveer Murthy <raghuveer.murthy@ti.com>,
Kishore Kadiyala <kishore.kadiyala@ti.com>
Subject: Re: [PATCH v2] OMAP4: Pandaboard: Fix MMC card detect gpio line
Date: Tue, 21 Dec 2010 17:57:27 -0800 [thread overview]
Message-ID: <20101222015726.GQ5829@atomide.com> (raw)
In-Reply-To: <1292940874-21419-1-git-send-email-nm@ti.com>
* Nishanth Menon <nm@ti.com> [101221 06:14]:
> From: Raghuveer Murthy <raghuveer.murthy@ti.com>
>
> commit bf56f0a6668cd (2.6.37-rc1), from Nishanth Menon attempted
> to fix card detection for PandaBoard, unfortunately, the fix missed
> to initialize .gpio_cd member of omap2_hsmmc_info. This results
> in a default value of '0', which is a valid GPIO line.
> On PandaBoard, the side effect of this is that GPIO line 0 controls
> the powering TFP410 DVI chip, and without the fix DVI chip is
> inadvertently powered.
>
> Tested-by: David Anders <x0132446@ti.com>
>
> Acked-by: Nishanth Menon <nm@ti.com>
>
> Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
> Signed-off-by: Raghuveer Murthy <raghuveer.murthy@ti.com>
> ---
> v2: updated comment description to point out the potential regression.
> it might be nice to have this in .37 rc cycle as the change was
> introduced in .37-rc1, however, the DVI functionality(which is impacted
> as a side effect) is not enabled in .37 rc.
I'll queue this for .38 because of "it never worked earlier either" logic.
Thanks,
Tony
prev parent reply other threads:[~2010-12-22 1:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 14:14 [PATCH v2] OMAP4: Pandaboard: Fix MMC card detect gpio line Nishanth Menon
2010-12-22 1:57 ` 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=20101222015726.GQ5829@atomide.com \
--to=tony@atomide.com \
--cc=kishore.kadiyala@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=raghuveer.murthy@ti.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).