Linux-RTC Archive on lore.kernel.org
 help / color / Atom feed
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: "David Müller (ELSOFT AG)" <d.mueller@elsoft.ch>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
	linux-rtc@vger.kernel.org,
	Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org
Subject: Re: rtc-pcf8563: circular locking dependency
Date: Tue, 10 Sep 2019 18:27:48 +0200
Message-ID: <20190910162748.GA21254@piout.net> (raw)
In-Reply-To: <a4d1f4f1-37e9-dbc8-72bf-024c1e4e70df@elsoft.ch>

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

      reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 14:14 David Müller (ELSOFT AG)
2017-12-06 10:19 ` Alexandre Belloni
2017-12-22 13:19   ` David Müller (ELSOFT AG)
2019-09-10 16:27     ` Alexandre Belloni [this message]

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190910162748.GA21254@piout.net \
    --to=alexandre.belloni@free-electrons.com \
    --cc=d.mueller@elsoft.ch \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-RTC Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-rtc/0 linux-rtc/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-rtc linux-rtc/ https://lore.kernel.org/linux-rtc \
		linux-rtc@vger.kernel.org linux-rtc@archiver.kernel.org
	public-inbox-index linux-rtc


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-rtc


AGPL code for this site: git clone https://public-inbox.org/ public-inbox