Re: [PATCH V2] Staging: dgnc: replace EXTRA_CFLAGS

On Sun, Mar 01, 2015 at 06:19:57PM +0100, Matteo Semenzato wrote: > From: Matteo Semenzato > > This patch removes EXTRA_CFLAGS from the Makefile and defines DDG_PART > in dgnc_driver.h > > Signed-off-by: Matteo Semenzato > --- > drivers/staging/dgnc/Makefile | 2 -- >

[PATCH V2] Staging: dgnc: replace EXTRA_CFLAGS

From: Matteo Semenzato This patch removes EXTRA_CFLAGS from the Makefile and defines DDG_PART in dgnc_driver.h Signed-off-by: Matteo Semenzato --- drivers/staging/dgnc/Makefile | 2 -- drivers/staging/dgnc/dgnc_driver.h | 1 + 2 files changed, 1 insertion(+), 2 deletions(-) diff --git

[GIT PULL] x86 fixes

Linus, Please pull the latest x86-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus # HEAD: 5b2bdbc84556774afbe11bcfd24c2f6411cfa92b x86: Init per-cpu shadow copy of CR4 on 32-bit CPUs too A CR4-shadow 32-bit init fix, plus

[GIT PULL] timer fixes

Linus, Please pull the latest timers-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-for-linus # HEAD: e3eff6fe7d8a877d94f5dbb8fea46b4f8ca4ce5a Merge branch 'clockevents/4.0-rc1' of git://git.linaro.org/people/daniel.lezcano/linux

[GIT PULL] perf fixes

Linus, Please pull the latest perf-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-for-linus # HEAD: 021f5f12f2ab44874193c68fb19eea154493f83a Merge tag 'perf-urgent-for-mingo' of

[GIT PULL] locking fix

Linus, Please pull the latest locking-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-urgent-for-linus # HEAD: 9d3e2d02f54160725d97f4ab1e1e8de493fbf33a locking/rtmutex: Set state back to running on error An rtmutex deadlock path fixlet.

Re: [tip:perf/urgent] perf tools: Fix pthread_attr_setaffinity_np build error

* tip-bot for Adrian Hunter wrote: > --- a/tools/perf/config/feature-checks/test-pthread-attr-setaffinity-np.c > +++ b/tools/perf/config/feature-checks/test-pthread-attr-setaffinity-np.c > @@ -5,10 +5,11 @@ int main(void) > { > int ret = 0; > pthread_attr_t thread_attr; > +

[tip:perf/urgent] perf tools: Fix pthread_attr_setaffinity_np build error

Commit-ID: 95a09cfa3cdf94231ce511f1697754482b918d39 Gitweb: http://git.kernel.org/tip/95a09cfa3cdf94231ce511f1697754482b918d39 Author: Adrian Hunter AuthorDate: Tue, 24 Feb 2015 12:46:06 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 25 Feb 2015 12:18:03 -0300 perf tools:

[tip:perf/urgent] perf tools: Make sparc64 arch point to sparc

Commit-ID: 4861f87cd3d133f03e3b39b6650f4e12f1a9e421 Gitweb: http://git.kernel.org/tip/4861f87cd3d133f03e3b39b6650f4e12f1a9e421 Author: David Ahern AuthorDate: Wed, 18 Feb 2015 19:37:02 -0500 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 25 Feb 2015 17:39:17 -0300 perf tools:

[tip:perf/urgent] perf symbols: Define EM_AARCH64 for older OSes

Commit-ID: e370a3d57664cd5e39c0b95d157ebc841b568409 Gitweb: http://git.kernel.org/tip/e370a3d57664cd5e39c0b95d157ebc841b568409 Author: David Ahern AuthorDate: Wed, 18 Feb 2015 19:33:37 -0500 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 25 Feb 2015 17:39:17 -0300 perf symbols:

[tip:perf/urgent] perf tools: Fix probing for PERF_FLAG_FD_CLOEXEC flag

Commit-ID: 48536c9195ae8c2a00fd8f400bac72ab613feaab Gitweb: http://git.kernel.org/tip/48536c9195ae8c2a00fd8f400bac72ab613feaab Author: Adrian Hunter AuthorDate: Tue, 24 Feb 2015 13:20:59 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 25 Feb 2015 16:40:13 -0300 perf tools:

[tip:perf/urgent] perf top: Fix SIGBUS on sparc64

Commit-ID: a73b6c199a663d64a38198f547d5c5be42163193 Gitweb: http://git.kernel.org/tip/a73b6c199a663d64a38198f547d5c5be42163193 Author: David Ahern AuthorDate: Wed, 18 Feb 2015 19:03:18 -0500 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 25 Feb 2015 17:37:44 -0300 perf top: Fix

[tip:perf/urgent] perf tools: Define _GNU_SOURCE on pthread_attr_setaffinity_np feature check

Commit-ID: 8eb733829cd17b9b66971f08110df7224d391d65 Gitweb: http://git.kernel.org/tip/8eb733829cd17b9b66971f08110df7224d391d65 Author: Josh Boyer AuthorDate: Wed, 11 Feb 2015 11:24:05 -0500 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 25 Feb 2015 12:17:38 -0300 perf tools:

[tip:perf/urgent] perf bench: Fix order of arguments to memcpy_alloc_mem

Commit-ID: e17fdaeaec066c725f73cd3cda1feae52b2646f5 Gitweb: http://git.kernel.org/tip/e17fdaeaec066c725f73cd3cda1feae52b2646f5 Author: Bruce Merry AuthorDate: Thu, 15 Jan 2015 11:20:22 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Sun, 22 Feb 2015 23:10:56 -0300 perf bench:

Re: [alsa-devel] [PATCH v2 0/3] Switch to ioremap_wc in the SRAM allocator code

On Sun, Mar 01, 2015 at 10:00:37PM +0530, Abhilash Kesavan wrote: > Hi Greg, > > On Fri, Feb 6, 2015 at 9:14 PM, Catalin Marinas > wrote: > > On Fri, Feb 06, 2015 at 01:45:25PM +, Abhilash Kesavan wrote: > >> Fix alignment faults seen during play-back of files with specific > >> sampling

Re: [PATCH] Staging: dgnc: replace EXTRA_CFLAGS

On Sun, Mar 01, 2015 at 09:41:26AM +0100, Matteo Semenzato wrote: > From: Matteo Semenzato > > This patch fixes the following warning: > Use of EXTRA_CFLAGS is deprecated, please use `ccflags-y instead. > > Signed-off-by: Matteo Semenzato > --- > drivers/staging/dgnc/Makefile | 2 +- > 1 file

Re: [PATCH] Staging: dgnc: replace printk

On Sun, Mar 01, 2015 at 09:31:41AM +0100, Matteo Semenzato wrote: > From: Matteo Semenzato > > This patch fixes the following warning: > Prefer [subsystem eg: netdev]_err([subsystem]dev, ... then dev_err(dev, > ... then pr_err(... to printk(KERN_ERR ... > > Signed-off-by: Matteo Semenzato >

Re: [alsa-devel] [PATCH v2 0/3] Switch to ioremap_wc in the SRAM allocator code

Hi Greg, On Fri, Feb 6, 2015 at 9:14 PM, Catalin Marinas wrote: > On Fri, Feb 06, 2015 at 01:45:25PM +, Abhilash Kesavan wrote: >> Fix alignment faults seen during play-back of files with specific >> sampling rates such as 44.1K. This is based on the discussion here: >>

[PATCH RESEND] ARM: EXYNOS: Remove ARCH_HAS_BANDGAP selection

Now that the samsung thermal driver dependency on ARCH_HAS_BANDGAP has been removed, fix the arch code selection too. Signed-off-by: Abhilash Kesavan Reviewed-by: Bartlomiej Zolnierkiewicz Acked-by: Lukasz Majewski --- arch/arm/mach-exynos/Kconfig | 1 - 1 file changed, 1 deletion(-) diff

Re: [PATCH v8 0/3] Add of-graph helpers to loop over endpoints and find ports by id

Hi Philipp and all, This series has been around for a long time, it seems to be time to get it merged. What's the plan ? If we wait for the v4.1 merge window there's a chance we'll get more conflicts, especially on patch 1/3. Could it be merged in v4.0-rc to avoid that ? On Monday 23

[PATCH] ipc/sem.c: Update/correct memory barriers

3rd version of the patch: sem_lock() did not properly pair memory barriers: !spin_is_locked() and spin_unlock_wait() are both only control barriers. The code needs an acquire barrier, otherwise the cpu might perform read operations before the lock test. The patch: - defines new barriers that

[PATCH v3 1/2] dts: vt8500: Add SDHC node to DTS file for WM8650

Since WM8650 has the same 'WMT' SDHC controller as WM8505, and the driver is already in the kernel, this node enables the controller support for WM8650 Signed-off-by: Roman Volkov Reviewed-by: Alexey Charkov --- arch/arm/boot/dts/wm8650.dtsi | 9 + 1 file changed, 9 insertions(+) diff

[PATCH v3 0/2] WM8505/WM8650 DT fixes for SD card controller

This patch set enables SD controller support for WM8650 and fixes minor errors in WM8505 Device Tree file. Changes in v3: 1. Add minor fixes for WM8505 SDHC node Tested on both WM8505 and WM8650. Roman Volkov (2): dts: vt8500: Add SDHC node to DTS file for WM8650 dts: vt8500: Fix errors in

[PATCH v3 2/2] dts: vt8500: Fix errors in SDHC node for WM8505

According to datasheet, the registers space of SDHC controller is 1Kb, not '0x1000', the correct value should be '0x400'. Bracket interrupt numbers individually per recommendations. Signed-off-by: Roman Volkov --- arch/arm/boot/dts/wm8505.dtsi | 4 ++-- 1 file changed, 2 insertions(+), 2

Re: [PATCH 3/3] x86: do not save callee-preserved registers around lockdep_sys_exit_thunk

On Fri, Feb 27, 2015 at 4:29 PM, Denys Vlasenko wrote: > Internally, lockdep_sys_exit_thunk saves callee-clobbered registers, > and calls a C function, lockdep_sys_exix. Thus, callee-preserved > won't be mangled, there is no need to save them. > > Patch was run-tested. Peterz, I think this was

Re: [PATCH] perf tools: Fix pthread_attr_setaffinity_np() feature detection on Ubuntu systems

* Jiri Olsa wrote: > agreed, sry about that.. I'll try to clean it up while moving > features detection into tools/ as you suggested before That would be nice! > > --- a/tools/perf/config/feature-checks/test-pthread-attr-setaffinity-np.c > > +++

[PATCH v2 -next 01/13] serial: earlycon: Refactor parse_options into serial core

Prepare to support console-defined matching; refactor the command line parameter string processing from parse_options() into a new core function, uart_parse_earlycon(), which decodes command line parameters of the form: earlycon=,io|mmio|mmio32,, console=,io|mmio|mmio32,, earlycon=,0x,

[PATCH v2 -next 08/13] serial: 8250_early: Fix setup() error code

If parsing failed to decode a valid uart addr, return -ENODEV instead of success. Although setup_earlycon() will detect the failure anyway (because the write() method has not been set), that behavior is not obvious and should not be relied on. Signed-off-by: Peter Hurley ---

[PATCH v2 -next 02/13] console: Preserve index after console setup()

Before register_console() calls the setup() method of the matched console, the registering console index is already equal to the index from the console command line; ie. newcon->index == c->index. This change is also required to support extensible console matching; (the command line index may

[PATCH v2 -next 07/13] serial: 8250_early: Assume uart already initialized if no baud option

The option string is not supplied if the earlycon is started via devicetree and OF_EARLYCON_DECLARE(). The option string is also not required if started via kernel command line parameters of the form: earlycon=uart,mmio, console=uart,mmio, If earlycon_device->baud is 0, then an option string

[PATCH v2 -next 04/13] serial: core: Fix kernel doc for uart_console_write()

'/**' is required to start a kernel-doc comment block. Signed-off-by: Peter Hurley --- drivers/tty/serial/serial_core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c index 3f823c26..373cfde 100644 ---

[PATCH v2 -next 09/13] serial: earlycon: Ignore parse_options() error code

Because setup_earlycon() continues to attempt console registration if an error occurred parsing the option string, the actual value of the error code from parse_options() is ignored. Signed-off-by: Peter Hurley --- drivers/tty/serial/earlycon.c | 3 +-- 1 file changed, 1 insertion(+), 2

[PATCH v2 -next 13/13] serial: 8250_early: Remove setup_early_serial8250_console()

setup_earlycon() will now match and register the desired earlycon from the param string (as if 'earlycon=...' had been set on the command line). Use setup_earlycon() from existing arch call sites which start an earlycon directly. Signed-off-by: Peter Hurley --- arch/mips/mti-malta/malta-init.c

Re: [PATCH] ipc/sem.c: Update/correct memory barriers.

Hi Oleg, On 03/01/2015 02:22 PM, Oleg Nesterov wrote: On 02/28, Peter Zijlstra wrote: On Sat, Feb 28, 2015 at 09:36:15PM +0100, Manfred Spraul wrote: +/* + * Place this after a control barrier (such as e.g. a spin_unlock_wait()) + * to ensure that reads cannot be moved ahead of the

[PATCH v2 -next 10/13] serial: earlycon: Allow earlycon params with name only

Allow earlycon param strings of the form earlycon= Signed-off-by: Peter Hurley --- drivers/tty/serial/earlycon.c | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/drivers/tty/serial/earlycon.c b/drivers/tty/serial/earlycon.c index da5e8c8..025ea01 100644 ---

[PATCH v2 -next 11/13] serial: earlycon: Refactor earlycon registration

Separate earlycon matching from registration; add register_earlycon which initializes and registers the matched earlycon. Signed-off-by: Peter Hurley --- drivers/tty/serial/earlycon.c | 42 +- 1 file changed, 25 insertions(+), 17 deletions(-) diff --git

[PATCH v2 -next 12/13] serial: earlycon: Enable earlycon without command line param

Earlycon matching can only be triggered if 'earlycon=...' has been specified on the kernel command line. To workaround this limitation requires tight coupling between arches and specific serial drivers in order to start an earlycon. Devicetree avoids this limitation with a link table that contains

[PATCH v2 -next 06/13] serial: earlycon: Move ->uartclk initialize

Initializing the ->uartclk field is not related to option parsing; relocate from parse_options() to setup_earlycon() (which mirrors the behavior of of_setup_earlycon()). Signed-off-by: Peter Hurley --- drivers/tty/serial/earlycon.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff

[PATCH v2 -next 03/13] console: Add extensible console matching

Add match() method to struct console which allows the console to perform console command line matching instead of (or in addition to) default console matching (ie., by fixed name and index). The match() method returns 0 to indicate a successful match; normal console matching occurs if no match()

[PATCH v2 -next 05/13] serial: 8250_early: Remove early_device variable

early_device was only required for serial8250_find_port_for_earlycon(), which was replaced by extensible console matching. Fixup early_serial8250_write() to get the earlycon_device * from console->data (which is initialized by {of_}setup_earlycon()). Signed-off-by: Peter Hurley ---

[PATCH v2 -next 00/13] Extensible console matching & direct earlycon

Changes from v1: * rebased on and requires "console: Fix console name size mismatch" Hi Greg & Andrew, This patch series implements: 1. console-definable (aka extensible) matching 2. generic earlycon-to-console handoff via extensible matching 3. arch/prom support for direct earlycon

[PATCH v2] usb/isp1760: set IRQ flags properly

The IRQF_DISABLED is a NOOP and scheduled to be removed. According to commit e58aa3d2d0cc ("genirq: Run irq handlers with interrupts disabled") running IRQ handlers with interrupts enabled can cause stack overflows when the interrupt line of the issuing device is still active. This patch removes

Re: [PATCH 1/8] x86, kaslr: get kaslr_enabled back correctly

(Cc:-ed Jiri and Kees as well.) * Borislav Petkov wrote: > On Sat, Feb 28, 2015 at 06:40:39PM -0800, Yinghai Lu wrote: > > > > oh, no. the offending commit already got into linus tree. > > We're working on it, follow this thread: > >

[PATCH resend] cpumask: don't perform while loop in cpumask_next_and()

cpumask_next_and() is looking for cpumask_next() in src1 in a loop and tests if found cpu is also present in src2. remove that loop, perform cpumask_and() of src1 and src2 first and use that new mask to find cpumask_next(). Apart from removing while loop, ./bloat-o-meter on x86_64 shows

[PATCH] console: Fix console name size mismatch

commit 6ae9200f2cab7 ("enlarge console.name") increased the storage for the console name to 16 bytes, but not the corresponding struct console_cmdline::name storage. Console names longer than 8 bytes cause read beyond end-of-string and failure to match console; I'm not sure if there are other

Re: [PATCH] clkdev: clk_add_alias don't put origin clock

On Sun, Mar 01, 2015 at 04:43:35PM +0900, Yoshinori Sato wrote: > Refer to 'r' later. > So don't put in clk_add_alias. > > Signed-off-by: Yoshinori Sato This isn't how I want to solve this. I'd much rather we converted clkdev to use struct clk_hw internally instead. This is something I'm

[PATCH] phy: berlin-usb: Use PTR_ERR_OR_ZERO

PTR_ERR_OR_ZERO simplifies the code. Signed-off-by: Axel Lin --- drivers/phy/phy-berlin-usb.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/phy/phy-berlin-usb.c b/drivers/phy/phy-berlin-usb.c index c8a8d53..9f7cc7e 100644 --- a/drivers/phy/phy-berlin-usb.c +++

[PATCH] phy: twl4030-usb: Remove redundant assignment for twl->linkstat

It's pointless to set twl->linkstat twice. Signed-off-by: Axel Lin --- drivers/phy/phy-twl4030-usb.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/phy/phy-twl4030-usb.c b/drivers/phy/phy-twl4030-usb.c index 8e87f54..bc42d6a 100644 --- a/drivers/phy/phy-twl4030-usb.c +++

[PATCH] i2c: tegra: match return type of wait_for_completion_timeout

return type of wait_for_completion_timeout is unsigned long not int. As ret was only used for wait_for_completion_timeout here it is renamed to time_left the type changed to unsigned long and references fixed up. Signed-off-by: Nicholas Mc Guire --- This patch was only compile tested with

Re: [patch] perf_event_open.2: 3.19 PERF_SAMPLE_REGS_INTR support

Hi, On Sat, Feb 28, 2015 at 5:26 PM, Jiri Olsa wrote: > On Thu, Feb 12, 2015 at 12:33:09AM -0500, Vince Weaver wrote: >> >> This manpage patch relates to the addition of PERF_SAMPLE_REGS_INTR >> support added in the following commit: > > hi, > sorry for late response.. > >> >>

[PATCH] Update version number references in README

As we have moved to 4.x, it should be reflected in README. Signed-off-by: Yaowei Bai --- README | 34 +- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/README b/README index a24ec89..67fc7a8 100644 --- a/README +++ b/README @@ -1,6 +1,6 @@ -

Re: [RFC][PATCH 6/9] seqlock: Better document raw_write_seqcount_latch()

- Original Message - > From: "Peter Zijlstra" > To: mi...@kernel.org, ru...@rustcorp.com.au, "mathieu desnoyers" > , o...@redhat.com, > paul...@linux.vnet.ibm.com > Cc: linux-kernel@vger.kernel.org, a...@firstfloor.org, rost...@goodmis.org, > t...@linutronix.de, pet...@infradead.org, >

Re: [RFC][PATCH 5/9] rbtree: Make lockless searches non-fatal

- Original Message - > From: "Peter Zijlstra" > To: mi...@kernel.org, ru...@rustcorp.com.au, "mathieu desnoyers" > , o...@redhat.com, > paul...@linux.vnet.ibm.com > Cc: linux-kernel@vger.kernel.org, a...@firstfloor.org, rost...@goodmis.org, > t...@linutronix.de, pet...@infradead.org, >

Re: [PATCH] ipc/sem.c: Update/correct memory barriers.

On 02/28, Paul E. McKenney wrote: > > The idea is that this would become a no-op on x86, s390, sparc , an isb > instruction on ARM, an isync instruction on Power, and I cannot remember > what on Itanium? The other idea being to provide read-to-read control > ordering in addition to the current

[PATCH] i2c: wmt: use msecs_to_jiffies for time conversions

This is only an API consolidation and should make things more readable it replaces var * HZ / 1000 by msecs_to_jiffies(var). Signed-off-by: Nicholas Mc Guire --- Converting milliseconds to jiffies by "val * HZ / 1000" is technically not wrong but msecs_to_jiffies(val) is the cleaner solution

Re: [PATCH] ipc/sem.c: Update/correct memory barriers.

On 02/28, Peter Zijlstra wrote: > > On Sat, Feb 28, 2015 at 09:36:15PM +0100, Manfred Spraul wrote: > > +/* > > + * Place this after a control barrier (such as e.g. a spin_unlock_wait()) > > + * to ensure that reads cannot be moved ahead of the control_barrier. > > + * Writes do not need a

Re: [PATCH 05/11] perf data: Add tracepoint events fields CTF conversion support

On Wed, Feb 25, 2015 at 04:23:44PM -0300, Arnaldo Carvalho de Melo wrote: > Em Fri, Feb 20, 2015 at 11:17:02PM +0100, Jiri Olsa escreveu: > > From: Sebastian Andrzej Siewior > > Adding support to convert tracepoint event fields into CTF > > event fields. > > > We parse each tracepoint event for

Re: [PATCH] Avoid null-pointer access in w1/slaves/w1_therm

Hi David, thanks for your feedback on my first patch, I wasn't aware of checkpatch.pl. Initially, I had just if-ed the usage of family-data, which did not look that nice. I was referring to this proof-of-concept workaround in my initial bug report. The patch I've submitted is different from my

Re: [PATCH] clk: samsung: Add CLKOUT driver support for Exynos3250 SoC.

2015-02-25 19:13 GMT+09:00 Inha Song : > Hi, Tomasz, > > Thanks for you comment :) > > On Wed, 25 Feb 2015 09:54:02 +0900 > Tomasz Figa wrote: > >> Hi Inha, >> >> Thanks for the patch. Please see my comments inline. >> >> 2015-02-24 18:22 GMT+09:00 Inha Song : >> > This patch add CLKOUT driver

[PATCH v8 03/18] clk: tegra: Add closed loop support for the DFLL

From: Tuomas Tynkkynen With closed loop support, the clock rate of the DFLL can be adjusted. The oscillator itself in the DFLL is a free-running oscillator whose rate is directly determined the supply voltage. However, the DFLL module contains logic to compare the DFLL output rate to a fixed

[PATCH v8 06/18] clk: tegra: Add DFLL DVCO reset control for Tegra124

From: Paul Walmsley The DVCO present in the DFLL IP block has a separate reset line, exposed via the CAR IP block. This reset line is asserted upon SoC reset. Unless something (such as the DFLL driver) deasserts this line, the DVCO will not oscillate, although reads and writes to the DFLL IP

[PATCH v8 08/18] clk: tegra: Save/restore CCLKG_BURST_POLICY on suspend

From: Tuomas Tynkkynen Save and restore this register since the LP1 restore assembly routines fiddle with it. Otherwise the CPU would keep running on PLLX after resume from suspend even when DFLL was the original clocksource. Signed-off-by: Tuomas Tynkkynen Signed-off-by: Mikko Perttunen

[PATCH v8 04/18] clk: tegra: Add functions for parsing CVB tables

From: Tuomas Tynkkynen Tegra CVB tables encode the relationship between operating voltage and optimal frequency as a function of the so-called speedo value. The speedo value is written to the on-chip fuses at the factory, which allows the voltage-frequency operating points to be calculated on an

[PATCH v8 14/18] cpufreq: tegra: Rename tegra-cpufreq to tegra20-cpufreq

From: Tuomas Tynkkynen The Tegra124 will use a different driver for frequency scaling, so rename the old driver (which handles only Tegra20) appropriately. Signed-off-by: Tuomas Tynkkynen Signed-off-by: Mikko Perttunen --- drivers/cpufreq/Kconfig.arm| 6 +++---

[PATCH v8 12/18] ARM: tegra: Enable the DFLL on the Jetson TK1

From: Tuomas Tynkkynen Add the board-specific properties of the DFLL for the Jetson TK1 board. On this board, the DFLL will take control of the sd0 regulator on the on-board AS3722 PMIC. Signed-off-by: Tuomas Tynkkynen Signed-off-by: Mikko Perttunen --- v8: - Changed dfll@ -> clock@

[PATCH v8 18/18] ARM: tegra: enable Tegra124 cpufreq driver by default

From: Tuomas Tynkkynen The Tegra124 cpufreq driver depends on CONFIG_CPUFREQ_DT, so enable it to get the Tegra driver to build by default. Signed-off-by: Tuomas Tynkkynen Signed-off-by: Mikko Perttunen --- arch/arm/configs/tegra_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v8 16/18] ARM: tegra: Add entries for cpufreq on Tegra124

From: Tuomas Tynkkynen The Tegra124 cpufreq driver relies on certain clocks being present in the /cpus/cpu@0 node. Signed-off-by: Tuomas Tynkkynen Signed-off-by: Mikko Perttunen --- arch/arm/boot/dts/tegra124.dtsi | 9 + 1 file changed, 9 insertions(+) diff --git

[PATCH v8 15/18] cpufreq: Add cpufreq driver for Tegra124

From: Tuomas Tynkkynen Add a new cpufreq driver for Tegra124. Instead of using the PLLX as the CPU clocksource, switch immediately to the DFLL. It allows the use of higher clock rates, and will automatically scale the CPU voltage as well. Besides the CPU clocksource switch, we let the cpufreq-dt

[PATCH v8 09/18] clk: tegra: Add the DFLL as a possible parent of the cclk_g clock

From: Tuomas Tynkkynen The DFLL clocksource was missing from the list of possible parents for the fast CPU cluster. Add it to the list. Signed-off-by: Tuomas Tynkkynen Signed-off-by: Mikko Perttunen --- drivers/clk/tegra/clk-tegra-super-gen4.c | 4 +++- 1 file changed, 3 insertions(+), 1

[PATCH] spi - fix a typo in comment.

alway -> always Signed-off-by: Marcin Bis --- include/linux/spi/spi.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h index ed9489d..856d34d 100644 --- a/include/linux/spi/spi.h +++ b/include/linux/spi/spi.h @@ -649,7 +649,7

[PATCH v8 11/18] ARM: tegra: Add the DFLL to Tegra124 device tree

From: Tuomas Tynkkynen The DFLL clocksource is a separate IP block from the usual clock-and-reset controller, so it gets its own device tree node. Signed-off-by: Tuomas Tynkkynen Signed-off-by: Mikko Perttunen --- v8: - Changed dfll@ -> clock@ - Added dvco reset control

[PATCH v8 02/18] clk: tegra: Add library for the DFLL clock source (open-loop mode)

From: Tuomas Tynkkynen Add shared code to support the Tegra DFLL clocksource in open-loop mode. This root clocksource is present on the Tegra124 SoCs. The DFLL is the intended primary clock source for the fast CPU cluster. This code is very closely based on a patch by Paul Walmsley from

[PATCH v8 17/18] ARM: tegra: Add CPU regulator to the Jetson TK1 device tree

Specify the CPU voltage regulator for the cpufreq driver. Signed-off-by: Tuomas Tynkkynen Signed-off-by: Mikko Perttunen --- arch/arm/boot/dts/tegra124-jetson-tk1.dts | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/tegra124-jetson-tk1.dts

[PATCH v8 05/18] clk: tegra: Introduce ability for SoC-specific reset control callbacks

This patch allows SoC-specific CAR initialization routines to register their own reset_assert and reset_deassert callbacks with the common Tegra CAR code. If defined, the common code will call these callbacks when a reset control with number >= 0x4000 is attempted to be asserted or deasserted

[PATCH v8 10/18] clk: tegra: Initialize PLL_X before CCLK_G to ensure it has a parent

This patch moves the initialization of PLL_X to be slightly before that of CCLK_G. This ensures that at boot, CCLK_G will immediately have a parent and the common clock framework can determine its clock rate correctly. Without this patch, calling clk_put on CCLK_G could cause the CCF to set its

[PATCH v8 00/18] Tegra124 CL-DVFS / DFLL clocksource + cpufreq

Hi, this is v8 of the Tegra124 cpufreq series. Aside rebasing on latest -next, the following changes have been done: clk: tegra: Add binding for the Tegra124 DFLL clocksource - Changed dfll@ -> clock@ - Changed compatibility string to "nvidia,tegra124-dfll" - Clarified how the vdd-cpu-supply

[PATCH v8 13/18] cpufreq: tegra124: Add device tree bindings

From: Tuomas Tynkkynen The cpufreq driver for Tegra124 will be a different one than the old Tegra20 cpufreq driver (tegra-cpufreq), which does not use the device tree. Signed-off-by: Tuomas Tynkkynen Signed-off-by: Mikko Perttunen Cc: devicet...@vger.kernel.org ---

[PATCH v8 07/18] clk: tegra: Add Tegra124 DFLL clocksource platform driver

From: Tuomas Tynkkynen Add basic platform driver support for the fast CPU cluster DFLL clocksource found on Tegra124 SoCs. This small driver selects the appropriate Tegra124-specific characterization data and integration code. It relies on the DFLL common code to do most of the work.

[PATCH v8 01/18] clk: tegra: Add binding for the Tegra124 DFLL clocksource

From: Tuomas Tynkkynen The DFLL is the main clocksource for the fast CPU cluster on Tegra124 and also provides automatic CPU rail voltage scaling as well. The DFLL is a separate IP block from the usual Tegra124 clock-and-reset controller, so it gets its own node in the device tree.

Re: [RFC/PATCH] pinctrl: sh-pfc: Accept standard function, pins and groups properties

Hi Linus, I'd like to move forward with this patch, could you please comment on my reply ? On Wednesday 04 February 2015 11:53:34 Laurent Pinchart wrote: > On Wednesday 04 February 2015 09:40:48 Linus Walleij wrote: > > On Tue, Jan 27, 2015 at 9:31 PM, Laurent Pinchart wrote: > >> The

Re: preempt in kprobe

Hi, (2015/03/01 20:27), zhaoxiaoqiang007 wrote: > > Hi, masami: >I have read your post at https://lkml.org/lkml/2011/7/1/185 which remove > the > preempt disable code in kprobe. Right, but it is only for x86 since the kprobe int3 handler runs in irq-disabled context, which completely

[PATCH 2/2] acpi/video: Propagate the error code for acpi_video_register

Report the actual error code from acpi_bus_register_driver(), it may help future debugging (typically ENODEV as previously reported, but the unusual cases are where it may help most). Signed-off-by: Chris Wilson Cc: Daniel Vetter Cc: Zhang Rui Cc: "Rafael J. Wysocki" Cc: Len Brown Cc:

[PATCH 1/2] acpi/video: Load the module even if ACPI is disabled

i915.ko depends upon the acpi/video.ko module and so refuses to load if ACPI is disabled at runtime if for example the BIOS is broken beyond repair. acpi/video provides an optional service for i915.ko and so we should just allow the modules to load, but do no nothing in order to let the machines

Re: [Intel-gfx] [Regression] BUG: unable to handle kernel NULL pointer dereference

On Sun, Mar 01, 2015 at 12:30:01PM +0300, Andrey Skvortsov wrote: > On 01 Mar, Chris Wilson wrote: > > On Sun, Mar 01, 2015 at 12:57:01AM +0300, Andrey Skvortsov wrote: > > > On 28 Feb, Chris Wilson wrote: > > > > On Sat, Feb 28, 2015 at 03:20:37PM +0300, Andrey Skvortsov wrote: > > > > >

[PATCH v2] rtc: add Abracon ABx80x driver

Add support for the i2c RTC from Abracon. Signed-off-by: Alexandre Belloni --- Changes in v2: - corrected style according to checkpatch --strict - renamed functions to abx80x_* - reordered makefile and kconfig additions drivers/rtc/Kconfig | 9 +++ drivers/rtc/Makefile | 1 +

Re: stand-alone kvmtool

On 2/26/15 1:02 PM, Alex Bennée wrote: If you can have it all it would be nice to preserve buildability all through your history for bisecting (and the moon on a stick please ;-) Is the dependency on the kernel sources something that has been stable over the projects history or something that's

Re: linux firewire implementation & DMA attack

On Feb 21 Pali Rohár wrote: > I would like to know if current firewire implementation in Linux > kernel v3.19 still have security problems like DMA attack. If yes > are there any prevention for it (maybe with intel_iommu)? Remote DMA via the OHCI 1394 physical response unit is still enabled by

[PATCH] arm64: mm: unexport set_memory_ro and set_memory_rw

This effectively unexports set_memory_ro and set_memory_rw functions from commit 11d91a770f1f ("arm64: Add CONFIG_DEBUG_SET_MODULE_RONX support"). No module user of those is in mainline kernel and we explicitly do not want modules to use these functions, as they i.e. RO-protect eBPF (interpreted

Re: [PATCH 0/4] hw_random: bcm63xx-rng: misc cleanups and reorg

On Mon, Feb 16, 2015 at 06:09:12PM -0800, Florian Fainelli wrote: > Hi, > > This patchset prepares the driver to be built on non-MIPS bcm63xx > architectures > such as the ARM bcm63xx variants, thanks! > > Although patch 3 touches a MIPS header file, there should be little to no > conflicts

Re: [PATCH net-next 09/10] arm64: unexport set_memory_ro and set_memory_rw

Hi Will, On 02/27/2015 09:05 PM, Daniel Borkmann wrote: On 02/27/2015 08:54 PM, Will Deacon wrote: ... Looks good to me. Can this be applied independently, or does it need to remain part of your series? Ideally, it should be seen as part of this series, but I have no problem if this one goes

Re: [PATCH 1/8] x86, kaslr: get kaslr_enabled back correctly

On Sat, Feb 28, 2015 at 06:40:39PM -0800, Yinghai Lu wrote: > oh, no. the offending commit already got into linus tree. We're working on it, follow this thread: http://lkml.kernel.org/r/1424929021.10337.24.ca...@intel.com -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you

[PATCH] mtd: nand: MTD_NAND_HISI504 should depend on HAS_DMA

If NO_DMA=y: drivers/built-in.o: In function `hisi_nfc_probe': hisi504_nand.c:(.text+0x23e646): undefined reference to `dmam_alloc_coherent' Signed-off-by: Geert Uytterhoeven --- drivers/mtd/nand/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/mtd/nand/Kconfig

[PATCH v2 2/2] ARM: dts: add rk3288 PopMetal board

PopMetal is a rockchip rk3288 based board made by ChipSpark, which has many interface such as VGA,HDMI,usb,ir,sdcad and lots of sensors such as gyroscope(L3G4200D),accelerometer(mma8452), compass(AK8963C). This patch add a basic support for this board, which make the board boot into a initramfs

[PATCH v2 1/2] dt-bindings: add root compatible property for PopMetal board

PopMetal board is a rk3288 based board made by ChipSpark, this add root compatible property for it Signed-off-by: Andy Yan --- Changes in v2: - change "PopMetal PopMetal-RK3288 board" to "ChipSPARK PopMetal-RK3288 board" Documentation/devicetree/bindings/arm/rockchip.txt | 4 1 file

Re: [Intel-gfx] [Regression] BUG: unable to handle kernel NULL pointer dereference

On 01 Mar, Chris Wilson wrote: > On Sun, Mar 01, 2015 at 12:57:01AM +0300, Andrey Skvortsov wrote: > > On 28 Feb, Chris Wilson wrote: > > > On Sat, Feb 28, 2015 at 03:20:37PM +0300, Andrey Skvortsov wrote: > > > > Unfortunately this is not the last bug, that breaks i915/drm working > > > > on my

[PATCH v2 0/2] add dts for PopMetal board

PopMetal is a rockchip rk3288 based board made by ChipSpark, which has many interface such as VGA,HDMI,usb,ir,sdcad and lots of sensors such as gyroscope(L3G4200D),accelerometer(mma8452),compass(AK8963C). http://wiki.chipspark.com/en/index.php?title=PopMetal This patch add basic support for it,

[tip:locking/urgent] locking/rtmutex: Set state back to running on error

Commit-ID: 9d3e2d02f54160725d97f4ab1e1e8de493fbf33a Gitweb: http://git.kernel.org/tip/9d3e2d02f54160725d97f4ab1e1e8de493fbf33a Author: Sebastian Andrzej Siewior AuthorDate: Fri, 27 Feb 2015 17:57:09 +0100 Committer: Ingo Molnar CommitDate: Sun, 1 Mar 2015 09:45:06 +0100

[PATCHv2 3/7] zram: factor out device reset from reset_store()

Device reset currently consists of two steps: a) holding ->bd_mutex we ensure that there are no device users (bdev->bd_openers) b) and internal part (executed under bdev->bd_mutex and partially under zram->init_lock) that resets the device - frees allocated memory and returns the device back to

[PATCHv2 5/7] zram: add dynamic device add/remove functionality

Introduce zram-control sysfs class, which has two sysfs attrs: - zram_add -- add a new specific (device_id) zram device - zram_remove -- remove a specific (device_id) zram device Usage example: # add a new specific zram device echo 4 > /sys/class/zram-control/zram_add

[PATCHv2 7/7] zram: report every added and removed device

With dynamic device creation/removal printing num_devices in zram_init() doesn't make a lot of sense, as well as printing the number of destroyed devices in destroy_devices(). Print per-device action (added/removed) in zram_add() and zram_remove() instead. Example: [ 3645.259652] zram: Added

<    1   2   3   4   5   6   7   >