[tip:sched/core] sched/fair: Clean up update_sg_lb_stats() a bit

Commit-ID: 380c9077b38df2962a22f00f21f6cd0db62d3390 Gitweb: http://git.kernel.org/tip/380c9077b38df2962a22f00f21f6cd0db62d3390 Author: Kamalesh Babulal AuthorDate: Fri, 15 Nov 2013 15:06:52 +0530 Committer: Ingo Molnar CommitDate: Wed, 27 Nov 2013 13:50:57 +0100 sched/fair: Clean up

[tip:core/locking] liblockdep: Add pthread_mutex_t test suite

Commit-ID: 878f968eeb852383ff79dc3f181db24e5b52fd75 Gitweb: http://git.kernel.org/tip/878f968eeb852383ff79dc3f181db24e5b52fd75 Author: Sasha Levin AuthorDate: Thu, 13 Jun 2013 18:41:19 -0400 Committer: Ingo Molnar CommitDate: Wed, 27 Nov 2013 11:55:22 +0100 liblockdep: Add

[tip:core/locking] liblockdep: Add the 'lockdep' user-space utility

Commit-ID: f612ac05b7ce66919507d25f4c81e4272f7a8705 Gitweb: http://git.kernel.org/tip/f612ac05b7ce66919507d25f4c81e4272f7a8705 Author: Sasha Levin AuthorDate: Thu, 13 Jun 2013 18:41:23 -0400 Committer: Ingo Molnar CommitDate: Wed, 27 Nov 2013 11:56:25 +0100 liblockdep: Add the

[tip:core/locking] liblockdep: Add public headers for pthread_mutex_t implementation

Commit-ID: 45e6207464b59dca63c8a9a79a7befbbf6a68fdb Gitweb: http://git.kernel.org/tip/45e6207464b59dca63c8a9a79a7befbbf6a68fdb Author: Sasha Levin AuthorDate: Thu, 13 Jun 2013 18:41:18 -0400 Committer: Ingo Molnar CommitDate: Wed, 27 Nov 2013 11:55:22 +0100 liblockdep: Add public

[tip:core/locking] liblockdep: Add pthread_rwlock_t test suite

Commit-ID: dbe941827eab53194eda5cd350a4e1414f192658 Gitweb: http://git.kernel.org/tip/dbe941827eab53194eda5cd350a4e1414f192658 Author: Sasha Levin AuthorDate: Thu, 13 Jun 2013 18:41:21 -0400 Committer: Ingo Molnar CommitDate: Wed, 27 Nov 2013 11:55:24 +0100 liblockdep: Add

[tip:core/locking] liblockdep: Support using LD_PRELOAD

Commit-ID: 231941eec8aeee4f0ac210a28e484200b20f74d8 Gitweb: http://git.kernel.org/tip/231941eec8aeee4f0ac210a28e484200b20f74d8 Author: Sasha Levin AuthorDate: Thu, 13 Jun 2013 18:41:22 -0400 Committer: Ingo Molnar CommitDate: Wed, 27 Nov 2013 11:55:24 +0100 liblockdep: Support using

[PATCH v2] firmware/dmi_scan: generalize for use by other archs

This patch makes a couple of changes to the SMBIOS/DMI scanning code so it can be used on other archs (such as ARM and arm64): (a) wrap the calls to ioremap()/iounmap(), this allows the use of a flavor of ioremap() more suitable for random unaligned access; (b) allow the non-EFI fallback probe

Re: [BUG] in sched fair on v3.13-rc1+ doing hotplug

On Wed, 27 Nov 2013 14:22:43 +0100 Peter Zijlstra wrote: > On Wed, Nov 27, 2013 at 08:13:45AM -0500, Steven Rostedt wrote: > > atomic_inc(>groups->sgp->nr_busy_cpus); << BUG > > unlock: > > rcu_read_unlock(); > > } > > tip/sched/urgent has this one: > > --- > commit

[tip:perf/core] perf: Add active_entry list head to struct perf_event

Commit-ID: 71ad88efebbcde374bddf904b96f3a7fc82d45d4 Gitweb: http://git.kernel.org/tip/71ad88efebbcde374bddf904b96f3a7fc82d45d4 Author: Stephane Eranian AuthorDate: Tue, 12 Nov 2013 17:58:48 +0100 Committer: Ingo Molnar CommitDate: Wed, 27 Nov 2013 11:16:38 +0100 perf: Add active_entry

[tip:core/locking] lockdep: Simplify a bit hardirq <-> softirq transitions

Commit-ID: 5c4853b60ca8ec3d989ce05a5e995d15c3ed52c0 Gitweb: http://git.kernel.org/tip/5c4853b60ca8ec3d989ce05a5e995d15c3ed52c0 Author: Frederic Weisbecker AuthorDate: Wed, 20 Nov 2013 01:07:34 +0100 Committer: Ingo Molnar CommitDate: Wed, 27 Nov 2013 11:09:40 +0100 lockdep: Simplify a

[tip:sched/core] sched: Fix a trivial syntax misuse

Commit-ID: 39e24d8ffbb6aa90222527dbd5991ec49fbbf323 Gitweb: http://git.kernel.org/tip/39e24d8ffbb6aa90222527dbd5991ec49fbbf323 Author: Shigeru Yoshida AuthorDate: Sat, 23 Nov 2013 18:38:01 +0900 Committer: Ingo Molnar CommitDate: Tue, 26 Nov 2013 18:37:55 +0100 sched: Fix a trivial

[tip:perf/core] tools/perf/stat: Add event unit and scale support

Commit-ID: 410136f5dd96b6013fe6d1011b523b1c247e1ccb Gitweb: http://git.kernel.org/tip/410136f5dd96b6013fe6d1011b523b1c247e1ccb Author: Stephane Eranian AuthorDate: Tue, 12 Nov 2013 17:58:49 +0100 Committer: Ingo Molnar CommitDate: Wed, 27 Nov 2013 11:16:39 +0100 tools/perf/stat: Add

[tip:sched/urgent] sched: Expose preempt_schedule_irq()

Commit-ID: 32e475d76a3e40879cd9ee4f69b19615062280d7 Gitweb: http://git.kernel.org/tip/32e475d76a3e40879cd9ee4f69b19615062280d7 Author: Thomas Gleixner AuthorDate: Thu, 21 Nov 2013 12:41:44 +0100 Committer: Ingo Molnar CommitDate: Wed, 27 Nov 2013 11:04:53 +0100 sched: Expose

Re: [PATCH v4 07/12] efi: passing kexec necessary efi data via setup_data

On Tue, Nov 26, 2013 at 01:57:52PM +0800, Dave Young wrote: > Add a new setup_data type SETUP_EFI for kexec use. > Passing the saved fw_vendor, runtime, config tables and > efi runtime mappings. > > When entering virtual mode, directly mapping the efi > runtime ragions which we passed in

Re: [PATCH] x86: override __compiletime_object_size()

* Jan Beulich wrote: > As discussed in the context of commits 3df7b41a ("x86: Unify > copy_from_user() size checking") and 7a3d9b0f ("x86: Unify > copy_to_user() and add size checking to it"), we want to leverage > __builtin_object_size() also on newer gcc versions, but with other >

Re: [PATCH] watchdog: davinci: rename platform driver to davinci-wdt

On Wednesday 27 November 2013 07:01 PM, Ivan Khoronzhuk wrote: > As we switch to use the watchdog core which permits more than one > active watchdog in the system, rename platform driver to > "davinci-wdt" to be identifiable. > > Signed-off-by: Ivan Khoronzhuk Looks good to me. Since bulk of

Re: [PATCH 02/14] sched: add extended scheduling interface. (new ABI)

* Peter Zijlstra wrote: > On Wed, Nov 27, 2013 at 02:23:54PM +0100, Ingo Molnar wrote: > > There are 3 main compatibility cases: > > > > - the kernel's 'sizeof sched_attr' is equal to sched_attr:size: the > >kernel version and user-space version matches, it's a straight ABI > >in

Re: [PATCH v5 1/2] regulator: max14577: Add regulator driver for Maxim 14577

On Wed, 27 Nov 2013, Krzysztof Kozlowski wrote: > MAX14577 chip is a multi-function device which includes MUIC, > charger and voltage regulator. The driver is located in drivers/mfd. > > This patch adds regulator driver for MAX14577 chip. There are two > regulators in this chip: > 1. Safeout LDO

Re: [PATCH 1/3] mfd: tps6586x: add version detection

> >>if (ret < 0) { > >>dev_err(>dev, "Chip ID read failed: %d\n", ret); > >>return -EIO; > > > > Why are you returning an error here when you have a valid enum of: > > TPS6586X_ANY = -1, > > > Hm, when the device is not answering on that request, the probe

[PATCH 1/2] perf: fix PERF_EVENT_IOC_PERIOD to force-reset the period

From: Peter Zijlstra Vince Weaver reports that, on all architectures apart from ARM, PERF_EVENT_IOC_PERIOD doesn't actually update the period until the next event fires. This is counter-intuitive behaviour and is better dealt with in the core code. This patch ensures that the period is

[PATCH 2/2] Revert "ARM: 7556/1: perf: fix updated event period in response to PERF_EVENT_IOC_PERIOD"

This reverts commit 3581fe0ef37ce12ac7a4f74831168352ae848edc. Updates to the handling of PERF_EVENT_IOC_PERIOD in the core code mean we no longer have to play this horrible game. Cc: Peter Zijlstra Signed-off-by: Will Deacon --- arch/arm/kernel/perf_event.c | 4 1 file changed, 4

[PATCH] lockref: include mutex.h rather than reinvent arch_mutex_cpu_relax

arch_mutex_cpu_relax is already conditionally defined in mutex.h, so simply include that header rather than replicate the code here. Signed-off-by: Will Deacon --- lib/lockref.c | 9 + 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/lib/lockref.c b/lib/lockref.c index

Re: [PATCH] Perf: Correct Assumptions about Sample Timestamps in Passes

* Joseph Schuchart wrote: > Sorry for my delayed reply, it's been a busy week and I really wanted to > give Ingo's idea below some thought. Please find my comments below. > > >>> If done that way then AFAICS we could even eliminate the > >>> ->max_timestamps[NR_CPUS] array. > >> > >> I can

[PATCH] i2c: omap: raw read and write endian fix

From: Victor Kamensky All OMAP IP blocks expect LE data, but CPU may operate in BE mode. Need to use endian neutral functions to read/write h/w registers. I.e instead of __raw_read[lw] and __raw_write[lw] functions code need to use read[lw]_relaxed and write[lw]_relaxed functions. If the first

[PATCH v5 2/2] mfd: max14577: Add device tree bindings document

Add document describing device tree bindings for MAX14577 MFD driver. Signed-off-by: Krzysztof Kozlowski Signed-off-by: Kyungmin Park --- Documentation/devicetree/bindings/mfd/max14577.txt | 48 1 file changed, 48 insertions(+) create mode 100644

[PATCH v5 1/2] regulator: max14577: Add regulator driver for Maxim 14577

MAX14577 chip is a multi-function device which includes MUIC, charger and voltage regulator. The driver is located in drivers/mfd. This patch adds regulator driver for MAX14577 chip. There are two regulators in this chip: 1. Safeout LDO with constant voltage output of 4.9V. It can be only

Re: [PATCH 1/3] mfd: tps6586x: add version detection

Am 2013-11-27 14:09, schrieb Lee Jones: > > >> static int __remove_subdev(struct device *dev, void *unused) >> { >> platform_device_unregister(to_platform_device(dev)); >> @@ -477,6 +486,7 @@ static int tps6586x_i2c_probe(struct i2c_client *client, >> { >> struct

Re: [PATCH 21/22] perf tools: Add trace-event global object for tracepoint interface

Hi Jiri, 2013-11-25 (월), 17:03 +0100, Jiri Olsa: > On Sat, Nov 23, 2013 at 12:47:14AM +0900, Namhyung Kim wrote: > > 2013-11-21 (목), 12:01 +0100, Jiri Olsa: > > > In order to get the proper plugins processing we need to > > > use full trace-event interface when creating tracepoint > > > events.

Re: netfilter: active obj WARN when cleaning up

On Wed, 27 Nov 2013, Russell King - ARM Linux wrote: > On Wed, Nov 27, 2013 at 01:32:31PM +, Russell King - ARM Linux wrote: > > On Wed, Nov 27, 2013 at 02:29:41PM +0100, Thomas Gleixner wrote: > > > Though the kobject is the only thing which has a delayed work embedded > > > inside struct

Re: [PATCH] perf timechart: dynamically determine event data offset

Em Wed, Nov 27, 2013 at 05:49:02PM +0900, Namhyung Kim escreveu: > On Tue, 26 Nov 2013 18:54:37 +0400, Stanislav Fomichev wrote: > > Since b000c8065a92 "tracing: Remove the extra 4 bytes of padding in events" > > removed padding bytes, perf timechart got out of sync with the kernel's > >

Re: [PATCH 08/14] sched: add latency tracing for -deadline tasks.

On 11/20/2013 10:33 PM, Steven Rostedt wrote: > On Thu, 7 Nov 2013 14:43:42 +0100 > Juri Lelli wrote: > > >> +/* >> + * Semantic is like this: >> + * - wakeup tracer handles all tasks in the system, independently >> + *from their scheduling class; >> + * - wakeup_rt

[PATCH] ima: store address of template_fmt_copy in a pointer before calling strsep

This patch stores the address of the 'template_fmt_copy' variable in a new variable, called 'template_fmt_ptr', so that the latter is passed as an argument of strsep() instead of the former. This modification is needed in order to correctly free the memory area referenced by 'template_fmt_copy'

Re: netfilter: active obj WARN when cleaning up

On Wed, 27 Nov 2013, Russell King - ARM Linux wrote: > On Wed, Nov 27, 2013 at 02:29:41PM +0100, Thomas Gleixner wrote: > > Though the kobject is the only thing which has a delayed work embedded > > inside struct kmem_cache. And the debug object splat points at the > > kmem_cache_free() of the

Re: netfilter: active obj WARN when cleaning up

On Wed, Nov 27, 2013 at 01:32:31PM +, Russell King - ARM Linux wrote: > On Wed, Nov 27, 2013 at 02:29:41PM +0100, Thomas Gleixner wrote: > > Though the kobject is the only thing which has a delayed work embedded > > inside struct kmem_cache. And the debug object splat points at the > >

Re: [patch 4/6] ia64: Use preempt_schedule_irq

* Peter Zijlstra wrote: > On Tue, Nov 26, 2013 at 10:37:59AM -0800, Tony Luck wrote: > > On Thu, Nov 21, 2013 at 10:57 AM, Tony Luck wrote: > > > On Thu, Nov 21, 2013 at 5:30 AM, Thomas Gleixner > > > wrote: > > >> On Thu, 21 Nov 2013, Peter Zijlstra wrote: > > >>> Anyway, I don't object to

Re: modules, add_kallsyms() && DEFINE_PER_CPU

On 11/27, Masami Hiramatsu wrote: > > (2013/11/27 2:50), Oleg Nesterov wrote: > > On 11/26, Oleg Nesterov wrote: > >> > >> Note: this doesn't work for modules, but module's per-cpu data is > >> not visible for kallsyms_lookup_name() anyway. > > > > Rusty, I am just curious if it makes sense to

[PATCH] watchdog: davinci: rename platform driver to davinci-wdt

As we switch to use the watchdog core which permits more than one active watchdog in the system, rename platform driver to "davinci-wdt" to be identifiable. Signed-off-by: Ivan Khoronzhuk --- based on: https://lkml.org/lkml/2013/11/27/164 CC: Sekhar Nori Guenter Roeck

Re: netfilter: active obj WARN when cleaning up

On Wed, Nov 27, 2013 at 02:29:41PM +0100, Thomas Gleixner wrote: > Though the kobject is the only thing which has a delayed work embedded > inside struct kmem_cache. And the debug object splat points at the > kmem_cache_free() of the struct kmem_cache itself. That's why I > assumed the wreckage

Re: [PATCH -tip v3 02/23] kprobes: Introduce NOKPROBE_SYMBOL() macro for blacklist

* Masami Hiramatsu wrote: > +#ifdef CONFIG_KPROBES > +/* > + * Blacklist ganerating macro. Specify functions which is not probed > + * by using this macro. > + */ > +#define __NOKPROBE_SYMBOL(fname) \ > +static struct kprobe_blackpoint __used \

Re: Re: Re: [PATCH -tip v3 00/23] kprobes: introduce NOKPROBE_SYMBOL() and general cleaning of kprobe blacklist

* Masami Hiramatsu wrote: > (2013/11/22 11:35), Masami Hiramatsu wrote: > > (2013/11/21 16:29), Ingo Molnar wrote: > >> > >> * Masami Hiramatsu wrote: > >> > >>> (2013/11/21 2:36), Frank Ch. Eigler wrote: > >> > >> [ ... ] > one needs to resort to something like: > > # cat

Re: [PATCH] cpuset: Fix memory allocator deadlock

On Tue, Nov 26, 2013 at 03:03:41PM +0100, Peter Zijlstra wrote: > Juri hit the below lockdep report: > > [4.303391] == > [4.303392] [ INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ] > [4.303394] 3.12.0-dl-peterz+ #144 Not

Re: [PATCH 02/14] sched: add extended scheduling interface. (new ABI)

On Wed, Nov 27, 2013 at 02:23:54PM +0100, Ingo Molnar wrote: > There are 3 main compatibility cases: > > - the kernel's 'sizeof sched_attr' is equal to sched_attr:size: the >kernel version and user-space version matches, it's a straight ABI >in this case with full functionality. > >

Re: netfilter: active obj WARN when cleaning up

On Wed, 27 Nov 2013, Russell King - ARM Linux wrote: > On Wed, Nov 27, 2013 at 11:45:17AM +0100, Thomas Gleixner wrote: > > On Wed, 27 Nov 2013, Pablo Neira Ayuso wrote: > > > > > On Tue, Nov 26, 2013 at 02:11:57PM -0500, Sasha Levin wrote: > > > > Ping? I still see this warning. > > > > > > Did

[PATCH] phy: Add exynos-phy driver

Add exynos-phy driver to support a single register PHY interfaces present on Exynos4 SoC. Signed-off-by: Tomasz Stanislawski Signed-off-by: Kyungmin Park --- drivers/phy/Kconfig |5 ++ drivers/phy/Makefile |1 + drivers/phy/exynos-phy.c | 152

[PATCH] phy: Add exynos-phy driver

Hello everyone, The Samsung SoCs from Exynos family are enhanced with a bunch of switches dedicated for IP blocks. Those switches are called PHYs in Exynos specification. They are usually controlled by a single bit in a single one-word-long register. A IP driver has to control such a switch in an

Re: [PATCH] mfd: wm5110: Give new AIF2 registers defaults and mark as readable

> The registers associated with the new channels on AIF2 were accidentally > missing defaults and not marked as readable this patch fixes this. > > Signed-off-by: Charles Keepax > --- > > This patch depends on the patch: > > "ASoC: wm5110: Add extra AIF2 channels" > > Which is going through

Re: [PATCH 02/14] sched: add extended scheduling interface. (new ABI)

* Juri Lelli wrote: > + * @__unused padding to allow future expansion without ABI issues > + */ > +struct sched_param2 { > + int sched_priority; > + unsigned int sched_flags; > + u64 sched_runtime; > + u64 sched_deadline; > + u64 sched_period; > + > + u64

Re: [BUG] in sched fair on v3.13-rc1+ doing hotplug

On Wed, Nov 27, 2013 at 08:13:45AM -0500, Steven Rostedt wrote: > atomic_inc(>groups->sgp->nr_busy_cpus); << BUG > unlock: > rcu_read_unlock(); > } tip/sched/urgent has this one: --- commit 42eb088ed246a5a817bb45a8b32fe234cf1c0f8b Author: Peter Zijlstra Date: Tue Nov 19

Re: [PATCH] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif

On 11/27/2013 03:07 PM, Sekhar Nori wrote: On Wednesday 27 November 2013 04:31 PM, ivan.khoronzhuk wrote: @@ -192,9 +193,15 @@ static __init void davinci_ntosd2_init(void) davinci_cfg_reg(DM644X_ATAEN_DISABLE); /* only one device will be jumpered and detected */ -

Re: [PATCH]: exec: avoid propagating PF_NO_SETAFFINITY into userspace child

On 11/27, zhang.y...@zte.com.cn wrote: > > Userspace process doesn't want the PF_NO_SETAFFINITY, but its parent may be > a kernel worker thread which has PF_NO_SETAFFINITY set, and this worker thread > can do kernel_thread() to create the child. > Clearing this flag in usersapce child to enable

Re: [PATCH v4 1/5] mfd: max14577: Add max14577 MFD driver core

On Fri, 22 Nov 2013, Krzysztof Kozlowski wrote: > From: Chanwoo Choi > > This patch adds max14577 core/irq driver to support MUIC(Micro USB IC) > device and charger device and support irq domain method to control > internal interrupt of max14577 device. Also, this patch supports DT > binding

Re: [PATCH v4 4/5] regulator: max14577: Add regulator driver for Maxim 14577

> MAX14577 chip is a multi-function device which includes MUIC, > charger and voltage regulator. The driver is located in drivers/mfd. > > This patch adds regulator driver for MAX14577 chip. There are two > regulators in this chip: > 1. Safeout LDO with constant voltage output of 4.9V. It can be

[BUG] in sched fair on v3.13-rc1+ doing hotplug

Running my tests on 3.13-rc1 I hit the following crash with my cpu hotplug stress test (attached): [ 82.455572] BUG: unable to handle kernel paging request at 016d0010 [ 82.456109] IP: [] set_cpu_sd_state_idle+0x42/0x54 [ 82.456109] PGD 0 [ 82.456109] Oops: [#1] PREEMPT SMP

Re: [PATCH 1/3] mfd: tps6586x: add version detection

Oh, and it's usually a good idea to CC all of the maintainers. This patch nearly slipped through the gaps. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the

Re: [PATCH 1/3] mfd: tps6586x: add version detection

> static int __remove_subdev(struct device *dev, void *unused) > { > platform_device_unregister(to_platform_device(dev)); > @@ -477,6 +486,7 @@ static int tps6586x_i2c_probe(struct i2c_client *client, > { > struct tps6586x_platform_data *pdata = dev_get_platdata(>dev); >

Re: [PATCH] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif

On Wednesday 27 November 2013 04:31 PM, ivan.khoronzhuk wrote: >>> @@ -192,9 +193,15 @@ static __init void davinci_ntosd2_init(void) >>> davinci_cfg_reg(DM644X_ATAEN_DISABLE); >>> >>> /* only one device will be jumpered and detected */ >>> -if (HAS_NAND) >>> +if

Re: [PATCH 3.10 00/80] 3.10.21-stable review

On 11/26/2013 04:56 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 3.10.21 release. There are 80 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

[PATCH] mfd: wm5110: Give new AIF2 registers defaults and mark as readable

The registers associated with the new channels on AIF2 were accidentally missing defaults and not marked as readable this patch fixes this. Signed-off-by: Charles Keepax --- This patch depends on the patch: "ASoC: wm5110: Add extra AIF2 channels" Which is going through the ASoC tree at the

Re: [PATCH v3] crypto: more robust crypto_memneq

On 11/26/2013 10:44 PM, Cesar Eduardo Barros wrote: Em 26-11-2013 17:27, Daniel Borkmann escreveu: On 11/26/2013 01:00 AM, Cesar Eduardo Barros wrote: Compile-tested on x86_64. Actually with yet another version, I hoped that the "compile-tested"-only statement would eventually disappear, ohh

Re: [PATCH 4/5] blk-lib.c: generic_make_request() handles large bios now

> int blkdev_issue_discard(struct block_device *bdev, sector_t sector, > sector_t nr_sects, gfp_t gfp_mask, unsigned long flags) > { > - DECLARE_COMPLETION_ONSTACK(wait); > struct request_queue *q = bdev_get_queue(bdev); > int type = REQ_WRITE | REQ_DISCARD; > -

[PATCH v4 0/5] Update Davinci watchdog driver

These patches are intended to update Davinci watchdog to use WDT core and reuse driver for keystone arch, because Keystone uses the similar IP like Davinci. See Documentation: Davinci DM646x - http://www.ti.com/lit/ug/spruer5b/spruer5b.pdf Keystone - http://www.ti.com/lit/ug/sprugv5a/sprugv5a.pdf

[PATCH v4 4/5] watchdog: davinci: add "timeout-sec" property

Since Davinci WDT has been switched to use WDT core, it became able to support timeout-sec property, so add it to it's binding description. Acked-by: Santosh Shilimkar Reviewed-by: Guenter Roeck Signed-off-by: Ivan Khoronzhuk --- .../devicetree/bindings/watchdog/davinci-wdt.txt |4

hci_h4p from linux-n900 branch: fix with new bluetooth for 3.13-rc1

commit d18adf907651766c97eedae993f14c6e042914a6 Author: Pavel Date: Wed Nov 27 13:43:40 2013 +0100 Fix compilation of hci_h4p after bluetooth core changes. Only compile tested. Signed-off-by: Pavel Machek -- When you update to 3.13-rc1, you'll likely need this one. (And good news is

[PATCH v4 3/5] watchdog: davinci: add GET_TIMELEFT option support

Currently, the davinci watchdog can be read while counting, so we can add ability to report the remaining time before the system will reboot. Acked-by: Santosh Shilimkar Reviewed-by: Guenter Roeck Signed-off-by: Ivan Khoronzhuk --- drivers/watchdog/davinci_wdt.c | 26

Re: [PATCH v4 00/12] kexec kernel efi runtime support

On Tue, 26 Nov, at 01:57:45PM, Dave Young wrote: > Hi, > > Here is the V4 resend for supporting kexec kernel efi runtime. > Per pervious discussion I pass the 1st kernel efi runtime mapping > via setup_data to 2nd kernel. Besides of the runtime mapping > info I also pass the fw_vendor, runtime,

[PATCH v4 2/5] watchdog: davinci: use davinci_wdt_device structure to hold device data

Some SoCs, like Keystone 2, can support more than one WDT and each watchdog device has to use it's own base address, clock source, watchdog device, so add new davinci_wdt_device structure to hold device data. Acked-by: Santosh Shilimkar Reviewed-by: Guenter roeck Signed-off-by: Ivan Khoronzhuk

[PATCH v4 1/5] watchdog: davinci: change driver to use WDT core

To reduce code duplicate and increase code readability use WDT core code to handle WDT interface. Remove io_lock as the WDT core uses mutex to lock each wdt device. Remove wdt_state as the WDT core tracks state with its own variable. The watchdog_init_timeout() can read timeout value from

[PATCH v4 5/5] watchdog: davinci: reuse driver for keystone arch

The keystone arch uses the same IP watchdog, so add "ti,keystone-wdt" compatible and correct identity. The Keystone arch is using clocks in DT and source clock for watchdog has to be specified, so add this to binding. Acked-by: Santosh Shilimkar Reviewed-by: Guenter Roeck Signed-off-by: Ivan

Re: [GIT PULL] ima: bug fixes for Linus

On 11/27/2013 01:11 PM, Sebastian Ott wrote: Hello, On Mon, 25 Nov 2013, Roberto Sassu wrote: On 11/25/2013 07:46 PM, Roberto Sassu wrote: On 11/25/2013 04:40 PM, James Morris wrote: On Mon, 25 Nov 2013, Mimi Zohar wrote: Hi James, These are the "essential fixes for regressions". The

[PATCH] swiotlb: update format

Documentation/kernel-parameters.txt doesn't contain up-to-date documentation regarding swiotlb= parameter. Update it. Signed-off-by: Jiri Kosina --- Documentation/kernel-parameters.txt |6 +- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git

[PATCH v2 2/2] clk: add accuracy support for fixed clock

This patch adds support for accuracy retrieval on fixed clocks. It also adds a new dt property called 'clock-accuracy' to define the clock accuracy. This can be usefull for oscillator (RC, crystal, ...) definitions which are always given an accuracy characteristic. Signed-off-by: Boris BREZILLON

[PATCH v2 1/2] clk: add clk accuracy retrieval support

The clock accuracy is expressed in ppb (parts per billion) and represents the possible clock drift. Say you have a clock (e.g. an oscillator) which provides a fixed clock of 20MHz with an accuracy of +- 20Hz. This accuracy expressed in ppb is 20Hz/20MHz = 1000 ppb (or 1 ppm). Clock users may need

Re: Supporting 4 way connections in LKSCTP

On Wed, Nov 27, 2013 at 07:10:49AM +0800, Sun Paul wrote: > Hi Vlad > > Thank for your reply. If it is based on the destination IP to find the > best route, why the problem didn't happen on single-homing sample? > Because You only ever use one address from NODE A (12.1.1.1) > In the

[PATCH v2 0/2] clk: add clk accuracy support

Hello, This patch series adds support for clock accuracy retrieval in the common clk framework. Best Regards, Boris Changes since v1: - remove HAVE_CLK_GET_ACCURACY option and enable clk accuracy support only when using the CCF - export __clk_get_accuracy (might be used by clk-providers)

Re: [PATCH] firmware/dmi_scan: generalize for use by other archs

On 27 November 2013 13:22, Grant Likely wrote: > On Wed, Nov 27, 2013 at 12:12 PM, Grant Likely > wrote: >> On Mon, 25 Nov 2013 13:07:23 +0100, Ard Biesheuvel >> wrote: >>> Hello all, >>> >>> Resending this patch to a slightly wider audience. >>> >>> The point of this patch is reworking the

Re: [GIT PULL] ima: bug fixes for Linus

Hello, On Mon, 25 Nov 2013, Roberto Sassu wrote: > On 11/25/2013 07:46 PM, Roberto Sassu wrote: > > On 11/25/2013 04:40 PM, James Morris wrote: > > > On Mon, 25 Nov 2013, Mimi Zohar wrote: > > > > > > > Hi James, > > > > > > > > These are the "essential fixes for regressions". > > > > > > > >

Re: [PATCH] firmware/dmi_scan: generalize for use by other archs

On Wed, Nov 27, 2013 at 12:12 PM, Grant Likely wrote: > On Mon, 25 Nov 2013 13:07:23 +0100, Ard Biesheuvel > wrote: >> Hello all, >> >> Resending this patch to a slightly wider audience. >> >> The point of this patch is reworking the dmi_scan code slightly so it >> can be reused on ARM and

Re: [PATCH v5 2/7] arm64: introduce interfaces to hotpatch kernel and module code

Hi Jiang Liu, On Sun, Nov 03, 2013 at 03:55:21PM +, Jiang Liu wrote: > On 10/30/2013 08:12 AM, Will Deacon wrote: > > If I try and email you at your Huawei address, I get a bounce from the mail > > server. Is that expected? If so, it's not very helpful from a commit log > > perspective if you

Re: [PATCH] mfd: twl-core: Clean up module by removing twl603x pdata handling

On Thu, 21 Nov 2013, Ruslan Ruslichenko wrote: > Since currently nobody uses TWL603x platform data and all new Hmm... when you say nobody, how did you come to this conclusion? Without digging into it and probably not that relevant, it appears there is some references to it in platform data

Re: [PATCH] ARM: asm: Configure caches as per the defconfig

On Wed, Nov 27, 2013 at 05:24:04PM +0530, Amit Virdi wrote: > From: Amit VIRDI > > In the current implementation of the decompression code, the caches are > enabled > irrespective of their configuration in the deconfig. This makes setting the > ICACHE and DCACHE disable options from the

Re: tty/serial eating \n regression in 3.13-rc1

On 11/26/2013 04:53 PM, Jason Gunthorpe wrote: Hello Peter, I have been testing 3.13-rc1 and I noticed a change in behavior in the tty/serial layer. Specifically I have a login running on serial that presents the usual login:/password: prompt. 3.10.12 does this: login: admin password: prompt>

Re: [PATCH] firmware/dmi_scan: generalize for use by other archs

On Mon, 25 Nov 2013 13:07:23 +0100, Ard Biesheuvel wrote: > Hello all, > > Resending this patch to a slightly wider audience. > > The point of this patch is reworking the dmi_scan code slightly so it > can be reused on ARM and arm64. > There are no functional changes for x86 or IA-64, just one

Re: omap-cpufreq compilation breakage in 3.13-rc1

On Wed, Nov 27, 2013 at 12:54:07PM +0100, Pavel Machek wrote: > Commit d4019f0a92ab802f385cc9c8ad3ab7b5449712cb broke compilation for > omap-cpufreq.c . Given impresive list of ACKs and Tested-bys, I'd not > expect such problem. This fixes it. This has already been fixed in

Re: [PATCH 4/5] mfd: sec: Add PM ops and make it a wake up source

On Tue, 26 Nov 2013, Krzysztof Kozlowski wrote: > Add PM suspend/resume ops to the sec MFD core driver and make it a wake > up source. This allows proper waking from suspend to RAM and also fixes > broken interrupts after resuming: > [ 42.705703] sec_pmic 7-0066: Failed to read IRQ status: -5 >

Re: [PATCH] tools/perf/util: Document and clean up readn() a bit

* Adrian Hunter wrote: > On 26/11/13 19:53, Ingo Molnar wrote: > > > > * Arnaldo Carvalho de Melo wrote: > > > >> Em Fri, Nov 22, 2013 at 03:24:26PM +0100, Jiri Olsa escreveu: > >>> } > >>> + > >>> +ssize_t perf_data_file__write(struct perf_data_file *file, > >>> +

Re: [PATCH 02/17] tracing/probes: Fix basic print type functions

(2013/11/27 15:19), Namhyung Kim wrote: > > -DEFINE_BASIC_PRINT_TYPE_FUNC(u8, "%x", unsigned int) > -DEFINE_BASIC_PRINT_TYPE_FUNC(u16, "%x", unsigned int) > -DEFINE_BASIC_PRINT_TYPE_FUNC(u32, "%lx", unsigned long) > -DEFINE_BASIC_PRINT_TYPE_FUNC(u64, "%llx", unsigned long long) >

Re: [PATCH 0/3] Hook up powerclamp with PM QOS and cpuidle

On Tue, Nov 26, 2013 at 03:20:08PM -0800, Jacob Pan wrote: > This patchset is intended to address the behavior change and efficiency > loss introduced by using consolidated idle routine in powerclamp driver. > > Specifically, > [PATCH 3/8] idle, thermal, acpi: Remove home grown idle

Re: [PATCH v2 3/3] intel_mid: switch to use SFI GPIO API

On Tue, 2013-11-26 at 10:38 +0100, Linus Walleij wrote: > On Wed, Nov 20, 2013 at 3:31 PM, Andy Shevchenko > wrote: > > > Instead of custom implementation of the SFI GPIO API let's use one provided > > by > > gpiolib. > > > > Signed-off-by: Andy Shevchenko > > So is it possible to move this

[PATCH] ARM: asm: Configure caches as per the defconfig

From: Amit VIRDI In the current implementation of the decompression code, the caches are enabled irrespective of their configuration in the deconfig. This makes setting the ICACHE and DCACHE disable options from the menuconfig irrelevant. Change this implementation to enable caches only if

omap-cpufreq compilation breakage in 3.13-rc1

Commit d4019f0a92ab802f385cc9c8ad3ab7b5449712cb broke compilation for omap-cpufreq.c . Given impresive list of ACKs and Tested-bys, I'd not expect such problem. This fixes it. Signed-off-by: Pavel Machek diff --git a/drivers/cpufreq/omap-cpufreq.c b/drivers/cpufreq/omap-cpufreq.c index

Re: [PATCH] perf tools: Fix not finding kcore in buildid cache

* Adrian Hunter wrote: > On 27/11/13 13:32, Ingo Molnar wrote: > > > > * Adrian Hunter wrote: > > > >> On 26/11/13 18:15, Ingo Molnar wrote: > >>> > >>> * Adrian Hunter wrote: > >>> > The logic was not looking in the buildid cache for kcore > if the host kernel buildid did not

Re: [PATCH 3.11 54/66] mm: migration: do not lose soft dirty bit if page is in migration state

Hi Cyrill, On Wed, Nov 27, 2013 at 12:50 PM, Cyrill Gorcunov wrote: > "Soft dirty bit" feature introduced in 3.11 kernel and as far as I know > we've no plans to backport it on 3.10 series. ok thanks for the information and the quick reply. -- William -- To unsubscribe from this list: send

Re: [PATCH v2 00/10] Reuse davinci-nand driver for Keystone arch

On 11/27/2013 03:33 AM, Brian Norris wrote: Hi Ivan, On Thu, Nov 21, 2013 at 01:28:15PM +0200, Ivan Khoronzhuk wrote: This series contains fixes and updates of Davinci nand driver in order to reuse it for Keystone platform. The series is combination of two following series: - Davinci nand

Re: [PATCH 00/23] mtd: st_spi_fsm: Add new device

> There seem to be multiple efforts going on that are vaguely related. I'd > like to see more of the same people appearing on the CC list, to keep > better coordinated. > > On that topic, is the SPI dev list relevant, or would anybody working on > the intersection of SPI and MTD be on the MTD

Re: [PATCHSET 00/17] tracing/uprobes: Add support for more fetch methods (v7)

(2013/11/27 15:19), Namhyung Kim wrote: > - print 0x prefix for unsigned types Ah, yeah, this is good for human, but not good for sscanf :P glibc's sscanf doesn't support %#x ... Thank you, -- Masami HIRAMATSU IT Management Research Dept. Linux Technology Center Hitachi, Ltd., Yokohama

Re: [PATCH 3.11 54/66] mm: migration: do not lose soft dirty bit if page is in migration state

On Wed, Nov 27, 2013 at 12:38:10PM +0100, William Dauchy wrote: > Hi Greg, > > I was wondering if v3.10.x stable branch was also concerned by this > patch since I did not found it in this later branch. > Maybe too hard to backport? (I saw that it requires new functions like > pte_swp_soft_dirty

Re: netfilter: active obj WARN when cleaning up

On Wed, Nov 27, 2013 at 11:45:17AM +0100, Thomas Gleixner wrote: > On Wed, 27 Nov 2013, Pablo Neira Ayuso wrote: > > > On Tue, Nov 26, 2013 at 02:11:57PM -0500, Sasha Levin wrote: > > > Ping? I still see this warning. > > > > Did your test include patch 0c3c6c00c6? > > And how is that patch

Re: perf events: how to implement TLB misses as SW event ?

On Sun, Nov 24, 2013 at 07:10:58PM +0100, christophe leroy wrote: > Today in the perfevents subsystem it looks like DTLB/ITLB misses are > implemented as HW counter only. > On some processors, like PowerPC 8xx, there is no counter for that. However > DTLB/ITLB misses are handled as exceptions via

Re: [PATCH v2] efi-pstore: Make efi-pstore return a unique id

On Sat, 23 Nov, at 07:55:37PM, Madper Xie wrote: > > Pstore fs expects that backends provide a uniqued id which could avoid > pstore making entries as duplication or denominating entries the same > name. So I combine the timestamp, part and count into id. > > Signed-off-by: Madper Xie > --- >

Re: [PATCH v4 06/12] efi: export efi runtime memory mapping to sysfs

On Tue, Nov 26, 2013 at 01:57:51PM +0800, Dave Young wrote: > kexec kernel will need exactly same mapping for > efi runtime memory ranges. Thus here export the > runtime ranges mapping to sysfs, kexec-tools > will assemble them and pass to 2nd kernel via > setup_data. > > Introducing a new

<    1   2   3   4   5   6   7   8   9   10   >