From: Lubomir Rintel <lkundrak@v3.sk> To: linux-rpi-kernel@lists.infradead.org Cc: Lee Jones <lee@kernel.org>, Stephen Warren <swarren@wwwdotorg.org>, Lubomir Rintel <lkundrak@v3.sk>, linux-pm@vger.kernel.org, Eric Anholt <eric@anholt.net>, linux-arm-kernel@lists.infradead.org Subject: [PATCH] bcm2835: Add Raspberry Pi CPU frequency control to the device tree Date: Sun, 11 Oct 2015 21:46:35 +0200 [thread overview] Message-ID: <1444592795-15129-1-git-send-email-lkundrak@v3.sk> (raw) This adds a device tree binding for Broadcom BCM2834 CPU frequency control driven via Raspberry Pi VideoCore 4 firmware interface. Signed-off-by: Lubomir Rintel <lkundrak@v3.sk> Cc: Stephen Warren <swarren@wwwdotorg.org> Cc: Lee Jones <lee@kernel.org> Cc: Eric Anholt <eric@anholt.net> Cc: linux-rpi-kernel@lists.infradead.org Cc: linux-arm-kernel@lists.infradead.org Cc: linux-pm@vger.kernel.org --- Depends on the RPi Firmware driver submitted on linux-rpi-kernel a while ago. Can't see it in arm-soc or linux-next yet though (?). Available in branch 'rpi-firmware' of https://github.com/anholt/linux .../bindings/cpufreq/raspberrypi,bcm2835-cpufreq.txt | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 Documentation/devicetree/bindings/cpufreq/raspberrypi,bcm2835-cpufreq.txt diff --git a/Documentation/devicetree/bindings/cpufreq/raspberrypi,bcm2835-cpufreq.txt b/Documentation/devicetree/bindings/cpufreq/raspberrypi,bcm2835-cpufreq.txt new file mode 100644 index 0000000..eb126d3 --- /dev/null +++ b/Documentation/devicetree/bindings/cpufreq/raspberrypi,bcm2835-cpufreq.txt @@ -0,0 +1,13 @@ +Raspberry Pi Broadcom BCM2835 CPU frequency control + +Required properties: + +- compatible : should be "raspberrypi,bcm2835-cpufreq" +- firmware : the Raspberry Pi firmware node + +Example: + +cpufreq { + compatible = "raspberrypi,bcm2835-cpufreq"; + firmware = <&firmware>; +}; -- 2.4.3
WARNING: multiple messages have this Message-ID (diff)
From: lkundrak@v3.sk (Lubomir Rintel) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] bcm2835: Add Raspberry Pi CPU frequency control to the device tree Date: Sun, 11 Oct 2015 21:46:35 +0200 [thread overview] Message-ID: <1444592795-15129-1-git-send-email-lkundrak@v3.sk> (raw) This adds a device tree binding for Broadcom BCM2834 CPU frequency control driven via Raspberry Pi VideoCore 4 firmware interface. Signed-off-by: Lubomir Rintel <lkundrak@v3.sk> Cc: Stephen Warren <swarren@wwwdotorg.org> Cc: Lee Jones <lee@kernel.org> Cc: Eric Anholt <eric@anholt.net> Cc: linux-rpi-kernel at lists.infradead.org Cc: linux-arm-kernel at lists.infradead.org Cc: linux-pm at vger.kernel.org --- Depends on the RPi Firmware driver submitted on linux-rpi-kernel a while ago. Can't see it in arm-soc or linux-next yet though (?). Available in branch 'rpi-firmware' of https://github.com/anholt/linux .../bindings/cpufreq/raspberrypi,bcm2835-cpufreq.txt | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 Documentation/devicetree/bindings/cpufreq/raspberrypi,bcm2835-cpufreq.txt diff --git a/Documentation/devicetree/bindings/cpufreq/raspberrypi,bcm2835-cpufreq.txt b/Documentation/devicetree/bindings/cpufreq/raspberrypi,bcm2835-cpufreq.txt new file mode 100644 index 0000000..eb126d3 --- /dev/null +++ b/Documentation/devicetree/bindings/cpufreq/raspberrypi,bcm2835-cpufreq.txt @@ -0,0 +1,13 @@ +Raspberry Pi Broadcom BCM2835 CPU frequency control + +Required properties: + +- compatible : should be "raspberrypi,bcm2835-cpufreq" +- firmware : the Raspberry Pi firmware node + +Example: + +cpufreq { + compatible = "raspberrypi,bcm2835-cpufreq"; + firmware = <&firmware>; +}; -- 2.4.3
next reply other threads:[~2015-10-11 19:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-11 19:46 Lubomir Rintel [this message] 2015-10-11 19:46 ` [PATCH] bcm2835: Add Raspberry Pi CPU frequency control to the device tree Lubomir Rintel 2015-10-15 0:29 ` Eric Anholt 2015-10-15 0:29 ` Eric Anholt 2015-10-21 3:00 ` Stephen Warren 2015-10-21 3:00 ` Stephen Warren
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=1444592795-15129-1-git-send-email-lkundrak@v3.sk \ --to=lkundrak@v3.sk \ --cc=eric@anholt.net \ --cc=lee@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-pm@vger.kernel.org \ --cc=linux-rpi-kernel@lists.infradead.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.