Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1520739 > unrolled thread
| Started by | "Rafael J. Wysocki" <rjw@rjwysocki.net> |
|---|---|
| First post | 2016-11-14 01:30 +0100 |
| Last post | 2016-11-14 01:30 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v5 0/3] Broadcom STB AVS CPUfreq driver "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2016-11-14 01:30 +0100
| From | "Rafael J. Wysocki" <rjw@rjwysocki.net> |
|---|---|
| Date | 2016-11-14 01:30 +0100 |
| Subject | Re: [PATCH v5 0/3] Broadcom STB AVS CPUfreq driver |
| Message-ID | <sDdjQ-7Jc-11@gated-at.bofh.it> |
On Friday, November 04, 2016 10:00:19 AM Markus Mayer wrote: > On 27 October 2016 at 14:05, Markus Mayer <code@mmayer.net> wrote: > > From: Markus Mayer <mmayer@broadcom.com> > > > > This series contains the CPUfreq driver for Broadcom SoCs that use "AVS > > Firmware" for voltage and frequency scaling. All voltage and frequency > > transitions are performed by the firmware and are therefore hidden from > > Linux. > > > > The driver provides a standard CPUfreq interface to other kernel > > components and to userland on the one hand and communicates with the > > AVS co-processor on the other. > > > > Communication between the two processors is via shared mailbox > > registers and interrupts (ARM -> AVS to tell the firmware that there is > > a command to process and AVS -> ARM to tell the driver that a command > > finished executing). > > Viresh, Rafael, are you ready to take this series? Rob gave his Ack > for the DT binding. Applied. Thanks, Rafael
Back to top | Article view | linux.kernel
csiph-web