Re: [PATCH v4 5/5] misc: pci_endpoint_test: Handle 64-bit BARs properly

On Thursday 08 March 2018 07:03 PM, Niklas Cassel wrote: > A 64-bit BAR consists of a BAR pair, where the second BAR has the > upper bits, so we cannot simply call pci_ioremap_bar() on every single > BAR index. > > The second BAR in a BAR pair will not have the IORESOURCE_MEM resource > flag

Re: [PATCH v4 5/5] misc: pci_endpoint_test: Handle 64-bit BARs properly

On Thursday 08 March 2018 07:03 PM, Niklas Cassel wrote: > A 64-bit BAR consists of a BAR pair, where the second BAR has the > upper bits, so we cannot simply call pci_ioremap_bar() on every single > BAR index. > > The second BAR in a BAR pair will not have the IORESOURCE_MEM resource > flag

Re: [PATCH v4 3/5] PCI: designware-ep: Make dw_pcie_ep_reset_bar() handle 64-bit BARs properly

Hi Niklas, On Thursday 08 March 2018 07:03 PM, Niklas Cassel wrote: > Since a 64-bit BAR consists of a BAR pair, we need to write to both > BARs in the BAR pair to clear the BAR properly. > > Signed-off-by: Niklas Cassel > --- > drivers/pci/dwc/pcie-designware-ep.c | 7

Re: [PATCH v4 3/5] PCI: designware-ep: Make dw_pcie_ep_reset_bar() handle 64-bit BARs properly

Hi Niklas, On Thursday 08 March 2018 07:03 PM, Niklas Cassel wrote: > Since a 64-bit BAR consists of a BAR pair, we need to write to both > BARs in the BAR pair to clear the BAR properly. > > Signed-off-by: Niklas Cassel > --- > drivers/pci/dwc/pcie-designware-ep.c | 7 +++ > 1 file

Re: [PATCH 2/3] i2c: mux: pca9541: namespace cleanup

On 2018-03-21 00:24, Vladimir Zapolskiy wrote: > Hi Peter, > > On 03/20/2018 11:31 AM, Peter Rosin wrote: >> In preparation for PCA9641 support, convert the mybus and busoff macros >> to functions, and in the process prefix them with pca9541_. Also prefix >> remaining chip specific macros with

Re: [PATCH 2/3] i2c: mux: pca9541: namespace cleanup

On 2018-03-21 00:24, Vladimir Zapolskiy wrote: > Hi Peter, > > On 03/20/2018 11:31 AM, Peter Rosin wrote: >> In preparation for PCA9641 support, convert the mybus and busoff macros >> to functions, and in the process prefix them with pca9541_. Also prefix >> remaining chip specific macros with

Re: update vruntime incorrectly When use rt_mutex

hi, Thanks for your feedback. On Fri, 2018-03-16 at 10:51 +0100, Peter Zijlstra wrote: > On Thu, Mar 15, 2018 at 03:36:10PM +0800, Kathleen Chang wrote: > > hi, > > > > We found the vruntime might update incorrectly when use rt_mutex. > > That's nice, on what kernel? > > Also, your email

Re: update vruntime incorrectly When use rt_mutex

hi, Thanks for your feedback. On Fri, 2018-03-16 at 10:51 +0100, Peter Zijlstra wrote: > On Thu, Mar 15, 2018 at 03:36:10PM +0800, Kathleen Chang wrote: > > hi, > > > > We found the vruntime might update incorrectly when use rt_mutex. > > That's nice, on what kernel? > > Also, your email

Re: [PATCH v4 2/5] PCI: designware-ep: Make dw_pcie_ep_set_bar() handle 64-bit BARs properly

Hi Niklas, On Thursday 08 March 2018 07:03 PM, Niklas Cassel wrote: > Since a 64-bit BAR consists of a BAR pair, we need to write to both > BARs in the BAR pair to setup the BAR properly. > > Signed-off-by: Niklas Cassel > --- > drivers/pci/dwc/pcie-designware-ep.c | 11

Re: [PATCH v4 2/5] PCI: designware-ep: Make dw_pcie_ep_set_bar() handle 64-bit BARs properly

Hi Niklas, On Thursday 08 March 2018 07:03 PM, Niklas Cassel wrote: > Since a 64-bit BAR consists of a BAR pair, we need to write to both > BARs in the BAR pair to setup the BAR properly. > > Signed-off-by: Niklas Cassel > --- > drivers/pci/dwc/pcie-designware-ep.c | 11 +-- > 1 file

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

On Wednesday 21 March 2018 08:15 AM, Mark Brown wrote: On Wed, Mar 21, 2018 at 01:30:40PM +1100, Stephen Rothwell wrote: Caused by commit 363fe37948e2 ("ASoC: amd: dma driver changes for BT I2S controller instance") I have used the sound-asoc tree from next-20180320 for today

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

On Wednesday 21 March 2018 08:15 AM, Mark Brown wrote: On Wed, Mar 21, 2018 at 01:30:40PM +1100, Stephen Rothwell wrote: Caused by commit 363fe37948e2 ("ASoC: amd: dma driver changes for BT I2S controller instance") I have used the sound-asoc tree from next-20180320 for today

Re: [PATCH 3/5] x86/smpboot: Make the check code more clear in prefill_possible_map()

Hi Peter, At 03/20/2018 08:39 PM, Peter Zijlstra wrote: On Tue, Mar 20, 2018 at 07:04:30PM +0800, Dou Liyang wrote: case 1: no | no | no | --> min (setup_possible_cpus, nr_cpu_ids, setup_max_cpus) case 2: no | no | yes| --> min (setup_possible_cpus, nr_cpu_ids) case 3: no | yes | no |

Re: [PATCH 3/5] x86/smpboot: Make the check code more clear in prefill_possible_map()

Hi Peter, At 03/20/2018 08:39 PM, Peter Zijlstra wrote: On Tue, Mar 20, 2018 at 07:04:30PM +0800, Dou Liyang wrote: case 1: no | no | no | --> min (setup_possible_cpus, nr_cpu_ids, setup_max_cpus) case 2: no | no | yes| --> min (setup_possible_cpus, nr_cpu_ids) case 3: no | yes | no |

[PATCH v2 2/2] dt-bindings: phy-qcom-qmp: Add UFS phy compitable string for sdm845

Update the compatible string for UFS QMP PHY on SDM845. Signed-off-by: Can Guo --- Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt

[PATCH v2 2/2] dt-bindings: phy-qcom-qmp: Add UFS phy compitable string for sdm845

Update the compatible string for UFS QMP PHY on SDM845. Signed-off-by: Can Guo --- Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt

[PATCH v2 0/2] Support for Qualcomm UFS QMP PHY on SDM845

This patch series adds support for UFS QMP PHY on SDM845 and the compitable string for it. This patch series depends on the current proposed QMP V3 USB3 UNI PHY support for sdm845 driver [1] and also based on the DT bindings for the QMP V3 USB3 PHYs based dirver [2]. This series can only be merged

[PATCH v2 0/2] Support for Qualcomm UFS QMP PHY on SDM845

This patch series adds support for UFS QMP PHY on SDM845 and the compitable string for it. This patch series depends on the current proposed QMP V3 USB3 UNI PHY support for sdm845 driver [1] and also based on the DT bindings for the QMP V3 USB3 PHYs based dirver [2]. This series can only be merged

[PATCH v2 1/2] phy: Add QMP phy based UFS phy support for sdm845

Add UFS PHY support to make SDM845 UFS work with common PHY framework. Signed-off-by: Can Guo --- drivers/phy/qualcomm/phy-qcom-qmp.c | 122 +++- drivers/phy/qualcomm/phy-qcom-qmp.h | 8 +++ 2 files changed, 127 insertions(+), 3

[PATCH] mtd: devices: check mtd_device_register() return code

stfsm_probe() misses error handling of mtd_device_register(). Signed-off-by: Arushi Singhal --- drivers/mtd/devices/st_spi_fsm.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/drivers/mtd/devices/st_spi_fsm.c

[PATCH v2 1/2] phy: Add QMP phy based UFS phy support for sdm845

Add UFS PHY support to make SDM845 UFS work with common PHY framework. Signed-off-by: Can Guo --- drivers/phy/qualcomm/phy-qcom-qmp.c | 122 +++- drivers/phy/qualcomm/phy-qcom-qmp.h | 8 +++ 2 files changed, 127 insertions(+), 3 deletions(-) diff --git

[PATCH] mtd: devices: check mtd_device_register() return code

stfsm_probe() misses error handling of mtd_device_register(). Signed-off-by: Arushi Singhal --- drivers/mtd/devices/st_spi_fsm.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/drivers/mtd/devices/st_spi_fsm.c b/drivers/mtd/devices/st_spi_fsm.c index 7bc29d7..e1aa4f8

[PATCH] eeprom: at25: sizeof t should be sizeof(t)

Resolved checkpatch warning "sizeof t should be sizeof(t)" issue found by checkpatch. Signed-off-by: Devang Panchal --- drivers/misc/eeprom/at25.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/misc/eeprom/at25.c

[PATCH] eeprom: at25: sizeof t should be sizeof(t)

Resolved checkpatch warning "sizeof t should be sizeof(t)" issue found by checkpatch. Signed-off-by: Devang Panchal --- drivers/misc/eeprom/at25.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/misc/eeprom/at25.c b/drivers/misc/eeprom/at25.c index 9282ffd..6a7d4a2

Re: [PATCH 1/5] x86/smpboot: Add the missing description of possible_cpus

Hi Peter, At 03/20/2018 08:37 PM, Peter Zijlstra wrote: On Tue, Mar 20, 2018 at 07:04:28PM +0800, Dou Liyang wrote: + possible_cpus= [s390,x86_64] Use this to set hotpluggable cpus. + This option sets possible_cpus bits in cpu_possible_map. +

Re: [PATCH 1/5] x86/smpboot: Add the missing description of possible_cpus

Hi Peter, At 03/20/2018 08:37 PM, Peter Zijlstra wrote: On Tue, Mar 20, 2018 at 07:04:28PM +0800, Dou Liyang wrote: + possible_cpus= [s390,x86_64] Use this to set hotpluggable cpus. + This option sets possible_cpus bits in cpu_possible_map. +

Re: [PATCH v4 1/5] PCI: endpoint: BAR width should not depend on sizeof dma_addr_t

On Thursday 08 March 2018 07:03 PM, Niklas Cassel wrote: > If a BAR supports 64-bit width or not depends on the hardware, > and should thus not depend on sizeof(dma_addr_t). > > Since this driver is generic, default to always using BAR width > of 32-bits. 64-bit BARs can easily be tested by

Re: [PATCH v4 1/5] PCI: endpoint: BAR width should not depend on sizeof dma_addr_t

On Thursday 08 March 2018 07:03 PM, Niklas Cassel wrote: > If a BAR supports 64-bit width or not depends on the hardware, > and should thus not depend on sizeof(dma_addr_t). > > Since this driver is generic, default to always using BAR width > of 32-bits. 64-bit BARs can easily be tested by

Re: [PATCH 4.4 000/134] 4.4.123-stable review

On Tue, Mar 20, 2018 at 06:32:00AM -0700, Guenter Roeck wrote: > On 03/19/2018 11:04 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.4.123 release. > > There are 134 patches in this series, all will be posted as a response > > to this one. If anyone has

Re: [PATCH 4.4 000/134] 4.4.123-stable review

On Tue, Mar 20, 2018 at 06:32:00AM -0700, Guenter Roeck wrote: > On 03/19/2018 11:04 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.4.123 release. > > There are 134 patches in this series, all will be posted as a response > > to this one. If anyone has

[PATCH] USB:fix USB3 devices behind USB3 hubs not resuming at hibernate thaw

USB3 hubs don't support global suspend. USB3 specification 10.10, Enhanced SuperSpeed hubs only support selective suspend and resume, they do not support global suspend/resume where the hub downstream facing ports states are not affected. When system enters hibernation it first enters freeze

[PATCH] USB:fix USB3 devices behind USB3 hubs not resuming at hibernate thaw

USB3 hubs don't support global suspend. USB3 specification 10.10, Enhanced SuperSpeed hubs only support selective suspend and resume, they do not support global suspend/resume where the hub downstream facing ports states are not affected. When system enters hibernation it first enters freeze

Re: [PATCH] ARM: dts: db600c: add support to pcie refclk

Thanks Bjorn for the review comments, On 21/03/18 11:35, Bjorn Andersson wrote: On Tue 20 Mar 17:28 HKT 2018, Srinivas Kandagatla wrote: From: Srinivas Kandagatla This patch adds support to external pcie refclk. Signed-off-by: Srinivas Kandagatla

Re: [PATCH] ARM: dts: db600c: add support to pcie refclk

Thanks Bjorn for the review comments, On 21/03/18 11:35, Bjorn Andersson wrote: On Tue 20 Mar 17:28 HKT 2018, Srinivas Kandagatla wrote: From: Srinivas Kandagatla This patch adds support to external pcie refclk. Signed-off-by: Srinivas Kandagatla ---

Re: [PATCH 10/15] mm/hmm: do not differentiate between empty entry or missing directory v2

On 03/19/2018 07:00 PM, jgli...@redhat.com wrote: > From: Jérôme Glisse > > There is no point in differentiating between a range for which there > is not even a directory (and thus entries) and empty entry (pte_none() > or pmd_none() returns true). > > Simply drop the

Re: [PATCH 10/15] mm/hmm: do not differentiate between empty entry or missing directory v2

On 03/19/2018 07:00 PM, jgli...@redhat.com wrote: > From: Jérôme Glisse > > There is no point in differentiating between a range for which there > is not even a directory (and thus entries) and empty entry (pte_none() > or pmd_none() returns true). > > Simply drop the distinction ie remove

Re: [PATCH] iommu/mediatek: Fix protect memory setting

Hi Joerg, On Tue, 2018-03-20 at 13:57 -0500, Joerg Roedel wrote: > On Sun, Mar 18, 2018 at 09:52:54AM +0800, Yong Wu wrote: > > To avoid adding this complex macro or a new function, I put > > it in the code and backup its value in the suspend registers. > > Missing Signed-off-by. Signed-off-by

Re: [PATCH] iommu/mediatek: Fix protect memory setting

Hi Joerg, On Tue, 2018-03-20 at 13:57 -0500, Joerg Roedel wrote: > On Sun, Mar 18, 2018 at 09:52:54AM +0800, Yong Wu wrote: > > To avoid adding this complex macro or a new function, I put > > it in the code and backup its value in the suspend registers. > > Missing Signed-off-by. Signed-off-by

[PATCH] builddeb: Fix header package regarding dtc source links

Since d5d332d3f7e8, a couple of links in scripts/dtc/include-prefixes are additionally required in order to build device trees with the header package. Signed-off-by: Jan Kiszka --- scripts/package/builddeb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH] builddeb: Fix header package regarding dtc source links

Since d5d332d3f7e8, a couple of links in scripts/dtc/include-prefixes are additionally required in order to build device trees with the header package. Signed-off-by: Jan Kiszka --- scripts/package/builddeb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[GIT PULL] extcon next for v4.17

Dear Greg, This is extcon-next pull request for v4.17. I add detailed description of this pull request on below. Please pull extcon with following updates. Best Regards, Chanwoo Choi The following changes since commit 4a3928c6f8a53fa1aed28ccba227742486e8ddcb: Linux 4.16-rc3 (2018-02-25

[GIT PULL] extcon next for v4.17

Dear Greg, This is extcon-next pull request for v4.17. I add detailed description of this pull request on below. Please pull extcon with following updates. Best Regards, Chanwoo Choi The following changes since commit 4a3928c6f8a53fa1aed28ccba227742486e8ddcb: Linux 4.16-rc3 (2018-02-25

Re: [PATCH 13/15] mm/hmm: factor out pte and pmd handling to simplify hmm_vma_walk_pmd()

On 03/19/2018 07:00 PM, jgli...@redhat.com wrote: > From: Jérôme Glisse > > No functional change, just create one function to handle pmd and one > to handle pte (hmm_vma_handle_pmd() and hmm_vma_handle_pte()). > > Signed-off-by: Jérôme Glisse > Cc:

Re: [PATCH 13/15] mm/hmm: factor out pte and pmd handling to simplify hmm_vma_walk_pmd()

On 03/19/2018 07:00 PM, jgli...@redhat.com wrote: > From: Jérôme Glisse > > No functional change, just create one function to handle pmd and one > to handle pte (hmm_vma_handle_pmd() and hmm_vma_handle_pte()). > > Signed-off-by: Jérôme Glisse > Cc: Evgeny Baskakov > Cc: Ralph Campbell > Cc:

Re: [RFC PATCH v2 2/4] mm/__free_one_page: skip merge for order-0 page unless compaction failed

On Tue, Mar 20, 2018 at 09:21:33PM -0700, Figo.zhang wrote: > suppose that in free_one_page() will try to merge to high order anytime , > but now in your patch, > those merge has postponed when system in low memory status, it is very easy > let system trigger > low memory state and get poor

Re: [RFC PATCH v2 2/4] mm/__free_one_page: skip merge for order-0 page unless compaction failed

On Tue, Mar 20, 2018 at 09:21:33PM -0700, Figo.zhang wrote: > suppose that in free_one_page() will try to merge to high order anytime , > but now in your patch, > those merge has postponed when system in low memory status, it is very easy > let system trigger > low memory state and get poor

[PATCH V2 6/9] arm64: tegra: Add pwm based fan support on Tegra186

Add pwm fan driver support on Tegra186 SoC. Signed-off-by: Rajkumar Rampelli --- V2: Removed generic-pwm-tachometer driver dt node and using pwm-fan driver for reading fan speed. arch/arm64/boot/dts/nvidia/tegra186.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff

[PATCH V2 6/9] arm64: tegra: Add pwm based fan support on Tegra186

Add pwm fan driver support on Tegra186 SoC. Signed-off-by: Rajkumar Rampelli --- V2: Removed generic-pwm-tachometer driver dt node and using pwm-fan driver for reading fan speed. arch/arm64/boot/dts/nvidia/tegra186.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH V2 0/9] Implementation of Tegra Tachometer driver

The following patches adds support for PWM based Tegra Tachometer driver which implements PWM capture interface to analyze the PWM signal of a electronic fan and reports it in periods and duty cycles. Added fan device attribute fan1_input in pwm-fan driver to monitor the speed of fan in rotations

[PATCH V2 0/9] Implementation of Tegra Tachometer driver

The following patches adds support for PWM based Tegra Tachometer driver which implements PWM capture interface to analyze the PWM signal of a electronic fan and reports it in periods and duty cycles. Added fan device attribute fan1_input in pwm-fan driver to monitor the speed of fan in rotations

[PATCH 0/1] cover-letter/lz4: Implement lz4 with dynamic offset length.

(Added cover letter to avoid much text in patch description) LZ4 specification defines 2 byte offset length for 64 KB data. But in case of ZRAM we compress data per page and in most of architecture PAGE_SIZE is 4KB. So we can decide offset length based on actual offset value. For this we can

[PATCH 0/1] cover-letter/lz4: Implement lz4 with dynamic offset length.

(Added cover letter to avoid much text in patch description) LZ4 specification defines 2 byte offset length for 64 KB data. But in case of ZRAM we compress data per page and in most of architecture PAGE_SIZE is 4KB. So we can decide offset length based on actual offset value. For this we can

[PATCH V2 8/9] arm64: defconfig: enable Nvidia Tegra Tachometer as a module

Tegra Tachometer driver implements PWM capture to measure period. Enable this driver as a module in the ARM64 defconfig. Signed-off-by: Rajkumar Rampelli --- V2: No changes in this patch arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH V2 9/9] arm64: defconfig: enable pwm-fan as a loadable module

Enable pwm-fan driver to make use of a PWM interface to read speed of a fan in rotations per minute. Signed-off-by: Rajkumar Rampelli --- V2: Added pwm-fan driver support as a loadable module. Removed generic-pwm-tachometer driver support which was added as part of v1

[PATCH V2 8/9] arm64: defconfig: enable Nvidia Tegra Tachometer as a module

Tegra Tachometer driver implements PWM capture to measure period. Enable this driver as a module in the ARM64 defconfig. Signed-off-by: Rajkumar Rampelli --- V2: No changes in this patch arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH V2 9/9] arm64: defconfig: enable pwm-fan as a loadable module

Enable pwm-fan driver to make use of a PWM interface to read speed of a fan in rotations per minute. Signed-off-by: Rajkumar Rampelli --- V2: Added pwm-fan driver support as a loadable module. Removed generic-pwm-tachometer driver support which was added as part of v1

[PATCH 1/1] lz4: Implement lz4 with dynamic offset length.

LZ4 specification defines 2 byte offset length for 64 KB data. But in case of ZRAM we compress data per page and in most of architecture PAGE_SIZE is 4KB. So we can decide offset length based on actual offset value. For this we can reserve 1 bit to decide offset length (1 byte or 2 byte). 2 byte

[PATCH V2 7/9] hwmon: pwm-fan: add sysfs node to read rpm of fan

Add fan device attribute fan1_input in pwm-fan driver to read speed of fan in rotations per minute. Signed-off-by: Rajkumar Rampelli --- V2: Removed generic-pwm-tachometer driver and using pwm-fan driver as per suggestions to read fan speed. Added fan device attribute

[PATCH V2 7/9] hwmon: pwm-fan: add sysfs node to read rpm of fan

Add fan device attribute fan1_input in pwm-fan driver to read speed of fan in rotations per minute. Signed-off-by: Rajkumar Rampelli --- V2: Removed generic-pwm-tachometer driver and using pwm-fan driver as per suggestions to read fan speed. Added fan device attribute to report speed

[PATCH 1/1] lz4: Implement lz4 with dynamic offset length.

LZ4 specification defines 2 byte offset length for 64 KB data. But in case of ZRAM we compress data per page and in most of architecture PAGE_SIZE is 4KB. So we can decide offset length based on actual offset value. For this we can reserve 1 bit to decide offset length (1 byte or 2 byte). 2 byte

[PATCH V2 5/9] pwm: tegra: Add PWM based Tachometer driver

PWM Tachometer driver capture the PWM signal which is output of FAN in general and provide the period of PWM signal which is converted to RPM by SW. Add Tegra Tachometer driver which implements the pwm-capture to measure period. Signed-off-by: Rajkumar Rampelli Signed-off-by:

[PATCH V2 5/9] pwm: tegra: Add PWM based Tachometer driver

PWM Tachometer driver capture the PWM signal which is output of FAN in general and provide the period of PWM signal which is converted to RPM by SW. Add Tegra Tachometer driver which implements the pwm-capture to measure period. Signed-off-by: Rajkumar Rampelli Signed-off-by: Laxman Dewangan

[PATCH V2 1/9] pwm: core: Add support for PWM HW driver with pwm capture only

Add support for pwm HW driver which has only capture functionality. This helps to implement the PWM based Tachometer driver which reads the PWM output signals from electronic fans. PWM Tachometer captures the period and duty cycle of the PWM signal Add conditional checks for callabacks enable(),

[PATCH V2 1/9] pwm: core: Add support for PWM HW driver with pwm capture only

Add support for pwm HW driver which has only capture functionality. This helps to implement the PWM based Tachometer driver which reads the PWM output signals from electronic fans. PWM Tachometer captures the period and duty cycle of the PWM signal Add conditional checks for callabacks enable(),

[PATCH V2 4/9] arm64: tegra: Add Tachometer Controller on Tegra186

The NVIDIA Tegra186 SoC has a Tachometer Controller that analyzes the PWM signal of a Fan and reports the period value through pwm interface. Signed-off-by: Rajkumar Rampelli --- V2: Renamed clock-names/reset-names dt properties values to "tachometer" Renamed compatible

[PATCH V2 4/9] arm64: tegra: Add Tachometer Controller on Tegra186

The NVIDIA Tegra186 SoC has a Tachometer Controller that analyzes the PWM signal of a Fan and reports the period value through pwm interface. Signed-off-by: Rajkumar Rampelli --- V2: Renamed clock-names/reset-names dt properties values to "tachometer" Renamed compatible property value to

[PATCH V2 2/9] arm64: tegra: Add PWM controller on Tegra186 soc

The NVIDIA Tegra186 SoC has a PWM controller which is used in FAN control use case. Signed-off-by: Rajkumar Rampelli --- V2: no changes in this patch arch/arm64/boot/dts/nvidia/tegra186.dtsi | 11 +++ 1 file changed, 11 insertions(+) diff --git

[PATCH V2 3/9] dt-bindings: Tegra186 tachometer device tree bindings

Supply Device tree binding documentation for the NVIDIA Tegra186 SoC's Tachometer Controller Signed-off-by: Rajkumar Rampelli --- V2: Renamed compatible string to "nvidia,tegra186-pwm-tachometer" Renamed dt property values of clock-names and reset-names to "tachometer"

[PATCH V2 2/9] arm64: tegra: Add PWM controller on Tegra186 soc

The NVIDIA Tegra186 SoC has a PWM controller which is used in FAN control use case. Signed-off-by: Rajkumar Rampelli --- V2: no changes in this patch arch/arm64/boot/dts/nvidia/tegra186.dtsi | 11 +++ 1 file changed, 11 insertions(+) diff --git

[PATCH V2 3/9] dt-bindings: Tegra186 tachometer device tree bindings

Supply Device tree binding documentation for the NVIDIA Tegra186 SoC's Tachometer Controller Signed-off-by: Rajkumar Rampelli --- V2: Renamed compatible string to "nvidia,tegra186-pwm-tachometer" Renamed dt property values of clock-names and reset-names to "tachometer" from "tach"

[PATCH v3 2/2] staging: media: davinci_vpfe: add kfree() on goto err statement

It needs to free of allocated params value in the goto error statement. Signed-off-by: Ji-Hun Kim --- Changes since v2: - add kfree(params) on the error case of the function - rename unclear goto statement name - declare the params value at start of the function, so

[PATCH v3 2/2] staging: media: davinci_vpfe: add kfree() on goto err statement

It needs to free of allocated params value in the goto error statement. Signed-off-by: Ji-Hun Kim --- Changes since v2: - add kfree(params) on the error case of the function - rename unclear goto statement name - declare the params value at start of the function, so it can be free end

Re: [PATCH 15/15] mm/hmm: use device driver encoding for HMM pfn v2

On 03/19/2018 07:00 PM, jgli...@redhat.com wrote: > From: Jérôme Glisse > > User of hmm_vma_fault() and hmm_vma_get_pfns() provide a flags array > and pfn shift value allowing them to define their own encoding for HMM > pfn that are fill inside the pfns array of the hmm_range

Re: [PATCH 15/15] mm/hmm: use device driver encoding for HMM pfn v2

On 03/19/2018 07:00 PM, jgli...@redhat.com wrote: > From: Jérôme Glisse > > User of hmm_vma_fault() and hmm_vma_get_pfns() provide a flags array > and pfn shift value allowing them to define their own encoding for HMM > pfn that are fill inside the pfns array of the hmm_range struct. With > this

[PATCH v3 1/2] staging: media: davinci_vpfe: add error handling on kmalloc failure

There is no failure checking on the param value which will be allocated memory by kmalloc. Add a null pointer checking statement. Then goto error: and return -ENOMEM error code when kmalloc is failed. Signed-off-by: Ji-Hun Kim --- Changes since v1: - Return with -ENOMEM

[PATCH v3 1/2] staging: media: davinci_vpfe: add error handling on kmalloc failure

There is no failure checking on the param value which will be allocated memory by kmalloc. Add a null pointer checking statement. Then goto error: and return -ENOMEM error code when kmalloc is failed. Signed-off-by: Ji-Hun Kim --- Changes since v1: - Return with -ENOMEM directly, instead of

[PATCH 1/1] mm/page_owner: fix recursion bug after changing skip entries

This patch fixes "5f48f0bd4e368425db4424b9afd1bd251d32367a". (mm, page_owner: skip unnecessary stack_trace entries) Because if we skip first two entries then logic of checking count value as 2 for recursion is broken and code will go in one depth recursion. so we need to check only one call of

[PATCH 1/1] mm/page_owner: fix recursion bug after changing skip entries

This patch fixes "5f48f0bd4e368425db4424b9afd1bd251d32367a". (mm, page_owner: skip unnecessary stack_trace entries) Because if we skip first two entries then logic of checking count value as 2 for recursion is broken and code will go in one depth recursion. so we need to check only one call of

Re: linux-next: manual merge of the ftrace tree with the jc_docs tree

Hi all, On Wed, 21 Mar 2018 15:31:27 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the ftrace tree got a conflict in: > > Documentation/trace/ftrace.txt > (converted to Documentation/trace/ftrace.rst) There was another conflict involving

Re: linux-next: manual merge of the ftrace tree with the jc_docs tree

Hi all, On Wed, 21 Mar 2018 15:31:27 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the ftrace tree got a conflict in: > > Documentation/trace/ftrace.txt > (converted to Documentation/trace/ftrace.rst) There was another conflict involving

[PATCH] tty/nozomi: refactor macros and functions

Cleanup a few messy sections of code by replacing constructs like `len__ > TMP_BUF_MAX ? TMP_BUF_MAX : len__` with `min_t(u32, len__, TMP_BUF_MAX)` and naming identifiers more descriptively (where appropriate). A few sections were nested pretty deeply and have been replaced with shallower (but

[PATCH] tty/nozomi: refactor macros and functions

Cleanup a few messy sections of code by replacing constructs like `len__ > TMP_BUF_MAX ? TMP_BUF_MAX : len__` with `min_t(u32, len__, TMP_BUF_MAX)` and naming identifiers more descriptively (where appropriate). A few sections were nested pretty deeply and have been replaced with shallower (but

linux-next: manual merge of the ftrace tree with the jc_docs tree

Hi Steven, Today's linux-next merge of the ftrace tree got a conflict in: Documentation/trace/ftrace.txt (converted to Documentation/trace/ftrace.rst) between commit: 1f198e22bc3a ("trace doc: convert trace/ftrace.txt to rst format") from the jc_docs tree and commit: 2c1ea60b195d

linux-next: manual merge of the ftrace tree with the jc_docs tree

Hi Steven, Today's linux-next merge of the ftrace tree got a conflict in: Documentation/trace/ftrace.txt (converted to Documentation/trace/ftrace.rst) between commit: 1f198e22bc3a ("trace doc: convert trace/ftrace.txt to rst format") from the jc_docs tree and commit: 2c1ea60b195d

[PATCH] libnvdimm, region: hide persistence_domain when unknown

Similar to other region attributes, do not emit the persistence_domain attribute if its contents are empty. Fixes: 96c3a239054a ("libnvdimm: expose platform persistence attr...") Cc: Dave Jiang Signed-off-by: Dan Williams ---

[PATCH] libnvdimm, region: hide persistence_domain when unknown

Similar to other region attributes, do not emit the persistence_domain attribute if its contents are empty. Fixes: 96c3a239054a ("libnvdimm: expose platform persistence attr...") Cc: Dave Jiang Signed-off-by: Dan Williams --- drivers/nvdimm/region_devs.c |7 +++ 1 file changed, 7

Re: [PATCH 04/15] mm/hmm: unregister mmu_notifier when last HMM client quit

On 03/19/2018 07:00 PM, jgli...@redhat.com wrote: > From: Jérôme Glisse > > This code was lost in translation at one point. This properly call > mmu_notifier_unregister_no_release() once last user is gone. This > fix the zombie mm_struct as without this patch we do not drop

Re: [PATCH 04/15] mm/hmm: unregister mmu_notifier when last HMM client quit

On 03/19/2018 07:00 PM, jgli...@redhat.com wrote: > From: Jérôme Glisse > > This code was lost in translation at one point. This properly call > mmu_notifier_unregister_no_release() once last user is gone. This > fix the zombie mm_struct as without this patch we do not drop the > refcount we

Re: [PATCH 03/15] mm/hmm: HMM should have a callback before MM is destroyed v2

On 03/19/2018 07:00 PM, jgli...@redhat.com wrote: > From: Ralph Campbell > > The hmm_mirror_register() function registers a callback for when > the CPU pagetable is modified. Normally, the device driver will > call hmm_mirror_unregister() when the process using the device

Re: [PATCH 03/15] mm/hmm: HMM should have a callback before MM is destroyed v2

On 03/19/2018 07:00 PM, jgli...@redhat.com wrote: > From: Ralph Campbell > > The hmm_mirror_register() function registers a callback for when > the CPU pagetable is modified. Normally, the device driver will > call hmm_mirror_unregister() when the process using the device is > finished. However,

Re: [PATCH v4 0/5] PCI endpoint 64-bit BAR fixes

On Mon, Mar 19, 2018 at 04:52:34PM +, Lorenzo Pieralisi wrote: > On Thu, Mar 08, 2018 at 02:33:25PM +0100, Niklas Cassel wrote: > > PCI endpoint fixes to improve the way 64-bit BARs are handled. > > > > > > There are still future improvements that could be made: > > > > pci-epf-test.c

Re: [PATCH v4 0/5] PCI endpoint 64-bit BAR fixes

On Mon, Mar 19, 2018 at 04:52:34PM +, Lorenzo Pieralisi wrote: > On Thu, Mar 08, 2018 at 02:33:25PM +0100, Niklas Cassel wrote: > > PCI endpoint fixes to improve the way 64-bit BARs are handled. > > > > > > There are still future improvements that could be made: > > > > pci-epf-test.c

Re: [PATCH 1/2] big key: get rid of stack array allocation

Hi Eric, On Wed, Mar 14, 2018 at 06:51:39PM -0700, Eric Biggers wrote: > On Mon, Mar 12, 2018 at 10:29:06PM -0600, Tycho Andersen wrote: > > We're interested in getting rid of all of the stack allocated arrays in the > > kernel [1]. This patch removes one in keys by switching to malloc/free. > >

Re: [PATCH 1/2] big key: get rid of stack array allocation

Hi Eric, On Wed, Mar 14, 2018 at 06:51:39PM -0700, Eric Biggers wrote: > On Mon, Mar 12, 2018 at 10:29:06PM -0600, Tycho Andersen wrote: > > We're interested in getting rid of all of the stack allocated arrays in the > > kernel [1]. This patch removes one in keys by switching to malloc/free. > >

Re: [PATCH 2/2] dh key: get rid of stack array allocation

Hi Eric, On Wed, Mar 14, 2018 at 07:21:12PM -0700, Eric Biggers wrote: > On Mon, Mar 12, 2018 at 10:29:07PM -0600, Tycho Andersen wrote: > > Similarly to the previous patch, we would like to get rid of stack > > allocated arrays: https://lkml.org/lkml/2018/3/7/621 > > > > In this case, we can

Re: [PATCH 2/2] dh key: get rid of stack array allocation

Hi Eric, On Wed, Mar 14, 2018 at 07:21:12PM -0700, Eric Biggers wrote: > On Mon, Mar 12, 2018 at 10:29:07PM -0600, Tycho Andersen wrote: > > Similarly to the previous patch, we would like to get rid of stack > > allocated arrays: https://lkml.org/lkml/2018/3/7/621 > > > > In this case, we can

Re: [PATCH v4 5/5] misc: pci_endpoint_test: Handle 64-bit BARs properly

Hello Greg, Lorenzo is fine with this series ( https://marc.info/?l=linux-kernel=152147837619191=2 ) However, he wants your ack on this patch before merging. Could you please have a look at this patch? Kind regards, Niklas On Thu, Mar 08, 2018 at 02:33:30PM +0100, Niklas Cassel wrote: > A

Re: [PATCH v4 5/5] misc: pci_endpoint_test: Handle 64-bit BARs properly

Hello Greg, Lorenzo is fine with this series ( https://marc.info/?l=linux-kernel=152147837619191=2 ) However, he wants your ack on this patch before merging. Could you please have a look at this patch? Kind regards, Niklas On Thu, Mar 08, 2018 at 02:33:30PM +0100, Niklas Cassel wrote: > A

Re: uvcvideo: Unknown video format,00000032-0002-0010-8000-00aa00389b71

Le mardi 20 mars 2018 à 20:04 +0200, Laurent Pinchart a écrit : > Hi Nicolas, > > On Tuesday, 20 March 2018 19:45:51 EET Nicolas Dufresne wrote: > > Le mardi 20 mars 2018 à 13:20 +0100, Paul Menzel a écrit : > > > Dear Linux folks, > > > > > > > > > On the Dell XPS 13 9370, Linux 4.16-rc6

Re: uvcvideo: Unknown video format,00000032-0002-0010-8000-00aa00389b71

Le mardi 20 mars 2018 à 20:04 +0200, Laurent Pinchart a écrit : > Hi Nicolas, > > On Tuesday, 20 March 2018 19:45:51 EET Nicolas Dufresne wrote: > > Le mardi 20 mars 2018 à 13:20 +0100, Paul Menzel a écrit : > > > Dear Linux folks, > > > > > > > > > On the Dell XPS 13 9370, Linux 4.16-rc6

  1   2   3   4   5   6   7   8   9   10   >