devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Joel A Fernandes <agnel.joel@gmail.com>
Cc: Chris Ball <cjb@laptop.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>,
	"Hiremath, Vaibhav" <hvaibhav@ti.com>,
	"balbi@ti.com" <balbi@ti.com>,
	Linux OMAP List <linux-omap@vger.kernel.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 18:05:01 +0300	[thread overview]
Message-ID: <20130615150500.GA27629@arwen.pp.htv.fi> (raw)
In-Reply-To: <CAD=GYpYfMAZeV1RUC=DqhYGZaKiiukpTZg7bhO582eKwimS9aA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1866 bytes --]

Hi,

On Fri, Jun 14, 2013 at 06:43:51PM -0500, Joel A Fernandes wrote:
> > > >> 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.

fair enough, then let's just add those interrupts to hwmod which will,
eventually, let us drop all of that data from hwmod.

cheers

-- 
balbi

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2013-06-15 15:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07  4:16 [PATCH 0/2] AM33xx mmc support Matt Porter
     [not found] ` <1362629799-22485-1-git-send-email-mporter-l0cyMroinI0@public.gmane.org>
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
     [not found]   ` <1362629799-22485-3-git-send-email-mporter-l0cyMroinI0@public.gmane.org>
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
     [not found]                         ` <20130614222537.GA25428-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-06-14 23:43                           ` Joel A Fernandes
     [not found]                             ` <CAD=GYpYfMAZeV1RUC=DqhYGZaKiiukpTZg7bhO582eKwimS9aA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-15  7:23                               ` Joel A Fernandes
2013-06-15 15:05                             ` Felipe Balbi [this message]
     [not found]                               ` <20130615150500.GA27629-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
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=20130615150500.GA27629@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;
as well as URLs for NNTP newsgroup(s).