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 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
