From: "Sheetal ." <sheetal@nvidia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
lgirdwood@gmail.com, broonie@kernel.org
Cc: perex@perex.cz, tiwai@suse.com, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sound@vger.kernel.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, spujar@nvidia.com, mkumard@nvidia.com
Subject: Re: [PATCH v3 01/11] dt-bindings: ASoC: admaif: Add missing properties
Date: Thu, 22 May 2025 21:35:56 +0530 [thread overview]
Message-ID: <6f3c4afa-e8e3-44c7-9323-eac02bd558d2@nvidia.com> (raw)
In-Reply-To: <54078715-84f9-4d6d-8c9c-2517f5972225@kernel.org>
On 22-05-2025 19:55, Krzysztof Kozlowski wrote:
> External email: Use caution opening links or attachments
>
>
> On 12/05/2025 07:17, Sheetal . wrote:
>> From: Sheetal <sheetal@nvidia.com>
>>
>> Add optional interconnect and iommu properties to admaif yaml. These
>> properties are supported from Tegra186 SoC onwards.
>>
>> This fixes below dtbs_check error for Tegra194 and Tegra234:
>> 'interconnect-names', 'interconnects', 'iommus' do not match any of the regexes: 'pinctrl-[0-9]+'
>
>
> You never responded - I reported it is not possible to reproduce it.
> Instead of sending the same, please address the feedback.
>
> How this can be reproduced?
Apologies for misinterpreting the comment. I have updated the patch with
properties based on compatibles and add info from which SoC onwards
these properties can be used.
Below command throws the errors for all the Tegra194 and Tegra234 dtbs,
"make dtbs_check DT_SCHEMA_FILES=nvidia,tegra210-admaif.yaml"
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-05-22 16:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 5:17 [PATCH v3 00/11] Add Tegra264 support in AHUB drivers Sheetal .
2025-05-12 5:17 ` [PATCH v3 01/11] dt-bindings: ASoC: admaif: Add missing properties Sheetal .
2025-05-14 21:46 ` Rob Herring (Arm)
2025-05-22 14:25 ` Krzysztof Kozlowski
2025-05-22 16:05 ` Sheetal . [this message]
2025-05-12 5:17 ` [PATCH v3 02/11] dt-bindings: ASoC: Document Tegra264 APE support Sheetal .
2025-05-12 5:17 ` [PATCH v3 03/11] ASoC: tegra: CIF: Add Tegra264 support Sheetal .
2025-05-12 5:17 ` [PATCH v3 04/11] ASoC: tegra: ADMAIF: " Sheetal .
2025-05-12 5:17 ` [PATCH v3 05/11] ASoC: tegra: ASRC: Update ARAM address Sheetal .
2025-05-12 5:17 ` [PATCH v3 06/11] ASoC: tegra: Update PLL rate for Tegra264 Sheetal .
2025-05-12 5:17 ` [PATCH v3 07/11] ASoC: tegra: I2S: Add Tegra264 support Sheetal .
2025-05-12 5:17 ` [PATCH v3 08/11] ASoC: tegra: AMX: " Sheetal .
2025-05-12 5:17 ` [PATCH v3 09/11] ASoC: tegra: ADX: " Sheetal .
2025-05-12 5:17 ` [PATCH v3 10/11] ASoC: tegra: AHUB: " Sheetal .
2025-05-12 5:17 ` [PATCH v3 11/11] ASoC: tegra: Tegra264 support in isomgr_bw Sheetal .
2025-05-22 14:22 ` [PATCH v3 00/11] Add Tegra264 support in AHUB drivers 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=6f3c4afa-e8e3-44c7-9323-eac02bd558d2@nvidia.com \
--to=sheetal@nvidia.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=spujar@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.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).