linux-kernel - Re: Headset driver detection problem during bootup

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: <20110820174017.GA28142@opensource.wolfsonmicro.com>
Date:	Sat, 20 Aug 2011 18:40:18 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	anish singh <anish198519851985@...il.com>
Cc:	linux-kernel-mail <linux-kernel@...r.kernel.org>,
	Kernel-newbies <kernelnewbies@...linux.org>,
	Jonathan Cameron <jic23@....ac.uk>,
	Dave Hylands <dhylands@...il.com>
Subject: Re: Headset driver detection problem during bootup

On Fri, Aug 19, 2011 at 09:23:13PM +0900, anish singh wrote:

> Once the handler is called then we find out if the headset
> is there or not using gpio and then normal detection happens

> Is it the right way to detect the device during power-up?

> After the device is powered up and then if we insert headset
> then it is working fine by calling the interrupt handler and
> everything goes fine.

The standard soc-jack code should already be reading the state of the
GPIO as part of its startup.
--
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/