[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f2f81d3e-ac2d-4b24-b071-7beb4fb867e3@nvidia.com>
Date: Tue, 16 Dec 2025 16:06:53 +0530
From: "Sheetal ." <sheetal@...dia.com>
To: Mark Brown <broonie@...nel.org>, linux-sound@...r.kernel.org
Cc: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Charles Keepax <ckeepax@...nsource.cirrus.com>,
Sander Vanheule <sander@...nheule.net>, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: tegra: Fix uninitialized flat cache warning in
tegra210_ahub
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
>
Powered by blists - more mailing lists