From: Eric Anholt <eric@anholt.net> To: Michael Turquette <mturquette@baylibre.com>, Stephen Boyd <sboyd@codeaurora.org> Cc: linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Stephen Warren <swarren@wwwdotorg.org>, Lee Jones <lee@kernel.org>, Eric Anholt <eric@anholt.net> Subject: [PATCH v3 0/4] clk: bcm2835: critical clocks and parent selection Date: Wed, 1 Jun 2016 12:05:32 -0700 [thread overview] Message-ID: <1464807936-532-1-git-send-email-eric@anholt.net> (raw) 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(-) -- 2.8.0.rc3
WARNING: multiple messages have this Message-ID (diff)
From: eric@anholt.net (Eric Anholt) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v3 0/4] clk: bcm2835: critical clocks and parent selection Date: Wed, 1 Jun 2016 12:05:32 -0700 [thread overview] Message-ID: <1464807936-532-1-git-send-email-eric@anholt.net> (raw) 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(-) -- 2.8.0.rc3
next reply other threads:[~2016-06-01 19:05 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-06-01 19:05 Eric Anholt [this message] 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 ` 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 ` 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 ` 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-06-01 19:05 ` Eric Anholt 2016-09-07 9:08 ` [PATCH v3 0/4] clk: bcm2835: critical clocks and parent selection Martin Sperl 2016-09-07 9:08 ` Martin Sperl 2016-09-07 15:58 ` Stephen Boyd 2016-09-07 15:58 ` 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=1464807936-532-1-git-send-email-eric@anholt.net \ --to=eric@anholt.net \ --cc=lee@kernel.org \ --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 \ --cc=swarren@wwwdotorg.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: linkBe 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.