From: sourav <sourav.poddar@ti.com>
To: balbi@ti.com
Cc: Paul Walmsley <paul@pwsan.com>,
tony@atomide.com, zbr@ioremap.net,
michael.opdenacker@free-electrons.com, wsa@the-dreams.de,
bcousson@baylibre.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/5] arm: omap2: skip device build from platform code for dt.
Date: Tue, 29 Apr 2014 14:21:36 +0530 [thread overview]
Message-ID: <535F6818.5060406@ti.com> (raw)
In-Reply-To: <20140428183922.GV30292@saruman.home>
On Tuesday 29 April 2014 12:09 AM, Felipe Balbi wrote:
> On Mon, Apr 28, 2014 at 06:28:45PM +0000, Paul Walmsley wrote:
>> On Wed, 16 Apr 2014, Sourav Poddar wrote:
>>
>>> For SOCs with dt enabled, device should be build through device tree.
>>> Prevent device build call from platform code, if device tree is
>>> enabled.
>>>
>>> Signed-off-by: Sourav Poddar<sourav.poddar@ti.com>
>> Isn't OMAP2+ only supporting DT device enumeration now?
> At least OMAP3 still isn't Dt-only.
>
Yes, for omap3 boards only, I have kept a #ifndef. Else we could
have remove this code.
WARNING: multiple messages have this Message-ID (diff)
From: sourav.poddar@ti.com (sourav)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] arm: omap2: skip device build from platform code for dt.
Date: Tue, 29 Apr 2014 14:21:36 +0530 [thread overview]
Message-ID: <535F6818.5060406@ti.com> (raw)
In-Reply-To: <20140428183922.GV30292@saruman.home>
On Tuesday 29 April 2014 12:09 AM, Felipe Balbi wrote:
> On Mon, Apr 28, 2014 at 06:28:45PM +0000, Paul Walmsley wrote:
>> On Wed, 16 Apr 2014, Sourav Poddar wrote:
>>
>>> For SOCs with dt enabled, device should be build through device tree.
>>> Prevent device build call from platform code, if device tree is
>>> enabled.
>>>
>>> Signed-off-by: Sourav Poddar<sourav.poddar@ti.com>
>> Isn't OMAP2+ only supporting DT device enumeration now?
> At least OMAP3 still isn't Dt-only.
>
Yes, for omap3 boards only, I have kept a #ifndef. Else we could
have remove this code.
next prev parent reply other threads:[~2014-04-29 8:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 12:32 [PATCH 0/5] AM437x: HDQ/1wire protocol Sourav Poddar
2014-04-16 12:32 ` Sourav Poddar
2014-04-16 12:32 ` [PATCH 1/5] drivers: w1: omap_hdq: cleanup and bug fixes Sourav Poddar
2014-04-16 12:32 ` Sourav Poddar
2014-04-28 19:19 ` Paul Walmsley
2014-04-28 19:19 ` Paul Walmsley
2014-04-29 9:15 ` sourav
2014-04-29 9:15 ` sourav
2014-04-16 12:32 ` [PATCH 2/5] w1: omap_hdq: Add compatible property for omap hdq driver Sourav Poddar
2014-04-16 12:32 ` Sourav Poddar
2014-04-16 12:32 ` [PATCH 3/5] arm: omap2: skip device build from platform code for dt Sourav Poddar
2014-04-16 12:32 ` Sourav Poddar
2014-04-28 18:28 ` Paul Walmsley
2014-04-28 18:28 ` Paul Walmsley
2014-04-28 18:39 ` Felipe Balbi
2014-04-28 18:39 ` Felipe Balbi
2014-04-29 8:51 ` sourav [this message]
2014-04-29 8:51 ` sourav
2014-04-16 12:32 ` [PATCH 4/5] arm: dts: am4372: Add hdq device tree data Sourav Poddar
2014-04-16 12:32 ` Sourav Poddar
2014-04-16 12:32 ` [PATCH 5/5] arm: hwmod: am437x: Add hwmod data for hdq1w Sourav Poddar
2014-04-16 12:32 ` Sourav Poddar
2014-04-28 22:07 ` Paul Walmsley
2014-04-28 22:07 ` Paul Walmsley
2014-04-29 8:49 ` sourav
2014-04-29 8:49 ` sourav
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=535F6818.5060406@ti.com \
--to=sourav.poddar@ti.com \
--cc=balbi@ti.com \
--cc=bcousson@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=michael.opdenacker@free-electrons.com \
--cc=paul@pwsan.com \
--cc=tony@atomide.com \
--cc=wsa@the-dreams.de \
--cc=zbr@ioremap.net \
/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.