All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Shubhi Garg <shgarg@nvidia.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	jonathanh@nvidia.com, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH v1 2/2] arm64: tegra: Add support for IGX Orin
Date: Thu, 4 May 2023 14:21:38 +0200	[thread overview]
Message-ID: <ZFOjUrUXMwxAgUXP@orome> (raw)
In-Reply-To: <20230502150249.773425-2-shgarg@nvidia.com>

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

On Tue, May 02, 2023 at 03:02:49PM +0000, Shubhi Garg wrote:
[...]
> diff --git a/arch/arm64/boot/dts/nvidia/tegra234-p3740-0002+p3701-0008.dts b/arch/arm64/boot/dts/nvidia/tegra234-p3740-0002+p3701-0008.dts
> new file mode 100644
> index 000000000000..3ac8070918bb
> --- /dev/null
> +++ b/arch/arm64/boot/dts/nvidia/tegra234-p3740-0002+p3701-0008.dts
> @@ -0,0 +1,155 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/dts-v1/;
> +
> +#include <dt-bindings/input/linux-event-codes.h>
> +#include <dt-bindings/input/gpio-keys.h>
> +#include "tegra234-p3701-0008.dtsi"
> +#include "tegra234-p3740-0002.dtsi"
> +
> +/ {
> +	model = "NVIDIA IGX Orin Development Kit";
> +	compatible = "nvidia,p3740-0002+p3701-0008", "nvidia,p3701-0008", "nvidia,tegra234";
> +
> +	bus@0 {
> +		host1x@13e00000 {
> +			nvdec@15480000 {
> +				status = "okay";
> +			};
> +		};
> +
> +		pcie@140e0000 {
> +			status = "okay";
> +			vddio-pex-ctl-supply = <&vdd_1v8_ls>;
> +			phys = <&p2u_gbe_4>, <&p2u_gbe_5>;
> +			phy-names = "p2u-0", "p2u-1";
> +		};
> +
> +		pcie@14100000 {
> +			status = "okay";
> +			vddio-pex-ctl-supply = <&vdd_1v8_ao>;
> +			phys = <&p2u_hsio_3>;
> +			phy-names = "p2u-0";
> +		};
> +
> +		pcie@14160000 {
> +			status = "okay";
> +			vddio-pex-ctl-supply = <&vdd_1v8_ao>;
> +			phys = <&p2u_hsio_7>, <&p2u_hsio_6>, <&p2u_hsio_5>,
> +			       <&p2u_hsio_4>;
> +			phy-names = "p2u-0", "p2u-1", "p2u-2", "p2u-3";
> +		};
> +
> +		pcie@141a0000 {
> +			status = "okay";
> +			vddio-pex-ctl-supply = <&vdd_1v8_ls>;
> +			phys = <&p2u_nvhs_0>, <&p2u_nvhs_1>, <&p2u_nvhs_2>,
> +				<&p2u_nvhs_3>, <&p2u_nvhs_4>, <&p2u_nvhs_5>,
> +				<&p2u_nvhs_6>, <&p2u_nvhs_7>;
> +			phy-names = "p2u-0", "p2u-1", "p2u-2", "p2u-3", "p2u-4",
> +				    "p2u-5", "p2u-6", "p2u-7";
> +		};
> +
> +		pcie@141e0000 {
> +			status = "okay";
> +			vddio-pex-ctl-supply = <&vdd_1v8_ls>;
> +			phys = <&p2u_gbe_0>, <&p2u_gbe_1>;
> +			phy-names = "p2u-0", "p2u-1";
> +		};
> +
> +		aconnect@2900000 {
> +			status = "okay";
> +		};
> +
> +		serial@3100000 {
> +			compatible = "nvidia,tegra194-hsuart";
> +			status = "okay";
> +		};
> +
> +		i2c@3160000 {
> +			status = "okay";
> +		};
> +
> +		i2c@3180000 {
> +			status = "okay";
> +		};
> +
> +		i2c@3190000 {
> +			status = "okay";
> +		};
> +
> +		i2c@31b0000 {
> +			status = "okay";
> +		};
> +
> +		i2c@31c0000 {
> +			status = "okay";
> +
> +		};
> +
> +		i2c@31e0000 {
> +			status = "okay";
> +		};
> +
> +		spi@3270000 {
> +			status = "okay";
> +		};
> +
> +		hda@3510000 {
> +			nvidia,model = "NVIDIA IGX HDA";
> +			status = "okay";
> +		};
> +
> +		fuse@3810000 {
> +			status = "okay";
> +		};
> +
> +		i2c@c240000 {
> +			status = "okay";
> +		};
> +
> +		i2c@c250000 {
> +			status = "okay";
> +		};
> +	};
> +
> +	aliases {
> +		serial0 = &tcu;
> +	};
> +
> +	chosen {
> +		bootargs = "console=ttyTCU0,115200n8";
> +		stdout-path = "serial0:115200n8";
> +	};

This is admittedly a little unintuitive, but "aliases" and "chosen" are
special in that they are ordered at the top of the file (i.e.
immediately before the bus@0 node, and then alphabetically). That's
because they have special meaning, as opposed to the others below which
are just devices that don't have an address region and therefore no
unit-address.

Also, can you try testing this with the "bootargs" property dropped? I
have done some testing on older platforms and that doesn't seem to be
necessary since we have "stdout-path". It'd be good to confirm that it
holds true on IGX and if so we can drop "bootargs". I have work in
progress patches to do this on several other devices.

Thierry

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

  reply	other threads:[~2023-05-04 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 15:02 [PATCH v1 1/2] dt-bindings: tegra: Document compatible for IGX Shubhi Garg
2023-05-02 15:02 ` [PATCH v1 2/2] arm64: tegra: Add support for IGX Orin Shubhi Garg
2023-05-04 12:21   ` Thierry Reding [this message]
2023-05-03  6:22 ` [PATCH v1 1/2] dt-bindings: tegra: Document compatible for IGX Krzysztof Kozlowski
2023-05-03  9:18   ` Thierry Reding
2023-05-03 14:07     ` 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=ZFOjUrUXMwxAgUXP@orome \
    --to=thierry.reding@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=shgarg@nvidia.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 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.