From: Tony Lindgren <tony@atomide.com>
To: Joel A Fernandes <agnel.joel@gmail.com>
Cc: Linux OMAP List <linux-omap@vger.kernel.org>,
Felipe Balbi <balbi@ti.com>, Rajendra Nayak <rnayak@ti.com>
Subject: Re: MMC breakage on 3.11/cleanup
Date: Mon, 24 Jun 2013 23:49:44 -0700 [thread overview]
Message-ID: <20130625064944.GX5523@atomide.com> (raw)
In-Reply-To: <CAD=GYpZGdLem1igUsLq7DzMu-Z=9d6apS-aT=MJ59_-ytZan7w@mail.gmail.com>
* Joel A Fernandes <agnel.joel@gmail.com> [130624 15:33]:
> Hi Tony,
>
> Following branch breaks MMC for me on am33xx (beaglebone):
> http://git.kernel.org/cgit/linux/kernel/git/tmlind/linux-omap.git/log/?h=omap-for-v3.11/cleanup
>
> I tried to work around it by specifying interrupt and reg property in DT:
> mmc1: mmc@48060000 {
> compatible = "ti,omap3-hsmmc";
> ti,hwmods = "mmc1";
> ti,dual-volt;
> ti,needs-special-reset;
> dmas = <&edma 24
> &edma 25>;
> dma-names = "tx", "rx";
> interrupts = <64>;
> interrupt-parent = <&intc>;
> reg = <0x48060000 0x1000>;
> status = "disabled";
> };
>
> The probe succeeds but I still get a "Waiting for root device
> /dev/mmcblk0p2" when booting over MMC.
>
> If you're planning to push the cleanup branch, can we temporarily add
> the hwmod data back while we work on this issue so that upstream MMC
> is kept working.
Yes the cleanup branch is queued up. Can you please send a patch
reverting the MMC parts of the hwmod change for am33xx for now,
then try to find the real cause for the breakage?
Regards,
Tony
next prev parent reply other threads:[~2013-06-25 6:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 22:27 MMC breakage on 3.11/cleanup Joel A Fernandes
2013-06-25 6:26 ` Balaji T K
2013-06-25 6:31 ` Joel A Fernandes
2013-06-25 6:49 ` Tony Lindgren [this message]
2013-06-25 10:40 ` Felipe Balbi
2013-06-25 13:56 ` Joel A Fernandes
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=20130625064944.GX5523@atomide.com \
--to=tony@atomide.com \
--cc=agnel.joel@gmail.com \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.