Re: [PATCH v3 7/8] clk: rockchip: fix usbphy-related clocks

Kishon, Am Donnerstag, 19. November 2015, 22:22:28 schrieb Heiko Stuebner: > The otgphy clocks really only drive the phy blocks. These in turn > contain plls that then generate the 480m clocks the clock controller > uses to supply some other clocks like uart0, gpu or the video-codec. > > So fix t

Re: [PATCH v3 7/8] clk: rockchip: fix usbphy-related clocks

Hi, On Saturday 19 December 2015 10:51 PM, Heiko Stübner wrote: > Hi Kishon, > > Am Dienstag, 15. Dezember 2015, 16:22:32 schrieb Kishon Vijay Abraham I: >> On Friday 20 November 2015 02:52 AM, Heiko Stuebner wrote: >>> The otgphy clocks really only drive the phy blocks. These in turn >>> contain

Re: [PATCH v3 7/8] clk: rockchip: fix usbphy-related clocks

Hi Kishon, Am Dienstag, 15. Dezember 2015, 16:22:32 schrieb Kishon Vijay Abraham I: > On Friday 20 November 2015 02:52 AM, Heiko Stuebner wrote: > > The otgphy clocks really only drive the phy blocks. These in turn > > contain plls that then generate the 480m clocks the clock controller > > uses t

Re: [PATCH v3 7/8] clk: rockchip: fix usbphy-related clocks

Hi Mike, On Friday 20 November 2015 02:52 AM, Heiko Stuebner wrote: > The otgphy clocks really only drive the phy blocks. These in turn > contain plls that then generate the 480m clocks the clock controller > uses to supply some other clocks like uart0, gpu or the video-codec. > > So fix this str

[PATCH v3 7/8] clk: rockchip: fix usbphy-related clocks

The otgphy clocks really only drive the phy blocks. These in turn contain plls that then generate the 480m clocks the clock controller uses to supply some other clocks like uart0, gpu or the video-codec. So fix this structure to actually respect that hirarchy and removed that usb480m fixed-rate cl