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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Mon, 28 Dec 2020 16:03:52 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc:     linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
        patches@...nsource.cirrus.com
Subject: Re: [PATCH] ASoC: wm_adsp: Improve handling of raw byte streams

On Wed, 16 Dec 2020 11:25:12 +0000, Richard Fitzgerald wrote:
> As the register map is 16-bit or 32-bit big-endian, the 24-bit
> DSP words appear padded and with the bytes swapped. When reading a
> raw stream of bytes, the pad bytes must be removed and the data bytes
> swapped back to their original order.
> 
> The previous implementation of this assumed that the be32_to_cpu() in
> wm_adsp_read_data_block() would swap back to little-endian. But this is
> obviously only true on a little-endian CPU. It also made two walks
> through the data, once to endian-swap and again to strip the pad bytes.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: wm_adsp: Improve handling of raw byte streams
      commit: 7726e49837af634accaec317c8d246d1d90d8fc5

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