From: "Rob Herring (Arm)" <robh@kernel.org>
To: "Sheetal ." <sheetal@nvidia.com>
Cc: linux-sound@vger.kernel.org, broonie@kernel.org,
krzk+dt@kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, perex@perex.cz, conor+dt@kernel.org,
lgirdwood@gmail.com, linux-tegra@vger.kernel.org, tiwai@suse.com
Subject: Re: [PATCH 2/3] dt-bindings: Document Tegra264 HDA Support
Date: Wed, 14 May 2025 16:52:04 -0500 [thread overview]
Message-ID: <174725952441.3101271.15433560346114148625.robh@kernel.org> (raw)
In-Reply-To: <20250512064258.1028331-3-sheetal@nvidia.com>
On Mon, 12 May 2025 06:42:57 +0000, Sheetal . wrote:
> From: Sheetal <sheetal@nvidia.com>
>
> For Tegra264 device there is one clock, two resets and no power-domain.
> Add the Tegra264 compatible and necessary logic to the binding doc to
> determine appropriate clocks, resets and power-domain properties based
> on the compatible string.
>
> Signed-off-by: Sheetal <sheetal@nvidia.com>
> ---
> .../bindings/sound/nvidia,tegra30-hda.yaml | 25 +++++++++++++++++--
> 1 file changed, 23 insertions(+), 2 deletions(-)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-05-14 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 6:42 [PATCH 0/2] HDA: Add Tegra264 support Sheetal .
2025-05-12 6:42 ` [PATCH 1/3] dt-bindings: Update Tegra194 and Tegra234 HDA bindings Sheetal .
2025-05-14 21:49 ` Rob Herring
2025-05-15 5:24 ` Sheetal .
2025-05-14 21:50 ` Rob Herring (Arm)
2025-05-12 6:42 ` [PATCH 2/3] dt-bindings: Document Tegra264 HDA Support Sheetal .
2025-05-14 21:52 ` Rob Herring (Arm) [this message]
2025-05-12 6:42 ` [PATCH 3/3] ALSA: hda/tegra: Add Tegra264 support Sheetal .
2025-05-15 10:48 ` [PATCH 0/2] HDA: " Takashi Iwai
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=174725952441.3101271.15433560346114148625.robh@kernel.org \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@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=perex@perex.cz \
--cc=sheetal@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