From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Sricharan R <r.sricharan@ti.com>,
Sourav Poddar <sourav.poddar@ti.com>,
bcousson@baylibre.com, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, "Nayak,
Rajendra" <rnayak@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [Resend/PATCH] arm: dts: dra7: Add qspi device.
Date: Mon, 16 Jun 2014 03:41:26 -0700 [thread overview]
Message-ID: <20140616104126.GC17845@atomide.com> (raw)
In-Reply-To: <538884C4.5070304@ti.com>
* Nishanth Menon <nm@ti.com> [140530 06:19]:
> On 05/30/2014 06:34 AM, Sricharan R wrote:
> > Hi,
> >
> > On Tuesday 06 May 2014 10:22 PM, Tony Lindgren wrote:
> >> * Sourav Poddar <sourav.poddar@ti.com> [140506 04:08]:
> >>> These add device tree entry for qspi controller driver on dra7-evm.
> >> Thanks applying into omap-for-v3.16/dt.
> > There is a problem with this. The qspi node defines crossbar number
> > as its interrupt number. Since the crossbar dts patches are not yet
> > there, this causes a warning during boot. So interrupts = < >
> > property should be removed from DT and added later by crossbar series.
> >
>
> https://github.com/nmenon/kernel-test-logs/blob/next-20140530/omap2plus_defconfig/dra7.txt#L151
> as an indication of the warning.
>
> Tony,
> Would you prefer a patch on top of omap-for-v3.16/dt-v2 branch?
Sorting through my mailbox.. If this is still an issue a
fix against v3.16-rc1 please.
Regards,
Tony
prev parent reply other threads:[~2014-06-16 10:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 11:07 [Resend/PATCH] arm: dts: dra7: Add qspi device Sourav Poddar
2014-05-06 11:07 ` Sourav Poddar
2014-05-06 16:52 ` Tony Lindgren
2014-05-30 11:34 ` Sricharan R
2014-05-30 11:34 ` Sricharan R
2014-05-30 13:16 ` Nishanth Menon
2014-05-30 13:16 ` Nishanth Menon
2014-06-16 10:41 ` 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=20140616104126.GC17845@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=r.sricharan@ti.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=sourav.poddar@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.