From: Martin Sperl <martin@sperl.org>
To: Eric Anholt <eric@anholt.net>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/4] clk: bcm2835: critical clocks and parent selection
Date: Wed, 7 Sep 2016 11:08:47 +0200 [thread overview]
Message-ID: <69F741EC-D4BB-461E-B3BA-FEF73DA70F2E@sperl.org> (raw)
In-Reply-To: <1464807936-532-1-git-send-email-eric@anholt.net>
> On 01.06.2016, at 21:05, Eric Anholt <eric@anholt.net> wrote:
>
> I figured out another critical clock (patch 3), but didn't use the
> CLK_IS_CRITICAL flag since I want to just protect whatever clock
> happens to be the parent (there are #ifdefs in the firmware indicating
> that they've experimented with using different clocks as the parent).
>
> I think these fixes are all suitable for 4.7.
>
> Eric Anholt (4):
> clk: bcm2835: Mark the VPU clock as critical
> clk: bcm2835: Mark GPIO clocks enabled at boot as critical
> clk: bcm2835: Mark the CM SDRAM clock's parent as critical
> clk: bcm2835: Skip PLLC clocks when deciding on a new clock parent
>
> drivers/clk/bcm/clk-bcm2835.c | 63 +++++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 61 insertions(+), 2 deletions(-)
Whole series:
Acked-by: Martin Sperl <kernel@martin.sperl.org>
Note that these patches are also seeing more testing downstream in 4.7
and there have been no hiccups seen either. Clock selection is working
as expected for I2S as well.
next prev parent reply other threads:[~2016-09-07 10:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 19:05 [PATCH v3 0/4] clk: bcm2835: critical clocks and parent selection Eric Anholt
2016-06-01 19:05 ` [PATCH v3 1/4] clk: bcm2835: Mark the VPU clock as critical Eric Anholt
2016-06-01 19:05 ` [PATCH v3 2/4] clk: bcm2835: Mark GPIO clocks enabled at boot " Eric Anholt
2016-06-01 19:05 ` [PATCH v3 3/4] clk: bcm2835: Mark the CM SDRAM clock's parent " Eric Anholt
2016-06-01 19:05 ` [PATCH v3 4/4] clk: bcm2835: Skip PLLC clocks when deciding on a new clock parent Eric Anholt
2016-09-07 9:08 ` Martin Sperl [this message]
2016-09-07 15:58 ` [PATCH v3 0/4] clk: bcm2835: critical clocks and parent selection 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=69F741EC-D4BB-461E-B3BA-FEF73DA70F2E@sperl.org \
--to=martin@sperl.org \
--cc=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).