Thread (1 message) 1 message, 1 author, 2014-08-01

Re: [PATCH 2/2] clk: initial clock driver for TWL6030

From: Mark Brown <hidden>
Date: 2014-08-01 10:38:24
Also in: linux-arm-kernel

Possibly related (same subject, not in this thread)

On Fri, Aug 01, 2014 at 12:04:35PM +0200, Stefan Assmann wrote:
probe function doesn't even get called without the clock being
powered/enabled. I've instrumented do_one_initcall() to verify this.
With the clock being enabled I see:
[   19.693511] init/main.c do_one_initcall:792 initcall wl1271_init+0x0/0x38 [wlcore_sdio]
[   20.993347] init/main.c do_one_initcall:792 initcall wl12xx_driver_init+0x0/0x14 [wl12xx]
If the clock is kept disabled none of the calls is made and we never get
to wl12xx_probe().
The device might not be discoverable without the clock.
Maybe we should rethink the idea of doing that single register write to
enable the device in twl-core code, if the TWL6030 is present.
Alternatively this could be done by u-boot. Seems like something that
should have been done by firmware upfront.
If this is a SDIO device please search the lists for discussion on how
to handle enabling required resources for them - Ulf was working on
something generic for that.

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help