linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <CAK7N6vrj8V+7EYLmd92qd+Mae2KZu8K6BVwnwda=3y2vrcDWRw@mail.gmail.com>
Date:	Fri, 19 Aug 2011 21:23:13 +0900
From:	anish singh <anish198519851985@...il.com>
To:	linux-kernel-mail <linux-kernel@...r.kernel.org>,
	Kernel-newbies <kernelnewbies@...linux.org>
Cc:	broonie@...nsource.wolfsonmicro.com,
	Jonathan Cameron <jic23@....ac.uk>,
	Dave Hylands <dhylands@...il.com>
Subject: Headset driver detection problem during bootup

I need some suggestions for below situation:

Headset if it is inserted before the device is powered up is
now detected by forcefully calling the interrupt handler in
the probe function of the headset driver.
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.

linux -2.3.5
Android Device
--
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/