| Age | Commit message (Collapse) | Author |
|---|
|
Select CONFIG_S3C24XX_ADC by defult for GTA01/GTA02.
Somebody will hate me if I don't send this patch soon.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
Remove glamo from defconfig.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
This patch applies upstream feedback to the group filter.
The algorithms are equivalent, thus we will get the same
results after applying this patch.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
He is not reachable at the OM address.
We need the right email if we send upstream.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
General cleanups. Now we pass checkpatch.pl.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
I had a patch by Vasily Khoruzhick <anarsoul@gmail.com>
in the linux-arm-kernel as a guide for some of the changes.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
Without this patch we cannot make the s3c2410/s3c2440 touchscreen
driver work.
Is this delay device-dependant?
Is there a better way to do this?
We specify the delay value (S3C2410_ADCDLY).
Signed-off-by: Vasily Khoruzhick <anarsoul@gmail.com>
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
This patch allow us to efficiently modify the number of
remaining conversions from the client side. This us useful
when we do not know in advance how many conversions we will
need or when we need to cancel pending conversions.
This change is simple enough to be compatible with existing
code that can just define the new pointer in the callback
and ignore it.
Sample usage:
http://tinyurl.com/s3c2410-ts-c (function stylus_adc_action).
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
|
|
Small cleanup.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
[ben-linux@fluff.org: rewrote subject]
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
|
|
Remove the dependence to the OLD NET DEV operation
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
|
|
Reported-by: Arnaud Patard <arnaud.patard@rtp-net.org>
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
This makes wake up on RTC alarm work properly, ported from rtc-pcf50633
commits 4caf79de95c26495e7cdc8204023d97598f887d2 and
c3e4e22fb0c3e1d82f66e67f6592949e48f3995a.
Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
This reverts commit 9c4451ff31b937a478f3d3eabef30b71cbe12b12.
This commit made wifi unusable after ifconfig down and sometimes after
unbinding.
|
|
This patch fixes a typo in the voltage setting of LDO1.
In the function mangle_pmu_pdata_by_system_rev() the value of min_uV
is set twice, while the value of max_uV stays at the initialized
value. This leaves us with .constraints.min_uV = 3300000 and
.constraints.max_uV = 1300000, which is probably not what we want.
This patch is only required on andy-tracking.
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
This allows to use gta01 battery driver on gta02.
echo bq27000-battery.0 > /sys/bus/platform/drivers/bq27000-battery/unbind
modprobe gta01_battery
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
We need to use a dedicated function because we can't get charger
status from an irq context and that is required by usb gadgets.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Current scheme is fragile and is likely to go off sync, especially on
batfull->adapter charging automatic MBC transition.
Query the status bit every time we need it instead.
We need to export another function to query for USB presence because
we can't read anything from PCF50633 (via I2C) inside irq context and
that is needed by usb gadgets.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
If chgmod == BATFULL, setting chgena has no effect. Datasheet says we
need to set resume instead but when autoresume is used resume doesn't
work. Clear and set chgena instead.
This enables a user to force charging by re-plugging USB even when the
charger entered Battery Full mode, might be handy before a long trip.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
After reaching Battery Full condition MBC state machine switches back
into charging mode when the battery voltage falls below 96% of a
battery float voltage. The voltage drop in Li-Ion batteries is
marginal (1-2%) till about 80% of its capacity - which means, after a
BATFULL, charging won't be restarted until 75-80%.
That is a desired behaviour recommended by battery manufacturers,
don't mess with it.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Current implementation is prone to races, this patch attempts to remove all
but one (in pcf50633_adc_sync_read).
The idea is that we need to guard the queue access only on inserting and
removing items. If we insert and there're no more items in the queue it
means that the last irq already happened and we need to trigger ADC
manually. If not, then the next conversion will be triggered by the irq
handler upon completion of the previous.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Using the default kernel "events" workqueue causes problems with
synchronous adc readings if initiated from some task on the same
workqueue.
I had a deadlock trying to use pcf50633_adc_sync_read from a
power_supply class driver because the reading was initiated from the
workqueue and it waited for the irq processing to complete (to get the
result) and that was put on the same workqueue.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
auto-restart
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Some userspace (notably Enlightment's batget) ignores "capacity"
completely if there're no other properties. Expose a fake value
(850mAh, typical for BL-5C) to make them happy.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Check if machine-specific hooks exist before calling, this allows to use
this driver with gta02 or any other device that is able to provide battery
voltage readings.
Report an estimate of capacity percentage left, based on discharge curves.
Strictly speaking, this is a violation of power_supply class specs but
since this is the only driver for dumb batteries and userspace lacks any
library to do the estimation itself, we have to stuff it here.
Please keep in mind that this estimation is by no means accurate, usually
cell phones have only 5 bars to represent charge status.
Credit goes to Joerg Reisenweber and SpeedEvil for helping with gathering
and analysing the data.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Driver data must be properly registered after allocation
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
gta02_pmu_force_shutdown is only defined when CONFIG_CHARGER_PCF50633
is set, but it's used unconditionally.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
|
|
If the battery is not present hdq_read will always return an error.
If the drivers knows that the battery is not present the correct thing to do is
to return -ENODEV instead of passing the error on.
Do this for all properties except POWER_SUPPLY_PROP_PRESENT.
The power supply sysfs expects us to do so, else it won't generate a proper
uevent file.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
|
|
According to power_supply class specification all voltages and currents
must be reported in uV and uA correspondingly.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Register cache space was not being allocated for the final register,
causing bugs when it was used. Allocate space for it.
Also ensure that the final register is displayed in sysfs.
[Commit message rewritten to document actual issue. -- broonie]
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
The wrong register cache variable was being used to provide the size for
the memcpy(), resulting in a copy of only a void * of data.
Reported-by: Lars-Peter Clausen <lars@metafoo.de>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
These codepages are still widely used by inferior operating systems to
represent cyrillic letters in filenames, both in fat filesystem and by some
samba-servers.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
F4t discovered that his freerunner panics on connect to his windows box.
This crude hack workarounds the problem.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Clean up debugging messages so that we don't see any output with loglevel=4
(default for Qi). This avoids slowing down suspend/resume by slow fb
output.
Checkpatch barks on this patch but i guess most of that debugging would
have to be changed prior to upstream submission anyway.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
This is because of commit
1f06c28eaa6e77384a366c3d2ab1ccdbb8a807e0
The BQ27000 Battery requires HDQ.
Otherwise the battery is not available at all.
Signed-off-by: Luca Capello <luca@pca.it>
|
|
Commit 4eaa9819dc08d7bfd1065ce530e31b18a119dcaf changed semantics of
private_value member of kcontrol. This resulted in inability to control
amplifier and subsequently in very low output volume.
Tested-by: Johannes Schauer <josch@pyneo.org>
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
As discussed on the ML, currently headset button reports "KEY_PAUSE
released" on press and "pressed" on release. For "pause" semantics it makes
sense but if someone thinks of that as of just another button, it'd be good
to have "pressed/released" events consistent with button press/release.
Luca Capello <luca@pca.it> suggested to change the button event to KEY_PLAY
and to invert the state to make it more consistent.
This trivial patch inverts button events for GTA03 KEY_PLUS and KEY_MINUS,
i'm not sure how undesirable that is. I can prepare an alternative that
preserves current behaviour on GTA03 per request.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
After suspending with GPS powered on power_on sysfs node reports 0 and GPS
is actually unpowered but "echo 1 > power_on" has no effect. This patch
fixes it.
Reported and analised by Timo Juhani Lindfors <timo.lindfors@iki.fi>,
ticket #2293.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
This option is meant for debugging and is not any more of interest to
ordinary users.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Enabling wakelocks leads to immediate suspend after resume. See
ce6840da7184043a09dd57d4c201a32ef7b6c083 for clarifications.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Using HAL for E's battery gadget highlighted an oddity: the kernel exposed
last full charge property but didn't expose current charge property. This
resulted in the wrong computation of current battery capacity by E's gadget
(and probably other programs as well).
This patch exposes a corresponding bq27000 register to make E battery
gadget happy (it is still not showing correct values because of bugs in HAL
resulting in 3 batteries (apm emulation and usb supply being bogus here)
instead of one).
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
This patch adds a call to cancel_delayed_work before a call
to schedule_delayed_work.
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
Signed-off-by: Daniel Willmann <daniel@totalueberwachung.de>
|
|
Without this jbt6k74 is not seen by the system and consequently
display doesn't work with Qi.
Rebasing to .28 introduced a regression (probably in
a6af63e826b79ae1ba2d8cbfa66805cc2dfe367c) resulting in jbt6k74 no longer
manageable by the kernel. This was unnoticed before because u-boot does its
own LCM initialization. With Qi it resulted in a white screen.
This patch is fixing it by making spi host bus number (unspecified,
defaults to 0) and spi device (jbt6k74) bus number match.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Signed-off-by: Mike Westerhof <mwester@dls.net>
|
|
Machines that do not route the USB vbus signal to a GPIO can use this
mechanism as an alternate way for the udc driver to detect the usb
connect/disconnect state, which is useful (for example) to enable the
link up/down state to be determined for the g_ether gadget.
Signed-off-by: Mike Westerhof <mwester@dls.net>
|
|
The g_ether USB gadget driver currently decides whether or not there's a
link to report back for eth_get_link based on if the USB link speed is
set. The USB gadget speed is however often set even before the device is
enumerated. It seems more sensible to only report a "link" if we're
actually connected to a host that wants to talk to us. The patch below
does this for me - tested with the PXA27x UDC driver.
Signed-off-by: Jonathan McDowell <noodles@earth.li>
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Cc: stable <stable@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
Avoid a kernel panic during an early call
to the pcf50633_mbc_get_status function.
|
|
This patch fixes a linking failure in the Glamo GPIO SPI bitbang support.
Signed-off-by: Rask Ingemann Lambertsen <rask@sygehus.dk>
|
