Hi Alexandre Belloni wrote: > Thanks for the report. This is actually a known issue (at least, I know > about it). > > I'm adding the clock framework maintainers as this is actually an issue > that affects any device exposing clocks that are on a bus using clock > operations in its transfer operations. Here, an i2c RTC, exposing clocks > and connected on an imx6. > > This has been solved by caching the registers for the m41t80 RTC, see: > > http://patchwork.ozlabs.org/project/rtc-linux/list/?series=11636&state=* > > But, I find that cumbersome and maybe something can be done in the clk > framework. I didn't check what the prepare_lock protects yet. But maybe > we can have another lock for get_rate and the like? > > Stephen, Mike, any input? Any update regarding this issue? Dave
