From: "Noralf Trønnes" <noralf@tronnes.org>
To: Maxime Ripard <maxime@cerno.tech>,
Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: linux-clk@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
Stefan Wahren <stefan.wahren@i2se.com>,
linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH] clk: bcm2835: Make peripheral PLLC critical
Date: Mon, 26 Sep 2022 16:51:54 +0200 [thread overview]
Message-ID: <61777940-b892-1e39-d9f1-4af9d3b31e4b@tronnes.org> (raw)
In-Reply-To: <20220926084509.12233-1-maxime@cerno.tech>
Den 26.09.2022 10.45, skrev Maxime Ripard:
> When testing for a series affecting the VEC, it was discovered that
> turning off and on the VEC clock is crashing the system.
>
> It turns out that, when disabling the VEC clock, it's the only child of
> the PLLC-per clock which will also get disabled. The source of the crash
> is PLLC-per being disabled.
>
> It's likely that some other device might not take a clock reference that
> it actually needs, but it's unclear which at this point. Let's make
> PLLC-per critical so that we don't have that crash.
>
> Reported-by: Noralf Trønnes <noralf@tronnes.org>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
> ---
Acked-by: Noralf Trønnes <noralf@tronnes.org>
next prev parent reply other threads:[~2022-09-26 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 8:45 [PATCH] clk: bcm2835: Make peripheral PLLC critical Maxime Ripard
2022-09-26 10:55 ` Stefan Wahren
2022-09-26 14:51 ` Noralf Trønnes [this message]
2022-09-30 21:28 ` Stephen Boyd
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=61777940-b892-1e39-d9f1-4af9d3b31e4b@tronnes.org \
--to=noralf@tronnes.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=maxime@cerno.tech \
--cc=mturquette@baylibre.com \
--cc=rjui@broadcom.com \
--cc=sboyd@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.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.