From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: rtc-pcf8563: circular locking dependency To: Alexandre Belloni Cc: Stephen Boyd , linux-rtc@vger.kernel.org, Michael Turquette , linux-clk@vger.kernel.org References: <20171206101906.GN21780@piout.net> From: =?UTF-8?Q?David_M=c3=bcller_=28ELSOFT_AG=29?= Message-ID: Date: Fri, 22 Dec 2017 14:19:47 +0100 MIME-Version: 1.0 In-Reply-To: <20171206101906.GN21780@piout.net> Content-Type: text/plain; charset=UTF-8 List-ID: 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