All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Rob Herring <robh+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
	Mike Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH 12/13] arm64: dts: add Allwinner A64 SoC .dtsi
Date: Fri, 9 Sep 2016 22:04:35 +0200	[thread overview]
Message-ID: <20160909200435.GJ8881@lukather> (raw)
In-Reply-To: <c2334630-edab-5b42-48dd-5e4edd5f3de1@arm.com>

[-- Attachment #1: Type: text/plain, Size: 2144 bytes --]

Hi,

On Thu, Sep 08, 2016 at 09:41:10AM +0100, Andre Przywara wrote:
> > +	timer {
> > +		compatible = "arm,armv8-timer";
> > +		interrupts = <GIC_PPI 13
> > +			(GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_HIGH)>,
> > +			     <GIC_PPI 14
> > +			(GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_HIGH)>,
> > +			     <GIC_PPI 11
> > +			(GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_HIGH)>,
> > +			     <GIC_PPI 10
> > +			(GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_HIGH)>;
> > +	};
> 
> Can you add a PMU node here? Or shall I send a patch on top of it?
> It would be:
> 
> 	pmu {
>         	compatible = "arm,cortex-a53-pmu", "arm,armv8-pmuv3";
> 		interrupts = <GIC_SPI 120 IRQ_TYPE_LEVEL_HIGH>,
> 			     <GIC_SPI 121 IRQ_TYPE_LEVEL_HIGH>,	
> 			     <GIC_SPI 122 IRQ_TYPE_LEVEL_HIGH>,
> 			     <GIC_SPI 123 IRQ_TYPE_LEVEL_HIGH>;
> 		interrupt-affinity = <&cpu0>,
> 				     <&cpu1>,
> 				     <&cpu2>,
> 				     <&cpu3>;
> 	};
> 
> This enables perf to use hardware counters (for cycles and instructions,
> for instance).
> 
> > +
> > +	clocks {
> > +		#address-cells = <1>;
> > +		#size-cells = <1>;
> > +		ranges;
> > +
> > +		osc24M: osc24M_clk {
> > +			#clock-cells = <0>;
> > +			compatible = "fixed-clock";
> > +			clock-frequency = <24000000>;
> > +			clock-output-names = "osc24M";
> > +		};
> > +
> > +		osc32k: osc32k_clk {
> > +			#clock-cells = <0>;
> > +			compatible = "fixed-clock";
> > +			clock-frequency = <32768>;
> > +			clock-output-names = "osc32k";
> > +		};
> > +	};
> 
> Can you remove this "clocks" node and put the two subnodes directly onto
> the top level?
> I know that putting clocks into a subnode is quite wide spread, but it
> does not represent any hardware hierarchy, especially in this
> fixed-clock case.
> So if we can (and it is easy here!) we should avoid any clocks subnode.
> 
> (Yes, I know that this was in my original DT as well, but Mark Rutland
> convinced me of this.)

I'll do those changes before sending the new version.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 12/13] arm64: dts: add Allwinner A64 SoC .dtsi
Date: Fri, 9 Sep 2016 22:04:35 +0200	[thread overview]
Message-ID: <20160909200435.GJ8881@lukather> (raw)
In-Reply-To: <c2334630-edab-5b42-48dd-5e4edd5f3de1@arm.com>

Hi,

On Thu, Sep 08, 2016 at 09:41:10AM +0100, Andre Przywara wrote:
> > +	timer {
> > +		compatible = "arm,armv8-timer";
> > +		interrupts = <GIC_PPI 13
> > +			(GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_HIGH)>,
> > +			     <GIC_PPI 14
> > +			(GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_HIGH)>,
> > +			     <GIC_PPI 11
> > +			(GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_HIGH)>,
> > +			     <GIC_PPI 10
> > +			(GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_HIGH)>;
> > +	};
> 
> Can you add a PMU node here? Or shall I send a patch on top of it?
> It would be:
> 
> 	pmu {
>         	compatible = "arm,cortex-a53-pmu", "arm,armv8-pmuv3";
> 		interrupts = <GIC_SPI 120 IRQ_TYPE_LEVEL_HIGH>,
> 			     <GIC_SPI 121 IRQ_TYPE_LEVEL_HIGH>,	
> 			     <GIC_SPI 122 IRQ_TYPE_LEVEL_HIGH>,
> 			     <GIC_SPI 123 IRQ_TYPE_LEVEL_HIGH>;
> 		interrupt-affinity = <&cpu0>,
> 				     <&cpu1>,
> 				     <&cpu2>,
> 				     <&cpu3>;
> 	};
> 
> This enables perf to use hardware counters (for cycles and instructions,
> for instance).
> 
> > +
> > +	clocks {
> > +		#address-cells = <1>;
> > +		#size-cells = <1>;
> > +		ranges;
> > +
> > +		osc24M: osc24M_clk {
> > +			#clock-cells = <0>;
> > +			compatible = "fixed-clock";
> > +			clock-frequency = <24000000>;
> > +			clock-output-names = "osc24M";
> > +		};
> > +
> > +		osc32k: osc32k_clk {
> > +			#clock-cells = <0>;
> > +			compatible = "fixed-clock";
> > +			clock-frequency = <32768>;
> > +			clock-output-names = "osc32k";
> > +		};
> > +	};
> 
> Can you remove this "clocks" node and put the two subnodes directly onto
> the top level?
> I know that putting clocks into a subnode is quite wide spread, but it
> does not represent any hardware hierarchy, especially in this
> fixed-clock case.
> So if we can (and it is easy here!) we should avoid any clocks subnode.
> 
> (Yes, I know that this was in my original DT as well, but Mark Rutland
> convinced me of this.)

I'll do those changes before sending the new version.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160909/87c052f4/attachment.sig>

  reply	other threads:[~2016-09-09 20:04 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 20:30 [PATCH 00/13] arm64: Allwinner A64 support based on sunxi-ng Maxime Ripard
2016-07-26 20:30 ` Maxime Ripard
2016-07-26 20:30 ` [PATCH 01/13] clk: sunxi-ng: mux: Rename mux macro to be consistent Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-26 20:30 ` [PATCH 02/13] clk: sunxi-ng: mux: Add mux table support Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-26 20:30 ` [PATCH 03/13] clk: sunxi-ng: sun8i: Rename DDR and video plls Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-27  7:57   ` kbuild test robot
2016-07-27  7:57     ` kbuild test robot
2016-07-27  7:57     ` kbuild test robot
2016-07-26 20:30 ` [PATCH 04/13] clk: sunxi-ng: sun8i: Fix register offset Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-26 20:30 ` [PATCH 05/13] clk: sunxi-ng: sun8i: Rename H3 only clocks Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-26 20:30 ` [PATCH 06/13] clk: sunxi-ng: sun8i: Move fixed factors around Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-26 20:30 ` [PATCH 07/13] clk: sunxi-ng: sun8i: Prefix clock defines by SoC Name Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-26 20:30 ` [PATCH 08/13] clk: sunxi-ng: Add A64 clocks Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-29 21:15   ` Rob Herring
2016-07-29 21:15     ` Rob Herring
2016-07-26 20:30 ` [PATCH 09/13] arm64: sunxi: Kconfig: add essential pinctrl driver Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-26 20:30 ` [PATCH 10/13] arm64: Kconfig: sunxi: add PINCTRL Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-26 20:30 ` [PATCH 11/13] Documentation: devicetree: add vendor prefix for Pine64 Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-26 20:30 ` [PATCH 12/13] arm64: dts: add Allwinner A64 SoC .dtsi Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-09-08  8:41   ` Andre Przywara
2016-09-08  8:41     ` Andre Przywara
2016-09-09 20:04     ` Maxime Ripard [this message]
2016-09-09 20:04       ` Maxime Ripard
2016-07-26 20:30 ` [PATCH 13/13] arm64: dts: add Pine64 support Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-26 20:30   ` Maxime Ripard
2016-07-27  8:46 ` [PATCH 00/13] arm64: Allwinner A64 support based on sunxi-ng Jean-Francois Moine
2016-07-27  8:46   ` Jean-Francois Moine
2016-07-27  8:46   ` Jean-Francois Moine
2016-07-28 20:07   ` Maxime Ripard
2016-07-28 20:07     ` Maxime Ripard
2016-07-29  5:48     ` Jean-Francois Moine
2016-07-29  5:48       ` Jean-Francois Moine
2016-07-29  5:48       ` Jean-Francois Moine
2016-07-31  8:51       ` Maxime Ripard
2016-07-31  8:51         ` Maxime Ripard
2016-08-01  1:43 ` André Przywara
2016-08-01  1:43   ` André Przywara
2016-08-01  1:43   ` André Przywara
2016-08-01  8:30   ` Jean-Francois Moine
2016-08-01  8:30     ` Jean-Francois Moine
2016-08-01  8:30     ` Jean-Francois Moine
2016-08-01  8:30     ` Jean-Francois Moine
2016-08-01  9:13     ` Chen-Yu Tsai
2016-08-01  9:13       ` Chen-Yu Tsai
2016-08-01  9:13       ` Chen-Yu Tsai
2016-08-01  9:13       ` Chen-Yu Tsai
2016-08-01 12:00       ` Jean-Francois Moine
2016-08-01 12:00         ` Jean-Francois Moine
2016-08-01 12:00         ` Jean-Francois Moine
2016-08-01 12:00         ` Jean-Francois Moine
2016-08-01 12:01         ` Chen-Yu Tsai
2016-08-01 12:01           ` Chen-Yu Tsai
2016-08-01 12:01           ` Chen-Yu Tsai
2016-08-01 12:11           ` Jean-Francois Moine
2016-08-01 12:11             ` Jean-Francois Moine
2016-08-01 12:11             ` Jean-Francois Moine
2016-08-01 10:44     ` Andre Przywara
2016-08-01 10:44       ` Andre Przywara
2016-08-01 12:19       ` Icenowy Zheng
2016-08-01 12:19         ` Icenowy Zheng
2016-08-01 12:19         ` Icenowy Zheng
2016-08-01  9:11   ` Chen-Yu Tsai
2016-08-01  9:11     ` Chen-Yu Tsai
2016-08-01  9:11     ` Chen-Yu Tsai
2016-08-11  0:36     ` André Przywara
2016-08-11  0:36       ` André Przywara
2016-08-23 19:31   ` Maxime Ripard
2016-08-23 19:31     ` Maxime Ripard
2016-08-23 19:31     ` Maxime Ripard
2016-08-24 23:54     ` André Przywara
2016-08-24 23:54       ` André Przywara
2016-08-24 23:54       ` André Przywara
2016-08-26 22:18       ` Maxime Ripard
2016-08-26 22:18         ` Maxime Ripard

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=20160909200435.GJ8881@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=andre.przywara@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=wens@csie.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 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.