From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH v2 0/4] OMAP serial device tree support Date: Mon, 28 Nov 2011 07:44:15 -0600 Message-ID: <4ED3902F.7080801@gmail.com> References: <1321969456-24266-1-git-send-email-rnayak@ti.com> <20111127033642.GA28378@kroah.com> <4ED32500.5060908@ti.com> <20111128063149.GB15189@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mail-yw0-f46.google.com ([209.85.213.46]:52829 "EHLO mail-yw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750876Ab1K1NoT (ORCPT ); Mon, 28 Nov 2011 08:44:19 -0500 In-Reply-To: <20111128063149.GB15189@kroah.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Greg KH Cc: Rajendra Nayak , 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 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: robherring2@gmail.com (Rob Herring) Date: Mon, 28 Nov 2011 07:44:15 -0600 Subject: [PATCH v2 0/4] OMAP serial device tree support In-Reply-To: <20111128063149.GB15189@kroah.com> References: <1321969456-24266-1-git-send-email-rnayak@ti.com> <20111127033642.GA28378@kroah.com> <4ED32500.5060908@ti.com> <20111128063149.GB15189@kroah.com> Message-ID: <4ED3902F.7080801@gmail.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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