| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- start switch to b_host role via sysfs
- control vbus output power
- can be used to start charging when a charger with ID
grounded is first connected to the device and then to the
wall outlet
- enable/disable pulldown resistors via sysfs,
can be used to emulate a connection to a usb host,
useful for switching to b_host when using y-cables
- script for entering b_host mode
Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
|
| |
|
|
|
|
| |
We keep also vram parameter for backward compatibility with older kernels.
Signed-off-by: Marek Belisko <marek@goldelico.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
so that we can now use a single configuration file for all
GTA04-custom variants. The trick is to evaluate the mux=
command line argument and update the kernel data structures
dynamically so that finally we load a different panel
driver and have different platform data for the touch
screen.
The same mechanism can be used in the future to enable
custom board specific features like RFID reader etc.
Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Enhance jack detection to differentiate with and without a microphone,
and to report a button-press when the microphone is shorted.
Signed-off-by: NeilBrown <neilb@suse.de>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As headset-insert doesn't generate an interrupt we need to
poll the MICSENSE line to see if a headset is present.
We do this every 500ms. It takes nearly that long to physically
insert a jack, so much faster wouldn't help and would impact
power drain more.
As detection is done by polling, a jack-insert or removal event cannot
wake the device from suspend. Events are only detected while device
is awake.
We keep the HSMIC bias enabled whenever the 'input' device is open,
except during suspend so that we can poll reliably. Turning it off
and on seems to interfere with reliable measurements.
Currently a reading below 100 is 'nothing plugged in' while a reading
above that is 'mic and headphone plugged in'.
I measure between 19 and 26 when nothing is plugged in, and between
804 and 811 when a headset is plugged in.
Input device will appear as
/dev/input/jack
if the udev rules file in GTA04/udev-rules/input.rules
is installed.
Signed-off-by: NeilBrown <neilb@suse.de>
|
| |
|
|
|
|
|
| |
Enhance jack detection to differentiate with and without a microphone,
and to report a button-press when the microphone is shorted.
Signed-off-by: NeilBrown <neilb@suse.de>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As headset-insert doesn't generate an interrupt we need to
poll the MICSENSE line to see if a headset is present.
We do this every 500ms. It takes nearly that long to physically
insert a jack, so much faster wouldn't help and would impact
power drain more.
As detection is done by polling, a jack-insert or removal event cannot
wake the device from suspend. Events are only detected while device
is awake.
We keep the HSMIC bias enabled whenever the 'input' device is open,
except during suspend so that we can poll reliably. Turning it off
and on seems to interfere with reliable measurements.
Currently a reading below 100 is 'nothing plugged in' while a reading
above that is 'mic and headphone plugged in'.
I measure between 19 and 26 when nothing is plugged in, and between
804 and 811 when a headset is plugged in.
Input device will appear as
/dev/input/jack
if the udev rules file in GTA04/udev-rules/input.rules
is installed.
Signed-off-by: NeilBrown <neilb@suse.de>
|
| |
|
|
|
|
| |
works with new jack driver support.
Signed-off-by: NeilBrown <neilb@suse.de>
|
| |
|
|
|
|
|
| |
This ensures correct wakeup handling and make it easy to
integrate with existing code.
Signed-off-by: NeilBrown <neilb@suse.de>
|
| |
|
|
|
|
|
| |
Add a 'multi_vibe' which rumbles several times in quick succession.
Can the interface a bit.
Signed-off-by: NeilBrown <neilb@suse.de>
|
| |
|
|
| |
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
Currently:
README: explaining other files and how to compile
udev-rules/: config files to ensure stable device names.
Signed-off-by: NeilBrown <neilb@suse.de>
|
