[PATCH 2/2] ARM: dts: add AM33XX MMC support

Joel A Fernandes agnel.joel at gmail.com
Sat Jun 15 09:43:51 EST 2013


Felipe,

On Friday, June 14, 2013, Felipe Balbi wrote:

> 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


No actually I think I wasn't very descriptive in my post. There is no
problem here. Whether it comes from DT or not, it works in both cases . (I
haven't tried adding interrupt node to dts but what I gathered from
Vaibhav's post is that it works also when added to dts)

But I can revisit Vaibhav's suggestion of adding it to dts for completeness
sake. My tree currently works and picks up the interrupt info from hwmod. I
just didn't see any activity on this thread for a while so I thought of
enquiring it was ok to pull it in for the 3.11 merge window or if the
consensus was that interrupt node be added to dts even though it works
without it.

Thanks,

-Joel


> day, we want to remove the redundant hwmod data if we already have DTS
> bindings covering the same requirements.
> --
> balbi
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/devicetree-discuss/attachments/20130614/d2614673/attachment.html>


More information about the devicetree-discuss mailing list