linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Davis <afd@ti.com>
To: Apurva Nandan <a-nandan@ti.com>, Nishanth Menon <nm@ti.com>,
	Vignesh Raghavendra <vigneshr@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>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-gpio@vger.kernel.org>
Cc: Hari Nagalla <hnagalla@ti.com>
Subject: Re: [PATCH v2 3/4] arm64: dts: ti: Add initial support for J784S4 SoC
Date: Wed, 19 Oct 2022 12:26:31 -0500	[thread overview]
Message-ID: <90cbb65b-389e-95b5-26d8-39bc33f88df6@ti.com> (raw)
In-Reply-To: <20221014082314.118361-4-a-nandan@ti.com>

On 10/14/22 3:23 AM, Apurva Nandan wrote:
> The J784S4 SoC belongs to the K3 Multicore SoC architecture
> platform, providing advanced system integration in automotive,
> ADAS and industrial applications requiring AI at the network edge.
> This SoC extends the K3 Jacinto 7 family of SoCs with focus on
> raising performance and integration while providing interfaces,
> memory architecture and compute performance for multi-sensor, high
> concurrency applications.
> 

[...]

> +
> +		hwspinlock: hwlock@30e00000 {
> +			compatible = "ti,am654-hwspinlock";
> +			reg = <0x00 0x30e00000 0x00 0x1000>;
> +			#hwlock-cells = <1>;
> +			status = "disabled";

Why is this disabled? The node is complete and usable.

I do not know if we settled on a set of rules for disabling nodes
by default in the dtsi, I couldn't find one if we did, but how does
this sound,

If a node in a dtsi file is incomplete, or the described hardware
unusable, without additional information provided by board-level
additions, then the node may be disabled. Otherwise it must be
left in the default enabled state.

Without something like that, we will end up with the same problem
we are trying to fix here, but in reverse, one will have to
enable nodes in board files that would not otherwise need to
refrenced. Worse that sounds like a configuration setting, not a
hardware description, so it would not belong in the device tree.

Same for main_ringacc, main_udmap, cpts, and mcu_navss below.

> +		};
> +

[...]

> +
> +#include <dt-bindings/interrupt-controller/irq.h>
> +#include <dt-bindings/interrupt-controller/arm-gic.h>
> +#include <dt-bindings/pinctrl/k3.h>
> +#include <dt-bindings/soc/ti,sci_pm_domain.h>
> +
> +/ {
> +

Extra newline not needed.

Andrew

> +	model = "Texas Instruments K3 J784S4 SoC";

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-10-19 17:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14  8:23 [PATCH v2 0/4] Add initial support for J784S4 SoC Apurva Nandan
2022-10-14  8:23 ` [PATCH v2 1/4] dt-bindings: arm: ti: Add bindings for J784s4 SoC Apurva Nandan
2022-10-14  8:23 ` [PATCH v2 2/4] dt-bindings: pinctrl: k3: Introduce pinmux definitions for J784s4 Apurva Nandan
2022-10-14  8:23 ` [PATCH v2 3/4] arm64: dts: ti: Add initial support for J784S4 SoC Apurva Nandan
2022-10-19 17:26   ` Andrew Davis [this message]
2022-10-14  8:23 ` [PATCH v2 4/4] arm64: dts: ti: Add support for J784S4 EVM board Apurva Nandan
2022-10-19 17:31   ` Andrew Davis
2022-11-11 12:18     ` Apurva Nandan
2022-11-15  4:52       ` Nishanth Menon

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=90cbb65b-389e-95b5-26d8-39bc33f88df6@ti.com \
    --to=afd@ti.com \
    --cc=a-nandan@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hnagalla@ti.com \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@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 \
    --cc=vigneshr@ti.com \
    /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;
as well as URLs for NNTP newsgroup(s).