Re: [PATCH 01/10] Documentation: dt-bindings: mailbox: tegra: Add binding for HSP mailbox

On 06/29/2016 03:08 AM, Stephen Warren wrote: On 06/28/2016 03:15 AM, Joseph Lo wrote: On 06/27/2016 11:55 PM, Stephen Warren wrote: On 06/27/2016 03:02 AM, Joseph Lo wrote: snip. Currently the usage of HSP HW in the downstream kernel is something like the model below. remote_processor_A-\

Re: [PATCH 01/10] Documentation: dt-bindings: mailbox: tegra: Add binding for HSP mailbox

On 06/29/2016 03:08 AM, Stephen Warren wrote: On 06/28/2016 03:15 AM, Joseph Lo wrote: On 06/27/2016 11:55 PM, Stephen Warren wrote: On 06/27/2016 03:02 AM, Joseph Lo wrote: snip. Currently the usage of HSP HW in the downstream kernel is something like the model below. remote_processor_A-\

[PATCH v5 0/5] regulator: add Ricoh RN5T567 PMIC support

This patchset adds RN5T567 PMIC support which is used on the Toradex Colibri iMX7S/iMX7D modules. The existing RN5T618 is from the same family, hence this patchset uses the same driver and adds variant support. The Colibris currently do not use the PMIC's power off capabilities, as do the

[PATCH v5 4/5] mfd: rn5t618: register power off callback optionally

Only register power off if the PMIC is defined as system power controller (see Documentation/devicetree/bindings/power/ power-controller.txt). Signed-off-by: Stefan Agner Reviewed-by: Marcel Ziswiler Acked-by: Lee Jones ---

[PATCH v5 4/5] mfd: rn5t618: register power off callback optionally

Only register power off if the PMIC is defined as system power controller (see Documentation/devicetree/bindings/power/ power-controller.txt). Signed-off-by: Stefan Agner Reviewed-by: Marcel Ziswiler Acked-by: Lee Jones --- drivers/mfd/rn5t618.c | 10 +++--- 1 file changed, 7

[PATCH v5 0/5] regulator: add Ricoh RN5T567 PMIC support

This patchset adds RN5T567 PMIC support which is used on the Toradex Colibri iMX7S/iMX7D modules. The existing RN5T618 is from the same family, hence this patchset uses the same driver and adds variant support. The Colibris currently do not use the PMIC's power off capabilities, as do the

[PATCH v5 5/5] mfd: rn5t618: register restart handler

Use the PMIC's repower capability for reboots. Register a restart handler and use a slightly elevated priority of 192 since the PMIC has suprior reset capability (causing a system wide reset). Signed-off-by: Stefan Agner Reviewed-by: Marcel Ziswiler

[PATCH v5 5/5] mfd: rn5t618: register restart handler

Use the PMIC's repower capability for reboots. Register a restart handler and use a slightly elevated priority of 192 since the PMIC has suprior reset capability (causing a system wide reset). Signed-off-by: Stefan Agner Reviewed-by: Marcel Ziswiler Acked-by: Lee Jones ---

Re: [PATCH 74/92] clocksource/drivers/bcm_kona: Remove useless header

Hi Daniel, On 6/28/2016 3:31 AM, Daniel Lezcano wrote: The driver includes the header but it is pointless. Remove it. Signed-off-by: Daniel Lezcano --- drivers/clocksource/bcm_kona_timer.c | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCH v5 2/5] mfd: add Ricoh RN5T567 PMIC support

The Ricoh RN5T567 is from the same family as the Ricoh RN5T618 is, the differences are: + DCDC4 + Slightly different output voltage/currents + 32kHz Output - ADC/Charger capabilities Signed-off-by: Stefan Agner Reviewed-by: Marcel Ziswiler

[PATCH v5 3/5] regulator: rn5t618: add RN5T567 PMIC support

Extend the driver to support Ricoh RN5T567. Support the additional DCDC and slightly different voltage range of LDORTC1. Signed-off-by: Stefan Agner Reviewed-by: Marcel Ziswiler Acked-by: Mark Brown Acked-by: Lee Jones

[PATCH v5 1/5] ARM: dts: meson: minix-neo-x8: define PMIC as power controller

The PMIC driver used to register itself as poweroff controller by default, hence assuming that this device is using the PMIC as system power controller. Signed-off-by: Stefan Agner Reviewed-by: Marcel Ziswiler Acked-by: Carlo Caione

Re: [PATCH 74/92] clocksource/drivers/bcm_kona: Remove useless header

Hi Daniel, On 6/28/2016 3:31 AM, Daniel Lezcano wrote: The driver includes the header but it is pointless. Remove it. Signed-off-by: Daniel Lezcano --- drivers/clocksource/bcm_kona_timer.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/clocksource/bcm_kona_timer.c

[PATCH v5 2/5] mfd: add Ricoh RN5T567 PMIC support

The Ricoh RN5T567 is from the same family as the Ricoh RN5T618 is, the differences are: + DCDC4 + Slightly different output voltage/currents + 32kHz Output - ADC/Charger capabilities Signed-off-by: Stefan Agner Reviewed-by: Marcel Ziswiler Acked-by: Rob Herring Acked-by: Lee Jones ---

[PATCH v5 3/5] regulator: rn5t618: add RN5T567 PMIC support

Extend the driver to support Ricoh RN5T567. Support the additional DCDC and slightly different voltage range of LDORTC1. Signed-off-by: Stefan Agner Reviewed-by: Marcel Ziswiler Acked-by: Mark Brown Acked-by: Lee Jones --- drivers/regulator/Kconfig | 5 +++--

[PATCH v5 1/5] ARM: dts: meson: minix-neo-x8: define PMIC as power controller

The PMIC driver used to register itself as poweroff controller by default, hence assuming that this device is using the PMIC as system power controller. Signed-off-by: Stefan Agner Reviewed-by: Marcel Ziswiler Acked-by: Carlo Caione --- arch/arm/boot/dts/meson8-minix-neo-x8.dts | 1 + 1 file

DONATION OF $ 1.5 MILLION DOLLARS!!!

My wife and I have awarded you with a donation of $ 1.5 million Dollars from part of our Jackpot Lottery of 161,653,000 Million Pounds,Send your name,Address, Phone for claims Now. To verify the genuineness of this email, check this web page;

DONATION OF $ 1.5 MILLION DOLLARS!!!

My wife and I have awarded you with a donation of $ 1.5 million Dollars from part of our Jackpot Lottery of 161,653,000 Million Pounds,Send your name,Address, Phone for claims Now. To verify the genuineness of this email, check this web page;

DONATION OF $ 1.5 MILLION DOLLARS!!!

My wife and I have awarded you with a donation of $ 1.5 million Dollars from part of our Jackpot Lottery of 161,653,000 Million Pounds,Send your name,Address, Phone for claims Now. To verify the genuineness of this email, check this web page;

DONATION OF $ 1.5 MILLION DOLLARS!!!

My wife and I have awarded you with a donation of $ 1.5 million Dollars from part of our Jackpot Lottery of 161,653,000 Million Pounds,Send your name,Address, Phone for claims Now. To verify the genuineness of this email, check this web page;

[PATCH] mm, vmscan: Give up balancing node for high order allocations earlier

To avoid excessive reclaim, we give up rebalancing for high order allocations right after reclaiming enough pages. Signed-off-by: Hillf Danton --- mm/vmscan.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/mm/vmscan.c b/mm/vmscan.c index

[PATCH] mm, vmscan: Give up balancing node for high order allocations earlier

To avoid excessive reclaim, we give up rebalancing for high order allocations right after reclaiming enough pages. Signed-off-by: Hillf Danton --- mm/vmscan.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/mm/vmscan.c b/mm/vmscan.c index ee7e531..d080fb2 100644 ---

Re: linux-next: manual merge of the kvm tree with the s390 tree

On Wed, Jun 29, 2016 at 02:36:58PM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the kvm tree got a conflict in: > > arch/s390/hypfs/hypfs_diag.c > > between commit: > > e030c1125eab ("s390/hypfs: use basic block for diag inline assembly") > > from the s390 tree

Re: linux-next: manual merge of the kvm tree with the s390 tree

On Wed, Jun 29, 2016 at 02:36:58PM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the kvm tree got a conflict in: > > arch/s390/hypfs/hypfs_diag.c > > between commit: > > e030c1125eab ("s390/hypfs: use basic block for diag inline assembly") > > from the s390 tree

Re: [PATCH v12 0/3] printk: Make printk() completely async

On (06/28/16 22:16), Joe Perches wrote: > On Wed, 2016-06-29 at 14:08 +0900, Sergey Senozhatsky wrote: > > the patch to fix the async KERN_CONT printk regression I mentioned > > several days ago in another thread. > > KERN_CONT is effectively a no-op. > This is any printk without a KERN_ if the

Re: [PATCH v12 0/3] printk: Make printk() completely async

On (06/28/16 22:16), Joe Perches wrote: > On Wed, 2016-06-29 at 14:08 +0900, Sergey Senozhatsky wrote: > > the patch to fix the async KERN_CONT printk regression I mentioned > > several days ago in another thread. > > KERN_CONT is effectively a no-op. > This is any printk without a KERN_ if the

Re: linux-next: manual merge of the powerpc tree with Linus' tree

On 2016/06/29 10:35AM, Stephen Rothwell wrote: > Hi all, Hi Stephen, > > Today's linux-next merge of the powerpc tree got a conflict in: > > arch/powerpc/Kconfig > > between commit: > > 844e3be47693 ("powerpc/bpf/jit: Disable classic BPF JIT on ppc64le") Ah, I see that the above commit

Re: linux-next: manual merge of the powerpc tree with Linus' tree

On 2016/06/29 10:35AM, Stephen Rothwell wrote: > Hi all, Hi Stephen, > > Today's linux-next merge of the powerpc tree got a conflict in: > > arch/powerpc/Kconfig > > between commit: > > 844e3be47693 ("powerpc/bpf/jit: Disable classic BPF JIT on ppc64le") Ah, I see that the above commit

Re: [PATCH] platform:x86 Remove Monitor MWAIT feature dependency

On Thu, Jun 23, 2016 at 02:59:58PM +0800, ong.hock...@intel.com wrote: > From: "Yu, Ong Hock" > > Telemetry capability does not depend on Monitor MWAIT feature. Thank you Ong Hock, queued to testing for 4.8. > > Signed-off-by: Yu, Ong Hock > --- >

Re: [PATCH] platform:x86 Remove Monitor MWAIT feature dependency

On Thu, Jun 23, 2016 at 02:59:58PM +0800, ong.hock...@intel.com wrote: > From: "Yu, Ong Hock" > > Telemetry capability does not depend on Monitor MWAIT feature. Thank you Ong Hock, queued to testing for 4.8. > > Signed-off-by: Yu, Ong Hock > --- >

Re: [PATCH] [linux-next] rtlwifi: Fix typo in printk

On 06/28/2016 10:37 PM, Masanari Iida wrote: This patch fix spelling typos found in drivers/net/wireless/realtek. Signed-off-by: Masanari Iida Acked--by: Larry Finger Thanks, Larry ---

Re: [PATCH] [linux-next] rtlwifi: Fix typo in printk

On 06/28/2016 10:37 PM, Masanari Iida wrote: This patch fix spelling typos found in drivers/net/wireless/realtek. Signed-off-by: Masanari Iida Acked--by: Larry Finger Thanks, Larry --- drivers/net/wireless/realtek/rtlwifi/rtl8188ee/phy.c | 2 +-

Re: [PATCH] platform/x86: Add IIO dependency to ACPI_TOSHIBA

2016-06-28 23:16 GMT-06:00 Darren Hart : > On Tue, Jun 28, 2016 at 01:58:55PM -0600, Azael Avalos wrote: >> The toshiba_acpi driver added support to the accelerometer axis >> via the IIO subsystem, but failed to add the dependency to the >> Kconfig file, making the driver

Re: [PATCH] platform/x86: Add IIO dependency to ACPI_TOSHIBA

2016-06-28 23:16 GMT-06:00 Darren Hart : > On Tue, Jun 28, 2016 at 01:58:55PM -0600, Azael Avalos wrote: >> The toshiba_acpi driver added support to the accelerometer axis >> via the IIO subsystem, but failed to add the dependency to the >> Kconfig file, making the driver fail to compile if the

Re: [PATCH v12 0/3] printk: Make printk() completely async

On Wed, 2016-06-29 at 14:08 +0900, Sergey Senozhatsky wrote: > the patch to fix the async KERN_CONT printk regression I mentioned > several days ago in another thread. KERN_CONT is effectively a no-op. This is any printk without a KERN_

Re: [PATCH] platform/x86: Add IIO dependency to ACPI_TOSHIBA

On Tue, Jun 28, 2016 at 01:58:55PM -0600, Azael Avalos wrote: > The toshiba_acpi driver added support to the accelerometer axis > via the IIO subsystem, but failed to add the dependency to the > Kconfig file, making the driver fail to compile if the IIO > subsystem is not selected. > > This patch

Re: [PATCH v12 0/3] printk: Make printk() completely async

On Wed, 2016-06-29 at 14:08 +0900, Sergey Senozhatsky wrote: > the patch to fix the async KERN_CONT printk regression I mentioned > several days ago in another thread. KERN_CONT is effectively a no-op. This is any printk without a KERN_

Re: [PATCH] platform/x86: Add IIO dependency to ACPI_TOSHIBA

On Tue, Jun 28, 2016 at 01:58:55PM -0600, Azael Avalos wrote: > The toshiba_acpi driver added support to the accelerometer axis > via the IIO subsystem, but failed to add the dependency to the > Kconfig file, making the driver fail to compile if the IIO > subsystem is not selected. > > This patch

[PATCH 1/2] x86/apic: shutdown local APIC before I/O APIC during crash

commit <522e66464467> disables I/O APIC before shutdown of the local APIC for both reboot and crash path. and commit <2885432aaf15> declares that 'it still makes sense to quiet IO APIC before disabling Local APIC'. However, the former introduced a bug for crashdown. If specify 'notsc' for

[PATCH 1/2] x86/apic: shutdown local APIC before I/O APIC during crash

commit <522e66464467> disables I/O APIC before shutdown of the local APIC for both reboot and crash path. and commit <2885432aaf15> declares that 'it still makes sense to quiet IO APIC before disabling Local APIC'. However, the former introduced a bug for crashdown. If specify 'notsc' for

Re: [RESEND PATCH] x86/mm: only allow memmap=XX!YY over existing RAM

On Wed, Jun 29, 2016 at 4:09 AM, Dan Williams wrote: > > On Tue, Jun 28, 2016 at 10:58 AM, H. Peter Anvin wrote: > > On 06/28/16 09:33, Dan Williams wrote: > >> On Tue, Jun 28, 2016 at 1:31 AM, Yigal Korman wrote: > >>> Before this

Re: [RESEND PATCH] x86/mm: only allow memmap=XX!YY over existing RAM

On Wed, Jun 29, 2016 at 4:09 AM, Dan Williams wrote: > > On Tue, Jun 28, 2016 at 10:58 AM, H. Peter Anvin wrote: > > On 06/28/16 09:33, Dan Williams wrote: > >> On Tue, Jun 28, 2016 at 1:31 AM, Yigal Korman wrote: > >>> Before this patch, passing a range that is beyond the physical memory > >>>

Re: [PATCH 1/1] gpio: max77620: get gpio value based on direction

On Mon, Jun 27, 2016 at 7:56 PM, Venkat Reddy Talla wrote: > Gpio direction is determined by DIRx bit of GPIO > configuration register, return max77620 gpio value > based on direction in or out. > > Signed-off-by: Venkat Reddy Talla > --- >

Re: [PATCH 1/1] gpio: max77620: get gpio value based on direction

On Mon, Jun 27, 2016 at 7:56 PM, Venkat Reddy Talla wrote: > Gpio direction is determined by DIRx bit of GPIO > configuration register, return max77620 gpio value > based on direction in or out. > > Signed-off-by: Venkat Reddy Talla > --- > drivers/gpio/gpio-max77620.c | 5 - > 1 file

Re: [PATCH v12 0/3] printk: Make printk() completely async

Hello, the patch to fix the async KERN_CONT printk regression I mentioned several days ago in another thread. as a separate patch for now, to ease the review. will squash with 0001. == 8< == >From 70f65ed55eb82a1b8b74fdbd1a7afc9e77e9b380 Mon Sep 17 00:00:00 2001 From:

Re: [PATCH v12 0/3] printk: Make printk() completely async

Hello, the patch to fix the async KERN_CONT printk regression I mentioned several days ago in another thread. as a separate patch for now, to ease the review. will squash with 0001. == 8< == >From 70f65ed55eb82a1b8b74fdbd1a7afc9e77e9b380 Mon Sep 17 00:00:00 2001 From:

Re: [PATCH 1/2] cgroup: pids: show number of failed forks since limit reset

On Sun, Jun 26, 2016 at 09:34:41PM +1000, Aleksa Sarai wrote: If a user has a setup where they wait for notifications on changes to pids.event, and then auto-adjust the cgroup limits based on the number of failures you have a race condition between reading the pids.event file and then setting

Re: Review of ptrace Yama ptrace_scope description

Hi Kees, On 06/28/2016 10:55 PM, Kees Cook wrote: On Mon, Jun 27, 2016 at 11:11 PM, Michael Kerrisk (man-pages) wrote: Hi Jann, On 06/25/2016 04:30 PM, Jann Horn wrote: On Sat, Jun 25, 2016 at 09:30:43AM +0200, Michael Kerrisk (man-pages) wrote: Hi Kees, So,

Re: [PATCH 1/2] cgroup: pids: show number of failed forks since limit reset

On Sun, Jun 26, 2016 at 09:34:41PM +1000, Aleksa Sarai wrote: If a user has a setup where they wait for notifications on changes to pids.event, and then auto-adjust the cgroup limits based on the number of failures you have a race condition between reading the pids.event file and then setting

Re: Review of ptrace Yama ptrace_scope description

Hi Kees, On 06/28/2016 10:55 PM, Kees Cook wrote: On Mon, Jun 27, 2016 at 11:11 PM, Michael Kerrisk (man-pages) wrote: Hi Jann, On 06/25/2016 04:30 PM, Jann Horn wrote: On Sat, Jun 25, 2016 at 09:30:43AM +0200, Michael Kerrisk (man-pages) wrote: Hi Kees, So, last year, I added some

Re: [PATCH v2] clk: fixed-factor: add optional dt-binding clock-flags

On 2016년 06월 29일 05:55, Rob Herring wrote: > On Fri, Jun 24, 2016 at 01:12:52PM +0900, Jongsung Kim wrote: >> There is no way to set additional flags for a DT-initialized fixed- >> factor-clock, and it can be problematic i.e., when the clock rate >> needs to be changed. [1][2] >> >> This patch

Re: [PATCH v2] clk: fixed-factor: add optional dt-binding clock-flags

On 2016년 06월 29일 05:55, Rob Herring wrote: > On Fri, Jun 24, 2016 at 01:12:52PM +0900, Jongsung Kim wrote: >> There is no way to set additional flags for a DT-initialized fixed- >> factor-clock, and it can be problematic i.e., when the clock rate >> needs to be changed. [1][2] >> >> This patch

Re: [PATCH 0/6] scripts/gdb: Fixes for 4.7

On 2016-06-28 17:22, Kieran Bingham wrote: > Hi Andrew, > > Please consider this series for integration into the current rc series. > I had hoped to get this to you, with a fixed radix-tree, rather than a > reverted one. Alas, time has gone against me, and we are nearing the end > of the window -

Re: [PATCH 0/6] scripts/gdb: Fixes for 4.7

On 2016-06-28 17:22, Kieran Bingham wrote: > Hi Andrew, > > Please consider this series for integration into the current rc series. > I had hoped to get this to you, with a fixed radix-tree, rather than a > reverted one. Alas, time has gone against me, and we are nearing the end > of the window -

Re: [PATCH v2] thermal: add Intel BXT WhiskeyCove PMIC thermal driver

Hi > +static int pmic_thermal_remove(struct platform_device *pdev) > +{ > + return 0; > +} > + Why this remove function still requires? Regards Manish Badarkhe

Re: [PATCH v2] thermal: add Intel BXT WhiskeyCove PMIC thermal driver

Hi > +static int pmic_thermal_remove(struct platform_device *pdev) > +{ > + return 0; > +} > + Why this remove function still requires? Regards Manish Badarkhe

[PATCH 2/2] time/tick-schede: fix typos

When investigating kdump's failure with 'notsc' and jiffies not incrementing, I found several spelling mistakes Signed-off-by: Wei Jiangang --- kernel/time/tick-sched.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

[PATCH 2/2] time/tick-schede: fix typos

When investigating kdump's failure with 'notsc' and jiffies not incrementing, I found several spelling mistakes Signed-off-by: Wei Jiangang --- kernel/time/tick-sched.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/kernel/time/tick-sched.c

Re: [PATCHv3 2/2] xenfs: replace xenbus and privcmd with symlinks

On 28/06/16 20:06, David Vrabel wrote: > /proc/xen/xenbus does not work correctly. A read blocked waiting for > a xenstore message holds the mutex needed for atomic file position > updates. This blocks any writes on the same file handle, which can > deadlock if the write is needed to unblock the

Re: [PATCHv3 2/2] xenfs: replace xenbus and privcmd with symlinks

On 28/06/16 20:06, David Vrabel wrote: > /proc/xen/xenbus does not work correctly. A read blocked waiting for > a xenstore message holds the mutex needed for atomic file position > updates. This blocks any writes on the same file handle, which can > deadlock if the write is needed to unblock the

Re: Review of ptrace Yama ptrace_scope description

Hi Jann, ... So I've made that section of text: A process that has the CAP_SYS_PTRACE capability can update the /proc/sys/kernel/yama/ptrace_scope file with one of the following values: 0 ("classic ptrace permissions") No additional restrictions

Re: Review of ptrace Yama ptrace_scope description

Hi Jann, ... So I've made that section of text: A process that has the CAP_SYS_PTRACE capability can update the /proc/sys/kernel/yama/ptrace_scope file with one of the following values: 0 ("classic ptrace permissions") No additional restrictions

[PATCH V5 1/3] devicetree/bindings: Add binding for operator panel on FSP machines

Add a binding to Documentation/devicetree/bindings/powerpc/opal (oppanel-opal.txt) for the operator panel which is present on IBM Power Systems machines with FSPs. Signed-off-by: Suraj Jitindar Singh Acked-by: Rob Herring Acked-by: Stewart Smith

[PATCH V5 1/3] devicetree/bindings: Add binding for operator panel on FSP machines

Add a binding to Documentation/devicetree/bindings/powerpc/opal (oppanel-opal.txt) for the operator panel which is present on IBM Power Systems machines with FSPs. Signed-off-by: Suraj Jitindar Singh Acked-by: Rob Herring Acked-by: Stewart Smith --- Change Log: V1 -> V2: - Nothing

linux-next: manual merge of the kvm tree with the s390 tree

Hi all, Today's linux-next merge of the kvm tree got a conflict in: arch/s390/hypfs/hypfs_diag.c between commit: e030c1125eab ("s390/hypfs: use basic block for diag inline assembly") from the s390 tree and commit: e65f30e0cb29 ("s390: hypfs: Move diag implementation and data

linux-next: manual merge of the kvm tree with the s390 tree

Hi all, Today's linux-next merge of the kvm tree got a conflict in: arch/s390/hypfs/hypfs_diag.c between commit: e030c1125eab ("s390/hypfs: use basic block for diag inline assembly") from the s390 tree and commit: e65f30e0cb29 ("s390: hypfs: Move diag implementation and data

Re: [PATCH 0/4] Mesh mpm fixes and enhancements

Hi Yaniv, On Tue, Jun 28, 2016 at 9:13 PM, Yaniv Machani wrote: > This patch set is addressing some issues found in the current 802.11s > implementation, > specifically when using hostap mpm. > It's aligning the beacon format and handling some corner cases. > > Maital Hahn (2):

Re: [PATCH 0/4] Mesh mpm fixes and enhancements

Hi Yaniv, On Tue, Jun 28, 2016 at 9:13 PM, Yaniv Machani wrote: > This patch set is addressing some issues found in the current 802.11s > implementation, > specifically when using hostap mpm. > It's aligning the beacon format and handling some corner cases. > > Maital Hahn (2): > mac80211:

Re: [PATCH 2/2 v16] drm/bridge: Add I2C based driver for ps8640 bridge

Hi Emil, One answer inline below. The rest I leave to Jitao... [snip...] On Fri, Jun 17, 2016 at 3:14 AM, Emil Velikov wrote: >> +static ssize_t ps8640_update_fw_store(struct device *dev, >> + struct device_attribute *attr, >> +

Re: [PATCH 2/2 v16] drm/bridge: Add I2C based driver for ps8640 bridge

Hi Emil, One answer inline below. The rest I leave to Jitao... [snip...] On Fri, Jun 17, 2016 at 3:14 AM, Emil Velikov wrote: >> +static ssize_t ps8640_update_fw_store(struct device *dev, >> + struct device_attribute *attr, >> +

[PATCH v2] thermal: add Intel BXT WhiskeyCove PMIC thermal driver

This change add support for pmic thermal driver which is intended to handle the alert interrupts triggered upon thermal trip point cross and notify the thermal framework appropriately with the zone, temp, crossed trip and event details. Signed-off-by: Yegnesh S Iyer

[PATCH v2] thermal: add Intel BXT WhiskeyCove PMIC thermal driver

This change add support for pmic thermal driver which is intended to handle the alert interrupts triggered upon thermal trip point cross and notify the thermal framework appropriately with the zone, temp, crossed trip and event details. Signed-off-by: Yegnesh S Iyer Signed-off-by: Bin Gao ---

RE: [PATCH v10 2/2] dmaengine: Add Xilinx zynqmp dma engine driver support

> -Original Message- > From: Vinod Koul [mailto:vinod.k...@intel.com] > Sent: Tuesday, June 28, 2016 9:45 AM > To: Punnaiah Choudary Kalluri > Cc: Appana Durga Kedareswara Rao ; > robh...@kernel.org; pawel.m...@arm.com; mark.rutl...@arm.com; >

RE: [PATCH v10 2/2] dmaengine: Add Xilinx zynqmp dma engine driver support

> -Original Message- > From: Vinod Koul [mailto:vinod.k...@intel.com] > Sent: Tuesday, June 28, 2016 9:45 AM > To: Punnaiah Choudary Kalluri > Cc: Appana Durga Kedareswara Rao ; > robh...@kernel.org; pawel.m...@arm.com; mark.rutl...@arm.com; > ijc+devicet...@hellion.org.uk;

Re: [PATCH] PM / suspend: show workqueues busy name in suspend flow

Dear Tejun, On Tue, 2016-06-28 at 12:56 -0400, Tejun Heo wrote: > Hello, Roger. > > On Mon, Jun 27, 2016 at 05:44:05PM +0800, Roger Lu wrote: > > show_workqueue_state() is a better choice to me. However, only freezable > > workqueue is able to affect suspend flow. So, is there other mailing > >

Re: [PATCH] PM / suspend: show workqueues busy name in suspend flow

Dear Tejun, On Tue, 2016-06-28 at 12:56 -0400, Tejun Heo wrote: > Hello, Roger. > > On Mon, Jun 27, 2016 at 05:44:05PM +0800, Roger Lu wrote: > > show_workqueue_state() is a better choice to me. However, only freezable > > workqueue is able to affect suspend flow. So, is there other mailing > >

[PATCH V5 3/3] powerpc/drivers: Add driver for operator panel on FSP machines

Implement new character device driver to allow access from user space to the operator panel display present on IBM Power Systems machines with FSPs. This will allow status information to be presented on the display which is visible to a user. The driver implements a character buffer which a user

[PATCH V5 3/3] powerpc/drivers: Add driver for operator panel on FSP machines

Implement new character device driver to allow access from user space to the operator panel display present on IBM Power Systems machines with FSPs. This will allow status information to be presented on the display which is visible to a user. The driver implements a character buffer which a user

[PATCH V5 2/3] powerpc/opal: Add inline function to get rc from an ASYNC_COMP opal_msg

An opal_msg of type OPAL_MSG_ASYNC_COMP contains the return code in the params[1] struct member. However this isn't intuitive or obvious when reading the code and requires that a user look at the skiboot documentation or opal-api.h to verify this. Add an inline function to get the return code

[PATCH V5 2/3] powerpc/opal: Add inline function to get rc from an ASYNC_COMP opal_msg

An opal_msg of type OPAL_MSG_ASYNC_COMP contains the return code in the params[1] struct member. However this isn't intuitive or obvious when reading the code and requires that a user look at the skiboot documentation or opal-api.h to verify this. Add an inline function to get the return code

linux-next: manual merge of the devicetree tree with the imx-mxs tree

Hi Rob, Today's linux-next merge of the devicetree tree got a conflict in: arch/arm/mach-imx/mach-imx51.c between commit: 463f90fa8a12 ("ARM: i.MX: Disable supervisor protect for i.MX51") from the imx-mxs tree and commit: 850bea2335e4 ("arm: Remove unnecessary of_platform_populate with

linux-next: manual merge of the devicetree tree with the imx-mxs tree

Hi Rob, Today's linux-next merge of the devicetree tree got a conflict in: arch/arm/mach-imx/mach-imx51.c between commit: 463f90fa8a12 ("ARM: i.MX: Disable supervisor protect for i.MX51") from the imx-mxs tree and commit: 850bea2335e4 ("arm: Remove unnecessary of_platform_populate with

Re: [PATCH] [linux-next] rtlwifi: Fix typo in printk

Hi All, On Wed, Jun 29, 2016 at 1:37 PM, Masanari Iida wrote: > This patch fix spelling typos found in drivers/net/wireless/realtek. > > Signed-off-by: Masanari Iida Looks right to me. Reviewed-by: Julian Calaby Thanks,

Re: [PATCH] [linux-next] rtlwifi: Fix typo in printk

Hi All, On Wed, Jun 29, 2016 at 1:37 PM, Masanari Iida wrote: > This patch fix spelling typos found in drivers/net/wireless/realtek. > > Signed-off-by: Masanari Iida Looks right to me. Reviewed-by: Julian Calaby Thanks, -- Julian Calaby Email: julian.cal...@gmail.com Profile:

[PATCH] [linux-next] rtlwifi: Fix typo in printk

This patch fix spelling typos found in drivers/net/wireless/realtek. Signed-off-by: Masanari Iida --- drivers/net/wireless/realtek/rtlwifi/rtl8188ee/phy.c | 2 +- drivers/net/wireless/realtek/rtlwifi/rtl8192c/phy_common.c | 2 +-

[PATCH] [linux-next] rtlwifi: Fix typo in printk

This patch fix spelling typos found in drivers/net/wireless/realtek. Signed-off-by: Masanari Iida --- drivers/net/wireless/realtek/rtlwifi/rtl8188ee/phy.c | 2 +- drivers/net/wireless/realtek/rtlwifi/rtl8192c/phy_common.c | 2 +- drivers/net/wireless/realtek/rtlwifi/rtl8192ee/dm.c

Re: [PATCH v3 10/10] drm/bridge: analogix_dp: fix no drm hpd event when panel plug in

Sean, On 06/23/2016 10:24 PM, Sean Paul wrote: On Tue, Jun 14, 2016 at 7:46 AM, Yakir Yang wrote: The enum value of DP_IRQ_TYPE_HP_CABLE_IN is zero, but driver only send drm hp event when the irq_type and the enum value is true. if (irq_type & DP_IRQ_TYPE_HP_CABLE_IN ||

Re: [PATCH v3 10/10] drm/bridge: analogix_dp: fix no drm hpd event when panel plug in

Sean, On 06/23/2016 10:24 PM, Sean Paul wrote: On Tue, Jun 14, 2016 at 7:46 AM, Yakir Yang wrote: The enum value of DP_IRQ_TYPE_HP_CABLE_IN is zero, but driver only send drm hp event when the irq_type and the enum value is true. if (irq_type & DP_IRQ_TYPE_HP_CABLE_IN || ...)

Re: [PATCH v4.1 1/2] drm/rockchip: analogix_dp: introduce the pclk for grf

Doug, On 06/23/2016 01:16 PM, Doug Anderson wrote: Yakir, On Wed, Jun 22, 2016 at 6:58 PM, Yakir Yang wrote: For RK3399's GRF module, if we want to operate the graphic related grf registers, we need to enable the pclk_vio_grf which supply power for VIO GRF IOs, so it's

Re: [PATCH v4.1 1/2] drm/rockchip: analogix_dp: introduce the pclk for grf

Doug, On 06/23/2016 01:16 PM, Doug Anderson wrote: Yakir, On Wed, Jun 22, 2016 at 6:58 PM, Yakir Yang wrote: For RK3399's GRF module, if we want to operate the graphic related grf registers, we need to enable the pclk_vio_grf which supply power for VIO GRF IOs, so it's better to introduce an

RE: [PATCH net-next v3 0/7] r8152: support new chips

> From: Hayes Wang > Sent: Tuesday, June 28, 2016 8:29 PM > To: net...@vger.kernel.org > Cc: nic_swsd; linux-kernel@vger.kernel.org; linux-...@vger.kernel.org; Hayes > Wang > Subject: [PATCH net-next v3 0/7] r8152: support new chips Excuse me. Please ignore these patches. We want to do more tests

RE: [PATCH net-next v3 0/7] r8152: support new chips

> From: Hayes Wang > Sent: Tuesday, June 28, 2016 8:29 PM > To: net...@vger.kernel.org > Cc: nic_swsd; linux-kernel@vger.kernel.org; linux-...@vger.kernel.org; Hayes > Wang > Subject: [PATCH net-next v3 0/7] r8152: support new chips Excuse me. Please ignore these patches. We want to do more tests

Re: [PATCH v2 3/3] drivers core: allow id match override when manually binding driver

On 28 June 2016 at 22:57, Mark Brown wrote: > On Tue, Jun 28, 2016 at 10:02:59PM +0200, Michal Suchanek wrote: > >> Of course I could add "my-shiny-new-board" compatible to the device >> tree and spidev. Then when I build my-shiny-new-board2 and it happens >> to also use

Re: [PATCH v2 3/3] drivers core: allow id match override when manually binding driver

On 28 June 2016 at 22:57, Mark Brown wrote: > On Tue, Jun 28, 2016 at 10:02:59PM +0200, Michal Suchanek wrote: > >> Of course I could add "my-shiny-new-board" compatible to the device >> tree and spidev. Then when I build my-shiny-new-board2 and it happens >> to also use userspace driver I will

Re: [PATCH v4 2/2] dt-bindings: analogix_dp: rockchip: correct the wrong compatible name

Doug, On 06/23/2016 01:17 PM, Doug Anderson wrote: Hi, On Wed, Jun 22, 2016 at 6:47 PM, Yakir Yang wrote: The document about rockchip platform make a mistaken in available compatible name of "rk3288-edp", we should correct it to "rk3288-dp" which correspond to the

Re: [PATCH v4 2/2] dt-bindings: analogix_dp: rockchip: correct the wrong compatible name

Doug, On 06/23/2016 01:17 PM, Doug Anderson wrote: Hi, On Wed, Jun 22, 2016 at 6:47 PM, Yakir Yang wrote: The document about rockchip platform make a mistaken in available compatible name of "rk3288-edp", we should correct it to "rk3288-dp" which correspond to the compatible name in driver.

Re: [PATCH v1 1/5] dt-bindings: Add support for LG LP079QX1-SP0V 1536x2048 panel

Rob, On 06/29/2016 04:59 AM, Rob Herring wrote: On Tue, Jun 28, 2016 at 12:51:12PM +0800, Yakir Yang wrote: The LG LP079QX1-SP0V is an 7.9" QXGA TFT with LED Backlight unit and 32 pins eDP interface. This module supports 1536x2048 mode. Signed-off-by: Yakir Yang ---

Re: [PATCH v1 1/5] dt-bindings: Add support for LG LP079QX1-SP0V 1536x2048 panel

Rob, On 06/29/2016 04:59 AM, Rob Herring wrote: On Tue, Jun 28, 2016 at 12:51:12PM +0800, Yakir Yang wrote: The LG LP079QX1-SP0V is an 7.9" QXGA TFT with LED Backlight unit and 32 pins eDP interface. This module supports 1536x2048 mode. Signed-off-by: Yakir Yang ---

Re: [PATCH 0/3] add support for Allwinner SoCs ADC

Hi, On Tue, Jun 28, 2016 at 4:45 PM, Quentin Schulz wrote: > The Allwinner SoCs all have an ADC that can also act as a touchscreen > controller > and a thermal sensor. The first four channels can be used either for the ADC > or > the touchscreen and the fifth

Re: [PATCH 0/3] add support for Allwinner SoCs ADC

Hi, On Tue, Jun 28, 2016 at 4:45 PM, Quentin Schulz wrote: > The Allwinner SoCs all have an ADC that can also act as a touchscreen > controller > and a thermal sensor. The first four channels can be used either for the ADC > or > the touchscreen and the fifth channel is used for the thermal

  1   2   3   4   5   6   7   8   9   10   >