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: <20151105102655.GN1717@sirena.org.uk>
Date:	Thu, 5 Nov 2015 10:26:55 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
Cc:	Robert Jarzmik <robert.jarzmik@...e.fr>,
	Liam Girdwood <lgirdwood@...il.com>,
	Jaroslav Kysela <perex@...ex.cz>,
	Takashi Iwai <tiwai@...e.com>,
	patches@...nsource.wolfsonmicro.com, alsa-devel@...a-project.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: wm9713: add gpio chip

On Wed, Nov 04, 2015 at 06:33:22PM +0000, Charles Keepax wrote:

> You should probably make a seperate driver within GPIO for this
> and then tie the two together, using an MFD. I appreciate that is
> more work but it is likely a nicer solution overall.

GPIO chips are small and simple enough that we've not worried about it
historically.  However my question here is why this is wm9713 specific -
the GPIO functionality is part of the AC'97 spec and present on many
AC'97 chips so it seems sensible to have something at the AC'97 level.
Unfortunately a quick check seems not to show anything indicating this
in the AC'97 capability information so we might want to make it opt in.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ