From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nishanth Menon Subject: Re: Linux kernel for OMAP5432 uEVM Date: Tue, 30 Jul 2013 08:09:19 -0500 Message-ID: <51F7BAFF.3080805@ti.com> References: <20130730033808.GA23486@cbz-workstation> <51F7387B.9060304@ti.com> <51F7B08C.1070200@ti.com> <83487AF3-0B91-4492-8B1E-C858972B541E@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from arroyo.ext.ti.com ([192.94.94.40]:40131 "EHLO arroyo.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755118Ab3G3NJU (ORCPT ); Tue, 30 Jul 2013 09:09:20 -0400 In-Reply-To: <83487AF3-0B91-4492-8B1E-C858972B541E@gmail.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Chen Baozi Cc: Lokesh Vutla , linux-omap@vger.kernel.org On 07/30/2013 07:44 AM, Chen Baozi wrote: > > On Jul 30, 2013, at 8:24 PM, Nishanth Menon wrote: > >> On 07/30/2013 01:07 AM, Chen Baozi wrote: >>> >>> On Jul 30, 2013, at 11:52 AM, Lokesh Vutla wrote: >>> >>>> Hi Chen, >>>> On Tuesday 30 July 2013 09:08 AM, Chen Baozi wrote: >>>>> Hi all, >>>>> >>>>> I'm trying to boot my OMAP5432 uEVM devboard with the lastest kernel of >>>>> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git. >>>> Which branch are you using ? >>> >>> the master branch. >>> >>>>> However, after u-boot loading uImage & DTB, there is no output message any >>>>> more, such as: >>>> Clk data might be missing here. Try merging the below branch and test it >>>> https://git.kernel.org/cgit/linux/kernel/git/ssantosh/linux.git/log/?h=for_3.11/out_of_tree/omap5_clk_data >>> >>> Thanks, I'll have a try. >> >> There is also clock data dts support now in Tero's series: >> http://marc.info/?l=linux-omap&m=137456411706971&w=2 > > Thanks, I'll have a look though Lokesh's suggestion has already booted my board. > > Might be a stupid question. What's the different functionality between these two series of patch set? For it seems clk data patches have done the some of initialization that make the system boot. two different approaches - one using clock data in kernel, other with clock data in dtb and generic clock drivers. Tero's approach is what is being massaged for upstream as we do not wish to add additional clock data into kernel source tree anymore. -- Regards, Nishanth Menon