devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Rajendra Nayak <rnayak@ti.com>,
	linux-serial@vger.kernel.org, linux-omap@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org, tony@atomide.com,
	khilman@ti.com, govindraj.raja@ti.com, b-cousson@ti.com,
	linux-arm-kernel@lists.infradead.org,
	linaro-dev@lists.linaro.org, patches@linaro.org
Subject: Re: [PATCH v2 0/4] OMAP serial device tree support
Date: Mon, 28 Nov 2011 07:44:15 -0600	[thread overview]
Message-ID: <4ED3902F.7080801@gmail.com> (raw)
In-Reply-To: <20111128063149.GB15189@kroah.com>

On 11/28/2011 12:31 AM, Greg KH wrote:
> On Mon, Nov 28, 2011 at 11:36:56AM +0530, Rajendra Nayak wrote:
>> On Sunday 27 November 2011 09:06 AM, Greg KH wrote:
>>> On Tue, Nov 22, 2011 at 07:14:12PM +0530, Rajendra Nayak wrote:
>>>> v2 is based on the latest omap-serial runtime patches, which
>>>> can be found here[1]
>>>>
>>>> The series passes minimal data that allows serial console
>>>> boot, with UART's initialised from device tree.
>>>> However some of low power support for UART and remote
>>>> wakeup needs more work.
>>>> Boot tested on OMAP4 panda and OMAP4 sdp boards.
>>>>
>>>> Patches can be found here..
>>>> git://gitorious.org/omap-pm/linux.git for-dt/serial
>>>
>>> What tree are these going to go through, some device tree one, or do you
>>> want me to take the serial driver patches?
>>
>> Hi Greg,
>>
>> These patches have a dependency on the omap-serial runtime series.
>> So once that makes it in, through the serial driver tree, and once we
>> have the necessary Acks from the Device Tree maintainers on the relevant
>> patches from this series, these could go through the serial driver tree
>> as well.
> 
> Then all of these should probably go through the device tree tree.

Generally, DT related driver changes go in thru the respective driver trees.

Rob

      reply	other threads:[~2011-11-28 13:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 13:44 [PATCH v2 0/4] OMAP serial device tree support Rajendra Nayak
     [not found] ` <1321969456-24266-1-git-send-email-rnayak-l0cyMroinI0@public.gmane.org>
2011-11-22 13:44   ` [PATCH v2 1/4] omap-serial: Get rid of all pdev->id usage Rajendra Nayak
2011-11-22 13:44   ` [PATCH v2 3/4] omap-serial: Add minimal device tree support Rajendra Nayak
2011-11-28 13:39     ` Rob Herring
2011-11-29  7:04       ` Rajendra Nayak
2011-11-22 13:44   ` [PATCH v2 4/4] ARM: omap: pass minimal SoC/board data for UART from dt Rajendra Nayak
2011-11-28 13:40     ` Rob Herring
2011-11-22 13:44 ` [PATCH v2 2/4] omap-serial: Use default clock speed (48Mhz) if not specified Rajendra Nayak
2011-11-27  3:36 ` [PATCH v2 0/4] OMAP serial device tree support Greg KH
2011-11-28  6:06   ` Rajendra Nayak
2011-11-28  6:31     ` Greg KH
2011-11-28 13:44       ` Rob Herring [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=4ED3902F.7080801@gmail.com \
    --to=robherring2@gmail.com \
    --cc=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=govindraj.raja@ti.com \
    --cc=greg@kroah.com \
    --cc=khilman@ti.com \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=rnayak@ti.com \
    --cc=tony@atomide.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).