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
| ||
|
Date: Tue, 16 Jun 2015 15:47:10 +0800 From: Zidan Wang <zidan.wang@...escale.com> To: Charles Keepax <ckeepax@...nsource.wolfsonmicro.com> CC: <broonie@...nel.org>, <lgirdwood@...il.com>, <perex@...ex.cz>, <tiwai@...e.de>, <lars@...afoo.de>, <patches@...nsource.wolfsonmicro.com>, <alsa-devel@...a-project.org>, <linux-kernel@...r.kernel.org> Subject: Re: [alsa-devel][PATCH 2/4] ASoC: wm8960: support configure headphone jack detect pin and polarity from device tree On Fri, Jun 12, 2015 at 01:50:05PM +0100, Charles Keepax wrote: > On Thu, Jun 11, 2015 at 07:14:34PM +0800, Zidan Wang wrote: > > The ADCLRC/GPIO1, LINPUT3/JD2 and RINPUT3/JD3 pins can be selected as > > headphone jack detect inputs to automatically disable the speaker output > > and enable the headphone. > > > > Signed-off-by: Zidan Wang <zidan.wang@...escale.com> > > --- > > This feels like this is missing some iteraction with DAPM, there > are DAPM widgets that represent both the Speaker and the > Headphone, in the case this feature is in use the power state > DAPM shows may no longer accurately reflects the actual power > state of the device. > > That said I have no idea if the registers update on the chip to > reflect this change (my guess is that they don't). I am not > really sure what the correct way to handle this sort of hardware > output switching would be in DAPM. > > Thanks, > Charles Yes, there are no registers represent that it is playback from headphone or speaker. So the hardware should connect the headphone detect output to CPU GPIO pin instead of the codec headphone detect pin? Best Regards, Zidan Wang -- 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