| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
|
|
| |
state changes.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
| |
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
|
|
|
| |
when enabled, prints out the function of each handler as they are called
Change-Id: I5ed251867e0e3aa3cd05f030ff3579808cedd0c2
Signed-off-by: Erik Gilling <konkers@android.com>
|
|
|
|
|
|
|
|
| |
Signed-off-by: Arve Hjønnevåg <arve@android.com>
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Conflicts:
kernel/power/Makefile
|
|
|
|
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Conflicts:
kernel/power/Makefile
kernel/power/power.h
|
|
|
|
|
|
|
|
|
| |
Since wall time can jump backwards, it cannot be used to determine if one
event occured before another or for how long a key was pressed.
Signed-off-by: Arve Hjønnevåg <arve@android.com>
Signed-off-by: Pankaj <pankaj.bharadiya@ti.com>
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
| |
This partially reverts commit 2b9b0b6a95cb7adbdd4fa03bff2c7dec86852aa0.
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
|
|
|
|
| |
Without that fix we have:
[...]/fs/binfmt_aout.c: In function 'load_aout_binary':
[...]/fs/binfmt_aout.c:255: error: 'SEGMENT_SIZE' undeclared (first use in this function)
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
|
|
|
|
| |
Without that fix we have:
activity_stats.c:(.text+0x46078): undefined reference to `rt6_lookup'
activity_stats.c:(.text+0x461b4): undefined reference to `in6addr_any'
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
|
|
| |
fix compilation.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
|
|
|
| |
Without that fix we have errors like:
error: plat/gpmc.h: No such file or directory
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
|
|
| |
I also enabled the wakelock for USB.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
| |
|
|
|
|
| |
Signed-off-by: PaulK <contact@paulk.fr>
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
|
|
|
| |
That permits us to experiment with different cmdline in the
bootloader: before there was CMDLINE_FORCE.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
| |
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
|
|
|
|
|
|
| |
pressures is being reported inverted - fix that
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
|
| |
One an hdq buss, a missing device reads as 0xff, not -1.
So do a translation to allow detecting of a missing bus.
Signed-off-by: NeilBrown <neilb@suse.de>
|
| |
|
|
|
|
|
|
| |
Seems to work at all
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
|
|
|
|
|
|
| |
If CORE and USBHOST both go the off-mode the first time
USBHOST does, then my device will not resume.
However if we let USBHOST go to off-mode and back will CORE is
in RETENSION at most, then subsequent off-mode transitions are
not a problem.
So for RETENTION for the first transition, and OFF for the next.
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is possible that the musb device will be runtime-active (not
suspended) when system suspend happens.
In particular, usb_suspend() will have called choose_wakeup() which
might have called pm_runtime_resume().
In that case, after system-resume, the state of the device will be
'active', but the state of the registers will have been lost (if
off_mode is enabled).
So we need to save_context in musb_suspend (if runtime state is
active), and restore_context on resume.
This effectively reverts
5d193ce8 (usb: musb: PM: fix context save/restore in suspend/resume path)
and adds a rest to avoid saving/restoring context if device is already
runtime suspended.
Tested-by: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Bilovol, Ruslan" <ruslan.bilovol@ti.com>
Cc: Igor Grinberg <grinberg@compulab.co.il>
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
|
| |
I'm sure sure that this does anything useful, but
let's have the code there and see.
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
|
| |
Before we enable off-mode, we really need the wakeup
to work, and I broke it recently.
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
| |
Maybe this will cause problems, maybe it will help...
|
|
|
|
|
|
|
| |
This primarily removes the pull up/down, which shouldn't
be much of a problem, but is best avoided.
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
| |
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
|
| |
If get_madc_conversion returns an error, we should ignore the value.
Reported-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
| |
It provides no value
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The context loss handling in dmtimer appears to assume that
omap_dm_timer_set_load_start() or omap_dm_timer_start()
and
omap_dm_timer_stop()
bracket all interactions. Only the first two restore the context and
the last updates the context loss counter.
However omap_dm_timer_set_load() or omap_dm_timer_set_match() can
reasonably be call outside this bracketing, and the fact that they
call omap_dm_timer_enable() / omap_dm_timer_disable() suggest that
is expected.
So if, after a transition into and out of off-mode, which would cause
the dm timer to loose all state, omap_dm_timer_set_match() is called
before omap_dm_timer_start(), the value read from OMAP_TIMER_CTRL_REG
will be 'wrong' and this wrong value will be stored context.tclr so
a subsequent omap_dm_timer_start() can fail (As the control register
is wrong).
Simplify this be doing the restore-from-context in
omap_dm_timer_enable() so that whenever the timer is enabled, the
context is correct.
Also update the ctx_loss_count at the same time as we notice it is
wrong - these is no value in delaying this until the
omap_dm_timer_disable() as it cannot change while the timer is
enabled.
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
| |
Signed-off-by: Marek Belisko <marek.belisko@open-nandra.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.
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
| |
works with new jack driver support.
Signed-off-by: NeilBrown <neilb@suse.de>
|