mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-gpio@vger.kernel.org>, Bryan Brattlof <bb@ti.com>
Subject: Re: [PATCH 3/4] arm64: dts: ti: Introduce AM62A7 family of SoCs
Date: Thu, 1 Sep 2022 11:09:36 +0530	[thread overview]
Message-ID: <f4b54ddb-3364-e765-f683-9af19076db13@ti.com> (raw)
In-Reply-To: <dc971b60-c2be-aabb-20d6-181ea34d55c4@linaro.org>



On 30/08/22 15:26, Krzysztof Kozlowski wrote:
> On 29/08/2022 11:21, Vignesh Raghavendra wrote:
> 
> (...)
> 
>> +		/*
>> +		 * vcpumntirq:
>> +		 * virtual CPU interface maintenance interrupt
>> +		 */
>> +		interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH>;
>> +
>> +		gic_its: msi-controller@1820000 {
>> +			compatible = "arm,gic-v3-its";
>> +			reg = <0x00 0x01820000 0x00 0x10000>;
>> +			socionext,synquacer-pre-its = <0x1000000 0x400000>;
>> +			msi-controller;
>> +			#msi-cells = <1>;
>> +		};
>> +	};
>> +
>> +	main_conf: syscon@100000 {
>> +		compatible = "syscon", "simple-mfd";
> 
> No, these are not allowed alone.

Will add device specific compatible

compatible = "ti,j721e-system-controller", "syscon", "simple-mfd";

> 
>> +		reg = <0x00 0x00100000 0x00 0x20000>;
>> +		#address-cells = <1>;
>> +		#size-cells = <1>;
>> +		ranges = <0x00 0x00 0x00100000 0x20000>;
>> +	};
>> +
>> +	dmss: bus@48000000 {
>> +		compatible = "simple-mfd";
> 
> No. Not allowed alone.

This can be "simple-bus". Will change accordingly

> 
>> +		#address-cells = <2>;
>> +		#size-cells = <2>;
>> +		dma-ranges;
>> +		ranges = <0x00 0x48000000 0x00 0x48000000 0x00 0x06000000>;
>> +
>> +		ti,sci-dev-id = <25>;
>> +
>> +		secure_proxy_main: mailbox@4d000000 {
>> +			compatible = "ti,am654-secure-proxy";
>> +			#mbox-cells = <1>;
>> +			reg-names = "target_data", "rt", "scfg";
>> +			reg = <0x00 0x4d000000 0x00 0x80000>,
>> +			      <0x00 0x4a600000 0x00 0x80000>,
>> +			      <0x00 0x4a400000 0x00 0x80000>;
>> +			interrupt-names = "rx_012";
>> +			interrupts = <GIC_SPI 34 IRQ_TYPE_LEVEL_HIGH>;
>> +		};
>> +	};
>> +
>> +	dmsc: system-controller@44043000 {
>> +		compatible = "ti,k2g-sci";
>> +		ti,host-id = <12>;
>> +		mbox-names = "rx", "tx";
>> +		mboxes= <&secure_proxy_main 12>,
>> +			<&secure_proxy_main 13>;
>> +		reg-names = "debug_messages";
>> +		reg = <0x00 0x44043000 0x00 0xfe0>;
> 
> First compatible, then reg, then the reset of properties.  This applies
> everywhere.

Will fix

> 
>> +
>> +		k3_pds: power-controller {
>> +			compatible = "ti,sci-pm-domain";
>> +			#power-domain-cells = <2>;
>> +		};
>> +
>> +		k3_clks: clock-controller {
>> +			compatible = "ti,k2g-sci-clk";
>> +			#clock-cells = <2>;
>> +		};
>> +
>> +		k3_reset: reset-controller {
>> +			compatible = "ti,sci-reset";
>> +			#reset-cells = <2>;
>> +		};
>> +	};
>> +
[...]
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62a-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-am62a-wakeup.dtsi
>> new file mode 100644
>> index 000000000000..fe6d682a0f33
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/ti/k3-am62a-wakeup.dtsi
>> @@ -0,0 +1,54 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +/*
>> + * Device Tree Source for AM62A SoC Family Wakeup Domain peripherals
>> + *
>> + * Copyright (C) 2022 Texas Instruments Incorporated - https://www.ti.com/
>> + */
>> +
>> +&cbass_wakeup {
>> +	wkup_conf: syscon@43000000 {
>> +		compatible = "syscon", "simple-mfd";
> 
> No. Not allowed alone.

Will change to

compatible = "ti,j721e-system-controller", "syscon", "simple-mfd";

> 
>> +		reg = <0x00 0x43000000 0x00 0x20000>;
>> +		#address-cells = <1>;
>> +		#size-cells = <1>;
>> +		ranges = <0x00 0x00 0x43000000 0x20000>;
>> +
>> +		chipid: chipid@14 {
>> +			compatible = "ti,am654-chipid";
>> +			reg = <0x14 0x4>;
>> +		};
>> +	};
>> +
> 
> 

Thanks for the review!
-- 
Regards
Vignesh

  reply	other threads:[~2022-09-01  5:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29  8:21 [PATCH 0/4] arm64: dts: ti: Add support for AM62A " Vignesh Raghavendra
2022-08-29  8:21 ` [PATCH 1/4] dt-bindings: arm: ti: Add bindings for AM62A7 SoC Vignesh Raghavendra
2022-08-30  9:52   ` Krzysztof Kozlowski
2022-09-01  5:30     ` Vignesh Raghavendra
2022-08-29  8:21 ` [PATCH 2/4] dt-bindings: pinctrl: k3: Introduce pinmux definitions for AM62A Vignesh Raghavendra
2022-08-30  9:53   ` Krzysztof Kozlowski
2022-09-01  5:32     ` Vignesh Raghavendra
2022-08-31 13:37   ` Linus Walleij
2022-08-29  8:21 ` [PATCH 3/4] arm64: dts: ti: Introduce AM62A7 family of SoCs Vignesh Raghavendra
2022-08-30  9:56   ` Krzysztof Kozlowski
2022-09-01  5:39     ` Vignesh Raghavendra [this message]
2022-08-29  8:22 ` [PATCH 4/4] arm64: dts: ti: Add support for AM62A7-SK Vignesh Raghavendra
2022-08-30  9:57   ` Krzysztof Kozlowski

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=f4b54ddb-3364-e765-f683-9af19076db13@ti.com \
    --to=vigneshr@ti.com \
    --cc=bb@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.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

all inboxes | Powered by JetHome®