Hi,
On 04/11/2013 08:52 PM, Mike Turquette wrote:
[...]
So, you enable CFF, it provides its own clk_* implementation like
clk_get_rate() etc. Now, PXA already has it defined in
arch/arm/mach-pxa/clock.c. Don't think this is going to fly.
agree.
Hi,
I came into this thread late and don't have the actual patches in my
inbox for review. That said, I don't understand why V4L2 cares about
the clk framework *implementation*? The clk.h api is the same for
platforms using the common struct clk and those still using the legacy
method of defining their own struct clk. If drivers are only consumers
of the clk.h api then the implementation underneath should not matter.
I came to similar conclusions previously, but in case when one of the two
drivers is the clock provider I think there is still an issue there.
The drivers are supposed to be platform agnostic, but the clock provider
would have to include mach specific declarations of struct clk, wouldn't
it ?
Regards,
Sylwester
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
