From mboxrd@z Thu Jan  1 00:00:00 1970
From: me@felipebalbi.com (Felipe Balbi)
Date: Wed, 30 Dec 2009 15:46:43 +0200
Subject: [patch-v2.6.34 7/9] usb: musb: use only clk framework for clk
	handling
In-Reply-To: <4B3B58F0.2070903@ru.mvista.com>
References: <1262127567-15202-1-git-send-email-felipe.balbi@nokia.com>
	<1262127567-15202-8-git-send-email-felipe.balbi@nokia.com>
	<4B3B3720.9070205@ru.mvista.com> <1262174012.28789.178.camel@gandalf>
	<4B3B504B.4020602@ru.mvista.com> <1262178881.17250.1.camel@gandalf>
	<4B3B54E1.9010600@ru.mvista.com> <1262179795.17250.7.camel@gandalf>
	<4B3B58F0.2070903@ru.mvista.com>
Message-ID: <1262180803.17250.9.camel@gandalf>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

Hi,

On Wed, 2009-12-30 at 16:43 +0300, Sergei Shtylyov wrote:
> > /*
> >  * Find the correct struct clk for the device and connection ID.
> >  * We do slightly fuzzy matching here:
> >  *  An entry with a NULL ID is assumed to be a wildcard.
> >  *  If an entry has a device ID, it must match
> >  *  If an entry has a connection ID, it must match
> >  * Then we take the most specific entry - with the following
> >  * order of precidence: dev+con > dev only > con only.
> >  */
> >
> > and then we have found our clock :-)
> 
>    Hm, you're right, I haven't completely followed the logic there... in 
> any case, specifying con_id wasn't really needed.

good we've sorted things out. Want me to send a patch for the device id
to davinci tree or can you take care of that ?

I have a for-kevin branch with a few patches I'll send to davinci tree
so I could add the device id patch there.

-- 
balbi