[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130117122757.GO18978@arwen.pp.htv.fi>
Date: Thu, 17 Jan 2013 14:27:57 +0200
From: Felipe Balbi <balbi@...com>
To: Roger Quadros <rogerq@...com>
CC: <balbi@...com>, <sameo@...ux.intel.com>, <tony@...mide.com>,
<kishon@...com>, <sshtylyov@...sta.com>, <bjorn@...k.no>,
<linux@....linux.org.uk>, <linux-usb@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v7 15/22] mfd: omap-usb-host: Manage HSIC clocks for HSIC
mode
On Thu, Jan 17, 2013 at 02:10:18PM +0200, Roger Quadros wrote:
> On 01/17/2013 01:45 PM, Felipe Balbi wrote:
> > Hi,
> >
> > On Thu, Jan 17, 2013 at 01:30:24PM +0200, Roger Quadros wrote:
> >> @@ -598,6 +639,24 @@ static int usbhs_omap_probe(struct platform_device *pdev)
> >> clkname, PTR_ERR(pclk));
> >> else
> >> omap->utmi_clk[i] = pclk;
> >> +
> >> + snprintf(clkname, sizeof(clkname),
> >> + "usb_host_hs_hsic480m_p%d_clk", i + 1);
> >
> > do we really need to know the exact clock node name ?
> >
> I think so. Do you have a better suggestion?
update CLKDEV entries ? I mean, what if we have a new OMAP or AMxxxx
device with a different clock name ? That will be a big bummer.
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists