Re: Bug in linux omap clock framework?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2008-12-11 at 09:17 -0700, ext Paul Walmsley wrote:
> Hi Jouni, Tomi, 
> 
> On Thu, 11 Dec 2008, Högander Jouni wrote:
> 
> > So it seems that cm_* register should not be written while there is
> > powerstate transition ongoing in * domain. Patch by Tomi is fixing
> > this. As it seems to be transition related rather than pwrdm state,
> > same line should be added into omap2_clkdm_clk_disable also.
> 
> Shouldn't this have also crashed the system if it needed to be done 
> in omap2_clkdm_clk_disable() ?  Perhaps we should avoid adding it there 
> until we can reproduce a crash there?
> 

Yep, I haven't seen a crash related to disabling the clock. So perhaps
it's better to just wait in enable for now. I'll resend the patch I sent
earlier.

 Tomi


--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux