On Mon, 2012-09-24 at 21:03 +0200, Florian Dazinger wrote:
> Hi,
> I think I've found a regression, which causes an early boot crash, I
> appended the kernel output via jpg file, since I do not have a serial
> console or sth.
>
> after bisection, it boils down to this commit:
>
>
Hi,
(please let me know if this is the wrong list to ask this)
I have a Crucial M4 512 GB SSD installed on my Thinkpad X220 (Ubuntu
Precise). Overall this runs very nicely, but it takes 10+ seconds to
resume from suspend, apparently because some issue with the hardrive.
The only message I
On 09/25/2012 02:06 PM, Frederic Weisbecker wrote:
> Sasha, sorry to burden you with more testing request.
> Could you please try out this new branch? It includes some fixes after Wu
> Fenguang and
> Dan Carpenter reports (not related to your warnings though) and a patch on
> the top
> of the
On Tue, Sep 25, 2012 at 01:51:47PM +0300, Dan Carpenter wrote:
> Added Tejun to the CC list.
>
> regards,
> dan carpenter
>
> On Fri, Sep 14, 2012 at 02:07:24AM +, Jongman Heo wrote:
> >
> > Hi Guys,
> >
> > I hit this warning with current linus + for-next branch of wq.git, running
> >
Hello,
On Tue, Sep 25, 2012 at 10:38:46AM +0200, Maxim Levitsky wrote:
> diff --git a/drivers/memstick/core/ms_block.c
> b/drivers/memstick/core/ms_block.c
> new file mode 100644
> index 000..318e40b
> --- /dev/null
> +++ b/drivers/memstick/core/ms_block.c
> @@ -0,0 +1,2422 @@
> +/*
> + *
On Tue, 2012-09-25 at 11:00 -0700, Greg KH wrote:
> Hi Steven,
Note, emailing my RH account is hit or miss. If I'm traveling I don't
read it, and I wont return messages until I'm back. It's best to email
my rost...@goodmis.org account, as I have better access to that account.
I author my patches
On Mon, Aug 27, 2012 at 02:34:28PM -0400, Steven Rostedt wrote:
>
> Thanks for pointing out that the kernel is patched with overlayfs. As
> the crash is within the filesystem, it looks to be a bug with that
> patch. You may want to report this bug to them.
>
> -- Steve
You were right. After
On 2012-09-25 19:59, Jens Axboe wrote:
> On 2012-09-25 19:49, Jeff Moyer wrote:
>> Jeff Moyer writes:
>>
>>> Mikulas Patocka writes:
>>>
Hi Jeff
Thanks for testing.
It would be interesting ... what happens if you take the patch 3, leave
"struct percpu_rw_semaphore
On Tue, Sep 25, 2012 at 02:40:24AM +0200, Michael S. Tsirkin wrote:
> > @@ -139,9 +158,15 @@ static void fill_balloon(struct virtio_balloon *vb,
> > size_t num)
> > break;
> > }
> > set_page_pfns(vb->pfns + vb->num_pfns, page);
> > -
ahci libahci pata_acpi ata_generic
dm_mirror dm_region_hash dm_log dm_mod
CPU 0
Pid: 753, comm: fsck.ext3 Not tainted 3.6.0-rc7-next-20120925+ #4
/DQ67SW
RIP: 0010:[] []
scsi_setup_fs_cmnd+0xec/0x180
RSP: 0018:880233aff9f8 EFLAGS: 00010002
RAX: 0003 RBX
Hello,
> * Swithced to using a workqueue.
> Unfortunelly, I still see that workqueue items are executed in parallel
> I suspect that this happens if one work item sleeps. In this case I
> don't want other work items to run too. I fixed this with a mutex, and
> anyway
> it nice to have it
Hi,
On Tue, Sep 25, 2012 at 11:22 PM, Mark Brown
wrote:
> On Wed, Sep 05, 2012 at 05:06:04PM +0530, Sourav Poddar wrote:
>
>> +static struct regmap_config smsc_regmap_config = {
>> + .reg_bits = 8,
>> + .val_bits = 8,
>> + .max_register = SMSC_MAX_REGISTER -
Hi Steven,
I'm trying to use ktest to do build tests of the stable patch series to
verify I didn't mess anything up, but I'm finding that ktest always
returns 0 when finished, no matter if the build test was successful or
failed.
Is this right? Is there some other way to determine if ktest
On 2012-09-25 19:49, Jeff Moyer wrote:
> Jeff Moyer writes:
>
>> Mikulas Patocka writes:
>>
>>> Hi Jeff
>>>
>>> Thanks for testing.
>>>
>>> It would be interesting ... what happens if you take the patch 3, leave
>>> "struct percpu_rw_semaphore bd_block_size_semaphore" in "struct
>>>
Hello,
On Tue, Sep 25, 2012 at 04:06:08PM +0530, Viresh Kumar wrote:
> +config MIGRATE_WQ
> + bool "(EXPERIMENTAL) Migrate Workqueues to non-idle cpu"
> + depends on SMP && EXPERIMENTAL
> + help
> + Workqueues queues work on current cpu, if the caller haven't passed a
> +
On 21/09/12 17:04, David Vrabel wrote:
> From: David Vrabel
>
> Backend drivers shouldn't transistion to CLOSED unless the frontend is
> CLOSED. If a backend does transition to CLOSED too soon then the
> frontend may not see the CLOSING state and will not properly shutdown.
>
> So, treat an
On Wed, Sep 05, 2012 at 05:06:04PM +0530, Sourav Poddar wrote:
> +static struct regmap_config smsc_regmap_config = {
> + .reg_bits = 8,
> + .val_bits = 8,
> + .max_register = SMSC_MAX_REGISTER - 1;
> + .cache_type = REGCACHE_COMPRESSED,
> +};
That
Jeff Moyer writes:
> Mikulas Patocka writes:
>
>> Hi Jeff
>>
>> Thanks for testing.
>>
>> It would be interesting ... what happens if you take the patch 3, leave
>> "struct percpu_rw_semaphore bd_block_size_semaphore" in "struct
>> block_device", but remove any use of the semaphore from
On Tue, Sep 25, 2012 at 04:06:07PM +0530, Viresh Kumar wrote:
> flush_delayed_work() and flush_delayed_work_sync() had major portion of code
> similar. This patch introduces another routine __flush_delayed_work() which
> contains the common part to avoid code duplication.
This part has seen a lot
On Tue, Sep 25, 2012 at 10:45:07AM -0700, Arnaldo Carvalho de Melo wrote:
> Em Tue, Sep 25, 2012 at 07:11:55PM +0200, Borislav Petkov escreveu:
> > On Tue, Sep 25, 2012 at 10:03:49AM -0700, Arnaldo Carvalho de Melo wrote:
> > > Em Tue, Sep 25, 2012 at 10:02:01AM -0700, Arnaldo Carvalho de Melo
>
Em Tue, Sep 25, 2012 at 07:11:55PM +0200, Borislav Petkov escreveu:
> On Tue, Sep 25, 2012 at 10:03:49AM -0700, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Sep 25, 2012 at 10:02:01AM -0700, Arnaldo Carvalho de Melo escreveu:
> > > Em Tue, Sep 25, 2012 at 05:52:35PM +0200, Borislav Petkov escreveu:
Le Tue, 25 Sep 2012 15:44:57 +,
Arnd Bergmann a écrit :
>
> It's not possible to build a kernel that runs on ARMv5 (or below) and
> also on ARMv6 (or above), so the effect would be exactly the same.
> While we are putting a lot of effort into making all sorts of ARMv6
> and ARMv7 based
Tomas Mraz wrote:
> You can use openssl ca that allows to set arbitrary start date to
> generate selfsigned certs as well (-selfsign option).
That seems to require some stuff I don't have installed:
warthog>openssl ca -in signing_key.priv -extensions v3_ca -out newcert.pem
Using configuration
On Tue, Sep 25, 2012 at 10:00 AM, Borislav Petkov wrote:
>
> 3.6-rc6+tip/auto-latest-kill select_idle_sibling()
Is this literally just removing it entirely? Because apart from the
latency spike at 4 procs (and the latency numbers look very noisy, so
that's probably just noise), it looks clearly
On 09/25/2012 12:14 PM, David Sterba wrote:
On Tue, Sep 25, 2012 at 10:02:16AM +0800, zwu.ker...@gmail.com wrote:
From: Zhi Yong Wu
Some code pathes forget to free memory on exit.
Same as with the fd's, kernel will free all memory for us at exit().
I strongly disagree with this
On Tue, Sep 25, 2012 at 10:03:49AM -0700, Arnaldo Carvalho de Melo wrote:
> Em Tue, Sep 25, 2012 at 10:02:01AM -0700, Arnaldo Carvalho de Melo escreveu:
> > Em Tue, Sep 25, 2012 at 05:52:35PM +0200, Borislav Petkov escreveu:
> > > I'm trying to use raw events and to read how exactly they're
On Tuesday 25 September 2012, Matthieu CASTET wrote:
> > static inline char __dcc_getchar(void)
> > {
> > char __c;
> >
> > if (__LINUX_ARM_ARCH >= 6)
> > asm volatile("mrc p14, 0, %0, c0, c5, 0 @ read comms data reg"
> > : "=r" (__c));
> >
On Tuesday 25 September 2012, Lee Jones wrote:
>
> An earlier change prevented User Interface Boards (UIBs) from being
> initialised on boards which did not support them. This change had
> the undesired effect of reordering the UIB initialisation calls with
> I2C registration. Here we ensure UIBs
On Tue, Sep 25, 2012 at 11:59:51AM -0400, KOSAKI Motohiro wrote:
> On Tue, Sep 25, 2012 at 9:56 AM, Naoya Horiguchi
> wrote:
> > KPF_THP can be set on non-huge compound pages like slab pages, because
> > PageTransCompound only sees PG_head and PG_tail. Obviously this is a bug
> > and breaks user
On Tuesday 25 of September 2012 09:44:54 Greg KH wrote:
> On Tue, Sep 25, 2012 at 06:31:36PM +0200, Paweł Sikora wrote:
> > On Monday 24 of September 2012 10:36:33 Greg KH wrote:
> > > On Mon, Sep 24, 2012 at 10:05:23AM +0200, Paweł Sikora wrote:
> > > > Hi,
> > > >
> > > > with the new stable
Em Tue, Sep 25, 2012 at 10:02:01AM -0700, Arnaldo Carvalho de Melo escreveu:
> Em Tue, Sep 25, 2012 at 05:52:35PM +0200, Borislav Petkov escreveu:
> > I'm trying to use raw events and to read how exactly they're specified.
> > Here's what do:
> >
> > $ perf list -h
> >
> > ...
> > rNNN
Em Tue, Sep 25, 2012 at 05:52:35PM +0200, Borislav Petkov escreveu:
> I'm trying to use raw events and to read how exactly they're specified.
> Here's what do:
>
> $ perf list -h
>
> ...
> rNNN [Raw hardware event
> descriptor]
>
On Tue, Sep 25, 2012 at 03:17:36PM +0200, Borislav Petkov wrote:
> For example, I did some measurements a couple of days ago on Bulldozer
> of tbench with and without select_idle_sibling:
Here are updated benchmark results with your patch here:
http://marc.info/?l=linux-kernel=134850871822587
I
On Tue, 2012-09-25 at 16:37 +0300, Andy Shevchenko wrote:
> On Tue, 2012-09-25 at 06:19 -0700, Joe Perches wrote:
> > You also added yourself as a maintainer.
> > Congrats/sympathies, etc...
> Actually I prefer to be just a supporter, because I introduce few
> additional files. But if I
On Tue, Sep 25, 2012 at 06:31:36PM +0200, Paweł Sikora wrote:
> On Monday 24 of September 2012 10:36:33 Greg KH wrote:
> > On Mon, Sep 24, 2012 at 10:05:23AM +0200, Paweł Sikora wrote:
> > > Hi,
> > >
> > > with the new stable line i'm observing strange locks on my old
> > > amd-phenom-II
On Tuesday 25 September 2012 02:47:28 Markus Trippelsdorf wrote:
> On 2012.09.24 at 19:58 -0400, Mike Frysinger wrote:
> > On Monday 24 September 2012 11:59:36 Arnaldo Carvalho de Melo wrote:
> > > --- a/tools/perf/Makefile
> > > +++ b/tools/perf/Makefile
> > >
> > > -
On Monday 24 of September 2012 10:36:33 Greg KH wrote:
> On Mon, Sep 24, 2012 at 10:05:23AM +0200, Paweł Sikora wrote:
> > Hi,
> >
> > with the new stable line i'm observing strange locks on my old
> > amd-phenom-II mini-server.
> > here's a dmesg:
>
> Did this show up in 3.5.3? If not, can
On Tue, 25 Sep 2012, Glauber Costa wrote:
> >> 1) Do like the events mechanism and allocate this in a separate
> >> structure. Add a pointer chase in the access, and I don't think it helps
> >> much because it gets allocated anyway. But we could at least
> >> defer it to the time when we limit
On Tue, Sep 25, 2012 at 7:25 AM, Matthew Garrett wrote:
> This could conceivably be hotpluggable, and we may want to displace it
> from devices under certain circustances, so add a release method to hand
s/circustances/circumstances/
> back the resources.
>
> Signed-off-by: Matthew Garrett
From: Kalle Komierowski
The CCMuxOffset bit is not kept set, this will force the columb counter
of the AB8500 to use the measure offset calibration.
This should increase the accuracy of the fuel gauge.
Signed-off-by: Kalle Komierowski
Signed-off-by: Marcus Cooper
Signed-off-by: Mathieu
On Tue, 25 Sep 2012, Glauber Costa wrote:
> No cache should ever pass those as a creation flags. We can just ignore
> this bit if it happens to be passed (such as when duplicating a cache in
> the kmem memcg patches)
Acked-by: Christoph Lameter
--
To unsubscribe from this list: send the line
From: Jonas Aaberg
Detect battery type in work queue instead of probe.
This reduces the system boot time with 1.5s
Signed-off-by: Jonas Aaberg
Signed-off-by: Mathieu Poirier
Reviewed-by: Karl KOMIEROWSKI
---
drivers/power/ab8500_btemp.c | 15 +++
1 files changed, 11
From: Paer-Olof Haakansson
Rename the ab8500_power_loss_handling function
to a more describing name ab8500_enable_disable_sw_fallback
Signed-off-by: Robert Marklund
Signed-off-by: Paer-Olof Haakansson
Signed-off-by: Mathieu Poirier
Reviewed-by: Par-Olof HAKANSSON
Reviewed-by: Karl
I recommend that you use KNC. Xeon Phi is a marketing name. PMU for followon
Xeon Phi chips will probably be different.
-Original Message-
From: Vince Weaver [mailto:vincent.wea...@maine.edu]
Sent: Tuesday, September 25, 2012 9:23 AM
To: linux-kernel@vger.kernel.org
Cc: Peter Zijlstra;
From: "Mathieu J. Poirier"
This patch set upgrades the current ux500 battery management driver
to the latest HW and functionality.
Pull request for convenience:
The following changes since commit 56d27adcb536b7430d5f8a6240df8ad261eb00bd:
Merge
From: Johan Bjornstedt
When enabling the CCEOC irq we might get false interrupt
from ab8500-driver due to the latched value will be saved
and interpreted as an IRQ when enabled
Signed-off-by: Johan Bjornstedt
Signed-off-by: Henrik Solver
Signed-off-by: Mathieu Poirier
Reviewed-by: Karl
From: Jonas Aaberg
Gracefully handle gpadc conversion errors.
Signed-off-by: Jonas Aaberg
Signed-off-by: Mathieu Poirier
Reviewed-by: Johan BJORNSTEDT
---
drivers/power/ab8500_charger.c | 22 ++
1 files changed, 18 insertions(+), 4 deletions(-)
diff --git
From: Marcus Cooper
Today the battery recharge is determined with a voltage threshold. This
voltage threshold is only valid when the battery is relaxed. In charging
algorithm the voltage read is the loaded battery voltage and no
compensation is done to get the relaxed voltage. When maintenance
From: Rickard Andersson
In case of time out error IRQ needs to be disabled
otherwise we will get unbalanced enable/disable pairs.
Signed-off-by: Rickard Andersson
Signed-off-by: Mathieu Poirier
Reviewed-by: Jonas ABERG
---
drivers/power/ab8500_fg.c |1 +
1 files changed, 1
From: Hakan Berg
Ignore the low btemp interrupts for ab8500 3.0 and 3.3
Signed-off-by: Hakan Berg
Signed-off-by: Mathieu Poirier
Reviewed-by: Jonas ABERG
---
drivers/power/ab8500_btemp.c | 22 +++---
include/linux/mfd/abx500/ab8500.h |5 +
2 files changed, 16
From: pender01
Round the capacity values for better enduser experience.
Signed-off-by: pender01
Signed-off-by: Mathieu Poirier
Reviewed-by: Jonas ABERG
---
drivers/power/ab8500_fg.c | 28 +++-
1 files changed, 15 insertions(+), 13 deletions(-)
diff --git
Hello
This is an updated version of the patch. It uses
ARCH_PERFMON_EVENTSEL_INT for the DATA_READ event, with the assumption
that x86_pmu_hw_config() is going to set that bit anyway. This lets
the code get through the test for an event being 0 without
triggering -ENOENT.
One remaining
From: Hakan Berg
Add support for the battery over-voltage situation
Signed-off-by: Hakan Berg
Signed-off-by: Mathieu Poirier
Reviewed-by: Karl KOMIEROWSKI
---
drivers/power/ab8500_fg.c | 32
1 files changed, 16 insertions(+), 16 deletions(-)
diff --git
From: Marcus Cooper
Cleanup of the ab8500_charger driver.
Signed-off-by: Marcus Cooper
Signed-off-by: Mathieu Poirier
Reviewed-by: Karl KOMIEROWSKI
---
drivers/power/ab8500_charger.c |5 -
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/drivers/power/ab8500_charger.c
From: Marcus Cooper
A Legacy USB charger should be handled directly by the charger
driver.
Signed-off-by: Marcus Cooper
Signed-off-by: Mathieu Poirier
Reviewed-by: Karl KOMIEROWSKI
Reviewed-by: Jonas ABERG
---
drivers/power/ab8500_charger.c | 66 ++-
1
From: Henrik Sölver
AB8500 refuses to start charging when some types of non standard
chargers are connected. This change force the AB to start charging.
Signed-off-by: Henrik Sölver
Signed-off-by: Mathieu Poirier
Reviewed-by: Yvan FILLION
Reviewed-by: Jonas ABERG
---
From: Loic Pallardy
Allow to indicate wheter AC and USB charge capabilities are
supported from platform data.
Signed-off-by: Loic Pallardy
Signed-off-by: Mathieu Poirier
Reviewed-on: http://gerrit.lud.stericsson.com/gerrit/58093
Reviewed-by: Marcus COOPER
Reviewed-by: Olivier CLERGEAUD
---
From: Michel JAOUEN
Add AB9540 and AB8505 support to ab8500_temp
driver.
Signed-off-by: Rajkumar Kasirajan
Signed-off-by: Mathieu Poirier
Reviewed-by: Michel JAOUEN
Reviewed-by: Marcus COOPER
Reviewed-by: Jonas ABERG
---
drivers/power/ab8500_btemp.c | 71
From: Paer-Olof Haakansson
When calculating the average current the nominator will
overflow when the charging current is high.
Signed-off-by: Henrik Sölver
Signed-off-by: Mathieu Poirier
Reviewed-by: Par-Olof HAKANSSON
Reviewed-by: Jonas ABERG
---
drivers/power/ab8500_fg.c | 15
From: Hakan Berg
BTEMP thermal compensation factor times 10 is applied in two
places, probe and get_property. Removed from probe.
Signed-off-by: Hakan Berg
Signed-off-by: Mathieu Poirier
Reviewed-by: Karl KOMIEROWSKI
---
drivers/power/ab8500_btemp.c |4 ++--
1 files changed, 2
From: Hakan Berg
The Travel and Carkit adapter should be handled directly by
the charger driver.
Signed-off-by: Marcus Cooper
Signed-off-by: Mathieu Poirier
Reviewed-by: Jonas ABERG
---
drivers/power/ab8500_charger.c | 94 +-
From: Jonas Aaberg
Signed-off-by: Jonas Aaberg
Signed-off-by: Mathieu Poirier
---
drivers/power/ab8500_charger.c | 122 +++-
1 files changed, 121 insertions(+), 1 deletions(-)
diff --git a/drivers/power/ab8500_charger.c b/drivers/power/ab8500_charger.c
From: Jonas Aaberg
Do flush sync on the fg workqueue at suspend instead of
just flushing it.
Signed-off-by: Jonas Aaberg
Signed-off-by: Mathieu Poirier
Reviewed-by: Johan BJORNSTEDT
---
drivers/power/ab8500_fg.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
From: Loic Pallardy
AB and PMxxx doesn't have same watchdog refresh period
Add watchdog to refresh period parameters in x500 charger structure,
this should kick watchdog every 30sec.
The AC charging should also kick both pm2xxx
and the AB charger watchdog.
Signed-off-by: Rajkumar Kasirajan
From: Nicolas Guion
The fallback software control register has moved in the ab8505
and ab9540.
Signed-off-by: Marcus Cooper
Signed-off-by: Mathieu Poirier
Reviewed-by: Mattias WALLIN
Reviewed-by: Nicolas GUION
Reviewed-by: Jonas ABERG
---
drivers/power/ab8500_charger.c | 53
From: Jonas Aaberg
Flush and sync all workqueues at suspend to avoid
that we suspend in the middle of a work.
Signed-off-by: Jonas Aaberg
Signed-off-by: Mathieu Poirier
Reviewed-by: Marcus COOPER
---
drivers/power/ab8500_charger.c | 11 +++
drivers/power/ab8500_fg.c |5
From: Jonas Aaberg
Do not touch the VBUSOVV in USBCHTRL2 when running on AB8505.
Signed-off-by: Jonas Aaberg
Signed-off-by: Mathieu Poirier
Reviewed-by: Marcus COOPER
---
drivers/power/ab8500_charger.c| 22 --
include/linux/mfd/abx500/ab8500.h | 10 ++
2
From: Paer-Olof Haakansson
If charging is started before USB enumeration of an
Accessory Charger Adapter has finished, the AB8500 will
generate a VBUS_ERROR. This in turn results in timeouts
and delays the enumeration with around 15 seconds.
This patch delays the charging and then ramps currents
From: Martin Bergstrom
Unscaled capacity should be reported for POWER_SUPPLY_PROP_CAPACITY.
Signed-off-by: Martin Bergstrom
Signed-off-by: Mathieu Poirier
Reviewed-by: Marcus COOPER
Reviewed-by: Jonas ABERG
---
drivers/power/ab8500_fg.c |6 ++
1 files changed, 2 insertions(+), 4
From: Rupesh Kumar
Fix for: charging not getting enabled in
charge only mode by external charger.
Signed-off-by: Rupesh Kumar
Signed-off-by: Mathieu Poirier
Reviewed-by: Marcus COOPER
Reviewed-by: Michel JAOUEN
Reviewed-by: Philippe LANGLAIS
Reviewed-by: Philippe LANGLAIS
---
From: Martin Sjoblom
Do not set higher current in stepping functionality if VBUS is dropping.
After VBUS has dropped try to set current once again. If dropping again
then we have found the maximum capability of the charger.
Signed-off-by: Martin Sjoblom
Signed-off-by: Mathieu Poirier
From: Marcus Cooper
When using ABx500_ADC_THERM_BATCTRL the battery ID resistor
is combined with a NTC resistor to both identify the battery and
to measure its temperature.
Signed-off-by: Marcus Cooper
Signed-off-by: Mathieu Poirier
Reviewed-by: Mian Yousaf KAUKAB
Reviewed-by: Michel JAOUEN
From: Hakan Berg
When battery capacity was going below 1% fg in not supposed
to report 0% unless we've got the LOW_BAT IRQ, no matter
what the FG-algorithm says. This made fg get stuck at 1% if
charger is connected when capacity is 1%.
That problem is addressed with this patch.
Signed-off-by:
From: Hakan Berg
Battery tempreature readings sometimes fails and results in
a value far from recent values. This patch adds a software
filter that disposes such readings, by allowing direct
updates on temperature only if two samples result in the
same temperature. Else only allow 1 degree
From: Hakan Berg
The ab8505 does not have the same address for USB link-status
as has ab8500. Add AB8505_USB_LINK_STATUS and code to switch
to correct constant.
Signed-off-by: Hakan Berg
Signed-off-by: Mathieu Poirier
Reviewed-by: Mian Yousaf KAUKAB
Reviewed-by: Marcus COOPER
Reviewed-by:
From: Kalle Komierowski
Due to a bug in some AB8500 ASICs charger removal cannot always
be detected if the removal and reinsertion is done to close in time.
This patch detects above described case and handles the situation
so that charging will be kept turned on.
Signed-off-by: Kalle
From: Martin Bergström
When the charger is removed we need to go to INIT_RECOVERY
state instead of directly to RECOVERY state.
Signed-off-by: Martin Bergstrom
Signed-off-by: Mathieu Poirier
Reviewed-by: Marcus COOPER
Reviewed-by: Jonas ABERG
---
drivers/power/ab8500_fg.c |2 +-
1 files
From: Michel JAOUEN
Add new sysfs interface to get current charge status
Signed-off-by: Michel JAOUEN
Signed-off-by: Loic Pallardy
Signed-off-by: Mathieu Poirier
Reviewed-by: Marcus COOPER
Reviewed-by: Olivier CLERGEAUD
Reviewed-by: Jonas ABERG
---
drivers/power/ab8500_charger.c |3
From: Rupesh Kumar
Due to btemp filtering enabled during init, temp values
reported to charge algorithm driver started from 0.
As a result,charge algorithm was going into wrong
state and charging was stopped.
This patch defers btemp filtering till init is done.
Signed-off-by: Rupesh Kumar
From: Yang QU
Add 2.7v, 2.9v, 3.0v, 3.2v and 3.3v charging voltage
for backup battery. Before that only 2.5v, 2.6v, 2.8v,
3.1v are available.
Signed-off-by: Yang QU
Signed-off-by: Mathieu Poirier
Reviewed-by: Maxime COQUELIN
Reviewed-by: Marcus COOPER
Reviewed-by: Xiao Mei ZHANG
---
From: "Mathieu J. Poirier"
Making platform data declaration and handling similar accross all
ab8500_xyc.c battery management files. Also adding gards against
NULL platform data.
Signed-off-by: Philippe Langlais
Signed-off-by: Mathieu Poirier
---
drivers/power/ab8500_btemp.c| 17
From: Rupesh Kumar
Quick re-attach charging behaviour is not required
for external ac charger. Internal AC/USB Charger removal
detection problem is due to a bug in AB8500 ASICs.
Signed-off-by: Rupesh Kumar
Signed-off-by: Mathieu Poirier
Reviewed-by: Hakan BERG
Reviewed-by: Philippe LANGLAIS
From: "Mathieu J. Poirier"
Signed-off-by: Mathieu Poirier
---
drivers/power/abx500_chargalg.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/power/abx500_chargalg.c b/drivers/power/abx500_chargalg.c
index ce58f20..4db0ef0 100644
---
From: Hakan Berg
When the charging safety timer is elapsed the battery health is shown as "Good".
This is misleading and also hard to distingiush problems reported on "phone
discharges although charger is attached".
When safety timer elapses that is an indication of a fault in the battery of
From: "Mathieu J. Poirier"
Signed-off-by: Mathieu Poirier
---
drivers/power/ab8500_fg.c | 196 +--
drivers/power/ab8500_fg.h | 201 +
2 files changed, 206 insertions(+), 191 deletions(-)
create mode 100644
From: Marcus Cooper
When the state of USB Charge detection is changed then the calls
use a define for another register in other bank. This change
creates a new define for the correct register and removes the
magic numbers that are present.
Signed-off-by: Marcus Cooper
Signed-off-by: Mathieu
From: Hakan Berg
Timers used for charging safety and maintenance must work even when
CPU is power collapsed. By using hrtimers with realtime clock, system
is able to trigger an alarm that wakes the CPU up and make it possible
to handle the event.
Allow a little slack of 5 minutes to the
From: Loic Pallardy
Upstream version of AB charge algo has been reverted
during kernel 3.4 port.
This patch restore state by:
- renaming ab8500_chargal.c in abx500_chargal.c
- renaming function from ab8500 to abx500
- moving generic structure in "include/mfd/abx500.h"
Goal is to ease next code
From: Marcus Cooper
Remove flag that serve no purpose from source code, Kconfig
and Makefile.
Signed-off-by: Marcus Cooper
Signed-off-by: Mathieu Poirier
Reviewed-by: Hakan BERG
Reviewed-by: Mian Yousaf KAUKAB
---
drivers/power/Kconfig |7 ---
Kasatkin, Dmitry wrote:
> Just one question about key description...
> request_asymmetric_key uses format for key description: ": ".
> Preparsing code creates description from those values.
> I see that key id is not 8 bytes anymore but full hash size of 20 bytes.
Remember: This is for
From: Marcus Cooper
The patch for 426250 added a change to check for the quick
re-attachment of the charger connection as an error in the
AB8500 HW meant that a quick detach/attach wouldn't be
detected.
This patch isolates the original change so that newer AB's
are not affected.
Signed-off-by:
From: Martin Bergstrom
The USB charger current is limited according to information comming
from the USB driver
Signed-off-by: Martin Bergstrom
Signed-off-by: Mathieu Poirier
Reviewed-by: Jonas ABERG
---
drivers/power/ab8500_charger.c |4
1 files changed, 4 insertions(+), 0
From: Marcus Cooper
The newer AB's such as the AB8505, AB9540 etc include a
USBLink1 Status register which detects a larger range of
external devices. This should be used instead of the
USBLine Status register.
Signed-off-by: Marcus Cooper
Signed-off-by: Mathieu Poirier
Reviewed-by: Hakan
From: "Mathieu J. Poirier"
A lot of developement happened internally since the first
mainlining of the battery managmenent driver. Most of the
new code can be historically accounted for but some of it
can't.
This patch is a gathering of the code for which history was
lost but still relevant to
From: Rikard Olsson
Add support for a power cut feature which allows user to
configure when ab8505 should shut down system due to low
battery.
Signed-off-by: Rikard Olsson
Signed-off-by: Mathieu Poirier
Reviewed-by: Martin SJOBLOM
Reviewed-by: Jonas ABERG
---
drivers/power/ab8500_fg.c
From: Rajkumar Kasirajan
If battery is not identified while fg probe, mah_max_design gets
initialized with unknown battery's charge full design. Reinitialize
mah_max_design if battery is identified after fg probe.
Signed-off-by: Rajkumar Kasirajan
Signed-off-by: Mathieu Poirier
Reviewed-by:
From: Hakan Berg
Changed conditions for restarting low battery measurements counter
and adjusted the interval between measurements to avoid RF burst
induced voltage drops, and to shorten time to decide to shut down.
Signed-off-by: Hakan Berg
Signed-off-by: Martin Bergstrom
Signed-off-by:
From: Daniel WILLERUD
Switchable depending on whether capacity scaling is enabled
Signed-off-by: Marcus Cooper
Signed-off-by: Daniel WILLERUD
Signed-off-by: Mathieu Poirier
Reviewed-by: Jonas ABERG
---
drivers/power/ab8500_fg.c | 57 -
1 files
From: Jonas Aaberg
Signed-off-by: Jonas ABERG
Signed-off-by: Mathieu Poirier
Reviewed-by: Johan BJORNSTEDT
---
drivers/power/ab8500_fg.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/power/ab8500_fg.c b/drivers/power/ab8500_fg.c
index 1e02b00..0db17c7
From: Philippe Langlais
Signed-off-by: Philippe Langlais
Signed-off-by: Mathieu Poirier
---
drivers/power/ab8500_btemp.c |8 ++--
drivers/power/ab8500_charger.c|9 +++--
drivers/power/ab8500_fg.c |8 ++--
drivers/power/abx500_chargalg.c |7
201 - 300 of 1384 matches
Mail list logo
