[PATCH v5 2/2] thermal: uniphier: add UniPhier thermal driver

Add a thermal driver for on-chip PVT (Process, Voltage and Temperature) monitoring unit implemented on UniPhier SoCs. This driver supports temperature monitoring and alert function. Signed-off-by: Kunihiko Hayashi --- drivers/thermal/Kconfig| 8 +

[PATCH v5 2/2] thermal: uniphier: add UniPhier thermal driver

Add a thermal driver for on-chip PVT (Process, Voltage and Temperature) monitoring unit implemented on UniPhier SoCs. This driver supports temperature monitoring and alert function. Signed-off-by: Kunihiko Hayashi --- drivers/thermal/Kconfig| 8 + drivers/thermal/Makefile

[PATCH v5 1/2] dt-bindings: thermal: add binding documentation for UniPhier thermal monitor

Add devicetree binding documentation for thermal monitor implemented on Socionext UniPhier SoCs. Signed-off-by: Kunihiko Hayashi Acked-by: Rob Herring --- .../bindings/thermal/uniphier-thermal.txt | 64 ++ 1 file

[PATCH v5 0/2] add UniPhier thermal support

This series adds support for CPU temperature monitor modules implemented on UniPhier LD20 and PXs2 SoCs. This driver supports temperature monitoring and alert function on the module. Changes in v4: - fix warnings from sparse by replacing u32 with __be32 Changes in v3: - remove TMOD_MASK and use

[PATCH v5 1/2] dt-bindings: thermal: add binding documentation for UniPhier thermal monitor

Add devicetree binding documentation for thermal monitor implemented on Socionext UniPhier SoCs. Signed-off-by: Kunihiko Hayashi Acked-by: Rob Herring --- .../bindings/thermal/uniphier-thermal.txt | 64 ++ 1 file changed, 64 insertions(+) create mode 100644

[PATCH v5 0/2] add UniPhier thermal support

This series adds support for CPU temperature monitor modules implemented on UniPhier LD20 and PXs2 SoCs. This driver supports temperature monitoring and alert function on the module. Changes in v4: - fix warnings from sparse by replacing u32 with __be32 Changes in v3: - remove TMOD_MASK and use

Re: [PATCH v4 3/5] pwm-backlight: add support for PWM delays proprieties.

On Fri 2017-07-21 12:48:11, Enric Balletbo i Serra wrote: > Some panels (i.e. N116BGE-L41), in their power sequence specifications, > request a delay between set the PWM signal and enable the backlight and > between clear the PWM signal and disable the backlight. Add support for > the new

Re: [PATCH v4 3/5] pwm-backlight: add support for PWM delays proprieties.

On Fri 2017-07-21 12:48:11, Enric Balletbo i Serra wrote: > Some panels (i.e. N116BGE-L41), in their power sequence specifications, > request a delay between set the PWM signal and enable the backlight and > between clear the PWM signal and disable the backlight. Add support for > the new

Re: [PATCH] irqchip/gic-v3-its: Allow GIC ITS number more than MAX_NUMNODES

On 21/07/17 11:06, Hanjun Guo wrote: > On 2017/7/21 17:51, Hanjun Guo wrote: >> From: Hanjun Guo >> >> When running 4.13-rc1 on top of D05, I got the boot log: >> >> [0.00] SRAT: PXM 0 -> ITS 0 -> Node 0 >> [0.00] SRAT: PXM 0 -> ITS 1 -> Node 0 >> [

Re: [PATCH] irqchip/gic-v3-its: Allow GIC ITS number more than MAX_NUMNODES

On 21/07/17 11:06, Hanjun Guo wrote: > On 2017/7/21 17:51, Hanjun Guo wrote: >> From: Hanjun Guo >> >> When running 4.13-rc1 on top of D05, I got the boot log: >> >> [0.00] SRAT: PXM 0 -> ITS 0 -> Node 0 >> [0.00] SRAT: PXM 0 -> ITS 1 -> Node 0 >> [0.00] SRAT: PXM 0 -> ITS

[PATCH] clk: samsung: exynos5420: The EPLL rate table corrections

This patch fixes values of the EPLL K coefficient and changes the EPLL output frequency values to match exactly what is possible to achieve with given M, P, S, K coefficients. This allows to avoid rounding errors and unexpected frequency being set with clk_set_rate(), due to recalc_rate returning

[PATCH] clk: samsung: exynos5420: The EPLL rate table corrections

This patch fixes values of the EPLL K coefficient and changes the EPLL output frequency values to match exactly what is possible to achieve with given M, P, S, K coefficients. This allows to avoid rounding errors and unexpected frequency being set with clk_set_rate(), due to recalc_rate returning

[PATCH v7 10/12] mfd: rk808: Add RK805 pinctrl support

Signed-off-by: Joseph Chen --- drivers/mfd/rk808.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/mfd/rk808.c b/drivers/mfd/rk808.c index 7276555..db90471 100644 --- a/drivers/mfd/rk808.c +++ b/drivers/mfd/rk808.c @@ -97,6 +97,7 @@ static bool

[PATCH v7 10/12] mfd: rk808: Add RK805 pinctrl support

Signed-off-by: Joseph Chen --- drivers/mfd/rk808.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/mfd/rk808.c b/drivers/mfd/rk808.c index 7276555..db90471 100644 --- a/drivers/mfd/rk808.c +++ b/drivers/mfd/rk808.c @@ -97,6 +97,7 @@ static bool rk808_is_volatile_reg(struct device

[PATCH v7 12/12] pinctrl: dt-bindings: add bindings for Rockchip RK805 PMIC

Signed-off-by: Joseph Chen --- .../devicetree/bindings/pinctrl/pinctrl-rk805.txt | 63 ++ 1 file changed, 63 insertions(+) create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-rk805.txt diff --git

[PATCH v7 11/12] mfd: rk808: Add RK805 power key support

Signed-off-by: Joseph Chen --- drivers/mfd/rk808.c | 17 + 1 file changed, 17 insertions(+) diff --git a/drivers/mfd/rk808.c b/drivers/mfd/rk808.c index db90471..6d9f96b 100644 --- a/drivers/mfd/rk808.c +++ b/drivers/mfd/rk808.c @@ -94,6 +94,19 @@ static

[PATCH v7 12/12] pinctrl: dt-bindings: add bindings for Rockchip RK805 PMIC

Signed-off-by: Joseph Chen --- .../devicetree/bindings/pinctrl/pinctrl-rk805.txt | 63 ++ 1 file changed, 63 insertions(+) create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-rk805.txt diff --git

[PATCH v7 11/12] mfd: rk808: Add RK805 power key support

Signed-off-by: Joseph Chen --- drivers/mfd/rk808.c | 17 + 1 file changed, 17 insertions(+) diff --git a/drivers/mfd/rk808.c b/drivers/mfd/rk808.c index db90471..6d9f96b 100644 --- a/drivers/mfd/rk808.c +++ b/drivers/mfd/rk808.c @@ -94,6 +94,19 @@ static bool

Re: [PATCH v3 0/4] Add xxhash and zstd modules

On 2017-07-21 07:16, Austin S. Hemmelgarn wrote: On 2017-07-20 17:27, Nick Terrell wrote: Well this is embarrassing, forgot to type anything before hitting send... Hi all, This patch set adds xxhash, zstd compression, and zstd decompression modules. It also adds zstd support to BtrFS and

[PATCH v7 08/12] pinctrl: Add pinctrl driver for the RK805 PMIC

RK805 is one of Rockchip PMICs family, it has 2 output only GPIOs. This driver is also designed for other Rockchip PMICs to expend. Different PMIC maybe have different pin features, for example, RK816 has one pin which can be used for TS or GPIO(input/out). The mainly difference between PMICs

[PATCH v7 09/12] Input: Add power key driver for Rockchip RK805 PMIC

This driver provides a input driver for the power key on the Rockchip RK805 PMIC. Signed-off-by: Joseph Chen --- drivers/input/misc/Kconfig| 6 +++ drivers/input/misc/Makefile | 1 + drivers/input/misc/rk805-pwrkey.c | 111

Re: [PATCH v3 0/4] Add xxhash and zstd modules

On 2017-07-21 07:16, Austin S. Hemmelgarn wrote: On 2017-07-20 17:27, Nick Terrell wrote: Well this is embarrassing, forgot to type anything before hitting send... Hi all, This patch set adds xxhash, zstd compression, and zstd decompression modules. It also adds zstd support to BtrFS and

[PATCH v7 08/12] pinctrl: Add pinctrl driver for the RK805 PMIC

RK805 is one of Rockchip PMICs family, it has 2 output only GPIOs. This driver is also designed for other Rockchip PMICs to expend. Different PMIC maybe have different pin features, for example, RK816 has one pin which can be used for TS or GPIO(input/out). The mainly difference between PMICs

[PATCH v7 09/12] Input: Add power key driver for Rockchip RK805 PMIC

This driver provides a input driver for the power key on the Rockchip RK805 PMIC. Signed-off-by: Joseph Chen --- drivers/input/misc/Kconfig| 6 +++ drivers/input/misc/Makefile | 1 + drivers/input/misc/rk805-pwrkey.c | 111 ++ 3 files

[PATCH v7 07/12] mfd: dt-bindings: Add RK805 device tree bindings document

From: Elaine Zhang Add device tree bindings documentation for Rockchip's RK805 PMIC. Signed-off-by: Elaine Zhang Acked-by: Rob Herring --- Documentation/devicetree/bindings/mfd/rk808.txt | 22 +- 1 file

[PATCH v7 07/12] mfd: dt-bindings: Add RK805 device tree bindings document

From: Elaine Zhang Add device tree bindings documentation for Rockchip's RK805 PMIC. Signed-off-by: Elaine Zhang Acked-by: Rob Herring --- Documentation/devicetree/bindings/mfd/rk808.txt | 22 +- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git

[PATCH v7 06/12] rtc: Kconfig: Name RK805 in Kconfig for RTC_DRV_RK808

From: Elaine Zhang The RK808 and RK805 PMICs are using a similar register map. We can reuse the rtc driver for the RK805 PMIC. So let's add the RK805 in the Kconfig description. Signed-off-by: Elaine Zhang --- drivers/rtc/Kconfig | 4 ++-- 1

[PATCH v7 06/12] rtc: Kconfig: Name RK805 in Kconfig for RTC_DRV_RK808

From: Elaine Zhang The RK808 and RK805 PMICs are using a similar register map. We can reuse the rtc driver for the RK805 PMIC. So let's add the RK805 in the Kconfig description. Signed-off-by: Elaine Zhang --- drivers/rtc/Kconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

[PATCH v7 01/12] mfd: rk808: fix up the chip id get failed

From: Elaine Zhang the rk8xx chip id is: ((MSB << 8) | LSB) & 0xfff0 Signed-off-by: Elaine Zhang --- drivers/mfd/rk808.c | 21 +++-- include/linux/mfd/rk808.h | 1 + 2 files changed, 16 insertions(+), 6 deletions(-)

[PATCH v7 02/12] mfd: rk808: add rk805 regs addr and ID

From: Elaine Zhang Signed-off-by: Elaine Zhang --- include/linux/mfd/rk808.h | 120 ++ 1 file changed, 120 insertions(+) diff --git a/include/linux/mfd/rk808.h b/include/linux/mfd/rk808.h index

[PATCH v7 03/12] regulator: rk808: Add regulator driver for RK805

From: Elaine Zhang Add support for the rk805 regulator. The regulator module consists of 4 DCDCs, 3 LDOs. The output voltages are configurable and are meant to supply power to the main processor and other components. Signed-off-by: Elaine Zhang

[PATCH v7 01/12] mfd: rk808: fix up the chip id get failed

From: Elaine Zhang the rk8xx chip id is: ((MSB << 8) | LSB) & 0xfff0 Signed-off-by: Elaine Zhang --- drivers/mfd/rk808.c | 21 +++-- include/linux/mfd/rk808.h | 1 + 2 files changed, 16 insertions(+), 6 deletions(-) diff --git a/drivers/mfd/rk808.c

[PATCH v7 02/12] mfd: rk808: add rk805 regs addr and ID

From: Elaine Zhang Signed-off-by: Elaine Zhang --- include/linux/mfd/rk808.h | 120 ++ 1 file changed, 120 insertions(+) diff --git a/include/linux/mfd/rk808.h b/include/linux/mfd/rk808.h index 54feb14..d315659 100644 --- a/include/linux/mfd/rk808.h

[PATCH v7 03/12] regulator: rk808: Add regulator driver for RK805

From: Elaine Zhang Add support for the rk805 regulator. The regulator module consists of 4 DCDCs, 3 LDOs. The output voltages are configurable and are meant to supply power to the main processor and other components. Signed-off-by: Elaine Zhang Acked-by: Mark Brown ---

[PATCH v7 04/12] mfd: rk808: Add RK805 support

From: Elaine Zhang The RK805 chip is a Power Management IC (PMIC) for multimedia and handheld devices. It contains the following components: - Regulators - RTC - Clocking Both RK808 and RK805 chips are using a similar register map, so we can reuse the RTC

[PATCH v7 04/12] mfd: rk808: Add RK805 support

From: Elaine Zhang The RK805 chip is a Power Management IC (PMIC) for multimedia and handheld devices. It contains the following components: - Regulators - RTC - Clocking Both RK808 and RK805 chips are using a similar register map, so we can reuse the RTC and Clocking

Re: [PATCH v3 0/4] Add xxhash and zstd modules

On 2017-07-20 17:27, Nick Terrell wrote: Hi all, This patch set adds xxhash, zstd compression, and zstd decompression modules. It also adds zstd support to BtrFS and SquashFS. Each patch has relevant summaries, benchmarks, and tests. Best, Nick Terrell Changelog: v1 -> v2: - Make pointer in

Re: [PATCH v3 0/4] Add xxhash and zstd modules

On 2017-07-20 17:27, Nick Terrell wrote: Hi all, This patch set adds xxhash, zstd compression, and zstd decompression modules. It also adds zstd support to BtrFS and SquashFS. Each patch has relevant summaries, benchmarks, and tests. Best, Nick Terrell Changelog: v1 -> v2: - Make pointer in

Re: [PATCH v4 2/2] thermal: uniphier: add UniPhier thermal driver

On Fri, 21 Jul 2017 02:09:18 +0900 wrote: > 2017-07-21 1:53 GMT+09:00 Masahiro Yamada : > > 2017-07-21 1:08 GMT+09:00 Masahiro Yamada : > >> 2017-07-07 10:54 GMT+09:00 Kunihiko Hayashi > >>

[PATCH v7 00/12] rk808: Add RK805 support

change in v7: PATCH V7 1/12: NO change in V7 PATCH V7 2/12: NO change in V7 PATCH V7 3/12: fix missing: Acked-by: Mark Brown PATCH V7 4/12: NO change in V7 PATCH V7 5/12: NO change in V7 PATCH V7 6/12: NO change in V7 PATCH V7 7/12: fix missing: Acked-by: Rob Herring

Re: [PATCH v4 2/2] thermal: uniphier: add UniPhier thermal driver

On Fri, 21 Jul 2017 02:09:18 +0900 wrote: > 2017-07-21 1:53 GMT+09:00 Masahiro Yamada : > > 2017-07-21 1:08 GMT+09:00 Masahiro Yamada : > >> 2017-07-07 10:54 GMT+09:00 Kunihiko Hayashi > >> : > >>> Add a thermal driver for on-chip PVT (Process, Voltage and Temperature) > >>> monitoring unit

[PATCH v7 00/12] rk808: Add RK805 support

change in v7: PATCH V7 1/12: NO change in V7 PATCH V7 2/12: NO change in V7 PATCH V7 3/12: fix missing: Acked-by: Mark Brown PATCH V7 4/12: NO change in V7 PATCH V7 5/12: NO change in V7 PATCH V7 6/12: NO change in V7 PATCH V7 7/12: fix missing: Acked-by: Rob Herring PATCH V7 8/12: abandon

[GIT PULL] Please pull powerpc/linux.git powerpc-4.13-3 tag

Hi Linus, Please pull some more powerpc fixes for 4.13: The following changes since commit 01e6a61aceb82e13bec29502a8eb70d9574f97ad: powerpc/64: Fix atomic64_inc_not_zero() to return an int (2017-07-12 21:49:55 +1000) are available in the git repository at:

[GIT PULL] Please pull powerpc/linux.git powerpc-4.13-3 tag

Hi Linus, Please pull some more powerpc fixes for 4.13: The following changes since commit 01e6a61aceb82e13bec29502a8eb70d9574f97ad: powerpc/64: Fix atomic64_inc_not_zero() to return an int (2017-07-12 21:49:55 +1000) are available in the git repository at:

Re: bluetooth in v4.13-rc1: lock init missing somewhere?

Hi! > > Is bluetooth expected to work on n900? > > > > It looks like lock init is missing somewhere: > > > > [ 402.901031] of_get_named_gpiod_flags: parsed > > 'bluetooth-wakeup-gpios' property of node > > '/ocp@6800/serial@4806c000/bluetooth[0]' - status (0) > > [ 403.042022] BUG: rwlock

Re: bluetooth in v4.13-rc1: lock init missing somewhere?

Hi! > > Is bluetooth expected to work on n900? > > > > It looks like lock init is missing somewhere: > > > > [ 402.901031] of_get_named_gpiod_flags: parsed > > 'bluetooth-wakeup-gpios' property of node > > '/ocp@6800/serial@4806c000/bluetooth[0]' - status (0) > > [ 403.042022] BUG: rwlock

[PATCH][media-next] media: dvb-frontends/stv0910: make various local variables static

From: Colin Ian King The list stvlist and arrays padc_lookup, s1_sn_lookup and s2_sn_lookup do not need to be in global scope, so make them all static. Cleans up a bunch of smatch warnings: symbol 'padc_lookup' was not declared. Should it be static? symbol

[PATCH][media-next] media: dvb-frontends/stv0910: make various local variables static

From: Colin Ian King The list stvlist and arrays padc_lookup, s1_sn_lookup and s2_sn_lookup do not need to be in global scope, so make them all static. Cleans up a bunch of smatch warnings: symbol 'padc_lookup' was not declared. Should it be static? symbol 's1_sn_lookup' was not declared.

[PATCH] checkpatch: testing more config for Kconfig help text

Current help text check only check a config option if it is followed by another config. Adding check for help text if the next entry is menuconfig, choice/ endchoice, comment, menu/endmenu, if/endif, source or end of file. Change-Id: I9f0b29cebb93df2cadaf77d1027208fd01efd976 Signed-off-by:

[PATCH] checkpatch: testing more config for Kconfig help text

Current help text check only check a config option if it is followed by another config. Adding check for help text if the next entry is menuconfig, choice/ endchoice, comment, menu/endmenu, if/endif, source or end of file. Change-Id: I9f0b29cebb93df2cadaf77d1027208fd01efd976 Signed-off-by:

[PATCH v1 5/6] phy: qcom-qmp: Add support for runtime PM

Driver can turn off clocks during runtime suspend. Also, runtime suspend is not as a result of host mode selective suspend then PHY can be powered off as well. Signed-off-by: Manu Gautam diff --git a/drivers/phy/qualcomm/phy-qcom-qmp.c

[PATCH v1 5/6] phy: qcom-qmp: Add support for runtime PM

Driver can turn off clocks during runtime suspend. Also, runtime suspend is not as a result of host mode selective suspend then PHY can be powered off as well. Signed-off-by: Manu Gautam diff --git a/drivers/phy/qualcomm/phy-qcom-qmp.c b/drivers/phy/qualcomm/phy-qcom-qmp.c index

[PATCH v1 6/6] usb: dwc3: core: Notify USB3 PHY as well for DRD modes

Driver currently notifies only USB3 PHY for mode change. Extend this to USB3 PHY so that driver based on the mode can release system resources - clocks, regulators etc. and can even turn off PHY during runtime suspend. Signed-off-by: Manu Gautam diff --git

[PATCH v1 6/6] usb: dwc3: core: Notify USB3 PHY as well for DRD modes

Driver currently notifies only USB3 PHY for mode change. Extend this to USB3 PHY so that driver based on the mode can release system resources - clocks, regulators etc. and can even turn off PHY during runtime suspend. Signed-off-by: Manu Gautam diff --git a/drivers/usb/dwc3/core.c

[PATCH v1 4/6] phy: qcom-qusb2: Add support for runtime PM

Driver can turn off clocks during runtime suspend. Also, runtime suspend is not as a result of host mode selective suspend then PHY can be powered off as well. Signed-off-by: Manu Gautam diff --git a/drivers/phy/qualcomm/phy-qcom-qusb2.c

[PATCH v1 4/6] phy: qcom-qusb2: Add support for runtime PM

Driver can turn off clocks during runtime suspend. Also, runtime suspend is not as a result of host mode selective suspend then PHY can be powered off as well. Signed-off-by: Manu Gautam diff --git a/drivers/phy/qualcomm/phy-qcom-qusb2.c b/drivers/phy/qualcomm/phy-qcom-qusb2.c index

[PATCH v1 3/6] phy: qcom-qusb2: Power-on PHY before initialization

PHY must be powered on before turning ON clocks and attempting to initialize it. Driver is exposing separate init and power_on routines for this. Apparently USB dwc3 core driver performs power-on after init. Also, poweron and init for QUSB2 PHY need to be executed together always, hence remove

[PATCH v1 3/6] phy: qcom-qusb2: Power-on PHY before initialization

PHY must be powered on before turning ON clocks and attempting to initialize it. Driver is exposing separate init and power_on routines for this. Apparently USB dwc3 core driver performs power-on after init. Also, poweron and init for QUSB2 PHY need to be executed together always, hence remove

[PATCH v1 2/6] phy: qcom-qmp: Power-on PHY before initialization

PHY must be powered on before turning ON clocks and attempting to initialize it. Driver is exposing separate init and power_on routines for this. Apparently USB dwc3 core driver performs power-on after init. Also, poweron and init for QMP PHY need to be executed together always, hence remove

[PATCH v1 2/6] phy: qcom-qmp: Power-on PHY before initialization

PHY must be powered on before turning ON clocks and attempting to initialize it. Driver is exposing separate init and power_on routines for this. Apparently USB dwc3 core driver performs power-on after init. Also, poweron and init for QMP PHY need to be executed together always, hence remove

[PATCH v1 1/6] phy: qcom-qmp: Fix phy pipe clock gating

From: Vivek Gautam Pipe clock comes out of the phy and is available as long as the phy is turned on. Clock controller fails to gate this clock after the phy is turned off and generates a warning. / # [ 33.048561] gcc_usb3_phy_pipe_clk status stuck at 'on' [

[PATCH v1 1/6] phy: qcom-qmp: Fix phy pipe clock gating

From: Vivek Gautam Pipe clock comes out of the phy and is available as long as the phy is turned on. Clock controller fails to gate this clock after the phy is turned off and generates a warning. / # [ 33.048561] gcc_usb3_phy_pipe_clk status stuck at 'on' [ 33.048585] [ cut here

[RESEND] [v3 PATCH 2/2] powernv/powerpc: Clear PECE1 in LPCR via stop-api only on Hotplug

From: "Gautham R. Shenoy" Currently we use the stop-api provided by the firmware to program the SLW engine to restore the values of hypervisor resources that get lost on deeper idle states (such as winkle). Since the deep states were only used for CPU-Hotplug on POWER8

[RESEND] [v3 PATCH 2/2] powernv/powerpc: Clear PECE1 in LPCR via stop-api only on Hotplug

From: "Gautham R. Shenoy" Currently we use the stop-api provided by the firmware to program the SLW engine to restore the values of hypervisor resources that get lost on deeper idle states (such as winkle). Since the deep states were only used for CPU-Hotplug on POWER8 systems, we would program

Re: [PATCH 1/5] iommu/arm-smmu-v3: put off the execution of TLBI* to reduce lock confliction

On Thu, 20 Jul 2017 15:07:05 -0400 Nate Watterson wrote: > Hi Jonathan, > > [...] > > > >>> Hi All, > >>> > >>> I'm a bit of late entry to this discussion. Just been running some more > >>> detailed tests on our d05 boards and wanted to bring some more

Re: [PATCH 1/5] iommu/arm-smmu-v3: put off the execution of TLBI* to reduce lock confliction

On Thu, 20 Jul 2017 15:07:05 -0400 Nate Watterson wrote: > Hi Jonathan, > > [...] > > > >>> Hi All, > >>> > >>> I'm a bit of late entry to this discussion. Just been running some more > >>> detailed tests on our d05 boards and wanted to bring some more numbers to > >>> the

Re: [PATCH] bluetooth: document config options

Hi Pavel, >>> Kernel config options should include useful help text; I had to look >>> up the terms on wikipedia. >>> >>> Signed-off-by: Pavel Machek >>> >>> diff --git a/net/bluetooth/Kconfig b/net/bluetooth/Kconfig >>> index 68f951b..133c8a6 100644 >>> ---

Re: [PATCH] bluetooth: document config options

Hi Pavel, >>> Kernel config options should include useful help text; I had to look >>> up the terms on wikipedia. >>> >>> Signed-off-by: Pavel Machek >>> >>> diff --git a/net/bluetooth/Kconfig b/net/bluetooth/Kconfig >>> index 68f951b..133c8a6 100644 >>> --- a/net/bluetooth/Kconfig >>> +++

[PATCH] scsi: megaraid_sas: fix memleak in megasas_alloc_cmdlist_fusion

From: Shu Wang Found this issue by kmemleak, a few kb mem was leaked in megasas_alloc_cmdlist_fusion when kzalloc failed for one megasas_cmd_fusion allocation. unreferenced object 0x88045dbd2000 (size 8192): comm "systemd-udevd", pid 323, jiffies 4294671759 (age

[PATCH] scsi: megaraid_sas: fix memleak in megasas_alloc_cmdlist_fusion

From: Shu Wang Found this issue by kmemleak, a few kb mem was leaked in megasas_alloc_cmdlist_fusion when kzalloc failed for one megasas_cmd_fusion allocation. unreferenced object 0x88045dbd2000 (size 8192): comm "systemd-udevd", pid 323, jiffies 4294671759 (age 49.008s) backtrace:

RE: [PATCH v2 5/7] input: goldfish: Fix multitouch event handling

Hello, Dmitry, Thanks for your valuable review - and sorry for my late response. For this patch, I am just the submitter, and I would ask Lingfang to make some additional comments/clarifications regarding architecture of user-kernel protocols for relevant drivers, and also regarding similar

RE: [PATCH v2 5/7] input: goldfish: Fix multitouch event handling

Hello, Dmitry, Thanks for your valuable review - and sorry for my late response. For this patch, I am just the submitter, and I would ask Lingfang to make some additional comments/clarifications regarding architecture of user-kernel protocols for relevant drivers, and also regarding similar

[PATCH v7 1/4] firmware: scm: Add new SCM call API for switching memory ownership

Two different processors on a SOC need to switch memory ownership during load/unload. To enable this, second level memory map table need to be updated, which is done by secure layer. This patch adds the interface for making secure monitor call for memory ownership switching request.

[PATCH v7 1/4] firmware: scm: Add new SCM call API for switching memory ownership

Two different processors on a SOC need to switch memory ownership during load/unload. To enable this, second level memory map table need to be updated, which is done by secure layer. This patch adds the interface for making secure monitor call for memory ownership switching request.

[PATCH v7 2/4] remoteproc: qcom: refactor mss fw image loading sequence

This patch refactor code to first load all firmware blobs and then update modem proc to authenticate and boot fw. Signed-off-by: Avaneesh Kumar Dwivedi --- drivers/remoteproc/qcom_q6v5_pil.c | 19 --- 1 file changed, 8 insertions(+), 11 deletions(-)

[PATCH v7 2/4] remoteproc: qcom: refactor mss fw image loading sequence

This patch refactor code to first load all firmware blobs and then update modem proc to authenticate and boot fw. Signed-off-by: Avaneesh Kumar Dwivedi --- drivers/remoteproc/qcom_q6v5_pil.c | 19 --- 1 file changed, 8 insertions(+), 11 deletions(-) diff --git

Re: [PATCH] irqchip/gic-v3-its: Allow GIC ITS number more than MAX_NUMNODES

On 21 July 2017 at 18:06, Hanjun Guo wrote: > > On 2017/7/21 17:51, Hanjun Guo wrote: > > From: Hanjun Guo > > > > When running 4.13-rc1 on top of D05, I got the boot log: > > > > [0.00] SRAT: PXM 0 -> ITS 0 -> Node 0 > > [0.00] SRAT:

Re: [PATCH] irqchip/gic-v3-its: Allow GIC ITS number more than MAX_NUMNODES

On 21 July 2017 at 18:06, Hanjun Guo wrote: > > On 2017/7/21 17:51, Hanjun Guo wrote: > > From: Hanjun Guo > > > > When running 4.13-rc1 on top of D05, I got the boot log: > > > > [0.00] SRAT: PXM 0 -> ITS 0 -> Node 0 > > [0.00] SRAT: PXM 0 -> ITS 1 -> Node 0 > > [0.00]

[PATCH v7 4/4] remoteproc: qcom: Add support for mss remoteproc on msm8996

This patch add support for mss boot on msm8996. Major changes include initializing mss rproc for msm8996, making appropriate change for executing mss reset sequence etc. Signed-off-by: Avaneesh Kumar Dwivedi --- .../devicetree/bindings/remoteproc/qcom,q6v5.txt | 1 +

[PATCH v7 4/4] remoteproc: qcom: Add support for mss remoteproc on msm8996

This patch add support for mss boot on msm8996. Major changes include initializing mss rproc for msm8996, making appropriate change for executing mss reset sequence etc. Signed-off-by: Avaneesh Kumar Dwivedi --- .../devicetree/bindings/remoteproc/qcom,q6v5.txt | 1 +

[PATCH v7 3/4] remoteproc: qcom: Make secure world call for mem ownership switch

MSS proc on msm8996 can not access fw loaded region without stage second translation of memory pages where mpss image are loaded. This patch in order to enable mss boot on msm8996 invoke scm call to switch or share ownership between apps and modem. Signed-off-by: Avaneesh Kumar Dwivedi

[PATCH v7 3/4] remoteproc: qcom: Make secure world call for mem ownership switch

MSS proc on msm8996 can not access fw loaded region without stage second translation of memory pages where mpss image are loaded. This patch in order to enable mss boot on msm8996 invoke scm call to switch or share ownership between apps and modem. Signed-off-by: Avaneesh Kumar Dwivedi ---

[PATCH v4 2/5] dt-bindings: pwm-backlight: add PWM delay proprieties.

Hardware needs a delay between setting an initial (non-zero) PWM and enabling the backlight using GPIO. The post-pwm-on-delay-ms specifies this delay in milli seconds. Hardware also needs a delay between disabing the backlight using GPIO and setting PWM value to 0. The pwm-off-delay-ms is this

[PATCH v4 2/5] dt-bindings: pwm-backlight: add PWM delay proprieties.

Hardware needs a delay between setting an initial (non-zero) PWM and enabling the backlight using GPIO. The post-pwm-on-delay-ms specifies this delay in milli seconds. Hardware also needs a delay between disabing the backlight using GPIO and setting PWM value to 0. The pwm-off-delay-ms is this

[PATCH v7 0/4] Add memory ownership switch support and enable mss rproc on msm8996

This patch set does following 1- Adds new scm call which helps in stage two translation of a memory region so that memory ownership sharing and switching can be achieved on armv8 and later. 2- Enable mss remoteproc on msm8996 Changes w.r.t. last patchset 1-

[PATCH v7 0/4] Add memory ownership switch support and enable mss rproc on msm8996

This patch set does following 1- Adds new scm call which helps in stage two translation of a memory region so that memory ownership sharing and switching can be achieved on armv8 and later. 2- Enable mss remoteproc on msm8996 Changes w.r.t. last patchset 1-

[PATCH v4 5/5] ARM: dts: rockchip: set PWM delay backlight settings for Minnie

The minnie devices comes with an AUO B101EAN01 panel which is different from default veyron devices, thus the power on/off timing sequence is slightly different. The datasheet specifies a pwm delay of 200 ms, so update the PMW delay proprieties accordingly. Signed-off-by: Enric Balletbo i Serra

[PATCH v4 5/5] ARM: dts: rockchip: set PWM delay backlight settings for Minnie

The minnie devices comes with an AUO B101EAN01 panel which is different from default veyron devices, thus the power on/off timing sequence is slightly different. The datasheet specifies a pwm delay of 200 ms, so update the PMW delay proprieties accordingly. Signed-off-by: Enric Balletbo i Serra

[PATCH v4 1/5] pwm-backlight: enable/disable the PWM before/after LCD enable toggle.

Before this patch the enable signal was set before the PWM signal and vice-versa on power off. This sequence is wrong, at least, it is on the different panels datasheets that I checked, so I inverted the sequence to follow the specs. For reference the following panels have the mentioned sequence:

[PATCH v4 1/5] pwm-backlight: enable/disable the PWM before/after LCD enable toggle.

Before this patch the enable signal was set before the PWM signal and vice-versa on power off. This sequence is wrong, at least, it is on the different panels datasheets that I checked, so I inverted the sequence to follow the specs. For reference the following panels have the mentioned sequence:

[PATCH v4 4/5] ARM: dts: rockchip: set PWM delay backlight settings for Veyron.

For veyron the binding should provide both PWM timings, the delay between you enable the PWM and set the enable signal, and the delay between you disable the PWM signal and clear the enable signal. Update the binding accordingly, in this case the panels connected to the veyron boards have a

[PATCH v4 3/5] pwm-backlight: add support for PWM delays proprieties.

Some panels (i.e. N116BGE-L41), in their power sequence specifications, request a delay between set the PWM signal and enable the backlight and between clear the PWM signal and disable the backlight. Add support for the new post-pwm-on-delay-ms and pwm-off-delay-ms proprieties to meet the timings.

[PATCH v4 4/5] ARM: dts: rockchip: set PWM delay backlight settings for Veyron.

For veyron the binding should provide both PWM timings, the delay between you enable the PWM and set the enable signal, and the delay between you disable the PWM signal and clear the enable signal. Update the binding accordingly, in this case the panels connected to the veyron boards have a

[PATCH v4 3/5] pwm-backlight: add support for PWM delays proprieties.

Some panels (i.e. N116BGE-L41), in their power sequence specifications, request a delay between set the PWM signal and enable the backlight and between clear the PWM signal and disable the backlight. Add support for the new post-pwm-on-delay-ms and pwm-off-delay-ms proprieties to meet the timings.

[v3 PATCH 1/2] powernv/powerpc:Save/Restore additional SPRs for stop4 cpuidle

From: "Gautham R. Shenoy" The stop4 idle state on POWER9 is a deep idle state which loses hypervisor resources, but whose latency is low enough that it can be exposed via cpuidle. Until now, the deep idle states which lose hypervisor resources (eg: winkle) were only

[v3 PATCH 1/2] powernv/powerpc:Save/Restore additional SPRs for stop4 cpuidle

From: "Gautham R. Shenoy" The stop4 idle state on POWER9 is a deep idle state which loses hypervisor resources, but whose latency is low enough that it can be exposed via cpuidle. Until now, the deep idle states which lose hypervisor resources (eg: winkle) were only exposed via CPU-Hotplug.

Re: [PATCH] bluetooth: document config options

Hi! > > Kernel config options should include useful help text; I had to look > > up the terms on wikipedia. > > > > Signed-off-by: Pavel Machek > > > > diff --git a/net/bluetooth/Kconfig b/net/bluetooth/Kconfig > > index 68f951b..133c8a6 100644 > > --- a/net/bluetooth/Kconfig > >

[v3 PATCH 0/2] powerpc: powernv: Enable stop4 via cpuidle

From: "Gautham R. Shenoy" Hi, This is the third iteration of the patchset to enable exploitation of stop4 idle state on POWER9 via cpuidle. The earlier version can be found here : [v2]: https://lkml.org/lkml/2017/7/19/152 [v1]: https://lkml.org/lkml/2017/7/18/691 The

Re: [PATCH] bluetooth: document config options

Hi! > > Kernel config options should include useful help text; I had to look > > up the terms on wikipedia. > > > > Signed-off-by: Pavel Machek > > > > diff --git a/net/bluetooth/Kconfig b/net/bluetooth/Kconfig > > index 68f951b..133c8a6 100644 > > --- a/net/bluetooth/Kconfig > > +++

[v3 PATCH 0/2] powerpc: powernv: Enable stop4 via cpuidle

From: "Gautham R. Shenoy" Hi, This is the third iteration of the patchset to enable exploitation of stop4 idle state on POWER9 via cpuidle. The earlier version can be found here : [v2]: https://lkml.org/lkml/2017/7/19/152 [v1]: https://lkml.org/lkml/2017/7/18/691 The changes across the

<    6   7   8   9   10   11   12   13   14   15   >