From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roger Quadros Subject: Re: how to specify an OMAP clock in device tree? Date: Tue, 5 Feb 2013 16:29:13 +0200 Message-ID: <51111739.2050805@ti.com> References: <1359993540-20780-1-git-send-email-rogerq@ti.com> <1359993540-20780-12-git-send-email-rogerq@ti.com> <5110D229.1000808@ti.com> <5110E9C4.9000301@ti.com> <51110D4B.50904@ti.com> <51111371.6050502@ti.com> <511114C1.4050809@ti.com> <5111157D.7040803@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5111157D.7040803@ti.com> Sender: linux-omap-owner@vger.kernel.org To: Rajendra Nayak Cc: tony@atomide.com, b-cousson@ti.com, balbi@ti.com, stern@rowland.harvard.edu, linux@arm.linux.org.uk, linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, paul@pwsan.com List-Id: devicetree@vger.kernel.org On 02/05/2013 04:21 PM, Rajendra Nayak wrote: > On Tuesday 05 February 2013 07:48 PM, Roger Quadros wrote: >> On 02/05/2013 04:13 PM, Rajendra Nayak wrote: >>> On Tuesday 05 February 2013 07:16 PM, Roger Quadros wrote: >>>> Fixing the device name doesn't really solve the problem. >>>> Not all OMAP boards will use the same clock for the external device. >>> >>> Are you saying different OMAP boards will use different Internal clocks? >>> Or different OMAP boards will use a single Internal clock or an >>> external one. >>> >> All I was saying is that one board can use for example auxclk1 whereas another >> one can use auxclk3, both generated by OMAP for the same PHY configuration. > > Ok, so lets keep DT aside for a while. How would something like this > work in a non-DT world? Would the driver then be able to do a > clk_get(dev, "main_clk"); and get say auxclk1 on one board and > auxclk3 on another? > Yes, all you need to do is specify an alias to the clock in the board file. e.g. in board 1 file clk_add_alias("main_clk", "phy.1", "auxclk1_ck", NULL); in board 2 file clk_add_alias("main_clk", "phy.1", "auxclk3_ck", NULL); cheers, -roger