Re: [PATCH 0/4] Add support for Exynos clock output configuration

[Daniel Drake]

Hi Tomasz,

On Tue, May 20, 2014 at 5:43 PM, Tomasz Figa <t.figa@xxxxxxxxxxx> wrote:
> Since the block responsible for handling the pin is PMU, not CMU,
> a separate driver, that binds to PMU node is required and acquires
> all input clocks by standard DT clock look-up. This way we don't need
> any cross-IP block drivers and cross-driver register sharing or
> nodes for fake devices.
>
> To represent the PMU mux/gate clock, generic composite clock is registered.
>
> Tested on Odroid U3, with HSIC/USB hub using CLKOUT as reference clock,
> with some additional patches.
>
> Depends on:
> [PATCHv5 0/4] Enable usbphy and hsotg for exynos4
> (No link, sorry, I could not find it in any archive yet...)
> for Exynos4210/4x12 PMU binding and DT nodes.

This isn't working for me.
Testing linus master e99cfa2d0634881b8a41d56c48b5956b9a3ba162 plus:
    ARM: dts: exynos4: add port sub-nodes to exynos usb host modules
    ARM: dts: exynos4412-odroidx: enable common hardware blocks
    ARM: dts: exynos4412-odroidx: add support for USB (phy, host, device)
    ARM: dts: refactor Odroid DTS file and add support for Odroid X2 and U2/U3

Testing on ODROID-U2.

I apply the first patch here (clk: samsung: exynos4: Add missing
CPU/DMC clock hierarchy) and things continue to work. Now when I add
the second patch "clk: samsung: exynos4: Add CLKOUT clock hierarchy"
boot hangs at:

[    4.753740] s3c-rtc 10070000.rtc: setting system clock to
2000-01-01 02:43:30 UTC (946694610)
[    4.753809] ### dt-test ### No testcase data in device tree; not
running tests
[    4.791155] gps-power-domain: Power-off latency e

Any ideas?
Thanks
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/