From: Mark Rutland <mark.rutland@arm.com>
To: Eric Anholt <eric@anholt.net>
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>,
Florian Fainelli <f.fainelli@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: bcm2835: Add devicetree for the Raspberry Pi 3.
Date: Fri, 4 Mar 2016 18:59:24 +0000 [thread overview]
Message-ID: <20160304185923.GC5033@leverpostej> (raw)
In-Reply-To: <874mcm3wfs.fsf@eliezer.anholt.net>
On Fri, Mar 04, 2016 at 10:55:03AM -0800, Eric Anholt wrote:
> Mark Rutland <mark.rutland@arm.com> writes:
>
> > On Fri, Mar 04, 2016 at 10:39:29AM -0800, Eric Anholt wrote:
> >> For now this doesn't support the new hardware present on the Pi 3 (BT,
> >> wifi, GPIO expander). Since the GPIO expander isn't supported, we
> >> also don't have the LEDs like the other board files do.
> >>
> >> Signed-off-by: Eric Anholt <eric@anholt.net>
> >> ---
> >> arch/arm/boot/dts/Makefile | 3 +-
> >> arch/arm/boot/dts/bcm2837-rpi-3-b.dts | 22 ++++++++++++
> >> arch/arm/boot/dts/bcm2837.dtsi | 68 +++++++++++++++++++++++++++++++++++
> >> 3 files changed, 92 insertions(+), 1 deletion(-)
> >> create mode 100644 arch/arm/boot/dts/bcm2837-rpi-3-b.dts
> >> create mode 100644 arch/arm/boot/dts/bcm2837.dtsi
> >
> >> + timer {
> >> + compatible = "arm,armv7-timer";
> >> + interrupt-parent = <&local_intc>;
> >> + interrupts = <0>, // PHYS_SECURE_PPI
> >> + <1>, // PHYS_NONSECURE_PPI
> >> + <3>, // VIRT_PPI
> >> + <2>; // HYP_PPI
> >> + always-on;
> >> + };
> >
> > Are the CPUs in an always-on power domain? Or is it jsut that the kernel
> > doesn't perform power management of CPUs?
> >
> > The always-on proeprty is only intended for the former.
>
> The kernel doesn't get to do power management of CPUs. We only have
> control of power domains through the firmware, and the firmware's
> keeping the CPU domain on.
So there is no way that the CPUs could request for the firmare to place
them in a state where the timer would lose context (but other events
coukd wake them up), even if they don't do that today?
Mark
next prev parent reply other threads:[~2016-03-04 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 18:39 [PATCH 1/2] dt-bindings: Add root properties for Raspberry Pi 3 Eric Anholt
2016-03-04 18:39 ` [PATCH 2/2] ARM: bcm2835: Add devicetree for the " Eric Anholt
2016-03-04 18:41 ` Mark Rutland
2016-03-04 18:55 ` Eric Anholt
2016-03-04 18:59 ` Mark Rutland [this message]
2016-03-04 19:39 ` Eric Anholt
2016-03-08 5:54 ` Stephen Warren
2016-03-17 11:53 ` [PATCH 1/2] dt-bindings: Add root properties for " Rob Herring
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=20160304185923.GC5033@leverpostej \
--to=mark.rutland@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--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=pawel.moll@arm.com \
--cc=robh+dt@kernel.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox