From: Stephen Boyd <sboyd@kernel.org>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-kernel@vger.kernel.org,
Michał Mirosław <mirq-linux@rere.qmqm.pl>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clk: at91: fix possible deadlock
Date: Mon, 16 Dec 2019 09:57:39 -0800 [thread overview]
Message-ID: <20191216175740.33577205ED@mail.kernel.org> (raw)
In-Reply-To: <20191128102531.817549-1-alexandre.belloni@bootlin.com>
Quoting Alexandre Belloni (2019-11-28 02:25:31)
> Lockdep warns about a possible circular locking dependency because using
> syscon_node_to_regmap() will make the created regmap get and enable the
> first clock it can parse from the device tree. This clock is not needed to
> access the registers and should not be enabled at that time.
>
> Use the recently introduced device_node_to_regmap to solve that as it looks
> up the regmap in the same list but doesn't care about the clocks.
>
> Reported-by: Micha\u0142 Miros\u0142aw <mirq-linux@rere.qmqm.pl>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> ---
Applied to clk-fixes
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-12-16 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 14:54 AT91: sama5d2: lockdep splat in sama5d2_pmc_of_clk_init_driver() Michał Mirosław
2019-07-26 14:54 ` Michał Mirosław
2019-11-27 17:19 ` Alexandre Belloni
2019-11-27 17:19 ` Alexandre Belloni
2019-11-28 10:25 ` [PATCH] clk: at91: fix possible deadlock Alexandre Belloni
2019-11-28 10:25 ` Alexandre Belloni
2019-11-28 13:58 ` Michał Mirosław
2019-11-28 13:58 ` Michał Mirosław
2019-12-16 17:57 ` Stephen Boyd [this message]
Reply instructions:
You may reply publicly 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=20191216175740.33577205ED@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=mturquette@baylibre.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.