[PATCH v4 0/3] meson-gx: Add mali-450 support

Since the merge of the Mali dt bindings at [1], add support for Mali clocks and DT node. The Mali is clocked by two identical clock paths behind a glitch free mux to safely change frequency while running. So these clocks must be added to the meson-gxbb clock controller. Changes since v3 at [7] :

[PATCH v2 0/5] clk: meson: Fix GXBB and GXL/GXM GP0 PLL

This patchset fixes support for the Amlogic GXBB then GXL/GXM embedded GP0 PLL. The current support is done via a very generic interface where only the N/M/OD parameters are changed in the control registers. But unlike the Fixed PLL, this PLL is not initialized by the bootloader or firmware, and

[PATCH v2 3/5] clk: meson-gxbb: Add GXL/GXM GP0 Variant

The clock tree in the Amlogic GXBB and GXL/GXM SoCs is shared, but the GXL/GXM SoCs embeds a different GP0 PLL, and needs different parameters with a vendor provided reduced rate table. This patch adds the GXL GP0 variant, and adds a GXL DT compatible in order to use the GXL GP0 PLL instead of the

Re: [PATCH v2 4/6] arm64: dts: rockchip: add core dtsi file for RK3328 SoCs

On 03/21/2017 04:55 PM, Heiko Stübner wrote: Hi, Am Donnerstag, 16. März 2017, 21:17:22 CET schrieb c...@rock-chips.com: From: Liang Chen This patch adds core dtsi file for Rockchip RK3328 SoCs. Signed-off-by: Liang Chen --- arch/arm64/boot/dts/rockchip/rk3328.dtsi | 1362 ++

[PATCH v2 2/5] clk: meson-gxbb: Add GP0 PLL init parameters

Tha Amlogic GXBB SoC GP0 PLL needs some vendor provided parameters to be initializated in the the GP0 control registers before configuring the rate with the rate table provided parameters. GXBB GP0 PLL tweaks are also selected to respect the vendor init procedure. Signed-off-by: Neil Armstrong -

[PATCH v2 4/5] clk: meson-gxbb: Expose GP0 dt-bindings clock id

This patch exposes the GP0 PLL clock id in the dt bindings. Signed-off-by: Neil Armstrong --- drivers/clk/meson/gxbb.h | 2 +- include/dt-bindings/clock/gxbb-clkc.h | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/clk/meson/gxbb.h b/drivers/clk/meson/gxbb

[PATCH v2 1/5] clk: meson: Add support for parameters for specific PLLs

In recent Amlogic GXBB, GXL and GXM SoCs, the GP0 PLL needs some specific parameters in order to initialize and lock correctly. This patch adds an optional PARAM table used to initialize the PLL to a default value with it's parameters in order to achieve to desired frequency. The GP0 PLL in GXBB,

Re: [PATCH v2 2/7] dt-bindings: pinctrl: Add RZ/A1 bindings doc

Hi Jacopo, On Mon, Mar 20, 2017 at 5:14 PM, Jacopo Mondi wrote: > Add device tree bindings documentation for Renesas RZ/A1 gpio and pin for the Renesas ... > controller. > > Signed-off-by: Jacopo Mondi > --- > .../bindings/pinctrl/renesas,rza1-pinctrl.txt | 144 > + >

[PATCH v2 5/5] dt-bindings: clock: gxbb-clkc: Add GXL compatible variant

Acked-by: Rob Herring Signed-off-by: Neil Armstrong --- Documentation/devicetree/bindings/clock/amlogic,gxbb-clkc.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/clock/amlogic,gxbb-clkc.txt b/Documentation/devicetree/bindings/clock/aml

Re: [Intel-gfx] [BUG][REGRESSION] i915 gpu hangs under load

On Wed, 22 Mar 2017, Martin Kepplinger wrote: > I know something similar is here: > https://bugs.freedesktop.org/show_bug.cgi?id=100110 too. > > But this is rc3 and my machine is totally *not usable*. Let me be > annoying :) I hope I can help: Please file a bug over at [1]. Thanks, Jani. [1]

Re: [PATCH v2 3/7] arm: dts: dt-bindings: Add Renesas RZ pinctrl header

On Mon, Mar 20, 2017 at 5:14 PM, Jacopo Mondi wrote: > Add dt-bindings for Renesas r7s72100 pin controller header file. > > Signed-off-by: Jacopo Mondi > --- > include/dt-bindings/pinctrl/r7s72100-pinctrl.h | 36 > ++ > 1 file changed, 36 insertions(+) > create mode 100

Re: [PATCH v5 1/2] usb: host: plat: Enable xhci plat runtime PM

Hi, On 22 March 2017 at 17:00, Felipe Balbi wrote: > > Hi, > > Baolin Wang writes: >> I don't yet understand why we can't just keep runtime pm disabled as a >> default for xhci platform devices. >> It could be enabled by whatever creates the platform device by setting >> some >>

Re: [PATCH 2/3] asm-generic, x86: wrap atomic operations

On Tue, Mar 21, 2017 at 10:20 PM, Arnd Bergmann wrote: > On Tue, Mar 21, 2017 at 7:06 PM, Dmitry Vyukov wrote: >> On Tue, Mar 21, 2017 at 11:41 AM, Mark Rutland wrote: >>> On Tue, Mar 21, 2017 at 12:25:06PM +0300, Andrey Ryabinin wrote: >> >> I don't mind changing READ_ONCE_NOCHECK to READ_ONCE.

[PATCH -v6 00/13] The arduous story of FUTEX_UNLOCK_PI

Hi all, Another installment of the futex patches that give you nightmares ;-) This version sports updated comments and Changelogs as requested last time around. It also includes two fixes, both reported by Sebastian who was kind enough to stick this in his RT tree for some testing. The last patc

[PATCH -v6 09/13] futex,rt_mutex: Introduce rt_mutex_init_waiter()

Since there's already two copies of this code, introduce a helper now before we get a third instance. Signed-off-by: Peter Zijlstra (Intel) --- kernel/futex.c |5 + kernel/locking/rtmutex.c| 12 +--- kernel/locking/rtmutex_common.h |1 + 3 files cha

[PATCH -v6 03/13] futex: Remove rt_mutex_deadlock_account_*()

These are unused and clutter up the code. Signed-off-by: Peter Zijlstra (Intel) --- kernel/locking/rtmutex-debug.c |9 --- kernel/locking/rtmutex-debug.h |3 -- kernel/locking/rtmutex.c | 47 +++-- kernel/locking/rtmutex.h |2 - 4

[PATCH -v6 01/13] futex: Cleanup variable names for futex_top_waiter()

futex_top_waiter() returns the top-waiter on the pi_mutex. Assinging this to a variable 'match' totally obscures the code. Signed-off-by: Peter Zijlstra (Intel) --- kernel/futex.c | 30 +++--- 1 file changed, 15 insertions(+), 15 deletions(-) --- a/kernel/futex.c +++ b

[PATCH -v6 06/13] futex: Cleanup refcounting

Since we're going to add more refcount fiddling, introduce get_pi_state() to match the existing put_pi_state(). Signed-off-by: Peter Zijlstra (Intel) --- kernel/futex.c | 13 + 1 file changed, 9 insertions(+), 4 deletions(-) --- a/kernel/futex.c +++ b/kernel/futex.c @@ -802,7 +802

[PATCH -v6 07/13] futex: Rework inconsistent rt_mutex/futex_q state

There is a weird state in the futex_unlock_pi() path when it interleaves with a concurrent futex_lock_pi() at the point where it drops hb->lock. In this case, it can happen that the rt_mutex wait_list and the futex_q disagree on pending waiters, in particular rt_mutex will find no pending waiters

[PATCH -v6 02/13] futex: Use smp_store_release() in mark_wake_futex()

Since the futex_q can dissapear the instruction after assigning NULL, this really should be a RELEASE barrier. That stops loads from hitting dead memory too. Signed-off-by: Peter Zijlstra (Intel) --- kernel/futex.c |3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) --- a/kernel/futex.c

[PATCH] qla4xxx: drop redundant init_completion

: x86_64_defconfig + SCSI_LOWLEVEL=y, CONFIG_SCSI_QLA_ISCSI=m (...quite a few sparse and coccinelle errors/warnings during build-tests) Patch is against 4.11-rc3 (localversion-next is next-20170322) drivers/scsi/qla4xxx/ql4_os.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/scsi/

[PATCH -v6 12/13] futex: futex_unlock_pi() determinism

The problem with returning -EAGAIN when the waiter state mismatches is that it becomes very hard to proof a bounded execution time on the operation. And seeing that this is a RT operation, this is somewhat important. While in practise; given the previous patch; it will be very unlikely to ever rea

[PATCH -v6 10/13] futex,rt_mutex: Restructure rt_mutex_finish_proxy_lock()

With the ultimate goal of keeping rt_mutex wait_list and futex_q waiters consistent we want to split 'rt_mutex_futex_lock()' into finer parts, such that only the actual blocking can be done without hb->lock held. This means we need to split rt_mutex_finish_proxy_lock() into two parts, one that doe

[PATCH -v6 08/13] futex: Pull rt_mutex_futex_unlock() out from under hb->lock

There's a number of 'interesting' problems, all caused by holding hb->lock while doing the rt_mutex_unlock() equivalient. Notably: - a PI inversion on hb->lock; and, - a DL crash because of pointer instability. Because of all the previous patches that: - allow us to do rt_mutex_futex_unlock

[PATCH -v6 04/13] futex,rt_mutex: Provide futex specific rt_mutex API

Part of what makes futex_unlock_pi() intricate is that rt_mutex_futex_unlock() -> rt_mutex_slowunlock() can drop rt_mutex::wait_lock. This means we cannot rely on the atomicy of wait_lock, which we would like to do in order to not rely on hb->lock so much. The reason rt_mutex_slowunlock() needs t

[PATCH -v6 11/13] futex: Rework futex_lock_pi() to use rt_mutex_*_proxy_lock()

By changing futex_lock_pi() to use rt_mutex_*_proxy_lock() we arrive at a point where all wait_list modifications are done under both hb->lock and wait_lock. This closes the obvious interleave pattern between futex_lock_pi() and futex_unlock_pi(), but not entirely so. See below: Before: futex_lo

[PATCH -v6 13/13] futex: futex_lock_pi() vs PREEMPT_RT_FULL

When PREEMPT_RT_FULL does the spinlock -> rt_mutex substitution the PI chain code will (falsely) report a deadlock and BUG. The problem is that we hold hb->lock (now an rt_mutex) while doing task_blocks_on_rt_mutex on the futex's pi_state::rtmutex. This, when interleaved just right with futex_unlo

[PATCH -v6 05/13] futex: Change locking rules

Currently futex-pi relies on hb->lock to serialize everything. Since hb->lock is giving us problems (PI inversions among other things, since on -rt hb lock itself is a rt_mutex), we want to break this up a bit. This patch reworks and documents the locking. Notably, it consistently uses rt_mutex::w

RE: [PATCH kernel v8 3/4] mm: add inerface to offer info about unused pages

Hi Andrew, Do you have any comments on my thoughts? Thanks. > On 03/17/2017 05:28 AM, Andrew Morton wrote: > > On Thu, 16 Mar 2017 15:08:46 +0800 Wei Wang > wrote: > > > >> From: Liang Li > >> > >> This patch adds a function to provides a snapshot of the present > >> system unused pages. An im

[PATCH v4 1/3] clk: meson-gxbb: Add MALI clock IDS

Add missing MALI clock IDs and expose the muxes and gates in the dt-bindings. Signed-off-by: Neil Armstrong --- drivers/clk/meson/gxbb.h | 9 - include/dt-bindings/clock/gxbb-clkc.h | 5 + 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/drivers/clk/meson/g

RE: [PATCH v2 1/2] dts: arm64: add LS1043A DPAA support

> -Original Message- > From: Shawn Guo [mailto:shawn...@kernel.org] > Sent: Tuesday, March 14, 2017 9:08 AM > On Wed, Mar 01, 2017 at 05:35:04PM +0200, Madalin Bucur wrote: > > Signed-off-by: Madalin Bucur > > Empty commit log is generally not welcome, especially when the commit > adds so

[PATCH v2 1/2] net: phy: Fix PHY AN done state machine for interrupt driven PHYs

he ethernet link on an interrupt driven PHY was not coming up if the ethernet cable was plugged before the ethernet interface was brought up. The PHY state machine seems to be stuck from RUNNING to AN state with no new interrupts from the PHY. So it doesn't know when the PHY Auto-negotiation has b

Re: [PATCH v4 1/2] backlight: pwm_bl: Move the checks for initial power state to a separate function

On Tue, 2017-03-21 at 19:48 +0100, Geert Uytterhoeven wrote: > Hi Peter, > > On Tue, Nov 22, 2016 at 2:41 PM, Peter Ujfalusi wrote: > > Move the checks to select the initial state for the backlight to a new > > function and document the checks we are doing. > > This is far from a simple "move"..

Re: [PATCH v3, 3/4] mtd: spi-nor: Add Xtensa CPU support for cadence-quadspi.

On 03/20/2017 12:26 PM, Artur Jedrysek wrote: > Cadence Quad SPI driver successfully runs on Xtensa CPU, and Kconfig > file is updated to indicate that. > > Signed-off-by: Artur Jedrysek Acked-by: Marek Vasut > --- > Changelog: > v2: This change is extracted from previous patch (updating CQSPI

Re: [PATCH v2 4/6] arm64: dts: rockchip: add core dtsi file for RK3328 SoCs

Am Mittwoch, 22. März 2017, 18:23:56 CET schrieb Elaine Zhang: > On 03/21/2017 04:55 PM, Heiko Stübner wrote: > > Am Donnerstag, 16. März 2017, 21:17:22 CET schrieb c...@rock-chips.com: > >> + cru: clock-controller@ff44 { > >> + compatible = "rockchip,rk3328-cru", "rockchip,cru", "sys

[PATCH v7 1/3] Input: max11801_ts: Add missing of_match_table

From: Jagan Teki Added missing of_match_table for max11801_ts driver with compatible as "maxim,max11801_ts" Cc: Dmitry Torokhov Cc: Shawn Guo Cc: Matteo Lisi Cc: Michael Trimarchi Signed-off-by: Jagan Teki --- Changes for v7: - newly added patch drivers/input/touchscreen/max11801_ts.c | 7

Re: [PATCH v3, 2/4] mtd: spi-nor: Add Octal SPI support to Cadence QSPI driver.

On 03/20/2017 12:25 PM, Artur Jedrysek wrote: > Recent versions of Cadence QSPI controller support Octal SPI transfers > as well. This patch updates existing driver to support such feature. > > It is not possible to determine whether or not octal mode is supported > just by looking at revision reg

[PATCH v7 2/3] dt-bindings: input: touchscreen: Add max11801-ts binding

From: Jagan Teki Add missing documentation of max11801-ts dt-binding details. Cc: Mark Rutland Cc: Rob Herring Cc: Shawn Guo Cc: Michael Trimarchi Signed-off-by: Jagan Teki --- Changes for v7: - add vendor prefix as maxim Changes for v6: - Replace the lable and name of the node ts: max11

Re: [v2 PATCH 4/4] powernv: Recover correct PACA on wakeup from a stop on P9 DD1

On Tue, Mar 21, 2017 at 02:59:46AM +1000, Nicholas Piggin wrote: > On Mon, 20 Mar 2017 21:24:18 +0530 > "Gautham R. Shenoy" wrote: > > > From: "Gautham R. Shenoy" > > > > POWER9 DD1.0 hardware has an issue due to which the SPRs of a thread > > waking up from stop 0,1,2 with ESL=1 can endup bein

[PATCH v7 3/3] ARM: dts: imx6q-icore: Add touchscreen node

From: Jagan Teki max11801 touchscreen on Engicam iCoreM6 Quad module is connected via i2c1, so add max11801: touchscreen@48 on i2c1. Cc: Domenico Acri Cc: Matteo Lisi Cc: Michael Trimarchi Cc: Shawn Guo Signed-off-by: Jagan Teki --- Changes for v7: - add vendor prefix as maxim on compatible

[PATCH] asm-generic: fix compilation failure in cmpxchg_double()

Arnd reported that the new code leads to compilation failures with some versions of gcc. I've filed gcc issue 72873, but we need a kernel fix as well. Remove instrumentation from cmpxchg_double() for now. Signed-off-by: Dmitry Vyukov Reported-by: Arnd Bergmann Cc: Mark Rutland Cc: Andrey Ryabi

Re: [PATCH] powerpc: fix /proc/self/stack

Thadeu Lima de Souza Cascardo writes: > For the current task, the kernel stack would only tell the last time the > process was rescheduled, if ever. Use the current stack pointer for the > current task. You say "fix" in the subject, but is it a bug, or just an enhancement? > This is also consis

Re: [PATCH V11 10/10] arm/arm64: KVM: add guest SEA support

Hi Wang Xiongfeng, On 22/03/17 02:46, Xiongfeng Wang wrote: >> Guests are a special case as QEMU may never access the faulty memory itself, >> so >> it won't receive the 'late' signal. It looks like ARM/arm64 KVM lacks support >> for KVM_PFN_ERR_HWPOISON which sends SIGBUS from KVM's fault-handli

Re: [PATCH] kvm: pass the virtual SEI syndrome to guest OS

On 21/03/17 22:10, Peter Maydell wrote: > On 21 March 2017 at 19:39, Christoffer Dall wrote: >> My confusion here comes from not thinking about QEMU or KVM as firmware, >> but as the machine, so it would be sort of like the functionality is >> baked into hardware rather than firmware. > > There i

[bug report] VMCI: queue pairs implementation.

Hello George Zhang, The patch 06164d2b72aa: "VMCI: queue pairs implementation." from Jan 8, 2013, leads to the following static checker warning: drivers/misc/vmw_vmci/vmci_queue_pair.c:1850 qp_broker_alloc() warn: we tested 'is_local' before and it was 'false' drivers/misc/vmw_vm

Re: [PATCH] drm/msm/hdmi: redefinitions of macros not required

On Wed, Mar 22, 2017 at 1:11 AM, Vinay Simha B N wrote: > hi, > > Could you please give some feedback or review comments for this patch looks good, I've pulled it into msm-next BR, -R > On 3/14/17, Vinay Simha BN wrote: >> 4 macros already defined in hdmi.h, >> which is not required to redefin

Re: [PATCH 3/5] perf/sdt/x86: Move OP parser to tools/perf/arch/x86/

Em Wed, Mar 22, 2017 at 08:00:18AM +0900, Masami Hiramatsu escreveu: > On Tue, 21 Mar 2017 11:10:49 -0300 > Arnaldo Carvalho de Melo wrote: > > > Em Tue, Feb 07, 2017 at 10:52:17AM +0530, Ravi Bangoria escreveu: > > > Thanks Masami for the review. > > > > > > On Tuesday 07 February 2017 08:41 AM

[PATCH v2 2/2] net: phy: Don't miss phy_suspend() on PHY_HALTED for PHYs with interrupts

phy_suspend() doesn't get called as part of phy_stop() for PHYs using interrupts because the phy state machine is never triggered after a phy_stop(). Explicitly trigger the PHY state machine in phy_stop() so that it can see the new PHY state (HALTED) and suspend the PHY. As most PHYLIB consumers

[PATCH] vmci: Fix a couple integer overflow tests

The "DIV_ROUND_UP(size, PAGE_SIZE)" operation can overflow if "size" is more than ULLONG_MAX - PAGE_SIZE. Signed-off-by: Dan Carpenter diff --git a/drivers/misc/vmw_vmci/vmci_queue_pair.c b/drivers/misc/vmw_vmci/vmci_queue_pair.c index 498c0854305f..06c4974ee8dd 100644 --- a/drivers/misc/vmw_vm

Re: [RFC] x86/tboot: add an option to disable iommu force on

Hi Shaohua, On Tue, Mar 21, 2017 at 11:37:51AM -0700, Shaohua Li wrote: > IOMMU harms performance signficantly when we run very fast networking > workloads. This is a limitation in hardware based on our observation, so > we'd like to disable the IOMMU force on, but we do want to use TBOOT and > we

Re: [PATCH] tpm: make check_locality return bool

On Sat, Mar 18, 2017 at 01:59:57AM -0700, Jerry Snitselaar wrote: > Since check_locality is checking to see if a certain > locality is active, return true if active otherwise > return false. > > Cc: Christophe Ricard > Cc: Jason Gunthorpe > Cc: Marcel Selhorst > Cc: Jarkko Sakkinen > Cc: Peter

Re: [GIT PULL] extcon fixes for v4.11-rc3

On Wed, Mar 22, 2017 at 06:47:01PM +0900, Chanwoo Choi wrote: > Dear Greg, > > This is extcon-fixes pull request for v4.11-rc3. I add detailed description of > this pull request on below. Please pull extcon with following updates. > > Best Regards, > Chanwoo Choi > > The following changes since

[PATCH v2 0/2] net: phy: state machine fixes for interrupt driven PHYs

Hi, These 2 patches fix the following 2 issues with the PHY state machine when used with interrupt driven PHYs. - PHY link not coming up if Ethernet cable is plugged before Ethernet network interface is brought up. - PHY not being suspended when PHY is halted. cheers, -roger Roger Quadros (2):

Re: [PATCH] asm-generic: fix compilation failure in cmpxchg_double()

On Wed, Mar 22, 2017 at 12:10 PM, Dmitry Vyukov wrote: > Arnd reported that the new code leads to compilation failures > with some versions of gcc. I've filed gcc issue 72873, > but we need a kernel fix as well. > > Remove instrumentation from cmpxchg_double() for now. Thanks, I also checked that

[PATCH 0/5] Intel PMIC: Intel PMIC mfd and OPRegion drivers must be built in

Hi All, Here is a series enforcing Intel PMIC mfd and OPRegion drivers to be built in, this is necessary so that the OPRegion handlers are registered before other drivers try to enter D0 which may require these OPRegion handlers. Note patches 4 & 5 are for drivers which have been submitted but no

[PATCH 3/5] mfd: axp20c-i2c: Select designware i2c-bus driver on x86

On x86 the axp288 PMIC provides an ACPI OPRegion handler, which must be available before other drivers using it are loaded, which can only be ensured if the mfd, opregion driver and i2c-bus drivers are built in. The opregion driver is a bool depending on MFD_AXP20X_I2C ensuring that it will be bui

[PATCH 1/5] ACPI / PMIC: Stop xpower OPRegion handler relying on IIO

The intel_pmic_xpower code provides an OPRegion handler, which must be available before other drivers using it are loaded, which can only be ensured if both the mfd and opregion drivers are built in, which is why the Kconfig option for intel_pmic_xpower is a bool. The use of IIO is causing trouble

[PATCH 4/5] mfd: intel_soc_pmic_chtwc: This driver must always be builtin when enabled

The chtwc PMIC provides an ACPI OPRegion handler, which must be available before other drivers using it are loaded, which can only be ensured if the mfd, opregion and i2c-bus drivers are built in. This commit changes the option for the mfd driver to bool and adds a select for the i2c-bus driver, e

[PATCH 2/5] mfd: intel_soc_pmic: Select designware i2c-bus driver

The Crystal Cove PMIC provides an ACPI OPRegion handler, which must be available before other drivers using it are loaded, which is why INTEL_SOC_PMIC is a bool. Just having the driver is not enough, the driver for the i2c-bus must also be built in, to ensure this, this patch adds a select for it.

[PATCH 5/5] ACPI / PMIC: mfd: intel_pmic_chtwc: This driver must always be builtin

The chtwc PMIC provides an ACPI OPRegion handler, which must be available before other drivers using it are loaded, which can only be ensured if both the mfd and opregion drivers are built in. This fixes errors like these during boot: mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA ACPI E

Re: [PATCH 2/3] asm-generic, x86: wrap atomic operations

On Wed, Mar 22, 2017 at 11:42 AM, Dmitry Vyukov wrote: > On Tue, Mar 21, 2017 at 10:20 PM, Arnd Bergmann wrote: >> On Tue, Mar 21, 2017 at 7:06 PM, Dmitry Vyukov wrote: > > Initially I've tested with my stock gcc 4.8.4 (Ubuntu > 4.8.4-2ubuntu1~14.04.3) and amusingly it works. But I can reproduce

Re: [PATCH v2 6/6] selftests: enable O and KBUILD_OUTPUT

Bamvor Zhang Jian writes: > Here is a fix. I could build individual test case in x86 and build the whole > x86 test cases successful respectively. And I do a quick test for all the > subsets. Please review the patch if it is make sense to you and Michael. > At the same time, I am buildind and test

Re: [PATCH v2 0/7] Add support for pinctrl/gpio on Armada 37xx Was Re: [PATCH v2 0/7] Hi,

Hi Linus, On mar., mars 21 2017, Gregory CLEMENT wrote: > Hi, > > Obviously this cover letter is wrong. Actually I forgot to commit it in > git series. Here it is the correct one: > > After several months here it is the second version of the series adding > support for the pin and gpio contro

[PATCH v3] usb: xhci: bInterval quirk for TI TUSB73x0

As per [1] issue #4, "The periodic EP scheduler always tries to schedule the EPs that have large intervals (interval equal to or greater than 128 microframes) into different microframes. So it maintains an internal counter and increments for each large interval EP added. When the counter is greater

Re: [PATCH] tpm2: fix off-by-one comparison and out-of-bounds read error

On 22/03/17 11:42, Jarkko Sakkinen wrote: > On Mon, Mar 20, 2017 at 02:23:36PM +, Colin King wrote: >> From: Colin Ian King >> >> The comparison of an out of range index into space->context_tbl is >> off-by-one and should be using >= rather than > in the comparison. >> >> Detected by CoverityS

Re: [PATCH] tpm2: fix off-by-one comparison and out-of-bounds read error

On Mon, Mar 20, 2017 at 02:23:36PM +, Colin King wrote: > From: Colin Ian King > > The comparison of an out of range index into space->context_tbl is > off-by-one and should be using >= rather than > in the comparison. > > Detected by CoverityScan, CID#1419694 ("Out-of-bounds read") > > Fix

Re: [PATCH v2 6/6] selftests: enable O and KBUILD_OUTPUT

Shuah Khan writes: > On 03/21/2017 03:00 AM, Bamvor Zhang Jian wrote: >> On 21 March 2017 at 16:35, Michael Ellerman wrote: >>> Andy Lutomirski writes: On Tue, Nov 29, 2016 at 3:55 AM, wrote: > From: Bamvor Jian Zhang > > Enable O and KBUILD_OUTPUT for kselftest. User could

Re: [PATCH v3 1/3] kexec: Move vmcoreinfo out of the kernel's .bss section

Hi Dave, On Wednesday 22 March 2017 10:00 AM, Dave Young wrote: On 03/21/17 at 10:18pm, Eric W. Biederman wrote: Dave Young writes: On 03/20/17 at 10:33pm, Eric W. Biederman wrote: Xunlei Pang writes: As Eric said, "what we need to do is move the variable vmcoreinfo_note out of the kern

[PATCH v2] arm64: kaslr: Fix up the kernel image alignment

From: Neeraj Upadhyay If kernel image extends across alignment boundary, existing code increases the KASLR offset by size of kernel image. The offset is masked after resizing. There are cases, where after masking, we may still have kernel image extending across boundary. This eventually results i

Re: [PATCH v2 6/6] selftests: enable O and KBUILD_OUTPUT

Bamvor Zhang Jian writes: > On 21 March 2017 at 16:35, Michael Ellerman wrote: >> I see at least 18 Makefile's in tools/testing/selftests that use >> $(OUTPUT)/, which would all need to be updated at least to use $(OUTPUT) >> (no trailing slash), and then some other changes to not propagate OUTPU

Re: [RFC] x86/tboot: add an option to disable iommu force on

On Wed, Mar 22, 2017 at 11:49:00AM +0100, Joerg Roedel wrote: > Hi Shaohua, > > On Tue, Mar 21, 2017 at 11:37:51AM -0700, Shaohua Li wrote: > > IOMMU harms performance signficantly when we run very fast networking > > workloads. This is a limitation in hardware based on our observation, so > > we'

Re: [PATCH 2/4] perf annotate: Avoid division by zero when calculating percent

On 03/21/2017 11:21 PM, Arnaldo Carvalho de Melo wrote: Em Tue, Mar 21, 2017 at 11:14:07AM -0300, Arnaldo Carvalho de Melo escreveu: Em Tue, Mar 21, 2017 at 07:20:20AM +0900, Taeung Song escreveu: And, I tested by perf-stat on the same situation as below. $ perf stat -e "{cycles,page-fault

Re: [PATCH v3 3/4] arm64: dts: rockchip: describe Gru/Kevin OPPs + CPU regulators

Am Montag, 20. März 2017, 16:53:43 CET schrieb Brian Norris: > Used for Gru/Kevin only, as they're the only ones which have a described > CPU regulator. Also, I'm not sure we've validated this table non-Gru > boards. > > At the same time, partially describe PWM regulators for Gru, so cpufreq > doe

Re: [PATCH] KVM: nVMX: Fix L2 guest hang if shadow page tables on EPT

On Sat, Mar 18, 2017 at 7:37 AM, Wanpeng Li wrote: > 2017-03-18 1:28 GMT+08:00 Ladi Prosek : >> On Fri, Mar 17, 2017 at 3:41 PM, Wanpeng Li wrote: >>> From: Wanpeng Li >>> >>> The L2 guest hang if shadow page tables on EPT, the trace on L1 shows that >>> L2 kvm_exit reason EXCEPTION_NMI and page

[PATCH] arm64: dts: rockchip: add dmac nodes for rk3368 SoCs

Add dmac bus and dmac peri dts nodes for peripherals, such as I2S, SPI, UART and so on. Signed-off-by: Huibin Hong --- arch/arm64/boot/dts/rockchip/rk3368.dtsi | 29 + 1 file changed, 29 insertions(+) diff --git a/arch/arm64/boot/dts/rockchip/rk3368.dtsi b/arch/arm6

Re: [PATCH v2 02/10] x86: assembly, FUNC_START for fn, DATA_START for data

Hi, On 03/21/2017, 03:08 PM, Pavel Machek wrote: >> -ENTRY(saved_rbp).quad 0 >> -ENTRY(saved_rsi).quad 0 >> -ENTRY(saved_rdi).quad 0 >> -ENTRY(saved_rbx).quad 0 >> +SYM_DATA_START(saved_rbp) .quad 0 >> +SYM_DATA_START(saved_rsi) .quad 0 >> +SYM_DATA_

Re: [PATCH] staging: media: Replace a bit shift by a use of BIT.

On Mar 22, 2017, at 00:20, Arushi Singhal wrote: > > This patch replaces bit shifting on 1 with the BIT(x) macro. > This was done with coccinelle: > @@ > constant c; > @@ > > -1 << c > +BIT(c) Hi Arushi, thanks for taking time to contribute to the kernel. There are a few problems with this p

Re: [PATCH] staging: lustre: Replace a bit shift by a use of BIT.

On Mar 21, 2017, at 22:39, Arushi Singhal wrote: > > This patch replaces bit shifting on 1 with the BIT(x) macro. > This was done with coccinelle: > @@ > constant c; > @@ > > -1 << c > +BIT(c) Did you take the time to look at what this Coccinelle script actually did, to see if it actually mak

Re: [PATCH v3 1/3] kexec: Move vmcoreinfo out of the kernel's .bss section

Hi Xunlei, On Wednesday 22 March 2017 03:04 PM, Xunlei Pang wrote: On 03/22/2017 at 12:30 PM, Dave Young wrote: On 03/21/17 at 10:18pm, Eric W. Biederman wrote: Dave Young writes: On 03/20/17 at 10:33pm, Eric W. Biederman wrote: Xunlei Pang writes: As Eric said, "what we need to do is

Re: [PATCH v2] arm64: kaslr: Fix up the kernel image alignment

On 22 March 2017 at 11:38, Srinivas Ramana wrote: > From: Neeraj Upadhyay > > If kernel image extends across alignment boundary, existing > code increases the KASLR offset by size of kernel image. The > offset is masked after resizing. There are cases, where after > masking, we may still have ker

Re: [PATCH V11 10/10] arm/arm64: KVM: add guest SEA support

Hi James, On 2017/3/22 19:14, James Morse wrote: > Hi Wang Xiongfeng, > > On 22/03/17 02:46, Xiongfeng Wang wrote: >>> Guests are a special case as QEMU may never access the faulty memory >>> itself, so >>> it won't receive the 'late' signal. It looks like ARM/arm64 KVM lacks >>> support >>> fo

Re: [RFC 0/1] add support for reclaiming priorities per mem cgroup

On 3/20/2017 8:53 PM, Johannes Weiner wrote: > On Mon, Mar 20, 2017 at 07:28:53PM +0530, Vinayak Menon wrote: >> From the discussions @ https://lkml.org/lkml/2017/3/3/752, I assume you are >> trying >> per-app memcg. We were trying to implement per app memory cgroups and were >> encountering some

Re: [PATCH 2/3] asm-generic, x86: wrap atomic operations

On Wed, Mar 22, 2017 at 12:30 PM, Arnd Bergmann wrote: > On Wed, Mar 22, 2017 at 11:42 AM, Dmitry Vyukov wrote: >> On Tue, Mar 21, 2017 at 10:20 PM, Arnd Bergmann wrote: >>> On Tue, Mar 21, 2017 at 7:06 PM, Dmitry Vyukov wrote: >> >> Initially I've tested with my stock gcc 4.8.4 (Ubuntu >> 4.8.

Re: [PATCH] pci: dwc: hisi needs PCI_HOST_COMMON

On 2017/3/22 16:00, Arnd Bergmann wrote: > On Mar 22, 2017 04:27, "Zhou Wang" > wrote: > > On 2017/3/21 23:48, Jingoo Han wrote: > > (+cc: Joao Pinto, Zhou Wang, Gabriele Paoloni) > > > > On Tuesday, March 21, 2017 10:32 AM, Arnd Bergmann wrote: >

Re: [PATCH 07/17] net: convert sock.sk_refcnt from atomic_t to refcount_t

On Tue, Mar 21, 2017 at 07:03:19PM -0700, Eric Dumazet wrote: > Note that we might define two refcount_inc() : One that does whole > tests, and refcount_inc_relaxed() that might translate to atomic_inc() > on non debug kernels. So you'd want a duplicate interface, such that most code, which does

Re: net/sctp: recursive locking in sctp_do_peeloff

On Wed, Mar 15, 2017 at 7:19 PM, Cong Wang wrote: > On Wed, Mar 15, 2017 at 5:52 AM, Marcelo Ricardo Leitner > wrote: >> On Tue, Mar 14, 2017 at 09:52:15PM -0700, Cong Wang wrote: >>> Instead of checking for the status of the sock, I believe the following >>> one-line fix should do the trick too.

[PATCH v11 0/2] Add support for Omnivision OV5647

Hello, This patchset adds support for the Omnivision OV5647 sensor. At the moment it only supports 640x480 in RAW 8. This is the eleventh version of the OV5647 camera driver patchset. v11: - Remove leftover debug code Suggested-by: Sakari Ailus v10: - Add more error info to model check - R

Re: [PATCH v4 1/2] backlight: pwm_bl: Move the checks for initial power state to a separate function

Hi Philip, On Wed, Mar 22, 2017 at 11:46 AM, Philipp Zabel wrote: > On Tue, 2017-03-21 at 19:48 +0100, Geert Uytterhoeven wrote: >> On Tue, Nov 22, 2016 at 2:41 PM, Peter Ujfalusi >> wrote: >> > Move the checks to select the initial state for the backlight to a new >> > function and document th

Re: [PATCH v2] staging: iio: Replace a bit shift by a use of BIT.

On 03/22/2017 09:38 AM, Arushi Singhal wrote: > This patch replaces bit shifting on 1 with the BIT(x) macro. > This was done with coccinelle: > @@ > constant c; > @@ > > -1 << c > +BIT(c) When it comes to doing this type of conversion semantics, i.e. the meaning of the value, are important. The B

[PATCH v11 1/2] Documentation: DT: Add OV5647 bindings

Create device tree bindings documentation. Signed-off-by: Ramiro Oliveira Acked-by: Rob Herring Reviewed-by: Vladimir Zapolskiy --- .../devicetree/bindings/media/i2c/ov5647.txt | 35 ++ 1 file changed, 35 insertions(+) create mode 100644 Documentation/devicetree/bin

Re: [PATCH] Add initial SX3000b platform code to MIPS arch

On Wed, Mar 22, 2017 at 05:38:09AM +, Amit Kama IL wrote: > Add initial support for boards based on Satixfy's SX3000b (Catniss) SoC. > The SoC includes a MIPS interAptiv dual core 4 VPE processor and boots > using device-tree. > > Signed-off-by: Amit Kama > > The irqchip file (irq-sx3000b.

Re: [PATCH v2] sched/deadline: Make find_later_rq() choose a closer cpu in topology

On Tue, Mar 21, 2017 at 04:52:24PM +0900, Byungchul Park wrote: > When cpudl_find() returns any among free_cpus, the cpu might not be > closer than others, considering sched domain. For example: > >this_cpu: 15 >free_cpus: 0, 1,..., 14 (== later_mask) >best_cpu: 0 > >topology: >

Re: [PATCH 2/3] net: stmmac: Restore DT backwards-compatibility

On Tue, Mar 21, 2017 at 04:12:10PM +0100, Thierry Reding wrote: > From: Thierry Reding > > Recent changes to support multiple queues in the device tree bindings > resulted in the number of RX and TX queues to be initialized to zero for > device trees not adhering to the new bindings. > > Restore

Re: [PATCH v2] arm64: kaslr: Fix up the kernel image alignment

On Wed, Mar 22, 2017 at 12:16:24PM +, Ard Biesheuvel wrote: > On 22 March 2017 at 11:38, Srinivas Ramana wrote: > > From: Neeraj Upadhyay > > > > If kernel image extends across alignment boundary, existing > > code increases the KASLR offset by size of kernel image. The > > offset is masked a

Re: [PATCH v5 1/2] usb: host: plat: Enable xhci plat runtime PM

On 22.03.2017 12:40, Baolin Wang wrote: Hi, On 22 March 2017 at 17:00, Felipe Balbi wrote: Hi, Baolin Wang writes: I don't yet understand why we can't just keep runtime pm disabled as a default for xhci platform devices. It could be enabled by whatever creates the platform device by settin

[PATCH v11 2/2] media: i2c: Add support for OV5647 sensor.

The OV5647 sensor from Omnivision supports up to 2592x1944 @ 15 fps, RAW 8 and RAW 10 output formats, and MIPI CSI-2 interface. The driver adds support for 640x480 RAW 8. Signed-off-by: Ramiro Oliveira Acked-by: Sakari Ailus Reviewed-by: Vladimir Zapolskiy --- MAINTAINERS|

[PATCH v2 0/3] perf annotate: Bugfixes

Hi, perf-annotate has little bugs so I fix them. I'd appreciate some feedback on this patchset. :) Thanks, Taeung v2: - more clearly commit log messages (Arnaldo) - rebased on current acme/perf/core Taeung Song (3): perf annotate: Fix a bug reading link name from a build-id file perf annota

[PATCH v2 3/3] perf annotate: Fix missing number of samples

If running 'perf annotate --stdio -l --show-total-period', you can see a problem showing only zero '0' for number of samples. Before: $ perf annotate --stdio -l --show-total-period ... 0 :400816: push %rbp 0 :400817: mov%rsp,%rbp 0 :

[PATCH v2 1/3] perf annotate: Fix a bug reading link name from a build-id file

It is wrong way to read link name from a build-id file. Because a build-id file is not symbolic link but build-id directory of it is symbolic link, so fix it. For example, if build-id file name gotten from dso__build_id_filename() is as below, /root/.debug/.build-id/4f/75c7d197c951659d1c1b8b5fd

Re: [PATCH 2/2] regulator: hi655x: Bump parent pmic module use count

On Tue, Mar 21, 2017 at 03:23:50PM -0500, Jeremy Linton wrote: > I don't understand why it was done this way, and I'm not sure that > this driver shouldn't be triggered based on 'hi655x-regulator' device > (which is being registered by the hi655x-pmic/mfd driver). The only > thing I know for sure,

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