Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1411476
| From | Eric Anholt <eric@anholt.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | [PATCH v3 0/4] clk: bcm2835: critical clocks and parent selection |
| Date | 2016-06-01 21:10 +0200 |
| Message-ID | <rFjGF-41O-9@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
[PATCH v3 0/4] clk: bcm2835: critical clocks and parent selection Eric Anholt <eric@anholt.net> - 2016-06-01 21:10 +0200 [PATCH v3 4/4] clk: bcm2835: Skip PLLC clocks when deciding on a new clock parent Eric Anholt <eric@anholt.net> - 2016-06-01 21:10 +0200 [PATCH v3 3/4] clk: bcm2835: Mark the CM SDRAM clock's parent as critical Eric Anholt <eric@anholt.net> - 2016-06-01 21:10 +0200 [PATCH v3 2/4] clk: bcm2835: Mark GPIO clocks enabled at boot as critical Eric Anholt <eric@anholt.net> - 2016-06-01 21:10 +0200 [PATCH v3 1/4] clk: bcm2835: Mark the VPU clock as critical Eric Anholt <eric@anholt.net> - 2016-06-01 21:10 +0200
csiph-web