[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56E9A01B.3010503@cogentembedded.com>
Date: Wed, 16 Mar 2016 21:04:11 +0300
From: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To: David Lechner <david@...hnology.com>, Sekhar Nori <nsekhar@...com>,
Kevin Hilman <khilman@...nel.org>,
Alan Stern <stern@...land.harvard.edu>, Bin Liu <b-liu@...com>,
Petr Kulhavy <petr@...ix.com>
Cc: Russell King <linux@....linux.org.uk>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Felipe Balbi <balbi@...nel.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-usb@...r.kernel.org
Subject: Re: [PATCH 2/5] ARM: davinci: da8xx: add usb phy clocks
On 03/16/2016 08:58 PM, David Lechner wrote:
>>> +static struct clk usb20_clk = {
>>> + .name = "usb20",
>>> + .parent = &pll0_sysclk2,
>>> + .lpsc = DA8XX_LPSC1_USB20,
>>> + .gpsc = 1,
>>> +};
>>
>> Why move it?
>
> For organization, to keep all of the USB clocks together. I can leave it alone
> if that is preferred.
I'd prefer to minimize the noise...
>>> +
>>> + /* Set the mux depending on the parent clock. */
>>> + if (clk->parent == &pll0_aux_clk)
>>> + val |= CFGCHIP2_USB2PHYCLKMUX;
>>> + else if (clk->parent == &usb_ref_clk)
>>> + val &= ~CFGCHIP2_USB2PHYCLKMUX;
>>
>> Don't we have clk_set_parent()for that?
>
> Yes. clk_set_parent() is already called in a loop for all clocks elsewhere, so
> not needed here.
No, I mean why is not this implemented as a part of clk_set_parent()?
MBR, Sergei
Powered by blists - more mailing lists