[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024020205-suffering-paparazzi-8a49@gregkh>
Date: Fri, 2 Feb 2024 17:13:50 -0800
From: Greg KH <gregkh@...uxfoundation.org>
To: kovalev@...linux.org
Cc: stable@...r.kernel.org, linux-kernel@...r.kernel.org,
alsa-devel@...a-project.org, u.kleine-koenig@...gutronix.de,
a.firago@...ro.com, sashal@...nel.org, zhuning0077@...il.com,
tiwai@...e.com, perex@...ex.cz, broonie@...nel.org,
lgirdwood@...il.com
Subject: Re: [PATCH 6.1.y 0/7] ASoC: codecs: es8326: fix support
On Tue, Jan 30, 2024 at 12:47:01PM +0300, kovalev@...linux.org wrote:
> These patches were backported from v6.6 upstream and
> are intended for 6.1.y stable kernel.
>
> Patches have been successfully tested on the latest 6.1.75 kernel.
>
> [PATCH 6.1.y 1/7] ASoC: codecs: es8326: Convert to i2c's .probe_new()
> [PATCH 6.1.y 2/7] ASoC: codecs: ES8326: Add es8326_mute function
> [PATCH 6.1.y 3/7] ASoC: codecs: ES8326: Change Hp_detect register names
> [PATCH 6.1.y 4/7] ASoC: codecs: ES8326: Change Volatile Reg function
> [PATCH 6.1.y 5/7] ASoC: codecs: ES8326: Fix power-up sequence
> [PATCH 6.1.y 6/7] ASOC: codecs: ES8326: Add calibration support for
> [PATCH 6.1.y 7/7] ASoC: codecs: ES8326: Update jact detection function
>
>
What exactly is being "fixed" here? Was the driver not working properly
in 5.15? What broke in 6.1? Or has this hardware just never worked?
These all don't seem to be fixes, so what is the need for these?
confused,
greg k-h
Powered by blists - more mailing lists