From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nishanth Menon Subject: Re: [PATCH v2 3/8] ARM: DRA7: Reuse all of PRCM and MPUSS SMP infra Date: Tue, 30 Jul 2013 07:41:39 -0500 Message-ID: <51F7B483.8060908@ti.com> References: <1375183546-12758-1-git-send-email-rnayak@ti.com> <1375183546-12758-4-git-send-email-rnayak@ti.com> <51F7B100.2020600@ti.com> <51F7B3E0.9020005@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from devils.ext.ti.com ([198.47.26.153]:40459 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752783Ab3G3MmF (ORCPT ); Tue, 30 Jul 2013 08:42:05 -0400 In-Reply-To: <51F7B3E0.9020005@ti.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Rajendra Nayak Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, tony@atomide.com, paul@pwsan.com, khilman@linaro.org, benoit.cousson@gmail.com, r.sricharan@ti.com, ambresh@ti.com, sourav.poddar@ti.com On 07/30/2013 07:38 AM, Rajendra Nayak wrote: > On Tuesday 30 July 2013 05:56 PM, Nishanth Menon wrote: >> On 07/30/2013 06:25 AM, Rajendra Nayak wrote: >>> From: R Sricharan >> [...] >>> # Clock framework >>> obj-$(CONFIG_ARCH_OMAP2) += $(clock-common) clock2xxx.o >>> @@ -181,6 +187,8 @@ obj-$(CONFIG_SOC_AM33XX) += $(clock-common) dpll3xxx.o >>> obj-$(CONFIG_SOC_AM33XX) += cclock33xx_data.o >>> obj-$(CONFIG_SOC_OMAP5) += $(clock-common) >>> obj-$(CONFIG_SOC_OMAP5) += dpll3xxx.o dpll44xx.o >>> +obj-$(CONFIG_SOC_DRA7XX) += $(clock-common) >>> +obj-$(CONFIG_SOC_DRA7XX) += dpll3xxx.o dpll44xx.o >>> >> >> are these in sync with DRA7 support being introduced for clock data in [1]? > > I don't want to have a dependency on those patches since I am not sure of them > making it into 3.12. Then we have to undo these changes again in clock data support. the chip wont bootup anyways without clock data information, so why not try and keep the changes that Tero is doing independent of these changes? > >> >> >> [1] http://marc.info/?l=linux-omap&m=137456411706971&w=2 >> > -- Regards, Nishanth Menon From mboxrd@z Thu Jan 1 00:00:00 1970 From: nm@ti.com (Nishanth Menon) Date: Tue, 30 Jul 2013 07:41:39 -0500 Subject: [PATCH v2 3/8] ARM: DRA7: Reuse all of PRCM and MPUSS SMP infra In-Reply-To: <51F7B3E0.9020005@ti.com> References: <1375183546-12758-1-git-send-email-rnayak@ti.com> <1375183546-12758-4-git-send-email-rnayak@ti.com> <51F7B100.2020600@ti.com> <51F7B3E0.9020005@ti.com> Message-ID: <51F7B483.8060908@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 07/30/2013 07:38 AM, Rajendra Nayak wrote: > On Tuesday 30 July 2013 05:56 PM, Nishanth Menon wrote: >> On 07/30/2013 06:25 AM, Rajendra Nayak wrote: >>> From: R Sricharan >> [...] >>> # Clock framework >>> obj-$(CONFIG_ARCH_OMAP2) += $(clock-common) clock2xxx.o >>> @@ -181,6 +187,8 @@ obj-$(CONFIG_SOC_AM33XX) += $(clock-common) dpll3xxx.o >>> obj-$(CONFIG_SOC_AM33XX) += cclock33xx_data.o >>> obj-$(CONFIG_SOC_OMAP5) += $(clock-common) >>> obj-$(CONFIG_SOC_OMAP5) += dpll3xxx.o dpll44xx.o >>> +obj-$(CONFIG_SOC_DRA7XX) += $(clock-common) >>> +obj-$(CONFIG_SOC_DRA7XX) += dpll3xxx.o dpll44xx.o >>> >> >> are these in sync with DRA7 support being introduced for clock data in [1]? > > I don't want to have a dependency on those patches since I am not sure of them > making it into 3.12. Then we have to undo these changes again in clock data support. the chip wont bootup anyways without clock data information, so why not try and keep the changes that Tero is doing independent of these changes? > >> >> >> [1] http://marc.info/?l=linux-omap&m=137456411706971&w=2 >> > -- Regards, Nishanth Menon