Re: [PATCH 2/2] mm, memory_hotplug: remove timeout from __offline_memory

On 09/04/2017 02:45 PM, Michal Hocko wrote: > On Mon 04-09-17 17:05:15, Xishi Qiu wrote: >> On 2017/9/4 17:01, Michal Hocko wrote: >> >>> On Mon 04-09-17 16:58:30, Xishi Qiu wrote: On 2017/9/4 16:21, Michal Hocko wrote: > From: Michal Hocko > > We have a

Re: [PATCH 2/2] mm, memory_hotplug: remove timeout from __offline_memory

On 09/04/2017 02:45 PM, Michal Hocko wrote: > On Mon 04-09-17 17:05:15, Xishi Qiu wrote: >> On 2017/9/4 17:01, Michal Hocko wrote: >> >>> On Mon 04-09-17 16:58:30, Xishi Qiu wrote: On 2017/9/4 16:21, Michal Hocko wrote: > From: Michal Hocko > > We have a hardcoded 120s

[RFC v3 3/7] platform/x86: intel_pmc_ipc: Use regmap calls for GCR updates

From: Kuppuswamy Sathyanarayanan Currently, update_no_reboot_bit() function implemented in this driver uses mutex_lock to protect its register updates. But this function is called with in atomic context in iTCO_wdt_start() and iTCO_wdt_stop() functions

[RFC v3 3/7] platform/x86: intel_pmc_ipc: Use regmap calls for GCR updates

From: Kuppuswamy Sathyanarayanan Currently, update_no_reboot_bit() function implemented in this driver uses mutex_lock to protect its register updates. But this function is called with in atomic context in iTCO_wdt_start() and iTCO_wdt_stop() functions in iTCO_wdt.c driver, which in turn causes

[RFC v3 5/7] platform/x86: intel_punit_ipc: Use generic intel ipc device calls

From: Kuppuswamy Sathyanarayanan Removed redundant IPC helper functions and refactored the driver to use APIs provided by generic IPC driver. This patch also cleans-up PUNIT IPC user drivers to use APIs provided by generic IPC driver. Signed-off-by:

[RFC v3 5/7] platform/x86: intel_punit_ipc: Use generic intel ipc device calls

From: Kuppuswamy Sathyanarayanan Removed redundant IPC helper functions and refactored the driver to use APIs provided by generic IPC driver. This patch also cleans-up PUNIT IPC user drivers to use APIs provided by generic IPC driver. Signed-off-by: Kuppuswamy Sathyanarayanan ---

[RFC v3 2/7] platform/x86: intel_pmc_ipc: Use MFD framework to create dependent devices

From: Kuppuswamy Sathyanarayanan Currently, we have lot of repetitive code in dependent device resource allocation and device creation handling code. This logic can be improved if we use MFD framework for dependent device creation. This patch adds this

[RFC v3 2/7] platform/x86: intel_pmc_ipc: Use MFD framework to create dependent devices

From: Kuppuswamy Sathyanarayanan Currently, we have lot of repetitive code in dependent device resource allocation and device creation handling code. This logic can be improved if we use MFD framework for dependent device creation. This patch adds this support. Signed-off-by: Kuppuswamy

[RFC v3 4/7] platform: x86: Add generic Intel IPC driver

From: Kuppuswamy Sathyanarayanan Currently intel_scu_ipc.c, intel_pmc_ipc.c and intel_punit_ipc.c redundantly implements the same IPC features and has lot of code duplication between them. This driver addresses this issue by grouping the common IPC

[RFC v3 0/7] PMC/PUNIT IPC driver cleanup

From: Kuppuswamy Sathyanarayanan Hi All, Currently intel_pmc_ipc.c, intel_punit_ipc.c, intel_scu_ipc.c drivers implements the same IPC features. This code duplication could be avoided if we implement the IPC driver as a generic library and let

[RFC v3 4/7] platform: x86: Add generic Intel IPC driver

From: Kuppuswamy Sathyanarayanan Currently intel_scu_ipc.c, intel_pmc_ipc.c and intel_punit_ipc.c redundantly implements the same IPC features and has lot of code duplication between them. This driver addresses this issue by grouping the common IPC functionalities under the same driver.

[RFC v3 0/7] PMC/PUNIT IPC driver cleanup

From: Kuppuswamy Sathyanarayanan Hi All, Currently intel_pmc_ipc.c, intel_punit_ipc.c, intel_scu_ipc.c drivers implements the same IPC features. This code duplication could be avoided if we implement the IPC driver as a generic library and let custom device drivers use API provided by generic

[RFC v3 1/7] platform/x86: intel_pmc_ipc: Use devm_* calls in driver probe function

From: Kuppuswamy Sathyanarayanan This patch cleans up unnecessary free/alloc calls in ipc_plat_probe(), ipc_pci_probe() and ipc_plat_get_res() functions by using devm_* calls. This patch also adds proper error handling for failure cases in

[RFC v3 6/7] platform/x86: intel_pmc_ipc: Use generic Intel IPC device calls

From: Kuppuswamy Sathyanarayanan Removed redundant IPC helper functions and refactored the driver to use generic IPC device driver APIs. Also, cleaned up the driver to minimize the usage of global variable ipcdev by propogating the struct

[RFC v3 7/7] platform/x86: intel_scu_ipc: Use generic Intel IPC device calls

From: Kuppuswamy Sathyanarayanan Removed redundant IPC helper functions and refactored the driver to use generic IPC device driver APIs. This patch also cleans-up SCU IPC user drivers to use APIs provided by generic IPC driver. Signed-off-by:

[RFC v3 1/7] platform/x86: intel_pmc_ipc: Use devm_* calls in driver probe function

From: Kuppuswamy Sathyanarayanan This patch cleans up unnecessary free/alloc calls in ipc_plat_probe(), ipc_pci_probe() and ipc_plat_get_res() functions by using devm_* calls. This patch also adds proper error handling for failure cases in ipc_pci_probe() function. Signed-off-by: Kuppuswamy

[RFC v3 6/7] platform/x86: intel_pmc_ipc: Use generic Intel IPC device calls

From: Kuppuswamy Sathyanarayanan Removed redundant IPC helper functions and refactored the driver to use generic IPC device driver APIs. Also, cleaned up the driver to minimize the usage of global variable ipcdev by propogating the struct intel_pmc_ipc_dev pointer or by getting it from device

[RFC v3 7/7] platform/x86: intel_scu_ipc: Use generic Intel IPC device calls

From: Kuppuswamy Sathyanarayanan Removed redundant IPC helper functions and refactored the driver to use generic IPC device driver APIs. This patch also cleans-up SCU IPC user drivers to use APIs provided by generic IPC driver. Signed-off-by: Kuppuswamy Sathyanarayanan ---

[PATCH] tracing: Fix clear of RECORDED_TGID flag when disabling trace event

When disabling one trace event, the RECORDED_TGID flag in the event file is not correctly cleared. It's clearing RECORDED_CMD flag when it should clear RECORDED_TGID flag. Fix d914ba37("tracing: Add support for recording tgid of tasks") Signed-off-by: Chunyu Hu ---

[PATCH] tracing: Fix clear of RECORDED_TGID flag when disabling trace event

When disabling one trace event, the RECORDED_TGID flag in the event file is not correctly cleared. It's clearing RECORDED_CMD flag when it should clear RECORDED_TGID flag. Fix d914ba37("tracing: Add support for recording tgid of tasks") Signed-off-by: Chunyu Hu --- kernel/trace/trace_events.c |

[tip:perf/urgent] perf intel-pt: Fix syntax in documentation of config option

Commit-ID: 4fb205392022ba99a45dd01a62c6e2df046e400a Gitweb: http://git.kernel.org/tip/4fb205392022ba99a45dd01a62c6e2df046e400a Author: Jack Henschel AuthorDate: Thu, 31 Aug 2017 10:05:35 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1

[tip:perf/urgent] perf intel-pt: Fix syntax in documentation of config option

Commit-ID: 4fb205392022ba99a45dd01a62c6e2df046e400a Gitweb: http://git.kernel.org/tip/4fb205392022ba99a45dd01a62c6e2df046e400a Author: Jack Henschel AuthorDate: Thu, 31 Aug 2017 10:05:35 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep 2017 14:45:59 -0300 perf

linux-next: manual merge of the akpm-current tree with the net-next tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: arch/sh/configs/se7751_defconfig between commit: 9efdb14f76f4 ("net: Remove CONFIG_NETFILTER_DEBUG and _ASSERT() macros.") from the net-next tree and commit: a83883ff2285 ("sh: defconfig: cleanup from old

linux-next: manual merge of the akpm-current tree with the net-next tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: arch/sh/configs/se7751_defconfig between commit: 9efdb14f76f4 ("net: Remove CONFIG_NETFILTER_DEBUG and _ASSERT() macros.") from the net-next tree and commit: a83883ff2285 ("sh: defconfig: cleanup from old

[tip:perf/urgent] perf stat: Only auto-merge events that are PMU aliases

Commit-ID: 63ce8449bc1081711eef1add68909e9bd758de62 Gitweb: http://git.kernel.org/tip/63ce8449bc1081711eef1add68909e9bd758de62 Author: Arnaldo Carvalho de Melo AuthorDate: Thu, 31 Aug 2017 15:32:18 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/urgent] perf stat: Only auto-merge events that are PMU aliases

Commit-ID: 63ce8449bc1081711eef1add68909e9bd758de62 Gitweb: http://git.kernel.org/tip/63ce8449bc1081711eef1add68909e9bd758de62 Author: Arnaldo Carvalho de Melo AuthorDate: Thu, 31 Aug 2017 15:32:18 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep 2017 14:48:59 -0300

[tip:perf/urgent] perf script: Support physical address

Commit-ID: 49d58f04eb6cdc18b3747fc4243a7114364f5420 Gitweb: http://git.kernel.org/tip/49d58f04eb6cdc18b3747fc4243a7114364f5420 Author: Kan Liang AuthorDate: Tue, 29 Aug 2017 13:11:11 -0400 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep

[tip:perf/urgent] perf test: Add test case for PERF_SAMPLE_PHYS_ADDR

Commit-ID: fc33dccba39584e403436b9cda3edc9c34b62bce Gitweb: http://git.kernel.org/tip/fc33dccba39584e403436b9cda3edc9c34b62bce Author: Kan Liang AuthorDate: Tue, 29 Aug 2017 13:11:12 -0400 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep

[tip:perf/urgent] perf annotate browser: Help for cycling thru hottest instructions with TAB/shift+TAB

Commit-ID: eba9fac017617e685d648339e29a1453a30cb065 Gitweb: http://git.kernel.org/tip/eba9fac017617e685d648339e29a1453a30cb065 Author: Arnaldo Carvalho de Melo AuthorDate: Fri, 1 Sep 2017 14:55:40 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/urgent] perf script: Support physical address

Commit-ID: 49d58f04eb6cdc18b3747fc4243a7114364f5420 Gitweb: http://git.kernel.org/tip/49d58f04eb6cdc18b3747fc4243a7114364f5420 Author: Kan Liang AuthorDate: Tue, 29 Aug 2017 13:11:11 -0400 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep 2017 14:46:29 -0300 perf script:

[tip:perf/urgent] perf test: Add test case for PERF_SAMPLE_PHYS_ADDR

Commit-ID: fc33dccba39584e403436b9cda3edc9c34b62bce Gitweb: http://git.kernel.org/tip/fc33dccba39584e403436b9cda3edc9c34b62bce Author: Kan Liang AuthorDate: Tue, 29 Aug 2017 13:11:12 -0400 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep 2017 14:46:34 -0300 perf test: Add

[tip:perf/urgent] perf annotate browser: Help for cycling thru hottest instructions with TAB/shift+TAB

Commit-ID: eba9fac017617e685d648339e29a1453a30cb065 Gitweb: http://git.kernel.org/tip/eba9fac017617e685d648339e29a1453a30cb065 Author: Arnaldo Carvalho de Melo AuthorDate: Fri, 1 Sep 2017 14:55:40 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep 2017 14:55:40 -0300

[tip:perf/urgent] perf mem: Support physical address

Commit-ID: c35aeb9dfe512422ca9ea28aae692c8f1d052b2d Gitweb: http://git.kernel.org/tip/c35aeb9dfe512422ca9ea28aae692c8f1d052b2d Author: Kan Liang AuthorDate: Tue, 29 Aug 2017 13:11:10 -0400 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep

[tip:perf/urgent] perf mem: Support physical address

Commit-ID: c35aeb9dfe512422ca9ea28aae692c8f1d052b2d Gitweb: http://git.kernel.org/tip/c35aeb9dfe512422ca9ea28aae692c8f1d052b2d Author: Kan Liang AuthorDate: Tue, 29 Aug 2017 13:11:10 -0400 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep 2017 14:46:23 -0300 perf mem: Support

[tip:perf/urgent] perf sort: Add sort option for physical address

Commit-ID: 8780fb25ab060bafa5a8149e79b703e0fc7ee847 Gitweb: http://git.kernel.org/tip/8780fb25ab060bafa5a8149e79b703e0fc7ee847 Author: Kan Liang AuthorDate: Tue, 29 Aug 2017 13:11:09 -0400 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep

[tip:perf/urgent] perf sort: Add sort option for physical address

Commit-ID: 8780fb25ab060bafa5a8149e79b703e0fc7ee847 Gitweb: http://git.kernel.org/tip/8780fb25ab060bafa5a8149e79b703e0fc7ee847 Author: Kan Liang AuthorDate: Tue, 29 Aug 2017 13:11:09 -0400 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep 2017 14:46:11 -0300 perf sort: Add

[tip:perf/urgent] perf tools: Support new sample type for physical address

Commit-ID: 3b0a5daa061076b2b75ffc294e74483ad9bf241a Gitweb: http://git.kernel.org/tip/3b0a5daa061076b2b75ffc294e74483ad9bf241a Author: Kan Liang AuthorDate: Tue, 29 Aug 2017 13:11:08 -0400 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep

[tip:perf/urgent] perf tools: Support new sample type for physical address

Commit-ID: 3b0a5daa061076b2b75ffc294e74483ad9bf241a Gitweb: http://git.kernel.org/tip/3b0a5daa061076b2b75ffc294e74483ad9bf241a Author: Kan Liang AuthorDate: Tue, 29 Aug 2017 13:11:08 -0400 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep 2017 14:46:00 -0300 perf tools:

[tip:perf/urgent] perf vendor events powerpc: Remove duplicate events

Commit-ID: 2a118e1bd22cad57318520d37e3a184b8846c6a2 Gitweb: http://git.kernel.org/tip/2a118e1bd22cad57318520d37e3a184b8846c6a2 Author: Sukadev Bhattiprolu AuthorDate: Wed, 30 Aug 2017 21:42:23 -0400 Committer: Arnaldo Carvalho de Melo

[tip:perf/urgent] perf vendor events powerpc: Remove duplicate events

Commit-ID: 2a118e1bd22cad57318520d37e3a184b8846c6a2 Gitweb: http://git.kernel.org/tip/2a118e1bd22cad57318520d37e3a184b8846c6a2 Author: Sukadev Bhattiprolu AuthorDate: Wed, 30 Aug 2017 21:42:23 -0400 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep 2017 14:46:00 -0300 perf

[tip:perf/urgent] perf test powerpc: Fix 'Object code reading' test

Commit-ID: 9a805d8648ee09c136130fe4114a09574bc0b1ef Gitweb: http://git.kernel.org/tip/9a805d8648ee09c136130fe4114a09574bc0b1ef Author: Ravi Bangoria AuthorDate: Thu, 31 Aug 2017 14:44:56 +0530 Committer: Arnaldo Carvalho de Melo

[tip:perf/urgent] perf test powerpc: Fix 'Object code reading' test

Commit-ID: 9a805d8648ee09c136130fe4114a09574bc0b1ef Gitweb: http://git.kernel.org/tip/9a805d8648ee09c136130fe4114a09574bc0b1ef Author: Ravi Bangoria AuthorDate: Thu, 31 Aug 2017 14:44:56 +0530 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep 2017 14:45:59 -0300 perf test

[tip:perf/urgent] perf report: Calculate the average cycles of iterations

Commit-ID: c4ee06251d4212a0d55e2371f2db464f6a1e0901 Gitweb: http://git.kernel.org/tip/c4ee06251d4212a0d55e2371f2db464f6a1e0901 Author: Jin Yao AuthorDate: Mon, 7 Aug 2017 21:05:15 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 30

[tip:perf/urgent] perf report: Calculate the average cycles of iterations

Commit-ID: c4ee06251d4212a0d55e2371f2db464f6a1e0901 Gitweb: http://git.kernel.org/tip/c4ee06251d4212a0d55e2371f2db464f6a1e0901 Author: Jin Yao AuthorDate: Mon, 7 Aug 2017 21:05:15 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Wed, 30 Aug 2017 10:03:27 -0300 perf report:

[tip:perf/urgent] perf trace: Support syscall name globbing

Commit-ID: 27702bcfe8a125a1feeeb5f07526d63b20cac47f Gitweb: http://git.kernel.org/tip/27702bcfe8a125a1feeeb5f07526d63b20cac47f Author: Arnaldo Carvalho de Melo AuthorDate: Thu, 31 Aug 2017 11:50:04 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/urgent] perf trace: Support syscall name globbing

Commit-ID: 27702bcfe8a125a1feeeb5f07526d63b20cac47f Gitweb: http://git.kernel.org/tip/27702bcfe8a125a1feeeb5f07526d63b20cac47f Author: Arnaldo Carvalho de Melo AuthorDate: Thu, 31 Aug 2017 11:50:04 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep 2017 14:45:58 -0300

[tip:perf/urgent] perf syscalltbl: Support glob matching on syscall names

Commit-ID: 89be3f8ab701180fc0329eff1b076528d64ac56b Gitweb: http://git.kernel.org/tip/89be3f8ab701180fc0329eff1b076528d64ac56b Author: Arnaldo Carvalho de Melo AuthorDate: Thu, 31 Aug 2017 11:46:49 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

Re: [PATCH] sound: soc: fsl: Do not set DAI sysclk when it is equal to system freq

On Sun, Sep 03, 2017 at 04:40:21PM +0200, Łukasz Majewski wrote: > >/* > >* Hardware limitation: The bclk rate must be > >* never greater than 1/5 IPG clock rate > >*/ > >if (freq * 5 > clk_get_rate(ssi_private->clk)) { > >dev_err(cpu_dai->dev, "bitclk > ipgclk/5\n"); > >return -EINVAL; > >} > > >

[tip:perf/urgent] perf syscalltbl: Support glob matching on syscall names

Commit-ID: 89be3f8ab701180fc0329eff1b076528d64ac56b Gitweb: http://git.kernel.org/tip/89be3f8ab701180fc0329eff1b076528d64ac56b Author: Arnaldo Carvalho de Melo AuthorDate: Thu, 31 Aug 2017 11:46:49 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 1 Sep 2017 14:45:48 -0300

Re: [PATCH] sound: soc: fsl: Do not set DAI sysclk when it is equal to system freq

On Sun, Sep 03, 2017 at 04:40:21PM +0200, Łukasz Majewski wrote: > >/* > >* Hardware limitation: The bclk rate must be > >* never greater than 1/5 IPG clock rate > >*/ > >if (freq * 5 > clk_get_rate(ssi_private->clk)) { > >dev_err(cpu_dai->dev, "bitclk > ipgclk/5\n"); > >return -EINVAL; > >} > > >

Re: [GIT PULL 00/13] perf/core improvements and fixes

* Arnaldo Carvalho de Melo wrote: > Hi Ingo, > > Please consider pulling, > > - Arnaldo > > Test results at the end of this message, as usual. > > The following changes since commit 1b2f76d77a277bb70d38ad0991ed7f16bbc115a9: > > Merge tag

Re: [GIT PULL 00/13] perf/core improvements and fixes

* Arnaldo Carvalho de Melo wrote: > Hi Ingo, > > Please consider pulling, > > - Arnaldo > > Test results at the end of this message, as usual. > > The following changes since commit 1b2f76d77a277bb70d38ad0991ed7f16bbc115a9: > > Merge tag 'perf-core-for-mingo-4.14-20170829' of >

[PATCH linux-next v6 1/1] spi: imx: Add support for SPI Slave mode

Previously i.MX SPI controller only works in Master mode. This patch adds support to i.MX51, i.MX53 and i.MX6 ECSPI controller to work also in Slave mode. Currently SPI Slave mode support patch has the following limitations: 1. The stale data in RXFIFO will be dropped when the Slave does any new

[PATCH linux-next v6 1/1] spi: imx: Add support for SPI Slave mode

Previously i.MX SPI controller only works in Master mode. This patch adds support to i.MX51, i.MX53 and i.MX6 ECSPI controller to work also in Slave mode. Currently SPI Slave mode support patch has the following limitations: 1. The stale data in RXFIFO will be dropped when the Slave does any new

Re: [PATCH] sound: soc: fsl: Do not set DAI sysclk when it is equal to system freq

On Sun, Sep 03, 2017 at 01:05:01PM +0200, Lukasz Majewski wrote: > The problem is visible in the following setup (on the imx6q): > "simple-audio-card" -> ssi2 -> I2S + I2C -> codec > > The function call log (simple-card probe -> CONFIG_SND_SIMPLE_CARD): > > asoc_simple_card_init_dai() @

Re: [PATCH] sound: soc: fsl: Do not set DAI sysclk when it is equal to system freq

On Sun, Sep 03, 2017 at 01:05:01PM +0200, Lukasz Majewski wrote: > The problem is visible in the following setup (on the imx6q): > "simple-audio-card" -> ssi2 -> I2S + I2C -> codec > > The function call log (simple-card probe -> CONFIG_SND_SIMPLE_CARD): > > asoc_simple_card_init_dai() @

Re: [RESENT PATCH v7 3/7] arm64: dts: rockchip: Update rt5514 devices' compatible for Gru

Hi Heiko, On 09/05/2017 06:33 AM, Heiko Stübner wrote: Am Donnerstag, 31. August 2017, 01:00:44 CEST schrieb jeffy: On 08/30/2017 09:30 PM, Heiko Stübner wrote: - compatible = "realtek,rt5514"; + compatible = "realtek,rt5514", "realtek,rt5514-i2c"; the rt5514-i2c

Re: [RESENT PATCH v7 3/7] arm64: dts: rockchip: Update rt5514 devices' compatible for Gru

Hi Heiko, On 09/05/2017 06:33 AM, Heiko Stübner wrote: Am Donnerstag, 31. August 2017, 01:00:44 CEST schrieb jeffy: On 08/30/2017 09:30 PM, Heiko Stübner wrote: - compatible = "realtek,rt5514"; + compatible = "realtek,rt5514", "realtek,rt5514-i2c"; the rt5514-i2c

[PATCH v8 2/2] arm64: dts: rockchip: Update rt5514 devices' compatible for Gru

Currently the rt5514 i2c driver and rt5514 spi driver are using the same compatible string. Add additional unused compatible strings to identify them for Gru boards. Signed-off-by: Jeffy Chen --- Changes in v8: Add new compatible to rt5514 dt doc.

[PATCH v8 1/2] ASoC: rt5514: Add devicetree bindings for rt5514-spi

Add devicetree bindings documentation file for rt5514 spi dsp codec. Also update rt5514 i2c dt-binding's compatible. Signed-off-by: Jeffy Chen --- Changes in v8: None .../devicetree/bindings/sound/rt5514-spi.txt | 32 ++

[PATCH v8 2/2] arm64: dts: rockchip: Update rt5514 devices' compatible for Gru

Currently the rt5514 i2c driver and rt5514 spi driver are using the same compatible string. Add additional unused compatible strings to identify them for Gru boards. Signed-off-by: Jeffy Chen --- Changes in v8: Add new compatible to rt5514 dt doc. arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi

[PATCH v8 1/2] ASoC: rt5514: Add devicetree bindings for rt5514-spi

Add devicetree bindings documentation file for rt5514 spi dsp codec. Also update rt5514 i2c dt-binding's compatible. Signed-off-by: Jeffy Chen --- Changes in v8: None .../devicetree/bindings/sound/rt5514-spi.txt | 32 ++

Re: [PATCH v2 2/2] dma: sprd: Add Spreadtrum DMA driver

On Tue, Aug 29, 2017 at 04:47:17PM +0800, Baolin Wang wrote: > +config SPRD_DMA > + bool "Spreadtrum DMA support" > + depends on ARCH_SPRD can you also add compile test to this, it helps in getting good coverage and easy to compile changes > +/* DMA global registers definition */ >

Re: [PATCH v2 2/2] dma: sprd: Add Spreadtrum DMA driver

On Tue, Aug 29, 2017 at 04:47:17PM +0800, Baolin Wang wrote: > +config SPRD_DMA > + bool "Spreadtrum DMA support" > + depends on ARCH_SPRD can you also add compile test to this, it helps in getting good coverage and easy to compile changes > +/* DMA global registers definition */ >

[PATCH] Asoc: rockchip: Init dapm routes dynamically

Currently we are using a fixed list of dapm routes. Init dapm routes dynamically when parsing dailinks, since we are supporting optional codecs. Signed-off-by: Jeffy Chen --- sound/soc/rockchip/rk3399_gru_sound.c | 88 +-- 1 file

[PATCH] Asoc: rockchip: Init dapm routes dynamically

Currently we are using a fixed list of dapm routes. Init dapm routes dynamically when parsing dailinks, since we are supporting optional codecs. Signed-off-by: Jeffy Chen --- sound/soc/rockchip/rk3399_gru_sound.c | 88 +-- 1 file changed, 74 insertions(+), 14

Re: [HMM-v25 19/19] mm/hmm: add new helper to hotplug CDM memory region v3

On 2017/9/5 10:38, Jerome Glisse wrote: > On Tue, Sep 05, 2017 at 09:13:24AM +0800, Bob Liu wrote: >> On 2017/9/4 23:51, Jerome Glisse wrote: >>> On Mon, Sep 04, 2017 at 11:09:14AM +0800, Bob Liu wrote: On 2017/8/17 8:05, Jérôme Glisse wrote: > Unlike unaddressable memory, coherent device

Re: [HMM-v25 19/19] mm/hmm: add new helper to hotplug CDM memory region v3

On 2017/9/5 10:38, Jerome Glisse wrote: > On Tue, Sep 05, 2017 at 09:13:24AM +0800, Bob Liu wrote: >> On 2017/9/4 23:51, Jerome Glisse wrote: >>> On Mon, Sep 04, 2017 at 11:09:14AM +0800, Bob Liu wrote: On 2017/8/17 8:05, Jérôme Glisse wrote: > Unlike unaddressable memory, coherent device

Re: broken cycle counts from perf record in frequency mode [Was: Re: deducing CPU clock rate over time from cycle samples]

> The cycle value gets associated with a sample via it's period value, which is > used by `perf report` in the analysis. If I get a single "broken" sample with I always thought it just used the number of samples? > a cycle count of, say 1E14 and then a million other samples, each with "sane"

Re: broken cycle counts from perf record in frequency mode [Was: Re: deducing CPU clock rate over time from cycle samples]

> The cycle value gets associated with a sample via it's period value, which is > used by `perf report` in the analysis. If I get a single "broken" sample with I always thought it just used the number of samples? > a cycle count of, say 1E14 and then a million other samples, each with "sane"

Re: [HMM-v25 19/19] mm/hmm: add new helper to hotplug CDM memory region v3

On Tue, Sep 5, 2017 at 1:51 AM, Jerome Glisse wrote: > On Mon, Sep 04, 2017 at 11:09:14AM +0800, Bob Liu wrote: >> On 2017/8/17 8:05, Jérôme Glisse wrote: >> > Unlike unaddressable memory, coherent device memory has a real >> > resource associated with it on the system (as CPU

Re: [HMM-v25 19/19] mm/hmm: add new helper to hotplug CDM memory region v3

On Tue, Sep 5, 2017 at 1:51 AM, Jerome Glisse wrote: > On Mon, Sep 04, 2017 at 11:09:14AM +0800, Bob Liu wrote: >> On 2017/8/17 8:05, Jérôme Glisse wrote: >> > Unlike unaddressable memory, coherent device memory has a real >> > resource associated with it on the system (as CPU can address >> >

Re: [PATCH RESEND 0/2] Allwinner V3s DMA support

On Tue, Aug 29, 2017 at 12:51:25PM +0800, Icenowy Zheng wrote: > This is a dedicated patchset of Allwinner V3s DMA support, which used > to be part of the audio codec support patchset. > > It's a derivation of the DMA part of v3 of the codec patchset. Applied, thanks -- ~Vinod

Re: [PATCH RESEND 0/2] Allwinner V3s DMA support

On Tue, Aug 29, 2017 at 12:51:25PM +0800, Icenowy Zheng wrote: > This is a dedicated patchset of Allwinner V3s DMA support, which used > to be part of the audio codec support patchset. > > It's a derivation of the DMA part of v3 of the codec patchset. Applied, thanks -- ~Vinod

Re: [PATCH 2/2] tracing: Add support for critical section events

On Mon, Sep 4, 2017 at 5:54 PM, Joel Fernandes wrote: > On Mon, Sep 4, 2017 at 4:34 PM, Steven Rostedt wrote: >> On Mon, 4 Sep 2017 21:44:26 +0200 >> Peter Zijlstra wrote: >> >>> > I can change the name to something else, but at the

Re: [PATCH 2/2] tracing: Add support for critical section events

On Mon, Sep 4, 2017 at 5:54 PM, Joel Fernandes wrote: > On Mon, Sep 4, 2017 at 4:34 PM, Steven Rostedt wrote: >> On Mon, 4 Sep 2017 21:44:26 +0200 >> Peter Zijlstra wrote: >> >>> > I can change the name to something else, but at the moment I can't >>> > think of anything better. Could you

[PATCH v3 2/2] ACPI / CPPC: Make cppc acpi driver aware of pcc subspace ids

Based on ACPI 6.2 Section 8.4.7.1.9 If the PCC register space is used, all PCC registers, for all processors in the same performance domain (as defined by _PSD), must be defined to be in the same subspace. Based on Section 14.1 of ACPI specification, it is possible to have a maximum of 256 PCC

[PATCH v3 2/2] ACPI / CPPC: Make cppc acpi driver aware of pcc subspace ids

Based on ACPI 6.2 Section 8.4.7.1.9 If the PCC register space is used, all PCC registers, for all processors in the same performance domain (as defined by _PSD), must be defined to be in the same subspace. Based on Section 14.1 of ACPI specification, it is possible to have a maximum of 256 PCC

[PATCH v3 0/2] Make cppc acpi driver aware of pcc subspace ids

The current cppc acpi driver works with only one pcc subspace id. It maintains and registers only one pcc channel even if the acpi table has different pcc subspace ids. As per ACPI 6.2 spec all PCC registers, for all processors in the same performance domain (as defined by _PSD), must be

[PATCH v3 1/2] mailbox: PCC: Move the MAX_PCC_SUBSPACES definition to header file

Move the MAX_PCC_SUBSPACES definition to acpi/pcc.h file. In preparation to add subspace id support for cppc_acpi driver. Signed-off-by: George Cherian --- drivers/mailbox/pcc.c | 1 - include/acpi/pcc.h| 1 + 2 files changed, 1 insertion(+), 1 deletion(-) diff

[PATCH v3 0/2] Make cppc acpi driver aware of pcc subspace ids

The current cppc acpi driver works with only one pcc subspace id. It maintains and registers only one pcc channel even if the acpi table has different pcc subspace ids. As per ACPI 6.2 spec all PCC registers, for all processors in the same performance domain (as defined by _PSD), must be

[PATCH v3 1/2] mailbox: PCC: Move the MAX_PCC_SUBSPACES definition to header file

Move the MAX_PCC_SUBSPACES definition to acpi/pcc.h file. In preparation to add subspace id support for cppc_acpi driver. Signed-off-by: George Cherian --- drivers/mailbox/pcc.c | 1 - include/acpi/pcc.h| 1 + 2 files changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

> I agree with your understanding. It's a rising threshold, just that the input > will only reflect high frequency changes in the signal. Thank you for the clarification. I am hoping this gets merged in the next window if no other issues. Thanks, Hari On Sun, Sep 3, 2017 at 12:24 PM, Jonathan

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

> I agree with your understanding. It's a rising threshold, just that the input > will only reflect high frequency changes in the signal. Thank you for the clarification. I am hoping this gets merged in the next window if no other issues. Thanks, Hari On Sun, Sep 3, 2017 at 12:24 PM, Jonathan

Re: [PATCH v4] bcache: Don't reinvent the wheel but use existing llist API

On 2017/9/5 上午10:37, Byungchul Park wrote: > On Fri, Aug 18, 2017 at 02:04:20PM +0800, Coly Li wrote: >> On 2017/8/18 上午9:24, Byungchul Park wrote: >>> On Fri, Aug 11, 2017 at 01:42:23PM +0900, Byungchul Park wrote: Although llist provides proper APIs, they are not used. Make them used. >>>

Re: [PATCH v4] bcache: Don't reinvent the wheel but use existing llist API

On 2017/9/5 上午10:37, Byungchul Park wrote: > On Fri, Aug 18, 2017 at 02:04:20PM +0800, Coly Li wrote: >> On 2017/8/18 上午9:24, Byungchul Park wrote: >>> On Fri, Aug 11, 2017 at 01:42:23PM +0900, Byungchul Park wrote: Although llist provides proper APIs, they are not used. Make them used. >>>

Re: [PATCH v2 1/3] arm: npcm: add basic support for Nuvoton BMCs

Le 08/31/17 à 15:53, Brendan Higgins a écrit : > Adds basic support for the Nuvoton NPCM750 BMC. > > Signed-off-by: Brendan Higgins > --- > arch/arm/Kconfig | 2 + > arch/arm/Makefile| 1 + > arch/arm/mach-npcm/Kconfig | 58

Re: [PATCH v2 1/3] arm: npcm: add basic support for Nuvoton BMCs

Le 08/31/17 à 15:53, Brendan Higgins a écrit : > Adds basic support for the Nuvoton NPCM750 BMC. > > Signed-off-by: Brendan Higgins > --- > arch/arm/Kconfig | 2 + > arch/arm/Makefile| 1 + > arch/arm/mach-npcm/Kconfig | 58 +++ >

[PATCH] block: fix bio.c kernel-doc notation warning

From: Randy Dunlap Sphinx treats symbols that end with '_' as some kind of special documentation indicator, so fix that by adding an ending '*' to it. ../block/bio.c:404: ERROR: Unknown target name: "gfp". Signed-off-by: Randy Dunlap ---

[PATCH] block: fix bio.c kernel-doc notation warning

From: Randy Dunlap Sphinx treats symbols that end with '_' as some kind of special documentation indicator, so fix that by adding an ending '*' to it. ../block/bio.c:404: ERROR: Unknown target name: "gfp". Signed-off-by: Randy Dunlap --- block/bio.c |2 +- 1 file changed, 1 insertion(+),

Re: [HMM-v25 19/19] mm/hmm: add new helper to hotplug CDM memory region v3

On Tue, Sep 05, 2017 at 09:13:24AM +0800, Bob Liu wrote: > On 2017/9/4 23:51, Jerome Glisse wrote: > > On Mon, Sep 04, 2017 at 11:09:14AM +0800, Bob Liu wrote: > >> On 2017/8/17 8:05, Jérôme Glisse wrote: > >>> Unlike unaddressable memory, coherent device memory has a real > >>> resource

Re: [HMM-v25 19/19] mm/hmm: add new helper to hotplug CDM memory region v3

On Tue, Sep 05, 2017 at 09:13:24AM +0800, Bob Liu wrote: > On 2017/9/4 23:51, Jerome Glisse wrote: > > On Mon, Sep 04, 2017 at 11:09:14AM +0800, Bob Liu wrote: > >> On 2017/8/17 8:05, Jérôme Glisse wrote: > >>> Unlike unaddressable memory, coherent device memory has a real > >>> resource

Re: [RESEND PATCH] irq_work: Don't reinvent the wheel but use existing llist API

On Wed, May 31, 2017 at 04:04:17PM +0200, Frederic Weisbecker wrote: > On Tue, May 30, 2017 at 02:29:20PM +0900, Byungchul Park wrote: > > On Fri, May 12, 2017 at 09:45:35AM +0900, Byungchul Park wrote: > > > Although llist provides proper APIs, they are not used. Make them used. > > > > +to

Re: [RESEND PATCH] irq_work: Don't reinvent the wheel but use existing llist API

On Wed, May 31, 2017 at 04:04:17PM +0200, Frederic Weisbecker wrote: > On Tue, May 30, 2017 at 02:29:20PM +0900, Byungchul Park wrote: > > On Fri, May 12, 2017 at 09:45:35AM +0900, Byungchul Park wrote: > > > Although llist provides proper APIs, they are not used. Make them used. > > > > +to

Re: [PATCH v4] bcache: Don't reinvent the wheel but use existing llist API

On Fri, Aug 18, 2017 at 02:04:20PM +0800, Coly Li wrote: > On 2017/8/18 上午9:24, Byungchul Park wrote: > > On Fri, Aug 11, 2017 at 01:42:23PM +0900, Byungchul Park wrote: > >> Although llist provides proper APIs, they are not used. Make them used. > > > > Any opinions about this? > > > > The

Re: [PATCH v4] bcache: Don't reinvent the wheel but use existing llist API

On Fri, Aug 18, 2017 at 02:04:20PM +0800, Coly Li wrote: > On 2017/8/18 上午9:24, Byungchul Park wrote: > > On Fri, Aug 11, 2017 at 01:42:23PM +0900, Byungchul Park wrote: > >> Although llist provides proper APIs, they are not used. Make them used. > > > > Any opinions about this? > > > > The

[PATCH 0/3] Fix the workqueue and lockdep annotation issue

We introduced the following commit to detect deadlocks caused by wait_for_completion() in flush_{workqueue, work}() and other locks. But now LOCKDEP_COMPLETIONS is introduced, such works are automatically done by LOCKDEP_COMPLETIONS. commit 4e6045f134784f4b158b3c0f7a282b04bd816887

[PATCH 0/3] Fix the workqueue and lockdep annotation issue

We introduced the following commit to detect deadlocks caused by wait_for_completion() in flush_{workqueue, work}() and other locks. But now LOCKDEP_COMPLETIONS is introduced, such works are automatically done by LOCKDEP_COMPLETIONS. commit 4e6045f134784f4b158b3c0f7a282b04bd816887

[PATCH 2/3] lockdep: Introduce lock_acquire_might()

>From the point of view of crossrelease, we can never be aware of the release context in advance, until we get to the lock_release(). However, this way we cannot report deadlocks occured at the time. Sometimes, we want to report that kind of problems, taking a risk generating false dependencies

[PATCH 1/3] lockdep: Use enum type on hlock->read instead of magic number

Currently hlock->read can have the following values: 0: write type 1: read type 2: read recursion type It would be better to use human readable type than magic numbers. Furthermore, this way it's easier to extend it so that hlock->read has another value. Signed-off-by: Byungchul Park

  1   2   3   4   5   6   7   8   9   10   >