From: Svyatoslav <clamor95@gmail.com>
To: Mikko Perttunen <mperttunen@nvidia.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <treding@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/4] ARM: tegra114: add missing HOST1X device nodes
Date: Wed, 17 Sep 2025 07:09:13 +0300 [thread overview]
Message-ID: <FF69608E-EE3A-40E3-A02B-A6BF8FDE4800@gmail.com> (raw)
In-Reply-To: <3549625.aeNJFYEL58@senjougahara>
17 вересня 2025 р. 05:44:42 GMT+03:00, Mikko Perttunen <mperttunen@nvidia.com> пише:
>On Wednesday, August 27, 2025 8:37 PM Svyatoslav Ryhel wrote:
>> Add nodes for devices on the HOST1X bus: VI, EPP, ISP, MSENC and TSEC.
>>
>> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
>> ---
>> arch/arm/boot/dts/nvidia/tegra114.dtsi | 64 ++++++++++++++++++++++++++
>> 1 file changed, 64 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/nvidia/tegra114.dtsi b/arch/arm/boot/dts/nvidia/tegra114.dtsi
>> index 4caf2073c556..8600a5c52be9 100644
>> --- a/arch/arm/boot/dts/nvidia/tegra114.dtsi
>> +++ b/arch/arm/boot/dts/nvidia/tegra114.dtsi
>> @@ -47,6 +47,45 @@ host1x@50000000 {
>>
>> ranges = <0x54000000 0x54000000 0x01000000>;
>>
>> + vi@54080000 {
>> + compatible = "nvidia,tegra114-vi";
>> + reg = <0x54080000 0x00040000>;
>> + interrupts = <GIC_SPI 69 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&tegra_car TEGRA114_CLK_VI>;
>> + resets = <&tegra_car 20>;
>> + reset-names = "vi";
>
>You are adding reset-names here, but in the last patch you're removing it where there's only one reset?
I am not "adding" it, it is present in the existing schema and I am making node accordingly. I have no intention to touch schema unless it is absolutely necessary.
>> +
>> + iommus = <&mc TEGRA_SWGROUP_VI>;
>> +
>> + status = "disabled";
>> + };
>> +
>> + epp@540c0000 {
>> + compatible = "nvidia,tegra114-epp";
>> + reg = <0x540c0000 0x00040000>;
>> + interrupts = <GIC_SPI 70 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&tegra_car TEGRA114_CLK_EPP>;
>> + resets = <&tegra_car TEGRA114_CLK_EPP>;
>> + reset-names = "epp";
>> +
>> + iommus = <&mc TEGRA_SWGROUP_EPP>;
>> +
>> + status = "disabled";
>> + };
>> +
>> + isp@54100000 {
>> + compatible = "nvidia,tegra114-isp";
>> + reg = <0x54100000 0x00040000>;
>> + interrupts = <GIC_SPI 71 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&tegra_car TEGRA114_CLK_ISP>;
>> + resets = <&tegra_car TEGRA114_CLK_ISP>;
>> + reset-names = "isp";
>> +
>> + iommus = <&mc TEGRA_SWGROUP_ISP>;
>> +
>> + status = "disabled";
>> + };
>> +
>> gr2d@54140000 {
>> compatible = "nvidia,tegra114-gr2d";
>> reg = <0x54140000 0x00040000>;
>> @@ -149,6 +188,31 @@ dsib: dsi@54400000 {
>> #address-cells = <1>;
>> #size-cells = <0>;
>> };
>> +
>> + msenc@544c0000 {
>> + compatible = "nvidia,tegra114-msenc";
>> + reg = <0x544c0000 0x00040000>;
>> + interrupts = <GIC_SPI 68 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&tegra_car TEGRA114_CLK_MSENC>;
>> + resets = <&tegra_car TEGRA114_CLK_MSENC>;
>> + reset-names = "mpe";
>
>FWIW, I think 'msenc' is the appropriate name to use on Tegra114/Tegra124. I believe MPE is a remnant from older chips, even if some downstream (and I guess upstreaming) naming still uses it.
>
Same here, I am making those according to schema and I will not touch it if not neceserry.
>> +
>> + iommus = <&mc TEGRA_SWGROUP_MSENC>;
>> +
>> + status = "disabled";
>> + };
>> +
>> + tsec@54500000 {
>> + compatible = "nvidia,tegra114-tsec";
>> + reg = <0x54500000 0x00040000>;
>> + interrupts = <GIC_SPI 50 IRQ_TYPE_LEVEL_HIGH>;
>> + clocks = <&tegra_car TEGRA114_CLK_TSEC>;
>> + resets = <&tegra_car TEGRA114_CLK_TSEC>;
>> +
>> + iommus = <&mc TEGRA_SWGROUP_TSEC>;
>> +
>> + status = "disabled";
>> + };
>> };
>>
>> gic: interrupt-controller@50041000 {
>>
>
>
>
next prev parent reply other threads:[~2025-09-17 4:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 11:37 [PATCH v5 0/4] ARM: tegra: complete Tegra 4 and Tegra K1 device trees Svyatoslav Ryhel
2025-08-27 11:37 ` [PATCH v5 1/4] dt-bindings: display: tegra: document EPP, ISP, MPE and TSEC for Tegra114+ Svyatoslav Ryhel
2025-08-29 16:50 ` Rob Herring (Arm)
2025-08-27 11:37 ` [PATCH v5 2/4] ARM: tegra114: add missing HOST1X device nodes Svyatoslav Ryhel
2025-09-17 2:44 ` Mikko Perttunen
2025-09-17 4:09 ` Svyatoslav [this message]
2025-08-27 11:37 ` [PATCH v5 3/4] ARM: tegra124: " Svyatoslav Ryhel
2025-08-27 11:37 ` [PATCH v5 4/4] arm64: tegra210: drop redundant clock and reset names from TSEC node Svyatoslav Ryhel
2025-09-18 1:41 ` [PATCH v5 0/4] ARM: tegra: complete Tegra 4 and Tegra K1 device trees Mikko Perttunen
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=FF69608E-EE3A-40E3-A02B-A6BF8FDE4800@gmail.com \
--to=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=treding@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox