Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1212605
| From | Eric Anholt <eric@anholt.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v5 1/3] clk: bcm2835: Add binding docs for the Raspberry Pi clock provider |
| Date | 2015-08-25 02:40 +0200 |
| Message-ID | <q1arn-7k8-9@gated-at.bofh.it> (permalink) |
| References | <pX9Nf-QH-3@gated-at.bofh.it> <pX9Ng-QH-29@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Eric Anholt <eric@anholt.net> writes: > The hardware clocks are not controllable by the ARM, so we have to > make requests to the firmware to do so from the VPU side. This will > let us replace fixed clocks in our DT with actual clock control (and > correct frequency information). Gordon from the Raspberry Pi Foundation just asked me "what do you mean, you can't access the clocks from the ARM?" I'd been assured I couldn't by another developer (who was originally going to write a Linux driver for this), and my own testing had also indicated I couldn't, but after a new round of hacking together some tests, I see things that look a lot like clockman registers. Looks like we're going to get a native driver, instead.
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [PATCH v5 1/3] clk: bcm2835: Add binding docs for the Raspberry Pi clock provider Eric Anholt <eric@anholt.net> - 2015-08-25 02:40 +0200
csiph-web