devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Archit Taneja <archit@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Andy Gross <andy.gross@ti.com>,
	linux-omap@vger.kernel.org, Benoit Cousson <b-cousson@ti.com>,
	devicetree-discuss@lists.ozlabs.org, Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH 2/2] ARM: OMAP2+: Remove dmm device creation
Date: Wed, 20 Mar 2013 11:46:33 +0530	[thread overview]
Message-ID: <51495441.1000606@ti.com> (raw)
In-Reply-To: <51494F89.4050308@ti.com>

On Wednesday 20 March 2013 11:26 AM, Santosh Shilimkar wrote:
> On Wednesday 20 March 2013 10:13 AM, Andy Gross wrote:
>> Remove DMM device creation via the hwmod entry.  The DMM device will
>> now be enumerated as part of the device tree information for the
>> processor.
>>
>> Signed-off-by: Andy Gross <andy.gross@ti.com>
>> ---
> OMAP4 is still not made DT only so I suggest you to hold on for this patch
> till that happens.

Wouldn't we need to at least prevent building the platform device using 
omap_device_build() when we are using DT?

Archit

>
> Regards,
> Santosh
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>


  reply	other threads:[~2013-03-20  6:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20  4:43 [PATCH 0/2] ARM: dts: OMAP4+: Add dmm device bindings Andy Gross
2013-03-20  4:43 ` [PATCH 1/2] ARM: dts: OMAP4+: Add DMM bindings Andy Gross
2013-03-20  5:59   ` Santosh Shilimkar
2013-03-20  4:43 ` [PATCH 2/2] ARM: OMAP2+: Remove dmm device creation Andy Gross
2013-03-20  5:56   ` Santosh Shilimkar
2013-03-20  6:16     ` Archit Taneja [this message]
2013-03-20  6:22       ` Santosh Shilimkar
2013-03-20  6:28         ` Gross, Andy

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=51495441.1000606@ti.com \
    --to=archit@ti.com \
    --cc=andy.gross@ti.com \
    --cc=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=santosh.shilimkar@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 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).