From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Sheetal ." <sheetal@nvidia.com>, "Rob Herring (Arm)" <robh@kernel.org>
Cc: devicetree@vger.kernel.org, Sameer Pujar <spujar@nvidia.com>,
linux-sound@vger.kernel.org, Mark Brown <broonie@kernel.org>,
dmaengine@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
Marc Zyngier <maz@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH V2 0/4] Add tegra264 audio device tree support
Date: Tue, 7 Oct 2025 10:07:40 +0900 [thread overview]
Message-ID: <164411f7-7925-491c-a24f-30021cab3f99@kernel.org> (raw)
In-Reply-To: <4cc27ab8-4e59-45b9-9383-183f78da47a6@nvidia.com>
On 30/09/2025 15:24, Sheetal . wrote:
>
>
> On 29-09-2025 20:58, Rob Herring (Arm) wrote:
>> External email: Use caution opening links or attachments
>>
>>
>> On Mon, 29 Sep 2025 16:29:26 +0530, Sheetal . wrote:
>>> From: sheetal <sheetal@nvidia.com>
>>>
>>> Add device tree support for tegra264 audio subsystem including:
>>> - Binding update for
>>> - 64-channel ADMA controller
>>> - 32 RX/TX ADMAIF channels
>>> - tegra264-agic binding for arm,gic
>>> - Add device tree nodes for
>>> - APE subsystem (ACONNECT, AGIC, ADMA, AHUB and children (ADMAIF, I2S,
>>> DMIC, DSPK, MVC, SFC, ASRC, AMX, ADX, OPE and Mixer) nodes
>>> - HDA controller
>>> - sound
>>>
>>> Note:
>>> The change is dependent on https://patchwork.ozlabs.org/project/linux-tegra/patch/20250818135241.3407180-1-thierry.reding@gmail.com/
>>>
>>> ...
>>> Changes in V2:
>>> - Update the allOf condition in Patch 2/4.
>>>
>>> sheetal (4):
>>> dt-bindings: dma: Update ADMA bindings for tegra264
>>> dt-bindings: sound: Update ADMAIF bindings for tegra264
>>> dt-bindings: interrupt-controller: arm,gic: Add tegra264-agic
>>> arm64: tegra: Add tegra264 audio support
>>>
>>> .../bindings/dma/nvidia,tegra210-adma.yaml | 15 +-
>>> .../interrupt-controller/arm,gic.yaml | 1 +
>>> .../sound/nvidia,tegra210-admaif.yaml | 106 +-
>>> .../arm64/boot/dts/nvidia/tegra264-p3971.dtsi | 106 +
>>> arch/arm64/boot/dts/nvidia/tegra264.dtsi | 3190 +++++++++++++++++
>>> 5 files changed, 3377 insertions(+), 41 deletions(-)
>>>
>>> --
>>> 2.34.1
>>>
>>>
>>>
>>
>>
>> My bot found new DTB warnings on the .dts files added or changed in this
>> series.
>>
>> Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
>> are fixed by another series. Ultimately, it is up to the platform
>> maintainer whether these warnings are acceptable or not. No need to reply
>> unless the platform maintainer has comments.
>>
>> If you already ran DT checks and didn't see these error(s), then
>> make sure dt-schema is up to date:
>>
>> pip3 install dtschema --upgrade
>>
>>
>> This patch series was applied (using b4) to base:
>> Base: attempting to guess base-commit...
>> Base: tags/v6.17-rc1-57-g635ae6f0a3ad (exact match)
>>
>> If this is not the correct base, please add 'base-commit' tag
>> (or use b4 which does this automatically)
>>
>> New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/nvidia/' for 20250929105930.1767294-1-sheetal@nvidia.com:
>>
>> In file included from arch/arm64/boot/dts/nvidia/tegra264-p3834.dtsi:3,
>> from arch/arm64/boot/dts/nvidia/tegra264-p3834-0008.dtsi:3,
>> from arch/arm64/boot/dts/nvidia/tegra264-p3971-0089+p3834-0008.dts:5:
>> arch/arm64/boot/dts/nvidia/tegra264.dtsi:8:10: fatal error: dt-bindings/power/nvidia,tegra264-powergate.h: No such file or directory
>
> This error is expected.
> "dt-bindings/power/nvidia,tegra264-powergate.h" file is being added in
> https://patchwork.ozlabs.org/project/linux-tegra/patch/20250818135241.3407180-1-thierry.reding@gmail.com/,
> in the cover letter it is mentioned as dependent of that change in the
> 'Note'.
>
If you expect your patch not to be ignored after such feedback, explain
briefly missing dependency in the patch changelog. Not cover letter.
You will get this report every time and maintainers might ignore your
patch, due to unresolved reports from automation.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-07 1:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 10:59 [PATCH V2 0/4] Add tegra264 audio device tree support Sheetal .
2025-09-29 10:59 ` [PATCH V2 1/4] dt-bindings: dma: Update ADMA bindings for tegra264 Sheetal .
2025-10-30 19:25 ` Thierry Reding
2025-09-29 10:59 ` [PATCH V2 2/4] dt-bindings: sound: Update ADMAIF " Sheetal .
2025-10-06 21:36 ` Rob Herring (Arm)
2025-09-29 10:59 ` [PATCH V2 3/4] dt-bindings: interrupt-controller: arm,gic: Add tegra264-agic Sheetal .
2025-09-29 10:59 ` [PATCH V2 4/4] arm64: tegra: Add tegra264 audio support Sheetal .
2025-10-30 19:24 ` Thierry Reding
2025-09-29 15:28 ` [PATCH V2 0/4] Add tegra264 audio device tree support Rob Herring (Arm)
2025-09-30 6:24 ` Sheetal .
2025-10-07 1:07 ` Krzysztof Kozlowski [this message]
2025-10-15 16:22 ` (subset) " Mark Brown
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=164411f7-7925-491c-a24f-30021cab3f99@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robh@kernel.org \
--cc=sheetal@nvidia.com \
--cc=spujar@nvidia.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).