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] [day] [month] [year] [list]
Date:	Thu, 20 Sep 2012 07:59:10 -0400
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Ashish Chavan <ashish.chavan@...tcummins.com>
Cc:	lrg <lrg@...com>, alsa-devel <alsa-devel@...a-project.org>,
	David Dajun Chen <david.chen@...semi.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [alsa-devel] [PATCH v2] ASoC: codecs: Add DA9055 codec driver

On Thu, Sep 20, 2012 at 05:28:55PM +0530, Ashish Chavan wrote:

> > > +	/* To select if MIC Bias powers MIC 1 or MIC 2 */
> > > +	SOC_ENUM("Mic Bias Select", da9055_mic_bias_select),

> > This would normally be something controlled by the board...  what
> > exactly is this doing?  How does the MICBIAS relate to the microphone
> > inputs?

> Yes, it should be controlled by the board.
> This control selects which of the two MIC Bias pins acts as the BIAS
> source. Earlier we misinterpreted it because of a hardware modification
> which was present on the board without our knowledge.

OK, that sounds like it should either be hooked up in the DAPM graph
or supplied as platform data then.

> > Given that there's no regulator support here
> > it's also a bit surprising that you need to do a sync outside of system
> > suspend...

> I am not sure if I understood this fully. Do you mean a sync is not
> required here?

You only need to resync if the device might have lost power and
forgotten it's register settings (or might've forgotten them for some
other reason).  If the device is left powered up then this isn't needed.
--
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