lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220614091548.GC38351@ediswmail.ad.cirrus.com>
Date:   Tue, 14 Jun 2022 09:15:48 +0000
From:   Charles Keepax <ckeepax@...nsource.cirrus.com>
To:     Samuel Holland <samuel@...lland.org>
CC:     <broonie@...nel.org>, <matthias.bgg@...il.com>, <wens@...e.org>,
        <jernej.skrabec@...il.com>, <linux-mediatek@...ts.infradead.org>,
        <linux-sunxi@...ts.linux.dev>, <lgirdwood@...il.com>,
        <alsa-devel@...a-project.org>, <patches@...nsource.cirrus.com>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] ASoC: sun8i-codec: Partial revert to fix clock
 specifiers

On Tue, Jun 14, 2022 at 01:39:20AM -0500, Samuel Holland wrote:
> Hi Charles,
> 
> On 6/13/22 11:15 AM, Charles Keepax wrote:
> > Recent updates accidentally updated the clock producer/consumer
> > specifiers on this device as part of refactoring the CPU side of the DAI
> > links. However, this device sits on the CODEC side and shouldn't have
> > been updated. Partially revert the changes keeping the switch to the new
> > clock terminology but going back to the CODEC defines.
> > 
> > Fixes: 7cc3965fde74 ("ASoC: sunxi: Update to use set_fmt_new callback")
> > Reported-by: Samuel Holland <samuel@...lland.org>
> > Signed-off-by: Charles Keepax <ckeepax@...nsource.cirrus.com>
> 
> Reviewed-by: Samuel Holland <samuel@...lland.org>
> Tested-by: Samuel Holland <samuel@...lland.org>
> 
> Thanks for the quick follow-up, and sorry for the confusion my earlier comment
> caused. I verified that sound is broken (loud static) on a Pine A64-LTS board
> with for-next, and is fixed by this patch.

Not at all man, thank you for spotting my foolish mistake. Glad
we got it fixed up for you, and thank you for testing it.

Thanks,
Charles

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ