Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759413AbcCDSzK (ORCPT ); Fri, 4 Mar 2016 13:55:10 -0500 Received: from anholt.net ([50.246.234.109]:34414 "EHLO anholt.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751414AbcCDSzI (ORCPT ); Fri, 4 Mar 2016 13:55:08 -0500 From: Eric Anholt To: Mark Rutland Cc: linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Stephen Warren , Lee Jones , Florian Fainelli , Rob Herring , Pawel Moll , Ian Campbell , Kumar Gala , devicetree@vger.kernel.org Subject: Re: [PATCH 2/2] ARM: bcm2835: Add devicetree for the Raspberry Pi 3. In-Reply-To: <20160304184136.GB5033@leverpostej> References: <1457116769-8567-1-git-send-email-eric@anholt.net> <1457116769-8567-2-git-send-email-eric@anholt.net> <20160304184136.GB5033@leverpostej> User-Agent: Notmuch/0.21 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Fri, 04 Mar 2016 10:55:03 -0800 Message-ID: <874mcm3wfs.fsf@eliezer.anholt.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2321 Lines: 61 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Mark Rutland 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. >>=20 >> Signed-off-by: Eric Anholt >> --- >> 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 =3D "arm,armv7-timer"; >> + interrupt-parent =3D <&local_intc>; >> + interrupts =3D <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. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJW2doHAAoJELXWKTbR/J7oePsP/0/2O7qonmHyKSejusdkjhFN KumkvvgEh31LRtPAO035ntXd76EEcC7wl3lKX/5cKTJEx1KxlPP0L4oFQRvKiq1l FV4B/cMG3QbQAqbWpXKwV3qkAjFjNi2T2mKhRauL99ZndNaauZGIiZd0sfeS9uAR tl6Kr7IlW3AKxKXkRlx5h7NJ2uaP7YeTC6qp2VJdwS9xgd1DWkolhbHXrxxKkyL7 lcEG5nvv6zt0pNI7cz5mK5+4c+KvxJK5CoRZf290qpsZ0nOp4ntNTcG85gNMuWre ESIeOu+/eB12IZbd08hX6TU+vz65cY7HeBXn1nUUsLCD3yUsAl0OkOm3Agtyo+yc PSOuk8vqPDArPcIiRJII3tKi6/iRI92wJLhYH4dR1fB1DeiJ1fvYFb/WNK8jznmJ p8BaSFA3AXD53DpNNDvVX72Ye9Vf+SVHpmGQuJL9fWfdn0UQHtLCYM3HTtChd11i jpGXHLyeeNUJoAqwAiTz3lEZ/DeNC+TcT12ztOYG6q8Sb0Zthw0KFLWsZZC0NaQh 6oiZg7BRmUa9hbBfB2klXwZ4mupc9+XokouMMQr92e4Myc7t+g9VQRwR6ZIzSPZb D+4RO2CIPicNk14TkAqN7C5goR5Z7uXo8e2QUs92mI1KbmuqKbc80kiZXQ47UE8x hnsYcHop/QZHNJER+Xc5 =JxV6 -----END PGP SIGNATURE----- --=-=-=--