[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d3c28a8b-878c-4894-aa23-5b360153b85d@sirena.org.uk>
Date: Wed, 6 Nov 2024 13:43:33 +0000
From: Mark Brown <broonie@...nel.org>
To: Claudiu <claudiu.beznea@...on.dev>
Cc: geert+renesas@...der.be, mturquette@...libre.com, sboyd@...nel.org,
robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
biju.das.jz@...renesas.com, prabhakar.mahadev-lad.rj@...renesas.com,
lgirdwood@...il.com, magnus.damm@...il.com,
linus.walleij@...aro.org, support.opensource@...semi.com,
perex@...ex.cz, tiwai@...e.com, p.zabel@...gutronix.de,
Adam.Thomson.Opensource@...semi.com,
linux-renesas-soc@...r.kernel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-sound@...r.kernel.org, linux-gpio@...r.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@...renesas.com>,
stable@...r.kernel.org
Subject: Re: [PATCH 22/31] ASoC: da7213: Populate max_register to
regmap_config
On Wed, Nov 06, 2024 at 10:18:17AM +0200, Claudiu wrote:
> From: Claudiu Beznea <claudiu.beznea.uj@...renesas.com>
>
> On the Renesas RZ/G3S SMARC Carrier II board having a DA7212 codec (using
> da7213 driver) connected to one SSIF-2 available on the Renesas RZ/G3S SoC
> it has been discovered that using the runtime PM API for suspend/resume
> (as will be proposed in the following commits) leads to the codec not
> being propertly initialized after resume. This is because w/o
> max_register populated to regmap_config the regcache_rbtree_sync()
> breaks on base_reg > max condition and the regcache_sync_block() call is
> skipped.
>
> Fixes: ef5c2eba2412 ("ASoC: codecs: Add da7213 codec")
> Cc: stable@...r.kernel.org
Why is this a stable fix when it only enables further work?
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists