From: Felipe Balbi <balbi@ti.com>
To: Joel A Fernandes <agnel.joel@gmail.com>
Cc: "Hiremath, Vaibhav" <hvaibhav@ti.com>,
Linux OMAP List <linux-omap@vger.kernel.org>,
Russell King <linux@arm.linux.org.uk>,
"Krishnamoorthy, Balaji T" <balajitk@ti.com>,
Devicetree Discuss <devicetree-discuss@lists.ozlabs.org>,
Linux MMC List <linux-mmc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chris Ball <cjb@laptop.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] ARM: dts: add AM33XX MMC support
Date: Sat, 15 Jun 2013 01:26:31 +0300 [thread overview]
Message-ID: <20130614222537.GA25428@arwen.pp.htv.fi> (raw)
In-Reply-To: <CAD=GYpb3+nvoz863+VKO7iJijRHnM5RzsVj-5VJfQ-OHoUy19Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
Hi,
On Fri, Jun 14, 2013 at 02:54:33PM -0500, Joel A Fernandes wrote:
> Hi Tony, Vaibhav,
>
> >> I just doublechecked MMC rootfs on bone and evmsk as it's the standard
> >> smoke test. My EVM is intermittent now so trying to coax it to power up
> >> to reverify.
> >>
> >
> > Matt,
> >
> > Your branch is working for me, I tested it on EVM. Not sure what is wrong with manual rebasing
> > I did yesterday. I will try to nail-down root-cause here.
> >
> > And you can submit the next version fixing the comments I have given.
>
> The only comment I could find in the whole discussion was adding of
> the interrupts property. I tested I don't have any problem booting
> with Matt's patch, without having the interrupts property.
might very well be, but we want to figure out why adding "intrrupts"
causes issues. Why does it have to come through hwmod ? You might have
uncovered a real problem which needs fixing. Besides, at the end of the
day, we want to remove the redundant hwmod data if we already have DTS
bindings covering the same requirements.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-14 22:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 4:16 [PATCH 0/2] AM33xx mmc support Matt Porter
2013-03-07 4:16 ` [PATCH 1/2] mmc: omap_hsmmc: set max_segs based on dma engine limits Matt Porter
2013-03-07 4:16 ` [PATCH 2/2] ARM: dts: add AM33XX MMC support Matt Porter
2013-03-07 5:29 ` Hiremath, Vaibhav
[not found] ` <41fde401c8e646689123d7c6d3a2dffc@DLEE71.ent.ti.com>
2013-03-07 14:12 ` Matt Porter
2013-03-07 14:39 ` Hiremath, Vaibhav
2013-03-07 14:46 ` Matt Porter
2013-03-07 14:51 ` Matt Porter
2013-03-07 14:53 ` Hiremath, Vaibhav
2013-03-07 15:00 ` Matt Porter
2013-03-07 15:03 ` Hiremath, Vaibhav
2013-03-07 14:59 ` Hiremath, Vaibhav
2013-03-07 15:04 ` Matt Porter
2013-03-07 15:50 ` Hiremath, Vaibhav
2013-03-07 16:02 ` Matt Porter
2013-03-08 12:29 ` Hiremath, Vaibhav
2013-06-14 19:54 ` Joel A Fernandes
2013-06-14 22:26 ` Felipe Balbi [this message]
[not found] ` <CAD=GYpYfMAZeV1RUC=DqhYGZaKiiukpTZg7bhO582eKwimS9aA@mail.gmail.com>
2013-06-15 7:23 ` Joel A Fernandes
2013-06-15 15:05 ` Felipe Balbi
2013-06-17 6:20 ` Tony Lindgren
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=20130614222537.GA25428@arwen.pp.htv.fi \
--to=balbi@ti.com \
--cc=agnel.joel@gmail.com \
--cc=balajitk@ti.com \
--cc=cjb@laptop.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®