On 15.03.2016 03:07, David Lechner wrote:
On 03/14/2016 02:00 AM, Felipe Balbi wrote:
Hi,
why isn't this an actual clock phandle ? Driver could, then, use
clk_get_rate() to figure this one out. You could just use a fixed clock
here to satisfy the clock API.
I've actually been working on getting the da8xx ohci driver working
with device tree. It has similar clock issues (in fact, the ohci clock
is a child of the musb clock). Petr, give me a day or two and will
have post some patches. It will have a clock that can be used here for
clk_get_rate().
Hi David,
I'm trying to move on with my USB2.0 patch set because my projects is
blocked waiting for it.
I've seen your PHY patch but it contains only on/off functions and does
not handle the clocks, which IMHO should be moved to the PHY driver as
well if we decided to do it properly.
How shall we proceed if both of us are working on the same piece of code?
Thanks
Petr
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html