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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 8 May 2013 16:07:29 +0100
From:	Lee Jones <lee.jones@...aro.org>
To:	Mark Brown <broonie@...nel.org>
Cc:	Fabio Baltieri <fabio.baltieri@...aro.org>,
	Liam Girdwood <lgirdwood@...il.com>,
	alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
	Linus Walleij <linus.walleij@...aro.org>,
	Ola Lilja <ola.o.lilja@...ricsson.com>
Subject: Re: [PATCH 3/6] ASoC: ux500: Drop pinctrl sleep support

On Wed, 08 May 2013, Mark Brown wrote:

> On Wed, May 08, 2013 at 04:27:34PM +0200, Fabio Baltieri wrote:
> > On Wed, May 08, 2013 at 04:17:23PM +0200, Fabio Baltieri wrote:
> 
> > > Ok, what I'm trying to say is that the codec used in this platform
> > > should be able to handle sleep modes without requiring any
> > > reconfiguration of the digital interface on the SoC side.  In support of
> > > this the fact that the STE fork of the driver does not do that, and the
> > > same goes for all other ASoC drivers currently in mainline.
> 
> > And by the way, if the current code is *really* setting the digital
> > audio bus pins in hi-z mode (without any pull-up/down/keeper) as it
> > claims, this is not just usless, it's plain wrong.  The bus should never
> > be left floating on both sides, right?
> 
> Probably not, no.

Why don't we wait and see what LinusW says?

If anyone would know, it's him.

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ