[PATCH v3] mm: pmd dirty emulation in page fault handler

Andreas reported [1] made a test in jemalloc hang in THP mode in arm64. http://lkml.kernel.org/r/mvmmvfy37g1@hawking.suse.de The problem is page fault handler supports only accessed flag emulation for THP page of SW-dirty/accessed architecture. This patch enables dirty-bit emulation for

[PATCH v3] mm: pmd dirty emulation in page fault handler

Andreas reported [1] made a test in jemalloc hang in THP mode in arm64. http://lkml.kernel.org/r/mvmmvfy37g1@hawking.suse.de The problem is page fault handler supports only accessed flag emulation for THP page of SW-dirty/accessed architecture. This patch enables dirty-bit emulation for

Re: [RFC PATCH v2] crypto: Add IV generation algorithms

On Thu, Dec 22, 2016 at 04:25:12PM +0530, Binoy Jayan wrote: > > > It doesn't have to live outside of dm-crypt. You can register > > these IV generators from there if you really want. > > Sorry, but I didn't understand this part. What I mean is that moving the IV generators into the crypto API

Re: [RFC PATCH v2] crypto: Add IV generation algorithms

On Thu, Dec 22, 2016 at 04:25:12PM +0530, Binoy Jayan wrote: > > > It doesn't have to live outside of dm-crypt. You can register > > these IV generators from there if you really want. > > Sorry, but I didn't understand this part. What I mean is that moving the IV generators into the crypto API

Re: [Intel-gfx] [PATCH] drm/i915: check if execlist_port is empty before using its content

On Fri, Dec 23, 2016 at 01:46:36PM +0800, changbin...@intel.com wrote: > From: "Du, Changbin" > > This patch fix a crash in function reset_common_ring. In this case, > the port[0].request is null when reset the render ring, so a null > dereference exception is raised. We

Re: [Intel-gfx] [PATCH] drm/i915: check if execlist_port is empty before using its content

On Fri, Dec 23, 2016 at 01:46:36PM +0800, changbin...@intel.com wrote: > From: "Du, Changbin" > > This patch fix a crash in function reset_common_ring. In this case, > the port[0].request is null when reset the render ring, so a null > dereference exception is raised. We need to check

Re: [4.10, panic, regression] iscsi: null pointer deref at iscsi_tcp_segment_done+0x20d/0x2e0

On Thu, Dec 22, 2016 at 12:22:27PM -0800, Hugh Dickins wrote: > On Wed, 21 Dec 2016, Linus Torvalds wrote: > > On Wed, Dec 21, 2016 at 9:13 PM, Dave Chinner wrote: > > > I unmounted the fs, mkfs'd it again, ran the > > > workload again and about a minute in this fired: > > >

Re: [4.10, panic, regression] iscsi: null pointer deref at iscsi_tcp_segment_done+0x20d/0x2e0

On Thu, Dec 22, 2016 at 12:22:27PM -0800, Hugh Dickins wrote: > On Wed, 21 Dec 2016, Linus Torvalds wrote: > > On Wed, Dec 21, 2016 at 9:13 PM, Dave Chinner wrote: > > > I unmounted the fs, mkfs'd it again, ran the > > > workload again and about a minute in this fired: > > > > > > [628867.607417]

Re: [PATCH V5 1/3] ARM64 LPC: Indirect ISA port IO introduced

On Fri, Dec 23, 2016 at 9:43 AM, zhichang.yuan wrote: > Hi，Ming, > > > On 2016/12/22 16:15, Ming Lei wrote: >> Hi Guys, >> >> On Tue, Nov 8, 2016 at 11:47 AM, zhichang.yuan >> wrote: >>> For arm64, there is no I/O space as other

Re: [PATCH V5 1/3] ARM64 LPC: Indirect ISA port IO introduced

On Fri, Dec 23, 2016 at 9:43 AM, zhichang.yuan wrote: > Hi，Ming, > > > On 2016/12/22 16:15, Ming Lei wrote: >> Hi Guys, >> >> On Tue, Nov 8, 2016 at 11:47 AM, zhichang.yuan >> wrote: >>> For arm64, there is no I/O space as other architectural platforms, such as >>> X86. Most I/O accesses are

Re: [PATCH] serial: 8250: use initializer instead of memset to clear local struct

On Fri, Dec 23, 2016 at 12:21:48PM +0900, Masahiro Yamada wrote: > Leave the way of zero-out to the compiler's decision; the compiler > may know a more optimized way than calling memset(). But no, it doesn't, it will leave "blank" areas in the structure with bad data in it, which is why we do

Re: [PATCH] serial: 8250: use initializer instead of memset to clear local struct

On Fri, Dec 23, 2016 at 12:21:48PM +0900, Masahiro Yamada wrote: > Leave the way of zero-out to the compiler's decision; the compiler > may know a more optimized way than calling memset(). But no, it doesn't, it will leave "blank" areas in the structure with bad data in it, which is why we do

Re: [PATCH] tpm: Restore functionality to xen vtpm driver.

On Thu, Dec 22, 2016 at 02:41:52PM -0600, Dr. Greg Wettstein wrote: > Functionality of the xen-tpmfront driver was lost secondary to > the introduction of xenbus multi-page support in the following > commit: > > ccc9d90a9a8b5c4ad7e9708ec41f75ff9e98d61d > > xenbus_client: Extend interface to

Re: [PATCH] tpm: Restore functionality to xen vtpm driver.

On Thu, Dec 22, 2016 at 02:41:52PM -0600, Dr. Greg Wettstein wrote: > Functionality of the xen-tpmfront driver was lost secondary to > the introduction of xenbus multi-page support in the following > commit: > > ccc9d90a9a8b5c4ad7e9708ec41f75ff9e98d61d > > xenbus_client: Extend interface to

Re: [PATCH] drm/i915: check if execlist_port is empty before using its content

On Fri, 23 Dec 2016, changbin...@intel.com wrote: > From: "Du, Changbin" > > This patch fix a crash in function reset_common_ring. In this case, > the port[0].request is null when reset the render ring, so a null > dereference exception is raised. We need to check

Re: [PATCH] drm/i915: check if execlist_port is empty before using its content

On Fri, 23 Dec 2016, changbin...@intel.com wrote: > From: "Du, Changbin" > > This patch fix a crash in function reset_common_ring. In this case, > the port[0].request is null when reset the render ring, so a null > dereference exception is raised. We need to check execlist_port status > first. >

[PATCH 3/4] usb: xhci: add XHCI_MISS_CA_EVENT quirk bit

Writing the CMD_RING_ABORT bit in xhci command register should cause a command completion event with the command completion code set to command ring stopped. However on some hosts, the CMD_RING_RUNNING bit is correctly cleared but the completion event is never sent. Current xhci driver treats the

[PATCH 3/4] usb: xhci: add XHCI_MISS_CA_EVENT quirk bit

Writing the CMD_RING_ABORT bit in xhci command register should cause a command completion event with the command completion code set to command ring stopped. However on some hosts, the CMD_RING_RUNNING bit is correctly cleared but the completion event is never sent. Current xhci driver treats the

[PATCH 1/4] usb: xhci: remove unnecessary second abort try

The second try was a workaround for (what we thought was) command ring failing to stop in the first place. But this turns out to be due to the race that we have fixed(see "xhci: Fix race related to abort operation"). With that fix, it is time to remove the second try. Signed-off-by: Lu Baolu

[PATCH 1/4] usb: xhci: remove unnecessary second abort try

The second try was a workaround for (what we thought was) command ring failing to stop in the first place. But this turns out to be due to the race that we have fixed(see "xhci: Fix race related to abort operation"). With that fix, it is time to remove the second try. Signed-off-by: Lu Baolu ---

[PATCH 0/4] refactor command timeout handling

Hi Mathias, This patch series is for command timeout refactoring. Patches usb: xhci: remove unnecessary second abort try usb: xhci: remove CRR polling in xhci_abort_cmd_ring() are follow-ups of your comments of "remove unnecessary second abort try as a separate patch, send to usb-next" and

[PATCH 2/4] usb: xhci: remove CRR polling in xhci_abort_cmd_ring()

xHCI driver aborts the command ring by setting CA (Command Abort) bit in the command register. With this setting, host should abort all command executions and generate a command completion event with the completion code set to command ring stopped. Software should time the completion of command

[PATCH 4/4] usb: xhci: warn on command timeout in stopped command ring

If xhci host fails to response to a command, the command watchdog timer will be fired. The callback function will abort and clear current command and restart the command execution. If driver fails to restart command execution, it will assume there is a larger problem in host and report the

[PATCH 0/4] refactor command timeout handling

Hi Mathias, This patch series is for command timeout refactoring. Patches usb: xhci: remove unnecessary second abort try usb: xhci: remove CRR polling in xhci_abort_cmd_ring() are follow-ups of your comments of "remove unnecessary second abort try as a separate patch, send to usb-next" and

[PATCH 2/4] usb: xhci: remove CRR polling in xhci_abort_cmd_ring()

xHCI driver aborts the command ring by setting CA (Command Abort) bit in the command register. With this setting, host should abort all command executions and generate a command completion event with the completion code set to command ring stopped. Software should time the completion of command

[PATCH 4/4] usb: xhci: warn on command timeout in stopped command ring

If xhci host fails to response to a command, the command watchdog timer will be fired. The callback function will abort and clear current command and restart the command execution. If driver fails to restart command execution, it will assume there is a larger problem in host and report the

[PATCH 0/1] xhci: Fix race related to abort operation

Hi Mathias, This is a follow-up patch for below comment "rebase OGAWA Hirofumi's changes on top of that, and send to usb-linus only" in below discussion thread. https://lkml.org/lkml/2016/12/21/186 I rebased the patch and added unlock-before and lock-after xhci->lock during waiting for the

[PATCH 1/1] xhci: Fix race related to abort operation

From: OGAWA Hirofumi Current abort operation has race. xhci_handle_command_timeout() xhci_abort_cmd_ring() xhci_write_64(CMD_RING_ABORT) xhci_handshake(5s) do { check CMD_RING_RUNNING udelay(1)

[PATCH 0/1] xhci: Fix race related to abort operation

Hi Mathias, This is a follow-up patch for below comment "rebase OGAWA Hirofumi's changes on top of that, and send to usb-linus only" in below discussion thread. https://lkml.org/lkml/2016/12/21/186 I rebased the patch and added unlock-before and lock-after xhci->lock during waiting for the

[PATCH 1/1] xhci: Fix race related to abort operation

From: OGAWA Hirofumi Current abort operation has race. xhci_handle_command_timeout() xhci_abort_cmd_ring() xhci_write_64(CMD_RING_ABORT) xhci_handshake(5s) do { check CMD_RING_RUNNING udelay(1)

[PATCH 0/1] usb: xhci: hold lock over xhci_abort_cmd_ring()

Hi Mathias, This is a follow-up patch for below comment "fix the lock to cover abort+CRR check, and send it to usb-linus +stable" in below discussion thread. https://lkml.org/lkml/2016/12/21/186 It's based on v4.9. Best regards, Lu Baolu Lu Baolu (1): usb: xhci: hold lock over

[PATCH 1/1] usb: xhci: hold lock over xhci_abort_cmd_ring()

In command timer function, xhci_handle_command_timeout(), xhci->lock is unlocked before call into xhci_abort_cmd_ring(). This might cause race between the timer function and the event handler. The xhci_abort_cmd_ring() function sets the CMD_RING_ABORT bit in the command register and polling it

[PATCH 0/1] usb: xhci: hold lock over xhci_abort_cmd_ring()

Hi Mathias, This is a follow-up patch for below comment "fix the lock to cover abort+CRR check, and send it to usb-linus +stable" in below discussion thread. https://lkml.org/lkml/2016/12/21/186 It's based on v4.9. Best regards, Lu Baolu Lu Baolu (1): usb: xhci: hold lock over

[PATCH 1/1] usb: xhci: hold lock over xhci_abort_cmd_ring()

In command timer function, xhci_handle_command_timeout(), xhci->lock is unlocked before call into xhci_abort_cmd_ring(). This might cause race between the timer function and the event handler. The xhci_abort_cmd_ring() function sets the CMD_RING_ABORT bit in the command register and polling it

Re: [PATCH 00/66] use permission-specific DEVICE_ATTR variants

> Hi Julia, > > I noticed that drivers/hwmon/gl518sm.c was not converted. Running your script > on it does not do anything. Any idea what might cause that ? I'll check. > I noticed that I get a warning if I specify a debug file: > > File "devattr-new.cocci", line 36, characters 5-6: > Warning

Re: [PATCH 00/66] use permission-specific DEVICE_ATTR variants

> Hi Julia, > > I noticed that drivers/hwmon/gl518sm.c was not converted. Running your script > on it does not do anything. Any idea what might cause that ? I'll check. > I noticed that I get a warning if I specify a debug file: > > File "devattr-new.cocci", line 36, characters 5-6: > Warning

Why do Zombie process' /proc entries have uid 0?

This is mostly out of curiosity, but I was surprised by the behavior, so I was hoping somebody might be able to explain why this behavior was chosen. In particular, consider any zombie process, e.g. $ cat /proc/77078/status Name: test State: Z (zombie) Tgid: 77078 Ngid: 0 Pid: 77078 PPid: 77077

Why do Zombie process' /proc entries have uid 0?

This is mostly out of curiosity, but I was surprised by the behavior, so I was hoping somebody might be able to explain why this behavior was chosen. In particular, consider any zombie process, e.g. $ cat /proc/77078/status Name: test State: Z (zombie) Tgid: 77078 Ngid: 0 Pid: 77078 PPid: 77077

Re: [PATCH V6 04/11] megaraid_sas: SAS3.5 Generic Megaraid Controllers Stream Detection and IO Coalescing

Hi Sasikumar, [auto build test WARNING on scsi/for-next] [also build test WARNING on next-20161223] [cannot apply to v4.9] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH V6 04/11] megaraid_sas: SAS3.5 Generic Megaraid Controllers Stream Detection and IO Coalescing

Hi Sasikumar, [auto build test WARNING on scsi/for-next] [also build test WARNING on next-20161223] [cannot apply to v4.9] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH] drm/i915: check if execlist_port is empty before using its content

From: "Du, Changbin" This patch fix a crash in function reset_common_ring. In this case, the port[0].request is null when reset the render ring, so a null dereference exception is raised. We need to check execlist_port status first. [ 35.748034] BUG: unable to handle

[PATCH] drm/i915: check if execlist_port is empty before using its content

From: "Du, Changbin" This patch fix a crash in function reset_common_ring. In this case, the port[0].request is null when reset the render ring, so a null dereference exception is raised. We need to check execlist_port status first. [ 35.748034] BUG: unable to handle kernel NULL pointer

Re: [PATCH] MIPS: ralink: fix incorrect assignment on ralink_soc

On 23/12/2016 00:52, Colin King wrote: > From: Colin Ian King > > ralink_soc sould be assigned to RT3883_SOC, replace incorrect > comparision with assignment. > > Signed-off-by: Colin Ian King Acked-by: John Crispin i

Re: [PATCH] MIPS: ralink: fix incorrect assignment on ralink_soc

On 23/12/2016 00:52, Colin King wrote: > From: Colin Ian King > > ralink_soc sould be assigned to RT3883_SOC, replace incorrect > comparision with assignment. > > Signed-off-by: Colin Ian King Acked-by: John Crispin i thought i had sent this fix upstream ages ago. luckily this bug never

Re: [PATCH 1/2] drm/panel: Add support for S6E3HA2 panel driver on TM2 board

On 12/20/2016 03:55 AM, Rob Herring wrote: On Wed, Dec 14, 2016 at 03:04:04PM +0900, Hoegeun Kwon wrote: This patch add support for MIPI-DSI based S6E3HA2 AMOLED panel driver. This panel has 1440x2560 resolution in 5.7-inch physical panel in the TM2 device. Signed-off-by: Donghwa Lee

Re: [PATCH 1/2] drm/panel: Add support for S6E3HA2 panel driver on TM2 board

On 12/20/2016 03:55 AM, Rob Herring wrote: On Wed, Dec 14, 2016 at 03:04:04PM +0900, Hoegeun Kwon wrote: This patch add support for MIPI-DSI based S6E3HA2 AMOLED panel driver. This panel has 1440x2560 resolution in 5.7-inch physical panel in the TM2 device. Signed-off-by: Donghwa Lee

RE: RE: [PATCH] Input: Change msleep to usleep_range for small msecs

Dear Aniroop Mathur Please see the acknowledgement below. Best regards Albert (Xu) ZHANG BST/ESA3.1 Tel. +86(21)2218-1283 -Original Message- From: Aniroop Mathur [mailto:a.mat...@samsung.com] Sent: Thursday, December 01, 2016 6:34 PM To: ZHANG Xu (BST/ESA3.1)

RE: RE: [PATCH] Input: Change msleep to usleep_range for small msecs

Dear Aniroop Mathur Please see the acknowledgement below. Best regards Albert (Xu) ZHANG BST/ESA3.1 Tel. +86(21)2218-1283 -Original Message- From: Aniroop Mathur [mailto:a.mat...@samsung.com] Sent: Thursday, December 01, 2016 6:34 PM To: ZHANG Xu (BST/ESA3.1) ; Dmitry Torokhov

Re: [PATCH 65/66] hwmon: (fam15h_power) use permission-specific DEVICE_ATTR variants

On Thu, Dec 22, 2016 at 01:05:34PM +0100, Julia Lawall wrote: > Use DEVICE_ATTR_RO etc. for read only attributes etc. This simplifies the > source code, improves readbility, and reduces the chance of > inconsistencies. > > The semantic patch for the RO case, in the case where the show function >

Re: [PATCH 65/66] hwmon: (fam15h_power) use permission-specific DEVICE_ATTR variants

On Thu, Dec 22, 2016 at 01:05:34PM +0100, Julia Lawall wrote: > Use DEVICE_ATTR_RO etc. for read only attributes etc. This simplifies the > source code, improves readbility, and reduces the chance of > inconsistencies. > > The semantic patch for the RO case, in the case where the show function >

[RFC PATCHv2 2/4] clk: mdm9615: Add EBI2 clock

Add definition of EBI2 clock used by MDM9615 NAND controller. Cc: Andy Gross Cc: David Brown Cc: Michael Turquette Cc: Stephen Boyd Cc: Rob Herring Cc: Mark Rutland

[RFC PATCHv2 2/4] clk: mdm9615: Add EBI2 clock

Add definition of EBI2 clock used by MDM9615 NAND controller. Cc: Andy Gross Cc: David Brown Cc: Michael Turquette Cc: Stephen Boyd Cc: Rob Herring Cc: Mark Rutland Cc: Neil Armstrong Cc: linux-arm-...@vger.kernel.org Cc: linux-...@vger.kernel.org Cc: linux-...@vger.kernel.org Cc:

Re: [PATCH v3 1/4] dt-bindings: phy: Add support for QUSB2 phy

Hi Rob, On Fri, Dec 23, 2016 at 2:46 AM, Rob Herring wrote: > On Tue, Dec 20, 2016 at 10:33:48PM +0530, Vivek Gautam wrote: >> Qualcomm chipsets have QUSB2 phy controller that provides >> HighSpeed functionality for DWC3 controller. >> Adding dt binding information for the

Re: [PATCH v3 1/4] dt-bindings: phy: Add support for QUSB2 phy

Hi Rob, On Fri, Dec 23, 2016 at 2:46 AM, Rob Herring wrote: > On Tue, Dec 20, 2016 at 10:33:48PM +0530, Vivek Gautam wrote: >> Qualcomm chipsets have QUSB2 phy controller that provides >> HighSpeed functionality for DWC3 controller. >> Adding dt binding information for the same. >> >>

[PATCH] tools build: replace $(CC) -E with $(CPP) for pre-processing

The top-level Makefile defines: CPP = $(CC) -E So, $(CC) -E can be replaced with $(CPP) and this makes more sense for pre-processing. Signed-off-by: Masahiro Yamada --- tools/build/Makefile.build | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH] tools build: replace $(CC) -E with $(CPP) for pre-processing

The top-level Makefile defines: CPP = $(CC) -E So, $(CC) -E can be replaced with $(CPP) and this makes more sense for pre-processing. Signed-off-by: Masahiro Yamada --- tools/build/Makefile.build | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] genirq: use simple work queue for polling spurious irq

Spurious irq will be disabled and then polled through mod_timer in interrupt context. While mod_timer has a common spin_lock operation thus will cause an error: BUG: sleeping function called from invalid context. Move the mod_timer into simple work queue to fix it. Signed-off-by: Zhang Xiao

[PATCH] genirq: use simple work queue for polling spurious irq

Spurious irq will be disabled and then polled through mod_timer in interrupt context. While mod_timer has a common spin_lock operation thus will cause an error: BUG: sleeping function called from invalid context. Move the mod_timer into simple work queue to fix it. Signed-off-by: Zhang Xiao ---

Re: [PATCH] cpufreq: powernv: Add boost files to export ultra-turbo frequencies

Hi Shilpa, On Fri, Dec 16, 2016 at 04:43:08PM +0530, Shilpasri G Bhat wrote: > In P8+, Workload Optimized Frequency(WOF) provides the capability to > boost the cpu frequency based on the utilization of the other cpus > running in the chip. The On-Chip-Controller(OCC) firmware will control > the

Re: [PATCH] cpufreq: powernv: Add boost files to export ultra-turbo frequencies

Hi Shilpa, On Fri, Dec 16, 2016 at 04:43:08PM +0530, Shilpasri G Bhat wrote: > In P8+, Workload Optimized Frequency(WOF) provides the capability to > boost the cpu frequency based on the utilization of the other cpus > running in the chip. The On-Chip-Controller(OCC) firmware will control > the

Re: [4.10, panic, regression] iscsi: null pointer deref at iscsi_tcp_segment_done+0x20d/0x2e0

On Fri, Dec 23, 2016 at 09:33:36AM +1100, Dave Chinner wrote: > On Fri, Dec 23, 2016 at 09:15:00AM +1100, Dave Chinner wrote: > > On Thu, Dec 22, 2016 at 01:10:19PM -0800, Linus Torvalds wrote: > > > Ok, so the numa issue was a red herring. With that fixed: > > > > > > On Thu, Dec 22, 2016 at

Re: [4.10, panic, regression] iscsi: null pointer deref at iscsi_tcp_segment_done+0x20d/0x2e0

On Fri, Dec 23, 2016 at 09:33:36AM +1100, Dave Chinner wrote: > On Fri, Dec 23, 2016 at 09:15:00AM +1100, Dave Chinner wrote: > > On Thu, Dec 22, 2016 at 01:10:19PM -0800, Linus Torvalds wrote: > > > Ok, so the numa issue was a red herring. With that fixed: > > > > > > On Thu, Dec 22, 2016 at

[PATCH v1 0/3] soc: rockchip: power-domain: support RK3328 SoC

Elaine Zhang (3): dt/bindings: power: add RK3328 SoCs header for idle-request dt-bindings: add binding for rk3328 power domains soc: rockchip: power-domain: Modify power domain driver for rk3328 .../bindings/soc/rockchip/power_domain.txt | 3 ++ drivers/soc/rockchip/pm_domains.c

[PATCH v1 2/3] dt-bindings: add binding for rk3328 power domains

Add binding documentation for the power domains found on Rockchip RK3328 SoCs. But RK3328 SoC just support idle, not support pd. Signed-off-by: Elaine Zhang --- Documentation/devicetree/bindings/soc/rockchip/power_domain.txt | 3 +++ 1 file changed, 3 insertions(+)

[PATCH v1 0/3] soc: rockchip: power-domain: support RK3328 SoC

Elaine Zhang (3): dt/bindings: power: add RK3328 SoCs header for idle-request dt-bindings: add binding for rk3328 power domains soc: rockchip: power-domain: Modify power domain driver for rk3328 .../bindings/soc/rockchip/power_domain.txt | 3 ++ drivers/soc/rockchip/pm_domains.c

[PATCH v1 2/3] dt-bindings: add binding for rk3328 power domains

Add binding documentation for the power domains found on Rockchip RK3328 SoCs. But RK3328 SoC just support idle, not support pd. Signed-off-by: Elaine Zhang --- Documentation/devicetree/bindings/soc/rockchip/power_domain.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git

[PATCH v1 3/3] soc: rockchip: power-domain: Modify power domain driver for rk3328

This driver is modified to support RK3328 SoC. RK3328 SoC is only support idle. add DOMAIN_M type, for support regs have write_enable bit. Signed-off-by: Elaine Zhang --- drivers/soc/rockchip/pm_domains.c | 63 +++ 1 file changed, 57

[PATCH v1 1/3] dt/bindings: power: add RK3328 SoCs header for idle-request

According to a description from TRM, add all the idle request. Signed-off-by: Elaine Zhang --- include/dt-bindings/power/rk3328-power.h | 18 ++ 1 file changed, 18 insertions(+) create mode 100644 include/dt-bindings/power/rk3328-power.h diff --git

[PATCH v1 3/3] soc: rockchip: power-domain: Modify power domain driver for rk3328

This driver is modified to support RK3328 SoC. RK3328 SoC is only support idle. add DOMAIN_M type, for support regs have write_enable bit. Signed-off-by: Elaine Zhang --- drivers/soc/rockchip/pm_domains.c | 63 +++ 1 file changed, 57 insertions(+), 6

[PATCH v1 1/3] dt/bindings: power: add RK3328 SoCs header for idle-request

According to a description from TRM, add all the idle request. Signed-off-by: Elaine Zhang --- include/dt-bindings/power/rk3328-power.h | 18 ++ 1 file changed, 18 insertions(+) create mode 100644 include/dt-bindings/power/rk3328-power.h diff --git

RE: A small window for a race condition in mm/rmap.c:page_lock_anon_vma_read

On Fri, 23 Dec 2016, Dashi DS1 Cao wrote: > The kernel version is "RELEASE: 3.10.0-327.36.3.el7.x86_64". It was the > latest kernel release of CentOS 7.2 at that time, or maybe still now. Okay, thanks: so, basically a v3.10 kernel, with lots of added patches, but also lacking many more recent

RE: A small window for a race condition in mm/rmap.c:page_lock_anon_vma_read

On Fri, 23 Dec 2016, Dashi DS1 Cao wrote: > The kernel version is "RELEASE: 3.10.0-327.36.3.el7.x86_64". It was the > latest kernel release of CentOS 7.2 at that time, or maybe still now. Okay, thanks: so, basically a v3.10 kernel, with lots of added patches, but also lacking many more recent

[PATCH] serial: 8250: use initializer instead of memset to clear local struct

Leave the way of zero-out to the compiler's decision; the compiler may know a more optimized way than calling memset(). It may end up with memset() for big structures like this after all, but the code will be cleaner at least. Signed-off-by: Masahiro Yamada ---

[PATCH] serial: 8250: use initializer instead of memset to clear local struct

Leave the way of zero-out to the compiler's decision; the compiler may know a more optimized way than calling memset(). It may end up with memset() for big structures like this after all, but the code will be cleaner at least. Signed-off-by: Masahiro Yamada ---

[PATCH] arm64: dts: uniphier: add eMMC controller node for LD11/LD20

Add Cadence's eMMC controller node for LD11/LD20. Signed-off-by: Masahiro Yamada --- arch/arm/boot/dts/uniphier-pinctrl.dtsi | 5 + arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi | 12 arch/arm64/boot/dts/socionext/uniphier-ld20.dtsi

[PATCH] arm64: dts: uniphier: add eMMC controller node for LD11/LD20

Add Cadence's eMMC controller node for LD11/LD20. Signed-off-by: Masahiro Yamada --- arch/arm/boot/dts/uniphier-pinctrl.dtsi | 5 + arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi | 12 arch/arm64/boot/dts/socionext/uniphier-ld20.dtsi | 12 3 files

Re: [PATCH] ACPI: small formatting fixes

On Tue, Dec 13, 2016 at 08:00:01PM +0100, Pavel Machek wrote: > Actually.. the ACPI cleanup is fine. You did well :-). > Pavel Cool, so (forgive the naive question) what happens next? Maybe I'm too used to the immediate

Re: [PATCH] ACPI: small formatting fixes

On Tue, Dec 13, 2016 at 08:00:01PM +0100, Pavel Machek wrote: > Actually.. the ACPI cleanup is fine. You did well :-). > Pavel Cool, so (forgive the naive question) what happens next? Maybe I'm too used to the immediate

[PATCH] powerpc: Fix build warning on 32-bit PPC - bisected to commit 989cea5c14be

I am getting the following warning when I build kernel 4.9-git on my PowerBook G4 with a 32-bit PPC processor: AS arch/powerpc/kernel/misc_32.o arch/powerpc/kernel/misc_32.S:299:7: warning: "CONFIG_FSL_BOOKE" is not defined [-Wundef] This problem is evident after commit 989cea5c14be

[PATCH] powerpc: Fix build warning on 32-bit PPC - bisected to commit 989cea5c14be

I am getting the following warning when I build kernel 4.9-git on my PowerBook G4 with a 32-bit PPC processor: AS arch/powerpc/kernel/misc_32.o arch/powerpc/kernel/misc_32.S:299:7: warning: "CONFIG_FSL_BOOKE" is not defined [-Wundef] This problem is evident after commit 989cea5c14be

Re: Still OOM problems with 4.9er kernels

On Fri, Dec 09, 2016 at 04:52:07PM +0100, Gerhard Wiesinger wrote: > On 09.12.2016 14:40, Michal Hocko wrote: > >On Fri 09-12-16 08:06:25, Gerhard Wiesinger wrote: > >>Hello, > >> > >>same with latest kernel rc, dnf still killed with OOM (but sometimes > >>better). > >> > >>./update.sh: line 40:

Re: Still OOM problems with 4.9er kernels

On Fri, Dec 09, 2016 at 04:52:07PM +0100, Gerhard Wiesinger wrote: > On 09.12.2016 14:40, Michal Hocko wrote: > >On Fri 09-12-16 08:06:25, Gerhard Wiesinger wrote: > >>Hello, > >> > >>same with latest kernel rc, dnf still killed with OOM (but sometimes > >>better). > >> > >>./update.sh: line 40:

RE: [PATCH v3 2/3] USB3/DWC3: Add property "snps, incr-burst-type-adjustment" for INCR burst type

Hi, Rob, > -Original Message- > From: Rob Herring [mailto:r...@kernel.org] > Sent: Friday, December 23, 2016 2:45 AM > To: Jerry Huang > Cc: ba...@kernel.org; mark.rutl...@arm.com; catalin.mari...@arm.com; > will.dea...@arm.com; li...@armlinux.org.uk;

RE: [PATCH v3 2/3] USB3/DWC3: Add property "snps, incr-burst-type-adjustment" for INCR burst type

Hi, Rob, > -Original Message- > From: Rob Herring [mailto:r...@kernel.org] > Sent: Friday, December 23, 2016 2:45 AM > To: Jerry Huang > Cc: ba...@kernel.org; mark.rutl...@arm.com; catalin.mari...@arm.com; > will.dea...@arm.com; li...@armlinux.org.uk; devicet...@vger.kernel.org; >

RE: A small window for a race condition in mm/rmap.c:page_lock_anon_vma_read

I'd expected that one or more tasks doing the free were the current task of other cpu cores, but only one of the four dumps has two swapd task that are concurrently at execution on different cpu. This is the task leading to the crash: PID: 247TASK: 881fcfad8000 CPU: 14 COMMAND:

RE: A small window for a race condition in mm/rmap.c:page_lock_anon_vma_read

I'd expected that one or more tasks doing the free were the current task of other cpu cores, but only one of the four dumps has two swapd task that are concurrently at execution on different cpu. This is the task leading to the crash: PID: 247TASK: 881fcfad8000 CPU: 14 COMMAND:

[PATCH v3 07/12] scsi: ufs: set default UFS power management level

UFS device and link can be put in multiple different low power modes hence UFS driver supports multiple different low power modes. This change sets the default UFS power management level which should put the link hibernate state and device in sleep state. This default power management level gives

[PATCH v3 08/12] scsi: ufs: add capability to keep auto bkops always enabled

UFS device requires to perform bkops (back ground operations) periodically but host can control (via auto-bkops parameter of device) when device can perform bkops based on its performance requirements. In general, host would like to enable the device's auto-bkops only when it's not doing any

[PATCH v3 07/12] scsi: ufs: set default UFS power management level

UFS device and link can be put in multiple different low power modes hence UFS driver supports multiple different low power modes. This change sets the default UFS power management level which should put the link hibernate state and device in sleep state. This default power management level gives

[PATCH v3 08/12] scsi: ufs: add capability to keep auto bkops always enabled

UFS device requires to perform bkops (back ground operations) periodically but host can control (via auto-bkops parameter of device) when device can perform bkops based on its performance requirements. In general, host would like to enable the device's auto-bkops only when it's not doing any

[PATCH v3 12/12] scsi: ufs: Improve fatal error logs

From: Dolev Raviv Errors such as UIC error, illegal OCS values, and others may require more information for debugging. Such information could be hibern8 events, events sequences, recoverable errors, error history, and more. This patch improves tracking of important errors

[PATCH v3 09/12] scsi: ufs: fix setting init power mode

Immediately after successful UFS link startup, UFS link power mode would be in PWM-G1, 1-lane, SLOW-AUTO mode. But currently we are doing few of the DME local/peer attributes access before setting the "hba->pwr_info" to default power mode. If we are doing link startup as part of error recovery

[PATCH v3 10/12] scsi: ufs: add time profiling support

This patch adds the profiling support for some of the time critical operations like hibern8 enter/exit, clock gating & clock scaling. Reviewed-by: Venkat Gopalakrishnan Signed-off-by: Subhash Jadavani --- drivers/scsi/ufs/ufshcd.c | 24

[PATCH v3 12/12] scsi: ufs: Improve fatal error logs

From: Dolev Raviv Errors such as UIC error, illegal OCS values, and others may require more information for debugging. Such information could be hibern8 events, events sequences, recoverable errors, error history, and more. This patch improves tracking of important errors and events in debug

[PATCH v3 09/12] scsi: ufs: fix setting init power mode

Immediately after successful UFS link startup, UFS link power mode would be in PWM-G1, 1-lane, SLOW-AUTO mode. But currently we are doing few of the DME local/peer attributes access before setting the "hba->pwr_info" to default power mode. If we are doing link startup as part of error recovery

[PATCH v3 10/12] scsi: ufs: add time profiling support

This patch adds the profiling support for some of the time critical operations like hibern8 enter/exit, clock gating & clock scaling. Reviewed-by: Venkat Gopalakrishnan Signed-off-by: Subhash Jadavani --- drivers/scsi/ufs/ufshcd.c | 24 include/trace/events/ufs.h | 40

[PATCH v3 11/12] scsi: ufs: add trace event for ufs commands

From: Lee Susman Use the ftrace infrastructure to conditionally trace ufs command events. New trace event is created, which samples the following ufs command data: - device name - optional identification string - task tag - doorbell register - number of transfer bytes -

[PATCH v3 06/12] scsi: ufs: provide sysfs attribute to select the PM level

This patch provides the sysfs attribute to choose the power management level for UFS runtime and system suspend. Reviewed-by: Sujit Reddy Thumma Signed-off-by: Subhash Jadavani --- drivers/scsi/ufs/ufshcd.c | 144

[PATCH v3 11/12] scsi: ufs: add trace event for ufs commands

From: Lee Susman Use the ftrace infrastructure to conditionally trace ufs command events. New trace event is created, which samples the following ufs command data: - device name - optional identification string - task tag - doorbell register - number of transfer bytes - interrupt status register

[PATCH v3 06/12] scsi: ufs: provide sysfs attribute to select the PM level

This patch provides the sysfs attribute to choose the power management level for UFS runtime and system suspend. Reviewed-by: Sujit Reddy Thumma Signed-off-by: Subhash Jadavani --- drivers/scsi/ufs/ufshcd.c | 144 ++ drivers/scsi/ufs/ufshcd.h | 2 +

  1   2   3   4   5   6   7   8   9   10   >