From: Jon Hunter <jonathanh@nvidia.com>
To: "Sheetal ." <sheetal@nvidia.com>, Mark Brown <broonie@kernel.org>
Cc: Sander Vanheule <sander@svanheule.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Thierry Reding <thierry.reding@gmail.com>,
Mohan kumar <mkumard@nvidia.com>,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [RFC PATCH v3 1/4] ASoC: tegra: Add AHUB writeable_reg for RX holes
Date: Tue, 27 Jan 2026 19:27:07 +0000 [thread overview]
Message-ID: <07c39248-db3f-4584-b466-492cd79994f2@nvidia.com> (raw)
In-Reply-To: <20260123095346.1258556-2-sheetal@nvidia.com>
On 23/01/2026 09:53, Sheetal . wrote:
> From: Sheetal <sheetal@nvidia.com>
>
> Add writeable_reg callbacks for Tegra210/186 AHUB RX registers so the
> flat cache only treats valid RX locations as writable, avoiding holes
> in the register map.
>
> Fixes: 16e1bcc2caf4 ("ASoC: tegra: Add Tegra210 based AHUB driver")
> Signed-off-by: Sheetal <sheetal@nvidia.com>
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Thanks
Jon
--
nvpublic
next prev parent reply other threads:[~2026-01-27 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 9:53 [RFC PATCH v3 0/4] regmap: reg_default_cb for flat cache defaults Sheetal .
2026-01-23 9:53 ` [RFC PATCH v3 1/4] ASoC: tegra: Add AHUB writeable_reg for RX holes Sheetal .
2026-01-27 19:27 ` Jon Hunter [this message]
2026-01-23 9:53 ` [RFC PATCH v3 2/4] regmap: Add reg_default_cb callback for flat cache defaults Sheetal .
2026-01-27 19:29 ` Jon Hunter
2026-01-23 9:53 ` [RFC PATCH v3 3/4] ASoC: tegra: set reg_default_cb callback Sheetal .
2026-01-27 19:29 ` Jon Hunter
2026-01-23 9:53 ` [RFC PATCH v3 4/4] regmap: add KUnit coverage for " Sheetal .
2026-01-28 4:31 ` (subset) [RFC PATCH v3 0/4] regmap: reg_default_cb for flat cache defaults Mark Brown
2026-01-29 11:13 ` 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=07c39248-db3f-4584-b466-492cd79994f2@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.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=rafael@kernel.org \
--cc=sander@svanheule.net \
--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