To cache the interrupt mask register, use the regmap RB_TREE
cache-ing mechanism in place of implementing it locally.
Signed-off-by: Laxman Dewangan
---
Changes V1 -> V2:
No change, generated new patch for V2 series.
drivers/mfd/tps6586x.c | 24
1 files changed, 16 in
The GPIO functionality of device tps6586x is added through
platform gpio driver and it can be register as the mfd sub
device and hence removing the duplicates code which register
the gpio functionality from core driver.
Signed-off-by: Laxman Dewangan
---
Changes from V1->V2
No changes in code, ju
Doing some enhancements in the tps6586x core driver which is
based on some recent driver framework enhancements.
Following are highlights of changes:
- Use devm for allocation to remove the code for freeing it.
- Use regmap i2c for register access in place of direct i2c apis.
This will give the d
Allocate memory for device state using devm_kzalloc(), get the
IRQ using devm_request_irq().
All to simplify accounting and letting the kernel do the
garbage-collection.
Signed-off-by: Laxman Dewangan
---
Changes V1 -> V2:
No change, generated new patch for V2 series.
drivers/mfd/tps6586x.c |
Using regmap apis for accessing the device registers.
Signed-off-by: Laxman Dewangan
---
Changes V1 -> V2:
No change, generated new patch for V2 series.
drivers/mfd/Kconfig|1 +
drivers/mfd/tps6586x.c | 157 ++--
2 files changed, 47 insertion
Enable GPIO_TPS6586X as the gpio functionality of
this device moved as platform driver.
Signed-off-by: Laxman Dewangan
---
Changes V1 -> V2:
New change in V2 series. To avoid bisect, added change in defconfig.
arch/arm/configs/tegra_defconfig |1 +
1 files changed, 1 insertions(+), 0 deleti
Converting the gpio driver of tps6586x to a platform
driver in place of registering the gpio through core
driver.
The motivation of the change is:
- This is inline with the mfd drivers implementation.
- This will move the related gpio support to gpio driver
folder where all gpio related drivers a
Hi Bob,
On Mon, Jul 16, 2012 at 4:44 AM, Bob Liu wrote:
> On Sat, Jul 14, 2012 at 4:02 AM, Geert Uytterhoeven
> wrote:
>> On Tue, Jun 26, 2012 at 9:59 PM, Geert Uytterhoeven
>> wrote:
>>> + drivers/i2c/busses/i2c-bfin-twi.c: error: 'ANAK' undeclared (first use in
>>> this function): => 154:19
* Linus Walleij [120714 13:21]:
> On Tue, Jul 10, 2012 at 11:11 AM, Tony Lindgren wrote:
>
> > OK so no comments for a while. Here's the patch updated to leave out
> > the comments in the binding example.
>
> I reason like this:
>
> - My fears is that the code gets hopeless to understand the m
On Mon, 16 Jul 2012, Vinod Koul wrote:
> On Mon, 2012-07-16 at 08:37 +0200, Guennadi Liakhovetski wrote:
> > On Mon, 16 Jul 2012, Vinod Koul wrote:
> >
> > > On Thu, 2012-07-05 at 12:29 +0200, Guennadi Liakhovetski wrote:
> > > > diff --git a/include/linux/sh_dma.h b/include/linux/sh_dma.h
> > >
Name the regulator as per board schematics and adds its
supply name info in regulator data.
Add the always on fixed regulator to refer the battery supply.
Use this fixed regulator for input supply of some of PMIC
regulator
Signed-off-by: Laxman Dewangan
---
This was 1/2 of the series
[PATCH 0/2]
Hi Greg,
On Fri, Jun 15, 2012 at 02:28:24PM -0700, Greg Kroah-Hartman wrote:
[...]
> This looks fine to me, but as it touches pstore and tracing code, I
> can't apply it without acks from the relevant maintainers/owners.
Now that the patchset has an ack from Steven Rostedt, can you please
apply i
Hi all,
Changes since 20120713:
The ext4 tree lost its build failure.
The vfs tree gained a build failure so I used the version from
next-20120713.
The drm tree gained a conflict against Linus' tree.
The battery tree tree gained a build failure so I used the version from
next-20120713.
The re
There are many userland reports of sensors with unreasonably small and
large temperatures. There seem to be several reasons for this:
Firstly, the major sensor type (sp78) is actually a signed number.
This explains why some sensors show very small or large values - they
are in fact all small, but
Not all sensors in the T range are useful temperatures. This patch
creates a subset of sensors to be exported to userland, excluding the
unknown types.
Signed-off-by: Henrik Rydberg
---
drivers/hwmon/applesmc.c | 75 ++--
1 file changed, 47 insertions
On 07/14/2012 06:43 PM, Julia Lawall wrote:
> From: Julia Lawall
>
> Typically, the return value desired for the failure of a function with an
> integer return value is a negative integer. In these cases, the return
> value is sometimes a negative integer and sometimes 0, due to a subsequent
> i
> I think it would be best if this got merged through whatever tree that
> was used to introduce ab8500_irq_get_virq(); otherwise it will have to
> wait till I resync with mainline sometime in the middle of the next
> release cycle.
I agree. Sam that's you, patch below. :)
From: Lee Jones
Date:
On 07/13/2012 07:24 PM, Srikar Dronamraju wrote:
On 12/07/12 21:18, Raghavendra K T wrote:
+#ifdef CONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT
[...]
+ struct {
+ bool cpu_relax_intercepted;
+ bool dy_eligible;
+ } ple;
+#endif
[...]
}
vcpu->run
Never reached lkml due to the HTML.
Resending, with a CC to linux-fbdev added.
-- Forwarded message --
From: Levin Du
Date: 2012/7/12
Subject: video/fbmem.c: Fix __u32 >= 0 condition in fb_do_show_logo.
To: linux-kernel@vger.kernel.org
Cc: b...@neruo.com
Dear all,
Since dx or d
Hi Federico,
On Fri, Jul 13, 2012 at 9:00 PM, Ohad Ben-Cohen wrote:
> I agree. I'll take it, but will change the commit log to make it
> omaprpc-agnostic.
Here's what I'm going to apply:
commit 913552b8c7a0f06cc1bff27f8e9953bffe6a1817
Author: Federico Fuga
Date: Mon Jul 16 10:36:51 2012 +030
On Mon, Jul 16, 2012 at 05:17:09PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20120713:
>
> The ext4 tree lost its build failure.
>
> The vfs tree gained a build failure so I used the version from
> next-20120713.
Details, please?
--
To unsubscribe from this list: send the line
On Mon, 16 Jul 2012 10:34:46 +0800, Alex Shi wrote:
> >
>
> > And the same applies to the other comments. So can you please grab the
> > latest linux-next, prepare a fixup patch and also check that the patch
> > is complete - not all of your changes have been applied.
> >
>
>
>
> Thanks for
On Mon, 16 Jul 2012 10:35:54 +0800, Alex Shi wrote:
> The function has no parameter @len now, so need to remove it from
> comments to avoid kernel-doc warning:
But it still does in my tree.
Please push this patch via whoever changed it?
Acked-by: Rusty Russell
Thanks,
Rusty.
--
To unsubscribe
On Mon, Jul 16, 2012 at 9:48 AM, Al Viro wrote:
> On Mon, Jul 16, 2012 at 05:17:09PM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20120713:
>>
>> The ext4 tree lost its build failure.
>>
>> The vfs tree gained a build failure so I used the version from
>> next-20120713.
>
> Detail
On Mon, Jul 16, 2012 at 9:54 AM, Sedat Dilek wrote:
> On Mon, Jul 16, 2012 at 9:48 AM, Al Viro wrote:
>> On Mon, Jul 16, 2012 at 05:17:09PM +1000, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20120713:
>>>
>>> The ext4 tree lost its build failure.
>>>
>>> The vfs tree gained a build
On 07/16/2012 03:35 PM, Rusty Russell wrote:
> On Mon, 16 Jul 2012 10:34:46 +0800, Alex Shi wrote:
>>>
>>
>>> And the same applies to the other comments. So can you please grab the
>>> latest linux-next, prepare a fixup patch and also check that the patch
>>> is complete - not all of your change
Steven,
please pick the following three patches which address the CPU hotplug
nightmare on RT.
I still hate them, but we want to have that addressed in the stable
series.
Aside of that there are the outstanding issues with btrfs and io unplug.
The missing spin_lock_init() fix should reach you v
Revert commit
Author: Peter Zijlstra
Date: Mon Oct 3 12:43:25 2011 +0200
workqueue: Fix PF_THREAD_BOUND abuse
As TREAD_BOUND no longer affects cpu down, and this code introduced
a lot of races with taking down a CPU.
Signed-off-by: Steven Rostedt
Signed-off-by: Thomas Gleixner
-
Revert
Author: Peter Zijlstra
Date: Fri Sep 30 11:57:58 2011 +0200
workqueue: Fix cpuhotplug trainwreck
As TREAD_BOUND no longer affects cpu down, and this code introduced
a lot of races with taking down a CPU.
Signed-off-by: Steven Rostedt
Signed-off-by: Thomas Gleixner
---
in
Bringing a CPU down is a pain with the PREEMPT_RT kernel because
tasks can be preempted in many more places than in non-RT. In
order to handle per_cpu variables, tasks may be pinned to a CPU
for a while, and even sleep. But these tasks need to be off the CPU
if that CPU is going down.
Several sync
On Thu, 12 Jul 2012, Michal Hocko wrote:
> On Wed 11-07-12 18:57:43, Hugh Dickins wrote:
> >
> > I mentioned in Johannes's [03/11] thread a couple of days ago, that
> > I was having a problem with your wait_on_page_writeback() in mmotm.
> >
> > It turns out that your original patch was fine, but
The below checkpatch warns was fixed,
drivers/staging/cptm1217/clearpad_tm1217.c:400: WARNING: quoted string split
across lines
drivers/staging/cptm1217/cp_tm1217.h:5: ERROR: open brace '{' following struct
go on the same line
Signed-off-by: Toshiaki Yamane
---
drivers/staging/cptm1217/clearp
On Mon, Jul 16, 2012 at 10:12 AM, Toshiaki Yamane wrote:
> The below checkpatch warns was fixed,
>
> drivers/staging/cptm1217/clearpad_tm1217.c:400: WARNING: quoted string split
> across lines
> drivers/staging/cptm1217/cp_tm1217.h:5: ERROR: open brace '{' following
> struct go on the same line
Hi,
On Mon, Jun 25, 2012 at 04:26:08PM +, Arnd Bergmann wrote:
> On Monday 25 June 2012, Felipe Balbi wrote:
> > > > Can't this live where the scp drivers live? Actually, where is that at?
> > > > Do we have scp drivers?
> > > AFAIK, there isn't any driver for scp. But we have a driver for oc
On Mon, 16 Jul 2012, Chen Gong wrote:
>
> Are you still care about this thread any more? Any plan to update it?
> Hope to get your feedback ASAP.
Can you please collect the latest series and send it to lkml, Tony and
Boris. I think it's ok as is now.
Thanks,
tglx
--
To unsubscribe from
Hi Ramakrishna,
On Mon, Jun 25, 2012 at 06:07:22PM +0530, Ramakrishna Pallala wrote:
> On some platforms one driver(or HW chip) may not be able to provide all
> the necessary attributes of the power supply connected to the platform or
> may provide very limited info which can be used by core/prima
On Sun, Jul 15, 2012 at 03:09:12PM -0700, da...@lang.hm wrote:
> On Mon, 16 Jul 2012, Cyrill Gorcunov wrote:
>
> >Replying to David's message (sorry for delay) I fear having a bunch of
> >miniconfig files will end up in a mess. Maybe (maybe (!) I don't know since
> >I've no time at moment to read
On 07/15/2012 03:16 PM, Catalin Marinas wrote:
>
> The AArch32 execution mode is optional, so it depends on the actual CPU
> implementation (while AArch64 is mandatory). If the implementation
> supports it, the most likely scenario for AArch32 at kernel level is in
> virtual machines or the secure
Currently Pause Loop Exit (PLE) handler is doing directed yield to a
random vcpu on pl-exit. We already have filtering while choosing
the candidate to yield_to. This change adds more checks while choosing
a candidate to yield_to.
On a large vcpu guests, there is a high probability of
yielding to
From: Raghavendra K T
Noting pause loop exited vcpu or cpu relax intercepted helps in
filtering right candidate to yield. Wrong selection of vcpu;
i.e., a vcpu that just did a pl-exit or cpu relax intercepted may
contribute to performance degradation.
Signed-off-by: Raghavendra K T
---
V2 was:
From: Raghavendra K T
Suggested-by: Avi Kivity
Signed-off-by: Raghavendra K T
---
arch/s390/kvm/Kconfig |1 +
arch/x86/kvm/Kconfig |1 +
virt/kvm/Kconfig |3 +++
3 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/arch/s390/kvm/Kconfig b/arch/s390/kvm/Kconfig
index
From: Raghavendra K T
Currently, on a large vcpu guests, there is a high probability of
yielding to the same vcpu who had recently done a pause-loop exit or
cpu relax intercepted. Such a yield can lead to the vcpu spinning
again and hence degrade the performance.
The patchset keeps track of the
Hi,
On Mon, Jul 16, 2012 at 1:42 PM, Felipe Balbi wrote:
> Hi,
>
> On Mon, Jun 25, 2012 at 04:26:08PM +, Arnd Bergmann wrote:
>> On Monday 25 June 2012, Felipe Balbi wrote:
>> > > > Can't this live where the scp drivers live? Actually, where is that
>> > > > at?
>> > > > Do we have scp driv
On Mon, 2012-07-16 at 09:13 +0200, Guennadi Liakhovetski wrote:
> > > They tell the driver how the channel has to be configured to
> support this
> > > specific client. They are values of two specific registers. In
> fact, CHCR
> > > means exactly that - CHannel Control Register.
> > what exactly
On 07/16/2012 03:40 PM, Rusty Russell wrote:
> On Mon, 16 Jul 2012 10:35:54 +0800, Alex Shi wrote:
>> The function has no parameter @len now, so need to remove it from
>> comments to avoid kernel-doc warning:
>
> But it still does in my tree.
>
> Please push this patch via whoever changed it?
>
On Thursday 12 July 2012 05:09, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in
> drivers/net/ethernet/mellanox/mlx4/main.c between commit 6634961c14d3
> ("mlx4: Put physical GID and P_Key table sizes in mlx4_phys_caps struct
> and paravirtuali
On Thursday 12 July 2012 05:13, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in
> include/linux/mlx4/device.h between commit 396f2feb05d7 ("mlx4_core:
> Implement mechanism for reserved Q_Keys") from the infiniband tree and
> commit 0ff1fb654be
On Fri, 13 Jul 2012, Michal Hocko wrote:
> On Thu 12-07-12 15:42:53, Hugh Dickins wrote:
> > On Thu, 12 Jul 2012, Andrew Morton wrote:
> > >
> > > I wasn't planning on 3.5, given the way it's been churning around.
> >
> > I don't know if you had been intending to send it in for 3.5 earlier;
> > b
On Mon, Jul 16, 2012 at 09:56:45AM +0200, Sedat Dilek wrote:
> On Mon, Jul 16, 2012 at 9:54 AM, Sedat Dilek wrote:
> > On Mon, Jul 16, 2012 at 9:48 AM, Al Viro wrote:
> >> On Mon, Jul 16, 2012 at 05:17:09PM +1000, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Changes since 20120713:
> >>>
> >
The may_enter_fs test turns out to be too restrictive: though I saw
no problem with it when testing on 3.5-rc6, it very soon OOMed when
I tested on 3.5-rc6-mm1. I don't know what the difference there is,
perhaps I just slightly changed the way I started off the testing:
dd if=/dev/zero of=/mnt/tem
The below checkpatch warn, error, and typo was fixed,
drivers/staging/cptm1217/clearpad_tm1217.c:400: WARNING: quoted string split
across lines
drivers/staging/cptm1217/cp_tm1217.h:5: ERROR: open brace '{' following struct
go on the same line
Signed-off-by: Toshiaki Yamane
---
drivers/staging
On Sun, Jul 15, 2012 at 10:43:25PM +0100, Daniel Drake wrote:
> From: Richard A. Smith
>
> upowerd wants to compute the energy in the battery by looking at this
> property. If it's not present then it falls back on using the reported
> voltage of the battery at time upowerd loads. That's close
On Mon, 16 Jul 2012, Vinod Koul wrote:
> On Mon, 2012-07-16 at 09:13 +0200, Guennadi Liakhovetski wrote:
> > > > They tell the driver how the channel has to be configured to
> > support this
> > > > specific client. They are values of two specific registers. In
> > fact, CHCR
> > > > means exact
On Mon 16-07-12 01:10:47, Hugh Dickins wrote:
> On Thu, 12 Jul 2012, Michal Hocko wrote:
> > On Wed 11-07-12 18:57:43, Hugh Dickins wrote:
> > >
> > > I mentioned in Johannes's [03/11] thread a couple of days ago, that
> > > I was having a problem with your wait_on_page_writeback() in mmotm.
> > >
Signed-off-by: Richard Zhao
---
drivers/mfd/anatop-mfd.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mfd/anatop-mfd.c b/drivers/mfd/anatop-mfd.c
index 6da0634..5576e07 100644
--- a/drivers/mfd/anatop-mfd.c
+++ b/drivers/mfd/anatop-mfd.c
@@ -83,7 +83,7 @@ static
On Mon, 16 Jul 2012, Mike Galbraith wrote:
> On Sun, 2012-07-15 at 11:14 +0200, Mike Galbraith wrote:
> > On Sun, 2012-07-15 at 10:59 +0200, Thomas Gleixner wrote:
>
> > > Can you figure out on which lock the stuck thread which did not unplug
> > > due to tsk_is_pi_blocked was blocked?
> >
> >
Hi Christoph,
On 07/14/2012 03:49 PM, Christoph Hellwig wrote:
Please send a version that does direct block I/O similar to xen-blkback
for now.
Seems xen-blkback converts the guest IO request to host bio and submit
them directly. I was wondering whether this has a performance gain
compared t
Hi Axel,
My apologies for the delay in responding to this one.
On Monday 09 July 2012 04:31 PM, Axel Lin wrote:
於 一，2012-07-09 於 11:22 +0800，Axel Lin 提到：
In twl6030ldo_set_voltage, current code use below formula to calculate vsel:
vsel = (min_uV/1000 - 1000)/100 + 1;
This is worng bec
From: Michael Wang
This patch is trying to provide a way for user to dynamically change
the behaviour of load balance by setting flags of schedule domain.
Currently it's rely on cpu cgroup and only SD_LOAD_BALANCE was
implemented, usage:
1. /sys/fs/cgroup/domain/domain.config_level
the
At Thu, 12 Jul 2012 23:30:31 +0200,
Ondrej Zary wrote:
>
> By setting SNDRV_PCM_INFO_RESUME, wss_lib claims that it can restore the card
> state fully on resume. But in fact, it can't as DMA is not restored so any
> playback/capture running during suspend will fail to continue after resume.
>
> R
At Mon, 16 Jul 2012 08:30:18 +0200,
Ondrej Zary wrote:
>
> Yamaha OPL3-SAx chips don't resume properly when playback is running -
> garbage is played after resume. Restoring the CS4231_PLAYBK_FORMAT register
> last fixes the problem.
>
> Signed-off-by: Ondrej Zary
Applied. Thanks.
Takashi
Copying Graeme and linux-omap list.
On Saturday 14 July 2012 11:07 AM, Axel Lin wrote:
The voltage selection logic is supposed to find the samllest voltage falls
within specified range. When using equation to calculate vsel, we need to
ensure the requested min_uV meet the range of using the equa
Copying Graeme and linux-omap list.
On Saturday 14 July 2012 11:11 AM, Axel Lin wrote:
Signed-off-by: Axel Lin
---
drivers/regulator/twl-regulator.c | 24 +---
1 file changed, 13 insertions(+), 11 deletions(-)
diff --git a/drivers/regulator/twl-regulator.c
b/drivers/re
* Michael S. Tsirkin wrote:
> KVM PV EOI optimization overrides eoi_write apic op with its own
> version. Add an API for this to avoid meddling with core x86 apic driver
> data structures directly.
>
> For KVM use, we don't need any guarantees about when the switch to the
> new op will take pla
On Sun, Jul 15, 2012 at 9:43 PM, Arnd Bergmann wrote:
> Yes, I agree that's the best way to handle this. Compared to other
> architectures, I think x86 is the only that allows booting either a
> 32 or 64 bit kernel on the same system. We used to support 32 bit
> kernels on 64 bit PowerMac, but nob
On Mon 16-07-12 01:35:34, Hugh Dickins wrote:
> The may_enter_fs test turns out to be too restrictive: though I saw
> no problem with it when testing on 3.5-rc6, it very soon OOMed when
> I tested on 3.5-rc6-mm1. I don't know what the difference there is,
> perhaps I just slightly changed the way
Hey Namhyung,
Thanks for your response!
On 07/16/2012 01:16 PM, Namhyung Kim wrote:
> Hi,
>
> (CC-ing Jiri)
>
> On Sun, 15 Jul 2012 22:32:14 +0800, Jeff Liu wrote:
>> Hello,
>>
>> I failed to compile perf tools on 3.5.0-rc7 with bison && flex
>> pre-installed.
>>
>> The error seems something li
On Thu, 12 Jul 2012, Jeff Liu wrote:
> On 07/12/2012 07:01 AM, Dave Chinner wrote:
> > On Wed, Jul 11, 2012 at 11:55:34AM -0700, Hugh Dickins wrote:
> >>
> >> But your vote would count for a lot more if you know of some app which
> >> would really benefit from this functionality in tmpfs: I've hear
On Mon, 2012-07-16 at 10:47 +0200, Guennadi Liakhovetski wrote:
> > I want to know what does ccr and mid_rid mean to dmac here?
>
> CHCR contains a few fields, some enable various interrupt sources, some
> specify repeat- and renew-modes, others yet specify transfer size, source
> and destinatio
This patch fix bug related to interrupt handling for MAX77693 devices.
- Unmask interrupt masking bit for charger/flash/muic to revolve
that interrupt isn't happened when external connector is attached.
- Fix wrong regmap instance when muic interrupt is happened.
Signed-off-by: Chanwoo Choi
Signe
From: Dong Hao
The function printk() at end of function kobject_init() already had '\n',
so remove it.
While the kobject has been initialized, assign error string and
jump to error case directly.
Signed-off-by: Dong Hao
---
lib/kobject.c |9 -
1 files changed, 4 insertions(+), 5 de
On Sun, 15 Jul 2012, Rafael J. Wysocki wrote:
> To everyone involved: the fact that this change, which was likely to introduce
> regressions from the look of it alone, has been pushed to Linus (an to -stable
> at the same time!) so late in the cycle, is seriuosly disappointing.
Well, we spent an m
On Mon, 2012-07-16 at 10:59 +0200, Thomas Gleixner wrote:
> On Mon, 16 Jul 2012, Mike Galbraith wrote:
> > On Sun, 2012-07-15 at 11:14 +0200, Mike Galbraith wrote:
> > > On Sun, 2012-07-15 at 10:59 +0200, Thomas Gleixner wrote:
> >
> > > > Can you figure out on which lock the stuck thread which
On Wednesday 11 July 2012 10:58:38 Julia Lawall wrote:
> From: Julia Lawall
>
> dev_get_platdata returns a pointer, so the failure value would be NULL
> rather than a negative integer.
>
> The semantic match that finds this problem is: (http://coccinelle.lip6.fr/)
>
> //
> @@
> expression x,e;
Hello,
The following series fixes the revision information for twl6040 and adds support
for twl6041.
While the first patch is changing a driver in sound/soc/codecs the series can go
via MFD since we do not have pending patches for twl6040 audio part for 3.6.
Regards,
Peter
---
Peter Ujfalusi (2)
twl6040 ES1.1 and ES1.2 have the same revid (0x01).
ES1.3 of twl6040 REVID is 0x02.
Signed-off-by: Peter Ujfalusi
---
include/linux/mfd/twl6040.h |4 ++--
sound/soc/codecs/twl6040.c |2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/linux/mfd/twl6040.h b/inclu
The delta between twl6040 and twl6041 is small, the main difference is in
the number of GPOs (3 on twl6040, 1 on twl6041).
Signed-off-by: Peter Ujfalusi
---
Documentation/devicetree/bindings/mfd/twl6040.txt |2 +-
drivers/mfd/twl6040-core.c|1 +
include/linux/mfd/
On 07/15/2012 03:56 PM, Michael S. Tsirkin wrote:
> KVM PV EOI optimization overrides eoi_write apic op with its own
> version. at Ingo's suggestion, add an API for this and switch kvm to use
> it, to avoid meddling with core x86 apic driver data structures
> directly.
Applied to next, thanks.
--
On Sun, 15 Jul 2012, Shuah Khan wrote:
> I can work on reshuffling the code. Do have a question though. This
> following sanity check is currently done only when CONFIG_DEBUG_VM is
> defined. However, it does appear to be something that is that should be
> checked even in regular path.
>
> struct
On Mon, 16 Jul 2012, Mike Galbraith wrote:
> On Mon, 2012-07-16 at 10:59 +0200, Thomas Gleixner wrote:
> > On Mon, 16 Jul 2012, Mike Galbraith wrote:
> > > On Sun, 2012-07-15 at 11:14 +0200, Mike Galbraith wrote:
> > > > On Sun, 2012-07-15 at 10:59 +0200, Thomas Gleixner wrote:
> > >
> > > > >
On Mon, 16 Jul 2012, Vinod Koul wrote:
> On Mon, 2012-07-16 at 10:47 +0200, Guennadi Liakhovetski wrote:
> > > I want to know what does ccr and mid_rid mean to dmac here?
> >
> > CHCR contains a few fields, some enable various interrupt sources, some
> > specify repeat- and renew-modes, others y
On 07/16/2012 11:25 AM, Raghavendra K T wrote:
> From: Raghavendra K T
>
> Noting pause loop exited vcpu or cpu relax intercepted helps in
> filtering right candidate to yield. Wrong selection of vcpu;
> i.e., a vcpu that just did a pl-exit or cpu relax intercepted may
> contribute to performance
On 07/16/2012 11:25 AM, Raghavendra K T wrote:
> From: Raghavendra K T
>
> Currently, on a large vcpu guests, there is a high probability of
> yielding to the same vcpu who had recently done a pause-loop exit or
> cpu relax intercepted. Such a yield can lead to the vcpu spinning
> again and hence
Hm, wonder how bad this sucks.. and if I should go hide under a big
sturdy rock after I poke xmit :)
---
block/blk-core.c |1 +
kernel/rtmutex.c | 11 +--
2 files changed, 10 insertions(+), 2 deletions(-)
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -2782,6 +2782,7 @@ void blk_
Hey Rob,
Op 13-07-12 17:38, Rob Clark schreef:
> ...
> +/**
> + * dma_buf_attach_fence - Attach a fence to a dma-buf.
> + *
> + * @buf: the dma-buf to attach to
> + * @fence: the fence to attach
> + *
> + * A fence can only be attached to a single dma-buf. The dma-buf takes
> + * ownership of the
On Mon, 2012-07-16 at 11:59 +0200, Thomas Gleixner wrote:
> On Mon, 16 Jul 2012, Mike Galbraith wrote:
> > On Mon, 2012-07-16 at 10:59 +0200, Thomas Gleixner wrote:
> > > On Mon, 16 Jul 2012, Mike Galbraith wrote:
> > > > On Sun, 2012-07-15 at 11:14 +0200, Mike Galbraith wrote:
> > > > > On Sun,
> Well I think I ACKed that from the point of view that it will work as
> expected with ux500 with these bindings. What is best from the I2C
> subsystem point of view is another question ...
Okay, thanks for clarifying.
> Overall I think we have this general problem with a lot of DT
> conversion
On Thu, Jul 12, 2012 at 10:33:04PM -0700, Joe Perches wrote:
> net-next commit ad7eee98be ("etherdevice: introduce eth_broadcast_addr")
> added a new style API. Rename random_ether_addr to eth_random_addr to
> create some API symmetry.
>
> Joe Perches (8):
> etherdevice: Rename random_ether_add
On Mon, 16 Jul 2012, Mike Galbraith wrote:
> Hm, wonder how bad this sucks.. and if I should go hide under a big
> sturdy rock after I poke xmit :)
>
> ---
> block/blk-core.c |1 +
> kernel/rtmutex.c | 11 +--
> 2 files changed, 10 insertions(+), 2 deletions(-)
>
> --- a/block/blk
> On Monday 09 July 2012 04:31 PM, Axel Lin wrote:
> > 於 一，2012-07-09 於 11:22 +0800，Axel Lin 提到：
> >> In twl6030ldo_set_voltage, current code use below formula to calculate
> >> vsel:
> >> vsel = (min_uV/1000 - 1000)/100 + 1;
> >> This is worng because when min_uV is 100 uV, vsel is
On Mon, 2012-07-16 at 12:01 +0200, Guennadi Liakhovetski wrote:
> On Mon, 16 Jul 2012, Vinod Koul wrote:
>
> > On Mon, 2012-07-16 at 10:47 +0200, Guennadi Liakhovetski wrote:
> > > > I want to know what does ccr and mid_rid mean to dmac here?
> > >
> > > CHCR contains a few fields, some enable va
From: Felipe Balbi
Date: Mon, 16 Jul 2012 13:14:38 +0300
> if you're really renaming the function, then this patch alone will break
> all of the below users. That should all be a single patch, I'm afraid.
It would help if you actually read his patches before saying what they
might or might not d
(hohum, gmx server went down, back to random address mode;)
On Mon, 2012-07-16 at 12:19 +0200, Thomas Gleixner wrote:
>
> That should do the trick.
I'll put it to work on 64 core box, and see if it survives. It better.
-Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-
According to the datasheet, the voltage for twl6030ldo_ops is not linear for
all cases. Linear mapping is only for the selection code from
0001 to 00011000.
Table 9. LDO Output Voltage Selection Code
CODE VOUT(V)COD VOUT(V)CODE VOUT(V)CODE VOUT(V)
0
The following series implements the infrastructure for parking and
unparking kernel threads to avoid the full teardown and fork on cpu
hotplug operations along with management infrastructure for hotplug
and users.
Changes vs. V2:
Use callbacks for all functionality. Thanks to Rusty for pointing
Signed-off-by: Thomas Gleixner
---
kernel/softirq.c | 107 +--
1 file changed, 26 insertions(+), 81 deletions(-)
Index: tip/kernel/softirq.c
===
--- tip.orig/kernel/softirq.c
+++
The rcu_yield() code is amazing. It's there to avoid starvation of the
system when lots of (boosting) work is to be done.
Now looking at the code it's functionality is:
Make the thread SCHED_OTHER and very nice, i.e. get it out of the way
Arm a timer with 2 ticks
schedule()
Now if the system
Signed-off-by: Thomas Gleixner
---
kernel/watchdog.c | 264 ++
1 file changed, 89 insertions(+), 175 deletions(-)
Index: tip/kernel/watchdog.c
===
--- tip.orig/kernel/watchdog.c
+
To avoid the full teardown/setup of per cpu kthreads in the case of
cpu hot(un)plug, provide a facility which allows to put the kthread
into a park position and unpark it when the cpu comes online again.
Signed-off-by: Thomas Gleixner
Reviewed-by: Namhyung Kim
---
include/linux/kthread.h | 11
Provide a generic interface for setting up and tearing down percpu
threads.
On registration the threads for already online cpus are created and
started. On deregistration (modules) the threads are stoppped.
During hotplug operations the threads are created, started, parked and
unparked. The datas
1 - 100 of 542 matches
Mail list logo
