Re: [RFC v2 00/13] usb/mmc/power: Fix USB/LAN when TFTP booting

On Tue, May 10, 2016 at 01:02:08PM +0200, Ulf Hansson wrote: > + Arnd > > [...] > > >> >> Solution > >> >> > >> >> This is very similar to the MMC pwrseq behavior so the idea is to: > >> >> 1. Move MMC pwrseq drivers to generic place, > >> > > >> > You can do that, but I'm going to NAK

Re: linux-next memleak after IO on dax mountpoint

On Fri, May 27, 2016 at 04:46:17PM +0800, Xiong Zhou wrote: ... > Still working on to id which commit in this merge causes this issuer, Narrowed down to: 37e5823 block: add offset in blk_add_request_payload() e048948 blk-mq: Export tagset iter function 58b4560 nvme: add helper nvme_map_len()

[PATCH 2/4] mfd: cros_ec: add EC_PWM function definitions

The EC_CMD_PWM_{GET,SET}_DUTY commands allow us to control a PWM that is attached to the EC, rather than the main host SoC. The API provides functionality-based (e.g., keyboard light, backlight) or index-based addressing of the PWM(s). Duty cycles are represented by a 16-bit value, where 0 maps to

[PATCH 3/4] doc: dt: pwm: add binding for ChromeOS EC PWM

The ChromeOS Embedded Controller can support controlling its attached PWMs via its host-command interface. The number of supported PWMs varies on a per-board basis, so we define a "google,max-pwms" property to handle this. And because the EC only allows specifying the duty cycle and not the

[PATCH 0/4] pwm: add support for ChromeOS EC PWM

Hi, This series adds support for the new ChromeOS EC PWM API, so we can control, e.g., the backlight when it's attached to the EC. It uses Boris's latest "atomic" hooks for the PWM API (i.e., the ->apply() callback), which were recently merged. It seems nice to have the cros_ec_cmd_xfer_status()

[PATCH 4/4] pwm: add ChromeOS EC PWM driver

Use the new ChromeOS EC EC_CMD_PWM_{GET,SET}_DUTY commands to control one or more PWMs attached to the Embedded Controller. Because the EC allows us to modify the duty cycle (as a percentage, where U16_MAX is 100%) but not the period, we assign the period a fixed value of EC_PWM_MAX_DUTY and

[PATCH 1/4] mfd: cros_ec: Add cros_ec_cmd_xfer_status helper

From: Tomeu Vizoso So that callers of cros_ec_cmd_xfer don't have to repeat boilerplate code when checking for errors from the EC side. Signed-off-by: Tomeu Vizoso Reviewed-by: Benson Leung Signed-off-by: Brian

Re: [PATCH] pv-qspinlock: Try to re-hash the lock after spurious_wakeup

On 05/27/2016 06:32 AM, xinhui wrote: On 2016年05月27日 02:31, Waiman Long wrote: On 05/25/2016 02:09 AM, Pan Xinhui wrote: In pv_wait_head_or_lock, if there is a spurious_wakeup, and it fails to get the lock as there is lock stealing, then after a short spin, we need hash the lock again and

Re: [PATCH] f2fs: fix to redirty page if fail to gc data page

Ping, On 2016/5/21 13:19, Chao Yu wrote: > From: Chao Yu > > If we fail to move data page during foreground GC, we should give another > chance to writeback that page which was set dirty previously by writer. > > Signed-off-by: Chao Yu > --- >

Re: [PATCH v4] platform/chrome: Add Chrome OS keyboard backlight LEDs support

On Fri, May 27, 2016 at 5:34 PM, Dmitry Torokhov wrote: > On Wed, May 11, 2016 at 11:06 AM, Olof Johansson wrote: >> On Wed, Mar 09, 2016 at 04:25:21PM -0800, Dmitry Torokhov wrote: >>> From: Simon Que >>> >>> This is a driver for

Re: [PATCH] Revert "platform/chrome: chromeos_laptop: Add Leon Touch"

On Thu, May 26, 2016 at 4:07 AM, Enric Balletbo i Serra wrote: > Hi Benson, Olof > > On 26/05/16 03:59, Benson Leung wrote: >> This reverts commit bff3c624dc7261a084a4d25a0b09c3fb0fec872a. >> >> Board "Leon" is otherwise known as "Toshiba CB35" and we already have >>

Re: [PATCH v2] watchdog: Add a device managed API for watchdog_register_device()

On 05/27/2016 08:33 AM, Neil Armstrong wrote: This helps in reducing code in .remove callbacks and sometimes dropping .remove callbacks entirely. Changes since v1 at http://lkml.kernel.org/r/1464251510-15554-1-git-send-email-narmstr...@baylibre.com : - Fix brackets in

[GIT PULL] target updates for v4.7-rc1

Hi Linus, Here are the outstanding target pending updates for v4.7-rc1. Please go ahead and pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git for-next The highlights this round include: - Allow external PR/ALUA metadata path be defined at runtime via top

Re: [PATCH] seccomp: plug syscall-dodging ptrace hole

On Fri, May 27, 2016 at 4:20 PM, Andy Lutomirski wrote: > On May 27, 2016 3:38 PM, "Kees Cook" wrote: >> >> On Fri, May 27, 2016 at 12:52 PM, Andy Lutomirski >> wrote: >> > On May 27, 2016 11:42 AM, "Kees Cook"

IOV iterator bug in net tree (was Re: Deadlock when running DevStack on latest pull of net tree)

On Fri, May 27, 2016 at 11:21 AM, Alexander Duyck wrote: > I started out this morning by trying to run DevStack on the latest > "net' kernel and it looks like I am hanging on some sort of locking > problem with RabbitMQ. Specifically I am seeing one CPU jump to 100% >

[patch v2] usb: f_fs: off by one bug in _ffs_func_bind()

This loop is supposed to set all the .num[] values to -1 but it's off by one so it skips the first element and sets one element past the end of the array. I've cleaned up the loop a little as well. Fixes: ddf8abd25994 ('USB: f_fs: the FunctionFS driver') Signed-off-by: Dan Carpenter

[patch] IB/hfi1: fix some indenting

That extra tabs are misleading. Signed-off-by: Dan Carpenter diff --git a/drivers/infiniband/hw/hfi1/init.c b/drivers/infiniband/hw/hfi1/init.c index 5cc492e..0d28a5a 100644 --- a/drivers/infiniband/hw/hfi1/init.c +++ b/drivers/infiniband/hw/hfi1/init.c @@ -1337,7

Re: [PATCH v4 0/2] cgroup: allow management of subtrees by new cgroup namespaces

Hi Tejun, >> > Unfortunately, cgroup hierarchy isn't designed to support this sort >> > of automatic delegation. Unpriv processes would be able to escape >> > constraints on v1 with some controllers and on v2 controllers have to >> > be explicitly enabled by root for delegated scope to have

[PATCH v2 3/4] Staging: comedi:Fix unsigned int to bare use of unsigned issue in s626.c

This is a patch to the s626.c file that fixes up a WARNING: Prefer 'unsigned int' to bare use of 'unsigned' found by the checkpatch.pl tool Signed-off-by: Ravishankar Karkala Mallikarjunayya --- changes since v1: No change --- drivers/staging/comedi/drivers/s626.c | 8

[PATCH v2 2/4] Staging: comedi: Fix WARNING issue in s626.c

This is a patch to the s626.c file that fixes up a Block comments issues found by the checkpatch.pl tool. i.e. Block comments use a trailing */ on a separate line Signed-off-by: Ravishankar Karkala Mallikarjunayya --- changes since v1: No change ---

[PATCH v2 4/4] Staging: comedi: fix line over 80 characters issue in s626.c

This is a patch to the s626.c file that fixes up a line over 80 characters issues found by the checkpatch.pl tool. Signed-off-by: Ravishankar Karkala Mallikarjunayya --- changes since v1: No change --- drivers/staging/comedi/drivers/s626.c | 3 ++- 1 file changed, 2

[PATCH v2 1/4] staging : comedi : fix type issues in s626.c

This is a patch to the s626.c file that fixes up a type issues like i.e Prefer kernel type 'u8' over 'uint8_t' Prefer kernel type 'u16' over 'uint16_t' Prefer kernel type 'u32' over 'uint32_t' Prefer kernel type 's16' over 'int16_t' Prefer kernel type 's32' over 'int32_t' found by

Re: [GIT PULL] Please pull NFS client changes for Linux 4.7

On Fri, May 27, 2016 at 10:14 AM, Boris Ostrovsky wrote: > > This breaks on older compilers: > > CC fs/nfs/nfs4state.o > /home/build/linux-linus/fs/nfs/nfs4state.c:69: error: unknown field > ‘data’ specified in initializer Does the attached patch fix it for

Re: [PATCH v4 08/10] powerpc/powernv: Add platform support for stop instruction

On Tue, May 24, 2016 at 06:45:12PM +0530, Shreyas B. Prabhu wrote: > POWER ISA v3 defines a new idle processor core mechanism. In summary, > a) new instruction named stop is added. This instruction replaces > instructions like nap, sleep, rvwinkle. > b) new per thread SPR named Processor

[git pull] vfs fixes

work.lookups followups - update docs, restore killability of the places that used to take ->i_mutex killably now that we have down_write_killable() merged. Additionally, it turns out that I missed a prereq for security_d_instantiate() stuff - ->getxattr() wasn't the only thing that could

[git pull] Input updates for 4.7-rc0 (part 2)

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus to receive updates for the input subsystem. Just a few more driver fixes; new drivers will be coming in the next merge window. There will be a trivial conflict in

Re: [GIT PULL] Please pull NFS client changes for Linux 4.7

- torva...@linux-foundation.org wrote: > On Fri, May 27, 2016 at 10:14 AM, Boris Ostrovsky > wrote: > > > > This breaks on older compilers: > > > > CC fs/nfs/nfs4state.o > > /home/build/linux-linus/fs/nfs/nfs4state.c:69: error: unknown field > > ‘data’

Re: [PATCH v5] KVM: halt-polling: poll for the upcoming fire timers

On Fri, 27 May 2016 11:49:26 +0200 Paolo Bonzini wrote: > > > On 26/05/2016 22:33, yunhong jiang wrote: > > On Thu, 26 May 2016 12:26:27 +0200 > > Paolo Bonzini wrote: > > > >> > >> > >> On 25/05/2016 04:47, Wanpeng Li wrote: > >>> From: Wanpeng Li

Re: [GIT PULL] Please pull NFS client changes for Linux 4.7

On Fri, May 27, 2016 at 5:17 PM, Boris Ostrovsky wrote: > > It does fix it. Ok, I've committed that in my tree, will do my usual build test and push out. > This is not the first time we've hit this and people have always been > changing code to initialize fields in

Re: [PATCH v4] platform/chrome: Add Chrome OS keyboard backlight LEDs support

On Wed, May 11, 2016 at 11:06 AM, Olof Johansson wrote: > On Wed, Mar 09, 2016 at 04:25:21PM -0800, Dmitry Torokhov wrote: >> From: Simon Que >> >> This is a driver for ACPI-based keyboard backlight LEDs found on >> Chromebooks. The driver locates \\_SB.KBLT

Re: [PATCH] oom_reaper: don't call mmput_async() on uninitialized mm

On Fri 27-05-16 10:00:48, Arnd Bergmann wrote: > The change to the oom_reaper to hold a mutex inside __oom_reap_task() > accidentally started calling mmput_async() on the local > mm before that variable got initialized, as reported by gcc > in linux-next: > > mm/oom_kill.c: In function

Re: [PATCH] mm: check the return value of lookup_page_ext for all call sites

On Fri, May 27, 2016 at 03:08:39PM +0900, Joonsoo Kim wrote: > On Fri, May 27, 2016 at 02:14:32PM +0900, Minchan Kim wrote: > > On Thu, May 26, 2016 at 04:15:28PM -0700, Shi, Yang wrote: > > > On 5/25/2016 5:37 PM, Minchan Kim wrote: > > > >On Tue, May 24, 2016 at 11:58:11AM +0900, Minchan Kim

Re: [LKP] [mm] 23047a96d7: vm-scalability.throughput -23.8% regression

On Wed, May 25, 2016 at 02:06:17PM +0800, Ye Xiaolong wrote: >On Mon, May 23, 2016 at 04:46:05PM -0400, Johannes Weiner wrote: >>Hi, >> >>thanks for your report. >> >>On Tue, May 17, 2016 at 12:58:05PM +0800, kernel test robot wrote: >>> FYI, we noticed vm-scalability.throughput -23.8% regression

Re: [PATCH 1/3] vfs: merge .d_select_inode() into .d_real()

On Sun, May 22, 2016 at 6:39 PM, James Bottomley wrote: > On Tue, 2016-05-17 at 23:53 +0200, Miklos Szeredi wrote: >> The two methods essentially do the same: find the real dentry/inode >> belonging to an overlay dentry. The difference is in the usage: >>

Re: [RFC PATCH 0/2] scpi: Add SCPI framework to handle vendors variants

Hi, On 05/26/2016 06:29 PM, Sudeep Holla wrote: > Hi Neil, > > On 26/05/16 10:38, Neil Armstrong wrote: >> Since the current SCPI implementation, based on [0]: >> - is (at leat) JUNO specific > > Agreed. > >> - does not specify a strong "standard" > > Not exactly, it's extensible. Refer

Re: [Intel-gfx] [v4.6-10530-g28165ec7a99b] i915: *ERROR* "CPU pipe/PCH transcoder" A FIFO underrun

On 25 May 2016 at 08:31, Sedat Dilek wrote: > Hi Daniel, > > with latest Linus Git I see this with my Intel SandyBridge GPU... > > [ 17.629014] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] > *ERROR* CPU pipe A FIFO underrun > [ 17.630652]

[PATCH v4 2/4] thermal: streamline get_trend callbacks

From: Sascha Hauer The .get_trend callback in struct thermal_zone_device_ops has the prototype: int (*get_trend) (struct thermal_zone_device *, int, enum thermal_trend *); whereas the .get_trend callback in struct

[PATCH v4 0/4] Thermal: Support for hardware-tracked trip points

The history patches come from Mikko and Sascha. http://thread.gmane.org/gmane.linux.power-management.general/59451 Now, I pick them up to continue upstream. Nevermind! This series history patches: v3: https://lkml.org/lkml/2016/5/24/797 v2: https://lkml.org/lkml/2016/5/3/220 v1:

Re: [RFC PATCH 1/3] watchdog: Add Meson GXBB Watchdog Driver

On 05/26/2016 12:06 PM, Carlo Caione wrote: > On 26/05/16 09:51, Neil Armstrong wrote: >> Add watchdog specific driver for Amlogic Meson GXBB SoC. >> >> Signed-off-by: Neil Armstrong >> + > > [...] >> +#define DEFAULT_TIMEOUT 10 /* seconds */ >> + >> +#define

Re: [RFC PATCH 1/3] watchdog: Add Meson GXBB Watchdog Driver

On 05/26/2016 03:54 PM, Guenter Roeck wrote: > On 05/26/2016 12:51 AM, Neil Armstrong wrote: >> Add watchdog specific driver for Amlogic Meson GXBB SoC. >> > > Wondering - why RFC ? For these precious comments ! Thanks Guenter. > >> Signed-off-by: Neil Armstrong >>

[PATCH v4 4/4] thermal: rockchip: add the set_trips function

Whenever the current temperature is updated, the trip points immediately below and above the current temperature are found. A sensor driver callback `set_trips' is then called with the temperatures. Lastly, The sensor will trigger the hardware high temperature interrupts to increase the sampleing

[PATCH v4 3/4] thermal: bang-bang governor: act on lower trip boundary

From: Sascha Hauer With interrupt driven thermal zones we pass the lower and upper temperature on which shall be acted, so in the governor we have to act on the exact lower temperature to be consistent. Otherwise an interrupt maybe generated on the exact lower

[PATCH v4 1/4] thermal: of: implement .set_trips for device tree thermal zones

From: Sascha Hauer This patch implements .set_trips for device tree thermal zones. As the hardware-tracked trip points is supported by thermal core patch[0]. patch[0] "thermal: Add support for hardware-tracked trip points". Signed-off-by: Sascha Hauer

Re: [PATCH 5/7] zram: use crypto api to check alg availability

On Fri, May 27, 2016 at 04:50:52PM +0900, Sergey Senozhatsky wrote: > On (05/27/16 13:43), Minchan Kim wrote: > [..] > > > modprobe zram > > > cat /proc/crypto | grep -i lz4 > > > modprobe lz4 > > > cat /proc/crypto | grep -i lz4 > > > name : lz4 > > > driver : lz4-generic > > >

Re: [PATCH 2/6] Documentation: bindings: add dt doc for Rockchip USB Type-C PHY

Hi Chris, Am Freitag, 27. Mai 2016, 14:02:15 schrieb Chris Zhong: > This patch adds a binding that describes the Rockchip USB Type-C PHY > for rk3399. > > Signed-off-by: Chris Zhong > --- > > .../devicetree/bindings/phy/phy-rockchip-typec.txt | 55 > ++

Re: [PATCH v3 4/4] soc: Add SoC driver for Freescale Vybrid platform

On Friday, May 27, 2016 12:03:01 PM CEST maitysancha...@gmail.com wrote: > > So if I understand correctly, the binding at the SoC level is fine. > Keeping that but removing the additional made-up properties, viz. below > > rom-revision: phandle to the on-chip ROM node > mscm: phandle to the MSCM

Re: [PATCH -v2 4/6] locking, arch: Update spin_unlock_wait()

On Thu, 26 May 2016 16:19:26 +0200 Peter Zijlstra wrote: > This patch updates/fixes all spin_unlock_wait() implementations. > > The update is in semantics; where it previously was only a control > dependency, we now upgrade to a full load-acquire to match the >

[RESEND PATCH v4 1/5] thermal: Add support for hardware-tracked trip points

From: Sascha Hauer This adds support for hardware-tracked trip points to the device tree thermal sensor framework. The framework supports an arbitrary number of trip points. Whenever the current temperature is updated, the trip points immediately below and above the

Re: [PATCH] arm64: defconfig: Enable cros-ec and battery driver

On 05/25/2016 09:44 PM, Rhyland Klein wrote: > On 5/25/2016 1:26 PM, Jon Hunter wrote: >> >> On 25/05/16 17:36, Rhyland Klein wrote: >> >> ... >> >>> I can see that getting the temperature could work. I would point out >>> that I don't see any recent changes to bq27xxx or the power_supply_core >>>

[RESEND PATCH v4 5/5] thermal: rockchip: add the set_trips function

Whenever the current temperature is updated, the trip points immediately below and above the current temperature are found. A sensor driver callback `set_trips' is then called with the temperatures. Lastly, The sensor will trigger the hardware high temperature interrupts to increase the sampleing

[RESEND PATCH v4 4/5] thermal: bang-bang governor: act on lower trip boundary

From: Sascha Hauer With interrupt driven thermal zones we pass the lower and upper temperature on which shall be acted, so in the governor we have to act on the exact lower temperature to be consistent. Otherwise an interrupt maybe generated on the exact lower

[RESEND PATCH v4 3/5] thermal: streamline get_trend callbacks

From: Sascha Hauer The .get_trend callback in struct thermal_zone_device_ops has the prototype: int (*get_trend) (struct thermal_zone_device *, int, enum thermal_trend *); whereas the .get_trend callback in struct

[RESEND PATCH v4 2/5] thermal: of: implement .set_trips for device tree thermal zones

From: Sascha Hauer This patch implements .set_trips for device tree thermal zones. As the hardware-tracked trip points is supported by thermal core patch[0]. patch[0] "thermal: Add support for hardware-tracked trip points". Signed-off-by: Sascha Hauer

Re: [PATCH v2 2/3] mm, thp: fix possible circular locking dependency caused by sum_vm_event()

Hi Ebru, On Fri, May 27, 2016 at 10:59:23AM +0300, Ebru Akagunduz wrote: > Nested circular locking dependency detected by kernel robot (udevadm). > > udevadm/221 is trying to acquire lock: >(>mmap_sem){++}, at: [] __might_fault+0x83/0x150 > but task is already holding lock: >

Re: [PATCH v4 0/4] Thermal: Support for hardware-tracked trip points

Forget to send a patch, sorry for the noise.:-( Please ignore this series patches [PATCH v4 0/4]. RESEND the new series patches "[RESEND PATCH v4 0/5]". On 2016年05月27日 16:23, Caesar Wang wrote: The history patches come from Mikko and Sascha.

Re: [PATCH] pinctrl: samsung: Suppress unbinding to prevent theoretical attacks

On 05/26/2016 11:08 AM, Linus Walleij wrote: > On Tue, May 17, 2016 at 8:02 AM, Krzysztof Kozlowski > wrote: > >> Although unbinding a pinctrl driver requires root privileges but it >> still might be used theoretically in certain attacks (by triggering NULL >> pointer

Re: [PATCH 5/7] zram: use crypto api to check alg availability

On Fri, May 27, 2016 at 05:27:44PM +0900, Minchan Kim wrote: > > Yes, it might be trivial to adding new "string" into the backend array > if we consider frequency of adding new compressoin algorithm in linux > but it would be better if we can get names of supported compression > algorithm name by

Re: [PATCH 01/23] all: syscall wrappers: add documentation

On Friday, May 27, 2016 8:03:57 AM CEST Heiko Carstens wrote: > > > > > Cost wise, this seems like it all cancels out in the end, but what > > > > > do I know? > > > > > > > > I think you know something, and I also think Heiko and other s390 guys > > > > know something as well. So I'd like to

Re: [PATCH v5 3/5] perf callchain: Add support for cross-platform unwind

On Fri, May 27, 2016 at 04:02:59PM +0800, Hekuang wrote: SNIP > > > The only concern is that, if later we support more platforms, > > > there will be too much files named as > > > 'tools/perf/util/unwind-libunwind*.c' > > > Is it acceptable or not? > > > > > > And I thought all files belongs

Re: [PATCH 2/6] Documentation: bindings: add dt doc for Rockchip USB Type-C PHY

Hi Heiko On 05/27/2016 04:29 PM, Heiko Stuebner wrote: Hi Chris, Am Freitag, 27. Mai 2016, 14:02:15 schrieb Chris Zhong: This patch adds a binding that describes the Rockchip USB Type-C PHY for rk3399. Signed-off-by: Chris Zhong ---

linux-next memleak after IO on dax mountpoint

Hi, Reporting an oom/memleak issue in linux-next tree: #Description: dbench invokes oom-killer, make host unavaiable. dbench was doing IO on nvdimm device mounted fs with dax mount option. It happens on both xfs and ext4 filesystems. It does not happen testing without dax mountoption. Seems

[PATCH v3 4/5] iommu/mediatek: add support for mtk iommu generation one HW

From: Honghui Zhang Mediatek SoC's M4U has two generations of HW architcture. Generation one uses flat, one layer pagetable, and was shipped with ARM architecture, it only supports 4K size page mapping. MT2701 SoC uses this generation one m4u HW. Generation two uses

Re: [PATCH 01/23] all: syscall wrappers: add documentation

On Fri, May 27, 2016 at 08:03:57AM +0200, Heiko Carstens wrote: > > > > The cost is pretty trivial though. See kernel/compat_wrapper.o: > > > > COMPAT_SYSCALL_WRAP2(creat, const char __user *, pathname, umode_t, > > > > mode); > > > > 0: a9bf7bfdstp x29, x30, [sp,#-16]! > > > > 4:

Re: [PATCH v3 02/12] of: add J-Core cpu bindings

On Thu, May 26, 2016 at 11:33:23AM -0400, Rich Felker wrote: > On Thu, May 26, 2016 at 11:38:29AM +0100, Mark Rutland wrote: > > On Wed, May 25, 2016 at 07:04:08PM -0400, Rich Felker wrote: > > > On Wed, May 25, 2016 at 11:22:15AM +0100, Mark Rutland wrote: > > > > * How must the value be written?

Re: Rcu synchronization of a list

On Fri, May 27, 2016 at 12:40:51PM +0300, Nikolay Borisov wrote: > Hello, > > I'm currently dealing with a synchronization scheme which utilizes RCU > but I'm observing a race condition. So I have an rcu-enabled list, which > contains various entries. The add/delete paths of the list are

Re: [PATCH v3 5/6] pv-qspinlock: use cmpxchg_release in __pv_queued_spin_unlock

On 2016年05月27日 00:57, Peter Zijlstra wrote: On Thu, May 26, 2016 at 06:47:29PM +0200, Peter Zijlstra wrote: On Wed, May 25, 2016 at 04:18:08PM +0800, Pan Xinhui wrote: cmpxchg_release is light-wight than cmpxchg, we can gain a better performace then. On some arch like ppc, barrier impact the

[RESEND PATCH 1/6] phy: Add USB Type-C PHY driver for rk3399

Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB Type-C PHY is designed to support the USB3 and DP applications. The PHY basically has two main components: USB3 and DisplyPort. USB3 operates in SuperSpeed mode and the DP can operate at RBR, HBR and HBR2 data rates. Signed-off-by:

[RESEND PATCH 3/6] drm/rockchip: vop: add cdn DP support for rk3399

Add support for cdn DP controller which is embedded in the rk3399 SoCs. The DP is compliant with DisplayPort Specification, Version 1.3, This IP is compatible with the rockchip type-c PHY IP. There is a uCPU in DP controller, it need a firmware to work, please put the firmware file to

[RESEND PATCH 5/6] ASoC: cdn-dp: Add cdn DP codec driver

codec driver get some interfaces from cdn-dp driver, than using those to set DP audio formats, corresponding to alsa formats. Signed-off-by: Chris Zhong --- sound/soc/codecs/Kconfig| 3 + sound/soc/codecs/Makefile | 2 + sound/soc/codecs/cdn-dp-audio.c |

[RESEND PATCH 4/6] Documentation: bindings: add dt documentation for cdn DP controller

This patch adds a binding that describes the cdn DP controller for rk3399. Signed-off-by: Chris Zhong --- .../bindings/display/rockchip/cdn-dp-rockchip.txt | 57 ++ 1 file changed, 57 insertions(+) create mode 100644

[RESEND PATCH 6/6] ASoC: rockchip: Add machine driver for cdn dp codec

The driver is used for cdn dp codec embedded in rk3399 Signed-off-by: Chris Zhong --- .../bindings/sound/rockchip-cdn-dp-audio.txt | 12 ++ sound/soc/rockchip/Kconfig | 9 ++ sound/soc/rockchip/Makefile| 2 +

[RESEND PATCH 0/6] Rockchip Type-C and DispplayPort driver

Sorry, forgot a head file in patch 1, so resend. Hi all This series patch is for rockchip Type-C phy and DisplayPort controller driver. The USB Type-C PHY is designed to support the USB3 and DP applications. The PHY basically has two main components: USB3 and DisplyPort. USB3 operates in

[RESEND PATCH 2/6] Documentation: bindings: add dt doc for Rockchip USB Type-C PHY

This patch adds a binding that describes the Rockchip USB Type-C PHY for rk3399. Signed-off-by: Chris Zhong --- .../devicetree/bindings/phy/phy-rockchip-typec.txt | 55 ++ 1 file changed, 55 insertions(+) create mode 100644

Re: [PATCH] dell-smm-hwmon: Cache fan_type() calls and use fan_status() for fan detection

On Friday 27 May 2016 12:01:21 Thorsten Leemhuis wrote: > Pali Rohár wrote on 27.05.2016 11:47: > > […] > > I do not see any long taking SMM call here. Are you really sure > > that your machine freeze when loading or using dell-smm-hwmon? > > Uhh, sorry, it seems something got mixed up somewhere.

Re: [PATCH v4] z3fold: the 3-fold allocator for compressed pages

On Fri, May 27, 2016 at 6:55 AM, Vitaly Wool wrote: > Hello Dan, > > On Fri, May 20, 2016 at 2:39 PM, Dan Streetman wrote: > > >>> +static int z3fold_compact_page(struct z3fold_header *zhdr) >>> +{ >>> + struct page *page = virt_to_page(zhdr); >>>

[RFC v2 0/3] Introduce the bulk mode method when sending request to crypto layer

This patchset will check if the cipher can support bulk mode, then dm-crypt will handle different ways to send requests to crypto layer according to cipher mode. For bulk mode, we can use sg table to map the whole bio and send all scatterlists of one bio to crypto engine to encrypt or decrypt,

Re: [PATCH] seqlock: fix raw_read_seqcount_latch()

On Sat, May 21, 2016 at 11:14:49PM +0300, Alexey Dobriyan wrote: > lockless_dereference() is supposed to take pointer not integer. > > Signed-off-by: Alexey Dobriyan > --- > > include/linux/seqlock.h |4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > ---

Re: [PATCH] arm64: defconfig: Enable cros-ec and battery driver

On 05/27/2016 12:28 PM, Jon Hunter wrote: > Hi Krzysztof, > > On 27/05/16 09:37, Krzysztof Kozlowski wrote: > > ... > >> Indeed I was struggling with similar issue in bq27x00_battery. The issue >> was introduced by... me :( when moving the ownership of power supply >> structure from driver to

[PATCH] crypto: s5p-sss - Use consistent indentation for variables and members

Bring some consistency by: 1. Replacing fixed-space indentation of structure members with just tabs. 2. Remove indentation in declaration of local variable between type and name. Driver was mixing usage of such indentation and lack of it. When removing indentation, reorder variables in

[PATCH 14/15] mtd: nand: hynix: rework NAND ID decoding to extract more information

The current NAND ID detection in nand_hynix.c is not handling the different scheme used by Hynix, thus forcing developers to add new entries in the nand_ids table each time they want to support a new MLC NAND. Enhance the detection logic to handle all known formats. This does not necessarily mean

Re: [PATCH v2 8/8] Input: atmel_mxt_ts - add support for reference data

On 05/04/2016 07:07 PM, Nick Dyer wrote: > There are different datatypes available from a maXTouch chip. Add > support to retrieve reference data as well. > > Signed-off-by: Nick Dyer > --- > drivers/input/touchscreen/atmel_mxt_ts.c | 66 >

Re: [PATCH 0/3] mm, thp: remove duplication and fix locking issues in swapin

On Mon 23-05-16 20:29:29, Ebru Akagunduz wrote: > On Mon, May 23, 2016 at 08:14:08PM +0300, Ebru Akagunduz wrote: > > This patch series removes duplication of included header > > and fixes locking inconsistency in khugepaged swapin > > > > Ebru Akagunduz (3): > > mm, thp: remove duplication of

Re: [PATCH] hwrng: stm32 - fix build warning

On Wednesday 25 May 2016 03:36 PM, Arnd Bergmann wrote: On Wednesday, May 25, 2016 7:35:17 AM CEST Sudip Mukherjee wrote: On Tuesday 24 May 2016 02:05 AM, Arnd Bergmann wrote: On Monday, May 23, 2016 6:14:08 PM CEST Sudip Mukherjee wrote: We have been getting build warning about:

[PATCH 2/2] usb: phy: phy-brcm-usb: Add Broadcom STB USB Phy driver

Add a new USB Phy driver for Broadcom STB SoCs. This driver supports all Broadcom STB ARM SoCs. This driver in combination with the generic ohci, ehci and xhci platform drivers will enable USB1.1, USB2.0 and USB3.0 support. This Phy driver also supports the Broadcom UDC gadget driver.

Re: [PATCH] drivers: usb: dwc3 : Configure DMA properties and ops from DT

Hi, Leo Li writes: >> Leo Li writes: > On certain platforms (e.g. ARM64) the dma_ops needs to be explicitly set > to be able to do DMA allocations, so use the of_dma_configure() helper > to populate the dma properties and assign an appropriate

Re: [4.1.x -- 4.6.x and probably HEAD] Reproducible unprivileged panic/TLB BUG on sparc via a stack-protected rt_sigaction() ka_restorer, courtesy of the glibc testsuite

Hi Nick! On 05/27/2016 03:19 PM, Nick Alcock wrote: > So I've been working on a patch series (see below) that applies GCC's > -fstack-protector{-all,-strong} to almost all of glibc bar the dynamic > linker. In trying to upstream it, one review commenter queried one > SPARC-specific patch in the

Re: [4.1.x -- 4.6.x and probably HEAD] Reproducible unprivileged panic/TLB BUG on sparc via a stack-protected rt_sigaction() ka_restorer, courtesy of the glibc testsuite

On 27 May 2016, John Paul Adrian Glaubitz outgrape: > Hi Nick! > > On 05/27/2016 03:19 PM, Nick Alcock wrote: >> So I've been working on a patch series (see below) that applies GCC's >> -fstack-protector{-all,-strong} to almost all of glibc bar the dynamic >> linker. In trying to upstream it, one

[RFC v2 3/3] ASoC: msm8916: Add msm8916-wcd codec driver

This patch adds support to msm8916-wcd codec. msm8916-wcd codec is found in Qualcomm msm8916 and apq8016 processors. This codec IP is split in to two parts(Digital & Analog), Analog part is integrated in to PMIC PM8916 and the digital part is integrated into Application processor. Register access

[RFC v2 0/3] ASoC: Add support to Qualcomm msm8916-wcd codec

This patchset aims at adding msm8916-wcd codec support. msm8916-wcd codec is found in Qualcomm msm8916 and apq8016 processors. This codec IP is split in to two parts(Digital & Analog), Analog part is integrated in to PMIC PM8916 and the digital part is integrated into Application processor.

[RFC v2 1/3] ASoC: msm8916: Add codec Device Tree bindings.

This patch adds DT bindings required for msm8916 codec which is integrated in msm8916 and apq8016 SOCs. Codec IP is divided into two parts, first analog which is integrated in pmic pm8916 and secondly digital part which is integrated into application processor. Codec register controls are also

Re: [PATCH RT] kernel/printk: Don't try to print from IRQ/NMI region

On Fri, 27 May 2016 15:58:12 +0200 Sebastian Andrzej Siewior wrote: > On -RT we try to acquire sleeping locks which might lead to warnings > from lockdep or a warn_on() from spin_try_lock() (which is a rtmutex on > RT). > We don't print in general from a IRQ off region so

Re: [PATCH] soc/tegra: pmc: Fix "scheduling while atomic"

On 27.05.2016 15:46, Jon Hunter wrote: On 26/05/16 18:01, Dmitry Osipenko wrote: On 26.05.2016 18:27, Jon Hunter wrote: On 26/05/16 15:57, Dmitry Osipenko wrote: ... That's how I see it: +--+ |CPU 0 |

[PATCH 06/15] mtd: nand: kill the MTD_NAND_IDS Kconfig option

MTD_NAND_IDS is selected by MTD_NAND, which makes it useless. Remove the Kconfig option and link nand_ids.o into the nand.o object file. Doing that also prevents adding an extra nand_ids.ko module when MTD_NAND is activated as a module. Signed-off-by: Boris Brezillon

[PATCH 05/15] mtd: nand: add vendor specific initialization step

A lot of NANDs are implementing generic features in a non-generic way, or are providing advanced auto-detection logic where the NAND ID bytes meaning changes with the NAND generation. Providing this vendor specific initialization step will allow us to get rid of the full ids in the nand_ids table

Re: [PATCH] dell-smm-hwmon: Cache fan_type() calls and use fan_status() for fan detection

Pali Rohár wrote on 27.05.2016 12:45: > […] > Looks like there are two different problems with dell-smm-hwmon driver: > 1) Fan speed going randomly up and down without system freeze > […] > So for problem 1) I need to know: > > * Is it regression? […] Yes, it is known to be a regression from

Re: [PATCH v4 01/18] remoteproc: st_xp70_rproc: add a xp70 slimcore rproc driver

On 05/25/2016 06:06 PM, Peter Griffin wrote: XP70 slim core is used as a basis for many IPs in the STi chipsets such as fdma, display, and demux. To avoid duplicating the elf loading code in each device driver an xp70 rproc driver has been created. This driver is designed to be used by other

Re: [PATCH v2 1/2] media: Media Device Allocator API

On 05/25/2016 01:39 AM, Shuah Khan wrote: > Media Device Allocator API to allows multiple drivers share a media device. > Using this API, drivers can allocate a media device with the shared struct > device as the key. Once the media device is allocated by a driver, other > drivers can get a

Re: [RFC/PATCH 1/2] doc: bindings: Add bindings documentation for mtd otp nvmem

Hi Moritz, On Thu, 26 May 2016 10:28:48 -0700 Moritz Fischer wrote: > Hi Boris, > > On Thu, May 26, 2016 at 1:04 AM, Boris Brezillon > wrote: > > > I think the MTD partition -> nvmem connection could benefit to non-OTP > >

[PATCH RT] kernel/printk: Don't try to print from IRQ/NMI region

On -RT we try to acquire sleeping locks which might lead to warnings from lockdep or a warn_on() from spin_try_lock() (which is a rtmutex on RT). We don't print in general from a IRQ off region so we should not try this via console_unblank() / bust_spinlocks() as well. Signed-off-by: Sebastian

Re: [RFC PATCH] usb: typec: Various API updates and fixes

On 05/27/2016 12:55 AM, Heikki Krogerus wrote: Hi, [ ... ] --- This patch applies on top of '[RFC PATCHv2] usb: USB Type-C Connector Class' from Heikki Krogerus. It provided the changes I made to get the code operational. drivers/usb/type-c/typec.c | 134

  1   2   3   4   5   6   7   8   9   10   >