From: Mark Brown <broonie@kernel.org>
To: Sameer Pujar <spujar@nvidia.com>
Cc: lgirdwood@gmail.com, tiwai@suse.com, perex@perex.cz,
robh+dt@kernel.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, mkumard@nvidia.com,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/5] ASoC: tegra: Update AHUB driver for Tegra234
Date: Wed, 26 Jan 2022 16:50:44 +0000 [thread overview]
Message-ID: <YfF75N97CzLNDRMs@sirena.org.uk> (raw)
In-Reply-To: <1643100491-5398-2-git-send-email-spujar@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
On Tue, Jan 25, 2022 at 02:18:07PM +0530, Sameer Pujar wrote:
> From: Mohan Kumar <mkumard@nvidia.com>
>
> The register offsets of switches connecting various AHUB internal
> modules have changed from previous chip. Address this variation by
> making use of Tegra234 based compatible.
This doesn't apply against current code, please check and resend.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-01-26 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 8:48 [PATCH 0/5] Tegra234 APE support Sameer Pujar
2022-01-25 8:48 ` [PATCH 1/5] ASoC: tegra: Update AHUB driver for Tegra234 Sameer Pujar
2022-01-26 16:50 ` Mark Brown [this message]
2022-01-25 8:48 ` [PATCH 2/5] dt-bindings: Add Tegra234 APE support Sameer Pujar
2022-01-25 8:48 ` [PATCH 3/5] dt-bindings: Document " Sameer Pujar
2022-01-25 8:48 ` [PATCH 4/5] arm64: tegra: Add audio devices on Tegra234 Sameer Pujar
2022-01-25 8:48 ` [PATCH 5/5] arm64: tegra: APE sound card for Jetson AGX Orin Sameer Pujar
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=YfF75N97CzLNDRMs@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=perex@perex.cz \
--cc=robh+dt@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).