linux-kernel - Re: [PATCH] ASoC: mxs-saif: check BUSY bit in hw_params() only if not mclk_in

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]

Date:	Fri, 05 Feb 2016 13:23:20 +0000
From:	Måns Rullgård <mans@...sr.com>
To:	Mark Brown <broonie@...nel.org>
Cc:	Liam Girdwood <lgirdwood@...il.com>,
	Jaroslav Kysela <perex@...ex.cz>,
	Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: mxs-saif: check BUSY bit in hw_params() only if not mclk_in_use

Mark Brown <broonie@...nel.org> writes:

> On Wed, Feb 03, 2016 at 01:18:20PM +0000, Mans Rullgard wrote:
>> If something else, typically a codec, has enabled mclk, the BUSY
>> bit may be set when hw_params() is called without this being an
>> error.  This check thus causes intermittent failures to configure
>> the sound device when used in such a manner.  Fix this by making
>> the test conditional on !saif->mclk_in_use.
>
> Please remember to CC the maintainers for the driver when sending
> patches.  

I CCd everybody scripts/get_maintainers.pl suggested.  How am I supposed
to know who the maintainers are if they're not listed in MAINTAINERS?

-- 
Måns Rullgård