Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Sheetal ." <sheetal@nvidia.com>
To: Mark Brown <broonie@kernel.org>, linux-sound@vger.kernel.org
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Charles Keepax <ckeepax@opensource.cirrus.com>,
	Sander Vanheule <sander@svanheule.net>,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: tegra: Fix uninitialized flat cache warning in tegra210_ahub
Date: Tue, 16 Dec 2025 16:06:53 +0530	[thread overview]
Message-ID: <f2f81d3e-ac2d-4b24-b071-7beb4fb867e3@nvidia.com> (raw)
In-Reply-To: <176580711685.161056.2870238132964388874.b4-ty@kernel.org>

Hi Mark,

This patch is causing issues with the tegra AHUB driver. Could you 
please drop it, or should I send a revert?

Thanks,
Sheetal

On 15-12-2025 19:28, Mark Brown wrote:
> External email: Use caution opening links or attachments
> 
> 
> On Mon, 08 Dec 2025 10:50:40 +0530, Sheetal . wrote:
>> The tegra210_ahub driver started triggering a warning after commit
>> e062bdfdd6ad ("regmap: warn users about uninitialized flat cache"),
>> which flags drivers using REGCACHE_FLAT without register defaults.
>> Since the driver omits default definitions because its registers are
>> zero initialized, the following warning is shown:
>>
>>    WARNING KERN tegra210-ahub 2900800.ahub: using zero-initialized flat cache, this may cause unexpected behavior
>>
>> [...]
> 
> Applied to
> 
>     https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
> 
> Thanks!
> 
> [1/1] ASoC: tegra: Fix uninitialized flat cache warning in tegra210_ahub
>        commit: 4d4021b0bbd1fad7c72b9155863f5b3ccb43ae91
> 
> All being well this means that it will be integrated into the linux-next
> tree (usually sometime in the next 24 hours) and sent to Linus during
> the next merge window (or sooner if it is a bug fix), however if
> problems are discovered then the patch may be dropped or reverted.
> 
> You may get further e-mails resulting from automated or manual testing
> and review of the tree, please engage with people reporting problems and
> send followup patches addressing any issues that are reported if needed.
> 
> If any updates are required or you are submitting further changes they
> should be sent as incremental updates against current git, existing
> patches will not be replaced.
> 
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
> 
> Thanks,
> Mark
> 


  reply	other threads:[~2025-12-16 10:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08  5:20 [PATCH] ASoC: tegra: Fix uninitialized flat cache warning in tegra210_ahub Sheetal .
2025-12-08 20:57 ` Sander Vanheule
2025-12-09  1:01   ` Mark Brown
2025-12-15 13:58 ` Mark Brown
2025-12-16 10:36   ` Sheetal . [this message]
2025-12-17 10:37     ` 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=f2f81d3e-ac2d-4b24-b071-7beb4fb867e3@nvidia.com \
    --to=sheetal@nvidia.com \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=jonathanh@nvidia.com \
    --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=sander@svanheule.net \
    --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