From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: linux-amlogic@lists.infradead.org, jbrunet@baylibre.com,
narmstrong@baylibre.com, linux-clk@vger.kernel.org
Cc: khilman@baylibre.com, carlo@caione.org, sboyd@codeaurora.org,
mturquette@baylibre.com, linux-arm-kernel@lists.infradead.org,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: [PATCH 0/1] mark clk81 as critical on Meson8b
Date: Thu, 4 May 2017 20:32:00 +0200 [thread overview]
Message-ID: <20170504183201.13175-1-martin.blumenstingl@googlemail.com> (raw)
The GX (gxbb.c) clock controller driver already marks the clk81 clock
as criticial. However, the Meson8b clock controller driver does not do
this yet.
This can lead to a freeze of the whole system when clk81 is disabled
by the common clock framework (for example after the last child clock
is disabled by a driver which used that child clock).
Martin Blumenstingl (1):
clk: meson: meson8b: mark clk81 as critical
drivers/clk/meson/meson8b.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.12.2
WARNING: multiple messages have this Message-ID (diff)
From: martin.blumenstingl@googlemail.com (Martin Blumenstingl)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/1] mark clk81 as critical on Meson8b
Date: Thu, 4 May 2017 20:32:00 +0200 [thread overview]
Message-ID: <20170504183201.13175-1-martin.blumenstingl@googlemail.com> (raw)
The GX (gxbb.c) clock controller driver already marks the clk81 clock
as criticial. However, the Meson8b clock controller driver does not do
this yet.
This can lead to a freeze of the whole system when clk81 is disabled
by the common clock framework (for example after the last child clock
is disabled by a driver which used that child clock).
Martin Blumenstingl (1):
clk: meson: meson8b: mark clk81 as critical
drivers/clk/meson/meson8b.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.12.2
WARNING: multiple messages have this Message-ID (diff)
From: martin.blumenstingl@googlemail.com (Martin Blumenstingl)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 0/1] mark clk81 as critical on Meson8b
Date: Thu, 4 May 2017 20:32:00 +0200 [thread overview]
Message-ID: <20170504183201.13175-1-martin.blumenstingl@googlemail.com> (raw)
The GX (gxbb.c) clock controller driver already marks the clk81 clock
as criticial. However, the Meson8b clock controller driver does not do
this yet.
This can lead to a freeze of the whole system when clk81 is disabled
by the common clock framework (for example after the last child clock
is disabled by a driver which used that child clock).
Martin Blumenstingl (1):
clk: meson: meson8b: mark clk81 as critical
drivers/clk/meson/meson8b.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.12.2
next reply other threads:[~2017-05-04 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 18:32 Martin Blumenstingl [this message]
2017-05-04 18:32 ` [PATCH 0/1] mark clk81 as critical on Meson8b Martin Blumenstingl
2017-05-04 18:32 ` Martin Blumenstingl
2017-05-04 18:32 ` [PATCH 1/1] clk: meson: meson8b: mark clk81 as critical Martin Blumenstingl
2017-05-04 18:32 ` Martin Blumenstingl
2017-05-04 18:32 ` Martin Blumenstingl
2017-05-29 7:57 ` Neil Armstrong
2017-05-29 7:57 ` Neil Armstrong
2017-05-29 7:57 ` Neil Armstrong
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=20170504183201.13175-1-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=carlo@caione.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=narmstrong@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
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.