[PATCH v5 12/13] net: ethernet: ti: cpts: calc mult and shift from refclk freq

The cyclecounter mult and shift values can be calculated based on the CPTS rfclk frequency and timekeepnig framework provides required algos and API's. Hence, calc mult and shift basing on CPTS rfclk frequency if both cpts_clock_shift and cpts_clock_mult properties are not provided in DT (the

[PATCH v5 04/13] net: ethernet: ti: cpts: fix unbalanced clk api usage in cpts_register/unregister

There are two issues with TI CPTS code which are reproducible when TI CPSW ethX device passes few up/down iterations: - cpts refclk prepare counter continuously incremented after each up/down iteration; - devm_clk_get(dev, "cpts") is called many times. Hence, fix these issues by using

[PATCH v5 06/13] net: ethernet: ti: cpts: disable cpts when unregistered

The cpts now is left enabled after unregistration. Hence, disable it in cpts_unregister(). Signed-off-by: Grygorii Strashko Acked-by: Richard Cochran --- drivers/net/ethernet/ti/cpts.c | 4 1 file changed, 4 insertions(+) diff --git

[PATCH v5 07/13] net: ethernet: ti: cpts: clean up event list if event pool is empty

From: WingMan Kwok When a CPTS user does not exit gracefully by disabling cpts timestamping and leaving a joined multicast group, the system continues to receive and timestamps the ptp packets which eventually occupy all the event list entries. When this happns, the added code

[PATCH v5 11/13] clocksource: export the clocks_calc_mult_shift to use by timestamp code

From: Murali Karicheri The CPSW CPTS driver is capable of doing timestamping on tx/rx packets and requires to know mult and shift factors for timestamp conversion from raw value to nanoseconds (ptp clock). Now these mult and shift factors are calculated manually and provided

[PATCH v5 06/13] net: ethernet: ti: cpts: disable cpts when unregistered

The cpts now is left enabled after unregistration. Hence, disable it in cpts_unregister(). Signed-off-by: Grygorii Strashko Acked-by: Richard Cochran --- drivers/net/ethernet/ti/cpts.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/net/ethernet/ti/cpts.c

[PATCH v5 07/13] net: ethernet: ti: cpts: clean up event list if event pool is empty

From: WingMan Kwok When a CPTS user does not exit gracefully by disabling cpts timestamping and leaving a joined multicast group, the system continues to receive and timestamps the ptp packets which eventually occupy all the event list entries. When this happns, the added code tries to remove

[PATCH v5 11/13] clocksource: export the clocks_calc_mult_shift to use by timestamp code

From: Murali Karicheri The CPSW CPTS driver is capable of doing timestamping on tx/rx packets and requires to know mult and shift factors for timestamp conversion from raw value to nanoseconds (ptp clock). Now these mult and shift factors are calculated manually and provided through DT, which

[PATCH v5 13/13] net: ethernet: ti: cpts: fix overflow check period

The CPTS drivers uses 8sec period for overflow checking with assumption that CPTS retclk will not exceed 500MHz. But that's not true on some TI platforms (Kesytone 2). As result, it is possible that CPTS counter will overflow more than once between two readings. Hence, fix it by selecting

[PATCH v5 13/13] net: ethernet: ti: cpts: fix overflow check period

The CPTS drivers uses 8sec period for overflow checking with assumption that CPTS retclk will not exceed 500MHz. But that's not true on some TI platforms (Kesytone 2). As result, it is possible that CPTS counter will overflow more than once between two readings. Hence, fix it by selecting

[PATCHv5 03/11] arm64: Move some macros under #ifndef __ASSEMBLY__

Several macros for various x_to_y exist outside the bounds of an __ASSEMBLY__ guard. Move them in preparation for support for CONFIG_DEBUG_VIRTUAL. Reviewed-by: Mark Rutland Tested-by: Mark Rutland Signed-off-by: Laura Abbott ---

[PATCHv5 07/11] drivers: firmware: psci: Use __pa_symbol for kernel symbol

__pa_symbol is technically the macro that should be used for kernel symbols. Switch to this as a pre-requisite for DEBUG_VIRTUAL which will do bounds checking. Signed-off-by: Laura Abbott --- v5: Split off from arm64 __pa_symbol conversion --- drivers/firmware/psci.c | 2 +-

[PATCHv5 03/11] arm64: Move some macros under #ifndef __ASSEMBLY__

Several macros for various x_to_y exist outside the bounds of an __ASSEMBLY__ guard. Move them in preparation for support for CONFIG_DEBUG_VIRTUAL. Reviewed-by: Mark Rutland Tested-by: Mark Rutland Signed-off-by: Laura Abbott --- v5: No changes --- arch/arm64/include/asm/memory.h | 38

[PATCHv5 07/11] drivers: firmware: psci: Use __pa_symbol for kernel symbol

__pa_symbol is technically the macro that should be used for kernel symbols. Switch to this as a pre-requisite for DEBUG_VIRTUAL which will do bounds checking. Signed-off-by: Laura Abbott --- v5: Split off from arm64 __pa_symbol conversion --- drivers/firmware/psci.c | 2 +- 1 file changed, 1

[PATCHv5 09/11] mm/kasan: Switch to using __pa_symbol and lm_alias

__pa_symbol is the correct API to find the physical address of symbols. Switch to it to allow for debugging APIs to work correctly. Other functions such as p*d_populate may call __pa internally. Ensure that the address passed is in the linear region by calling lm_alias. Reviewed-by: Mark Rutland

[PATCHv5 11/11] arm64: Add support for CONFIG_DEBUG_VIRTUAL

x86 has an option CONFIG_DEBUG_VIRTUAL to do additional checks on virt_to_phys calls. The goal is to catch users who are calling virt_to_phys on non-linear addresses immediately. This inclues callers using virt_to_phys on image addresses instead of __pa_symbol. As features such as

[PATCHv5 05/11] mm: Introduce lm_alias

Certain architectures may have the kernel image mapped separately to alias the linear map. Introduce a macro lm_alias to translate a kernel image symbol into its linear alias. This is used in part with work to add CONFIG_DEBUG_VIRTUAL support for arm64. Signed-off-by: Laura Abbott

[PATCHv5 06/11] arm64: Use __pa_symbol for kernel symbols

__pa_symbol is technically the marcro that should be used for kernel symbols. Switch to this as a pre-requisite for DEBUG_VIRTUAL which will do bounds checking. Tested-by: James Morse Signed-off-by: Laura Abbott --- v5: #include more places, drop arm64

[PATCHv5 09/11] mm/kasan: Switch to using __pa_symbol and lm_alias

__pa_symbol is the correct API to find the physical address of symbols. Switch to it to allow for debugging APIs to work correctly. Other functions such as p*d_populate may call __pa internally. Ensure that the address passed is in the linear region by calling lm_alias. Reviewed-by: Mark Rutland

[PATCHv5 11/11] arm64: Add support for CONFIG_DEBUG_VIRTUAL

x86 has an option CONFIG_DEBUG_VIRTUAL to do additional checks on virt_to_phys calls. The goal is to catch users who are calling virt_to_phys on non-linear addresses immediately. This inclues callers using virt_to_phys on image addresses instead of __pa_symbol. As features such as

[PATCHv5 05/11] mm: Introduce lm_alias

Certain architectures may have the kernel image mapped separately to alias the linear map. Introduce a macro lm_alias to translate a kernel image symbol into its linear alias. This is used in part with work to add CONFIG_DEBUG_VIRTUAL support for arm64. Signed-off-by: Laura Abbott --- v5: Split

[PATCHv5 06/11] arm64: Use __pa_symbol for kernel symbols

__pa_symbol is technically the marcro that should be used for kernel symbols. Switch to this as a pre-requisite for DEBUG_VIRTUAL which will do bounds checking. Tested-by: James Morse Signed-off-by: Laura Abbott --- v5: #include more places, drop arm64 specific lm_alias, correct hibernation

[PATCHv5 08/11] kexec: Switch to __pa_symbol

__pa_symbol is the correct api to get the physical address of kernel symbols. Switch to it to allow for better debug checking. Acked-by: "Eric W. Biederman" Signed-off-by: Laura Abbott --- v5: No changes, just acks --- kernel/kexec_core.c | 2 +- 1

[PATCHv5 10/11] mm/usercopy: Switch to using lm_alias

The usercopy checking code currently calls __va(__pa(...)) to check for aliases on symbols. Switch to using lm_alias instead. Reviewed-by: Mark Rutland Tested-by: Mark Rutland Acked-by: Kees Cook Signed-off-by: Laura Abbott

[PATCHv5 08/11] kexec: Switch to __pa_symbol

__pa_symbol is the correct api to get the physical address of kernel symbols. Switch to it to allow for better debug checking. Acked-by: "Eric W. Biederman" Signed-off-by: Laura Abbott --- v5: No changes, just acks --- kernel/kexec_core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCHv5 10/11] mm/usercopy: Switch to using lm_alias

The usercopy checking code currently calls __va(__pa(...)) to check for aliases on symbols. Switch to using lm_alias instead. Reviewed-by: Mark Rutland Tested-by: Mark Rutland Acked-by: Kees Cook Signed-off-by: Laura Abbott --- v5: No changes, just acks --- mm/usercopy.c | 4 ++-- 1 file

[PATCHv5 04/11] arm64: Add cast for virt_to_pfn

virt_to_pfn lacks a cast at the top level. Don't rely on __virt_to_phys and explicitly cast to unsigned long. Reviewed-by: Mark Rutland Tested-by: Mark Rutland Signed-off-by: Laura Abbott --- v5: No changes ---

[PATCHv5 02/11] mm/cma: Cleanup highmem check

6b101e2a3ce4 ("mm/CMA: fix boot regression due to physical address of high_memory") added checks to use __pa_nodebug on x86 since CONFIG_DEBUG_VIRTUAL complains about high_memory not being linearlly mapped. arm64 is now getting support for CONFIG_DEBUG_VIRTUAL as well. Rather than add an

[PATCHv5 02/11] mm/cma: Cleanup highmem check

6b101e2a3ce4 ("mm/CMA: fix boot regression due to physical address of high_memory") added checks to use __pa_nodebug on x86 since CONFIG_DEBUG_VIRTUAL complains about high_memory not being linearlly mapped. arm64 is now getting support for CONFIG_DEBUG_VIRTUAL as well. Rather than add an

[PATCHv5 04/11] arm64: Add cast for virt_to_pfn

virt_to_pfn lacks a cast at the top level. Don't rely on __virt_to_phys and explicitly cast to unsigned long. Reviewed-by: Mark Rutland Tested-by: Mark Rutland Signed-off-by: Laura Abbott --- v5: No changes --- arch/arm64/include/asm/memory.h | 2 +- 1 file changed, 1 insertion(+), 1

[PATCHv5 00/11] CONFIG_DEBUG_VIRTUAL for arm64

Hi, This is v5 of the series to add CONFIG_DEBUG_VIRTUAL for arm64. This mostly contains minor fixups including adding a few extra headers around and splitting things out into a few more sub-patches. With a few more acks I think this should be ready to go. More testing is always appreciated

[PATCHv5 01/11] lib/Kconfig.debug: Add ARCH_HAS_DEBUG_VIRTUAL

DEBUG_VIRTUAL currently depends on DEBUG_KERNEL && X86. arm64 is getting the same support. Rather than add a list of architectures, switch this to ARCH_HAS_DEBUG_VIRTUAL and let architectures select it as appropriate. Acked-by: Ingo Molnar Reviewed-by: Mark Rutland

[PATCHv5 00/11] CONFIG_DEBUG_VIRTUAL for arm64

Hi, This is v5 of the series to add CONFIG_DEBUG_VIRTUAL for arm64. This mostly contains minor fixups including adding a few extra headers around and splitting things out into a few more sub-patches. With a few more acks I think this should be ready to go. More testing is always appreciated

[PATCHv5 01/11] lib/Kconfig.debug: Add ARCH_HAS_DEBUG_VIRTUAL

DEBUG_VIRTUAL currently depends on DEBUG_KERNEL && X86. arm64 is getting the same support. Rather than add a list of architectures, switch this to ARCH_HAS_DEBUG_VIRTUAL and let architectures select it as appropriate. Acked-by: Ingo Molnar Reviewed-by: Mark Rutland Tested-by: Mark Rutland

[PATCH 2/2] Input: i8042 - change dbg to pr_warn when returning errors

Signed-off-by: Marcos Paulo de Souza --- drivers/input/serio/i8042.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/input/serio/i8042.c b/drivers/input/serio/i8042.c index 1c70747..bc54ce5 100644 --- a/drivers/input/serio/i8042.c +++

mmotm 2016-12-06-15-45 uploaded

The mm-of-the-moment snapshot 2016-12-06-15-45 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

[PATCH 1/2] Input: i8042 - Add warn when a command can't write its parameter

This can happen in cases like bug #102951[1], so add a proper warn as done in wait_read. [1] https://bugzilla.kernel.org/show_bug.cgi?id=102951 Signed-off-by: Marcos Paulo de Souza --- drivers/input/serio/i8042.c | 4 +++- 1 file changed, 3 insertions(+), 1

[PATCH 2/2] Input: i8042 - change dbg to pr_warn when returning errors

Signed-off-by: Marcos Paulo de Souza --- drivers/input/serio/i8042.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/input/serio/i8042.c b/drivers/input/serio/i8042.c index 1c70747..bc54ce5 100644 --- a/drivers/input/serio/i8042.c +++ b/drivers/input/serio/i8042.c

mmotm 2016-12-06-15-45 uploaded

The mm-of-the-moment snapshot 2016-12-06-15-45 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

[PATCH 1/2] Input: i8042 - Add warn when a command can't write its parameter

This can happen in cases like bug #102951[1], so add a proper warn as done in wait_read. [1] https://bugzilla.kernel.org/show_bug.cgi?id=102951 Signed-off-by: Marcos Paulo de Souza --- drivers/input/serio/i8042.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

Re: unable to load modules with CONFIG_MODVERSIONS=y after commit 8ab2ae655b

Hi all, just for the record. I was also not able to boot my system. In x86_64 architecture it however worked, only in i686 I had to revert 8ab2ae6 and apply Adam's patch to make it work: https://patchwork.kernel.org/patch/9408985 greez, Philip

Re: unable to load modules with CONFIG_MODVERSIONS=y after commit 8ab2ae655b

Hi all, just for the record. I was also not able to boot my system. In x86_64 architecture it however worked, only in i686 I had to revert 8ab2ae6 and apply Adam's patch to make it work: https://patchwork.kernel.org/patch/9408985 greez, Philip

Re: [RFC][PATCH 1/3 v2] usb: dwc2: Add extcon support to dwc2 driver

On 12/6/2016 12:06 AM, John Stultz wrote: > This patch wires up extcon support to the dwc2 driver > so that devices that use a modern generic phy driver > and don't use the usb-phy infrastructure can still > signal connect/disconnect events. > > Cc: Wei Xu > Cc: Guodong Xu

Re: [RFC][PATCH 1/3 v2] usb: dwc2: Add extcon support to dwc2 driver

On 12/6/2016 12:06 AM, John Stultz wrote: > This patch wires up extcon support to the dwc2 driver > so that devices that use a modern generic phy driver > and don't use the usb-phy infrastructure can still > signal connect/disconnect events. > > Cc: Wei Xu > Cc: Guodong Xu > Cc: Amit Pundir >

Re: [PATCH] clk: uniphier: Fix build with gcc-4.4.

On 12/03, Masahiro Yamada wrote: > Hi Vinson, > > 2016-12-03 9:37 GMT+09:00 Vinson Lee : > > gcc-4.4 has issues with anonymous unions in initializers. > > > > CC drivers/clk/uniphier/clk-uniphier-sys.o > > drivers/clk/uniphier/clk-uniphier-sys.c:45: error: unknown

Re: [PATCH] clk: uniphier: Fix build with gcc-4.4.

On 12/03, Masahiro Yamada wrote: > Hi Vinson, > > 2016-12-03 9:37 GMT+09:00 Vinson Lee : > > gcc-4.4 has issues with anonymous unions in initializers. > > > > CC drivers/clk/uniphier/clk-uniphier-sys.o > > drivers/clk/uniphier/clk-uniphier-sys.c:45: error: unknown field ‘factor’ > >

Re: [PATCH 1/2] dt-bindings: mmc: add DT binding for S3C24XX MMC/SD/SDIO controller

On Fri, Dec 02, 2016 at 09:48:45AM +0900, Jaehoon Chung wrote: > On 12/02/2016 09:14 AM, Sergio Prado wrote: > > Adds the device tree bindings description for Samsung S3C24XX > > MMC/SD/SDIO controller, used as a connectivity interface with external > > MMC, SD and SDIO storage mediums. > > > >

Re: [PATCH 1/2] dt-bindings: mmc: add DT binding for S3C24XX MMC/SD/SDIO controller

On Fri, Dec 02, 2016 at 09:48:45AM +0900, Jaehoon Chung wrote: > On 12/02/2016 09:14 AM, Sergio Prado wrote: > > Adds the device tree bindings description for Samsung S3C24XX > > MMC/SD/SDIO controller, used as a connectivity interface with external > > MMC, SD and SDIO storage mediums. > > > >

Re: linux-next: build failure after merge of the pinctrl tree

On 2016-12-06 23:46, Stephen Rothwell wrote: > Hi Peter, > > On Tue, 6 Dec 2016 23:27:48 +0100 Peter Rosin wrote: >> >> The bug you are referring to is in the gpio tree, not pinctrl. >> That had me confused for a while, and is the reason I'm writing >> this. Maybe the next

Re: linux-next: build failure after merge of the pinctrl tree

On 2016-12-06 23:46, Stephen Rothwell wrote: > Hi Peter, > > On Tue, 6 Dec 2016 23:27:48 +0100 Peter Rosin wrote: >> >> The bug you are referring to is in the gpio tree, not pinctrl. >> That had me confused for a while, and is the reason I'm writing >> this. Maybe the next person need not be

[PATCH] x86: Optimize TIF checking in __switch_to_xtra.

For the TIF_BLOCKSTEP and TIF_NOTSC cases, __switch_to_xtra only needs to act if the value of the flags changes with the task switch. That leads to C code like: if (test_tsk_thread_flag(prev_p, TIF_BLOCKSTEP) ^ test_tsk_thread_flag(next_p, TIF_BLOCKSTEP)) { /* do work */ }

[PATCH] x86: Optimize TIF checking in __switch_to_xtra.

For the TIF_BLOCKSTEP and TIF_NOTSC cases, __switch_to_xtra only needs to act if the value of the flags changes with the task switch. That leads to C code like: if (test_tsk_thread_flag(prev_p, TIF_BLOCKSTEP) ^ test_tsk_thread_flag(next_p, TIF_BLOCKSTEP)) { /* do work */ }

[PATCH V4 08/11] megaraid_sas: Enable or Disable Fast path based on the PCI Threshold Bandwidth

Large SEQ IO workload should sent as non fast path commands This patch is depending on patch 7 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas.h| 8 + drivers/scsi/megaraid/megaraid_sas_base.c | 48

[PATCH V4 02/11] megaraid_sas: 128 MSIX Support

SAS3.5 Generic Megaraid based Controllers will have the support for 128 MSI-X vectors, resulting in the need to support 128 reply queues This patch is depending on patch 1 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas.h| 1 +

[PATCH V4 08/11] megaraid_sas: Enable or Disable Fast path based on the PCI Threshold Bandwidth

Large SEQ IO workload should sent as non fast path commands This patch is depending on patch 7 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas.h| 8 + drivers/scsi/megaraid/megaraid_sas_base.c | 48 +

[PATCH V4 02/11] megaraid_sas: 128 MSIX Support

SAS3.5 Generic Megaraid based Controllers will have the support for 128 MSI-X vectors, resulting in the need to support 128 reply queues This patch is depending on patch 1 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas.h| 1 +

[PATCH V4 06/11] megaraid_sas: Dynamic Raid Map Changes for SAS3.5 Generic Megaraid Controllers

SAS3.5 Generic Megaraid Controllers FW will support new dynamic RaidMap to have different sizes for different number of supported VDs. This patch is depending on patch 5 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas.h| 7 +

[PATCH V4 06/11] megaraid_sas: Dynamic Raid Map Changes for SAS3.5 Generic Megaraid Controllers

SAS3.5 Generic Megaraid Controllers FW will support new dynamic RaidMap to have different sizes for different number of supported VDs. This patch is depending on patch 5 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas.h| 7 +

[PATCH V4 07/11] megaraid_sas: Add the Support for SAS3.5 Generic Megaraid Controllers Capabilities

The Megaraid driver has to support the SAS3.5 Generic Megaraid Controllers Firmware functionality. This patch is depending on patch 6 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas_base.c | 53 ++---

[PATCH V4 07/11] megaraid_sas: Add the Support for SAS3.5 Generic Megaraid Controllers Capabilities

The Megaraid driver has to support the SAS3.5 Generic Megaraid Controllers Firmware functionality. This patch is depending on patch 6 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas_base.c | 53 ++---

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

Detect sequential IO streams and pass those IOs directly to FW. This patch is depending on patch 3 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas.h| 5 +- drivers/scsi/megaraid/megaraid_sas_base.c | 43 +++-

[PATCH V4 09/11] megaraid_sas: ldio_outstanding variable is not decremented in completion path

ldio outstanding variable needs to be decremented in io completion path for iMR dual queue depth This patch is depending on patch 8 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas_fusion.c | 9 +++-- 1 file changed, 7 insertions(+),

[PATCH V4 10/11] megaraid_sas: Implement the PD Map support for SAS3.5 Generic Megaraid Controllers

Update Linux driver to use new pdTargetId field for JBOD target ID This patch is depending on patch 9 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas.h| 105 +--- drivers/scsi/megaraid/megaraid_sas_base.c

[PATCH V4 03/11] megaraid_sas: EEDP Escape Mode Support for SAS3.5 Generic Megaraid Controllers

An UNMAP command on a PI formatted device will leave the Logical Block Application Tag and Logical Block Reference Tag as all F's (for those LBAs that are unmapped). To avoid IO errors if those LBAs are subsequently read before they are written with valid tag fields, the MPI SCSI IO requests

[PATCH V4 01/11] megaraid_sas: Add new pci device Ids for SAS3.5 Generic Megaraid Controllers

This patch contains new pci device ids for SAS3.5 Generic Megaraid Controllers V4: Removed the not supported PCI Device Ids Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas.h| 8 +++-

[PATCH V4 05/11] megaraid_sas: SAS3.5 Generic Megaraid Controllers Fast Path for RAID 1/10 Writes

To improve RAID 1/10 Write performance, OS drivers need to issue the required Write IOs as Fast Path IOs (after the appropriate checks allowing Fast Path to be used) to the appropriate physical drives (translated from the OS logical IO) and wait for all Write IOs to complete. If any of the

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

Detect sequential IO streams and pass those IOs directly to FW. This patch is depending on patch 3 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas.h| 5 +- drivers/scsi/megaraid/megaraid_sas_base.c | 43 +++-

[PATCH V4 09/11] megaraid_sas: ldio_outstanding variable is not decremented in completion path

ldio outstanding variable needs to be decremented in io completion path for iMR dual queue depth This patch is depending on patch 8 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas_fusion.c | 9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git

[PATCH V4 10/11] megaraid_sas: Implement the PD Map support for SAS3.5 Generic Megaraid Controllers

Update Linux driver to use new pdTargetId field for JBOD target ID This patch is depending on patch 9 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas.h| 105 +--- drivers/scsi/megaraid/megaraid_sas_base.c | 3 +

[PATCH V4 03/11] megaraid_sas: EEDP Escape Mode Support for SAS3.5 Generic Megaraid Controllers

An UNMAP command on a PI formatted device will leave the Logical Block Application Tag and Logical Block Reference Tag as all F's (for those LBAs that are unmapped). To avoid IO errors if those LBAs are subsequently read before they are written with valid tag fields, the MPI SCSI IO requests

[PATCH V4 01/11] megaraid_sas: Add new pci device Ids for SAS3.5 Generic Megaraid Controllers

This patch contains new pci device ids for SAS3.5 Generic Megaraid Controllers V4: Removed the not supported PCI Device Ids Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas.h| 8 +++- drivers/scsi/megaraid/megaraid_sas_base.c | 14 +-

[PATCH V4 05/11] megaraid_sas: SAS3.5 Generic Megaraid Controllers Fast Path for RAID 1/10 Writes

To improve RAID 1/10 Write performance, OS drivers need to issue the required Write IOs as Fast Path IOs (after the appropriate checks allowing Fast Path to be used) to the appropriate physical drives (translated from the OS logical IO) and wait for all Write IOs to complete. If any of the

[PATCH V4 11/11] megaraid_sas: driver version upgrade

Upgrade driver version. This patch is depending on patch 10 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/scsi/megaraid/megaraid_sas.h

[PATCH V4 11/11] megaraid_sas: driver version upgrade

Upgrade driver version. This patch is depending on patch 10 Signed-off-by: Sasikumar Chandrasekaran --- drivers/scsi/megaraid/megaraid_sas.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/scsi/megaraid/megaraid_sas.h b/drivers/scsi/megaraid/megaraid_sas.h

[PATCH V4 00/11] megaraid_sas: Updates for scsi-next

Sasikumar Chandrasekaran (11): megaraid_sas: Add new pci device Ids for SAS3.5 Generic Megaraid Controllers megaraid_sas: 128 MSIX Support megaraid_sas: EEDP Escape Mode Support for SAS3.5 Generic Megaraid Controllers megaraid_sas: SAS3.5 Generic Megaraid Controllers Stream

[PATCH V4 00/11] megaraid_sas: Updates for scsi-next

Sasikumar Chandrasekaran (11): megaraid_sas: Add new pci device Ids for SAS3.5 Generic Megaraid Controllers megaraid_sas: 128 MSIX Support megaraid_sas: EEDP Escape Mode Support for SAS3.5 Generic Megaraid Controllers megaraid_sas: SAS3.5 Generic Megaraid Controllers Stream

[PATCH v2 5/6] fscrypt: Delay bounce page pool allocation until needed

Since fscrypt users can now indicated if fscrypt_encrypt_page() should use a bounce page, we can delay the bounce page pool initialization util it is really needed. That is until fscrypt_operations has no FS_CFLG_OWN_PAGES flag set. Signed-off-by: David Gstir ---

[PATCH v2 2/6] fscrypt: Never allocate fscrypt_ctx on in-place encryption

In case of in-place encryption fscrypt_ctx was allocated but never released. Since we don't need it for in-place encryption, we skip allocating it. Fixes: 1c7dcf69eea3 ("fscrypt: Add in-place encryption mode") Signed-off-by: David Gstir --- fs/crypto/crypto.c | 30

[PATCH v2 5/6] fscrypt: Delay bounce page pool allocation until needed

Since fscrypt users can now indicated if fscrypt_encrypt_page() should use a bounce page, we can delay the bounce page pool initialization util it is really needed. That is until fscrypt_operations has no FS_CFLG_OWN_PAGES flag set. Signed-off-by: David Gstir --- fs/crypto/crypto.c | 9

[PATCH v2 2/6] fscrypt: Never allocate fscrypt_ctx on in-place encryption

In case of in-place encryption fscrypt_ctx was allocated but never released. Since we don't need it for in-place encryption, we skip allocating it. Fixes: 1c7dcf69eea3 ("fscrypt: Add in-place encryption mode") Signed-off-by: David Gstir --- fs/crypto/crypto.c | 30

[PATCH v2 4/6] fscrypt: Cleanup page locking requirements for fscrypt_{decrypt,encrypt}_page()

Rename the FS_CFLG_INPLACE_ENCRYPTION flag to FS_CFLG_OWN_PAGES which, when set, indicates that the fs uses pages under its own control as opposed to writeback pages which require locking and a bounce buffer for encryption. Signed-off-by: David Gstir --- fs/crypto/crypto.c

Re: Tearing down DMA transfer setup after DMA client has finished

On 06/12/2016 16:34, Måns Rullgård wrote: > Mason writes: > >> Meh. The two controller blocks share the I/O pins to the outside >> world, so it's not possible to have two concurrent accesses. > > OK, you failed to mention that part. Why are there two controllers at > all if only one or the

[PATCH v2 0/6] UBIFS related fscrypt updates

This series applies on top of Ted's fscrypt tree[0] addresses the review comments from Eric. Changes since v1: - Never allocate fscrypt_ctx in "own pages" mode - Fix code comments - Fix issues reported by checkpatch.pl [0] git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git fscrypt

[PATCH v2 3/6] fscrypt: Cleanup fscrypt_{decrypt,encrypt}_page()

- Improve documentation - Add BUG_ON(len == 0) to avoid accidental switch of offs and len parameters - Improve variable names for readability Signed-off-by: David Gstir --- fs/crypto/crypto.c | 93 +++-

Re: Tearing down DMA transfer setup after DMA client has finished

On 06/12/2016 16:34, Måns Rullgård wrote: > Mason writes: > >> Meh. The two controller blocks share the I/O pins to the outside >> world, so it's not possible to have two concurrent accesses. > > OK, you failed to mention that part. Why are there two controllers at > all if only one or the

[PATCH v2 0/6] UBIFS related fscrypt updates

This series applies on top of Ted's fscrypt tree[0] addresses the review comments from Eric. Changes since v1: - Never allocate fscrypt_ctx in "own pages" mode - Fix code comments - Fix issues reported by checkpatch.pl [0] git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git fscrypt

[PATCH v2 3/6] fscrypt: Cleanup fscrypt_{decrypt,encrypt}_page()

- Improve documentation - Add BUG_ON(len == 0) to avoid accidental switch of offs and len parameters - Improve variable names for readability Signed-off-by: David Gstir --- fs/crypto/crypto.c | 93 +++- include/linux/fscrypto.h | 8 ++--- 2

[PATCH v2 4/6] fscrypt: Cleanup page locking requirements for fscrypt_{decrypt,encrypt}_page()

Rename the FS_CFLG_INPLACE_ENCRYPTION flag to FS_CFLG_OWN_PAGES which, when set, indicates that the fs uses pages under its own control as opposed to writeback pages which require locking and a bounce buffer for encryption. Signed-off-by: David Gstir --- fs/crypto/crypto.c | 11

[PATCH v2 1/6] fscrypt: Use correct index in decrypt path.

Actually use the fs-provided index instead of always using page->index which is only set for page-cache pages. Fixes: 9c4bb8a3a9b4 ("fscrypt: Let fs select encryption index/tweak") Signed-off-by: David Gstir --- fs/crypto/crypto.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH v2 6/6] fscrypt: Rename FS_WRITE_PATH_FL to FS_CTX_HAS_BOUNCE_BUFFER_FL

... to better explain its purpose after introducing in-place encryption without bounce buffer. Signed-off-by: David Gstir --- fs/crypto/crypto.c | 6 +++--- include/linux/fscrypto.h | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v2 1/6] fscrypt: Use correct index in decrypt path.

Actually use the fs-provided index instead of always using page->index which is only set for page-cache pages. Fixes: 9c4bb8a3a9b4 ("fscrypt: Let fs select encryption index/tweak") Signed-off-by: David Gstir --- fs/crypto/crypto.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH v2 6/6] fscrypt: Rename FS_WRITE_PATH_FL to FS_CTX_HAS_BOUNCE_BUFFER_FL

... to better explain its purpose after introducing in-place encryption without bounce buffer. Signed-off-by: David Gstir --- fs/crypto/crypto.c | 6 +++--- include/linux/fscrypto.h | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/fs/crypto/crypto.c

[PATCH RT] net: Have __napi_schedule_irqoff() disable interrupts on RT

A customer hit a crash where the napi sd->poll_list became corrupted. The customer had the bnx2x driver, which does a __napi_schedule_irqoff() in its interrupt handler. Unfortunately, when running with CONFIG_PREEMPT_RT_FULL, this interrupt handler is run as a thread and is preemptable. The call

[PATCH RT] net: Have __napi_schedule_irqoff() disable interrupts on RT

A customer hit a crash where the napi sd->poll_list became corrupted. The customer had the bnx2x driver, which does a __napi_schedule_irqoff() in its interrupt handler. Unfortunately, when running with CONFIG_PREEMPT_RT_FULL, this interrupt handler is run as a thread and is preemptable. The call

Re: [PATCH 1/3] ARM: Define KERNEL_START and KERNEL_END

On 12/06/2016 02:43 PM, Chris Brandt wrote: > On 12/6/2016, Florian Fainelli wrote: >> diff --git a/arch/arm/mm/mmu.c b/arch/arm/mm/mmu.c >> index 4001dd15818d..18ef688a796e 100644 >> --- a/arch/arm/mm/mmu.c >> +++ b/arch/arm/mm/mmu.c >> @@ -1437,12 +1437,8 @@ static void __init kmap_init(void) >>

Re: [PATCH 1/3] ARM: Define KERNEL_START and KERNEL_END

On 12/06/2016 02:43 PM, Chris Brandt wrote: > On 12/6/2016, Florian Fainelli wrote: >> diff --git a/arch/arm/mm/mmu.c b/arch/arm/mm/mmu.c >> index 4001dd15818d..18ef688a796e 100644 >> --- a/arch/arm/mm/mmu.c >> +++ b/arch/arm/mm/mmu.c >> @@ -1437,12 +1437,8 @@ static void __init kmap_init(void) >>

Re: linux-next: build failure after merge of the pinctrl tree

Hi Peter, On Tue, 6 Dec 2016 23:27:48 +0100 Peter Rosin wrote: > > The bug you are referring to is in the gpio tree, not pinctrl. > That had me confused for a while, and is the reason I'm writing > this. Maybe the next person need not be confused... Part of the gpio tree has

RE: [PATCH 7/8] staging: fsl-dpaa2/eth: Add TODO file

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Tuesday, December 06, 2016 11:56 AM > To: Stuart Yoder > Cc: Ruxandra Ioana Radulescu ; > de...@driverdev.osuosl.org; linux- > ker...@vger.kernel.org;

Re: linux-next: build failure after merge of the pinctrl tree

Hi Peter, On Tue, 6 Dec 2016 23:27:48 +0100 Peter Rosin wrote: > > The bug you are referring to is in the gpio tree, not pinctrl. > That had me confused for a while, and is the reason I'm writing > this. Maybe the next person need not be confused... Part of the gpio tree has been merged into

RE: [PATCH 7/8] staging: fsl-dpaa2/eth: Add TODO file

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Tuesday, December 06, 2016 11:56 AM > To: Stuart Yoder > Cc: Ruxandra Ioana Radulescu ; > de...@driverdev.osuosl.org; linux- > ker...@vger.kernel.org; ag...@suse.de; a...@arndb.de; Alexandru Marginean > ;

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