From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D2335C5AE59 for ; Tue, 10 Sep 2019 16:27:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AA74921479 for ; Tue, 10 Sep 2019 16:27:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2436700AbfIJQ1y (ORCPT ); Tue, 10 Sep 2019 12:27:54 -0400 Received: from relay12.mail.gandi.net ([217.70.178.232]:36567 "EHLO relay12.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2436494AbfIJQ1y (ORCPT ); Tue, 10 Sep 2019 12:27:54 -0400 Received: from localhost (unknown [148.69.85.38]) (Authenticated sender: alexandre.belloni@bootlin.com) by relay12.mail.gandi.net (Postfix) with ESMTPSA id A733620000D; Tue, 10 Sep 2019 16:27:51 +0000 (UTC) Date: Tue, 10 Sep 2019 18:27:48 +0200 From: Alexandre Belloni To: David =?iso-8859-1?Q?M=FCller_=28ELSOFT_AG=29?= Cc: Stephen Boyd , linux-rtc@vger.kernel.org, Michael Turquette , linux-clk@vger.kernel.org Subject: Re: rtc-pcf8563: circular locking dependency Message-ID: <20190910162748.GA21254@piout.net> References: <20171206101906.GN21780@piout.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-clk-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org Hello, On 22/12/2017 14:19:47+0100, David Müller (ELSOFT AG) wrote: > 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? > I believe this issue has been solved by 90ad2cbe88c2 ("i2c: imx: use clk notifier for rate changes"). > > Dave -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com