On 23.05.2018 21:51, Christoph Hellwig wrote:
> On Wed, May 23, 2018 at 05:11:51PM +0200, David Hildenbrand wrote:
>> Kernel modules that want to control how/when memory is onlined/offlined
>> need a proper interface to these functions. Also, for adding memory
>> properly, memory_block_size_bytes
On 23.05.2018 21:51, Christoph Hellwig wrote:
> On Wed, May 23, 2018 at 05:11:51PM +0200, David Hildenbrand wrote:
>> Kernel modules that want to control how/when memory is onlined/offlined
>> need a proper interface to these functions. Also, for adding memory
>> properly, memory_block_size_bytes
Document devicetree bindings for ROHM BD71837 PMIC clock output.
Signed-off-by: Matti Vaittinen
---
.../bindings/clock/rohm,bd71837-clock.txt | 37 ++
1 file changed, 37 insertions(+)
create mode 100644
Document devicetree bindings for ROHM BD71837 PMIC clock output.
Signed-off-by: Matti Vaittinen
---
.../bindings/clock/rohm,bd71837-clock.txt | 37 ++
1 file changed, 37 insertions(+)
create mode 100644
Document devicetree bindings for ROHM BD71837 PMIC regulators.
Signed-off-by: Matti Vaittinen
---
.../bindings/regulator/rohm,bd71837-regulator.txt | 124 +
1 file changed, 124 insertions(+)
create mode 100644
Document devicetree bindings for ROHM BD71837 PMIC regulators.
Signed-off-by: Matti Vaittinen
---
.../bindings/regulator/rohm,bd71837-regulator.txt | 124 +
1 file changed, 124 insertions(+)
create mode 100644
Document devicetree bindings for ROHM BD71837 PMIC MFD.
Signed-off-by: Matti Vaittinen
---
.../devicetree/bindings/mfd/rohm,bd71837-pmic.txt | 55 ++
1 file changed, 55 insertions(+)
create mode 100644
Document devicetree bindings for ROHM BD71837 PMIC MFD.
Signed-off-by: Matti Vaittinen
---
.../devicetree/bindings/mfd/rohm,bd71837-pmic.txt | 55 ++
1 file changed, 55 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt
diff --git
ROHM BD71837 PMIC MFD driver providing interrupts and support
for two subsystems:
- clk
- Regulators
Signed-off-by: Matti Vaittinen
---
drivers/mfd/bd71837.c | 238 +
include/linux/mfd/bd71837.h | 316
ROHM BD71837 PMIC MFD driver providing interrupts and support
for two subsystems:
- clk
- Regulators
Signed-off-by: Matti Vaittinen
---
drivers/mfd/bd71837.c | 238 +
include/linux/mfd/bd71837.h | 316
2 files
Configuration options and Makefile for BD71837 PMIC MFD driver
Signed-off-by: Matti Vaittinen
---
drivers/mfd/Kconfig | 13 +
drivers/mfd/Makefile | 1 +
2 files changed, 14 insertions(+)
diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
Configuration options and Makefile for BD71837 PMIC MFD driver
Signed-off-by: Matti Vaittinen
---
drivers/mfd/Kconfig | 13 +
drivers/mfd/Makefile | 1 +
2 files changed, 14 insertions(+)
diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
index b860eb5aa194..7aa05fc9ed8e
Patch series adding support for ROHM BD71837 PMIC.
BD71837 is a programmable Power Management IC for powering single-core,
dual-core, and quad-core SoC’s such as NXP-i.MX 8M. It is optimized for
low BOM cost and compact solution footprint. It integrates 8 buck
regulators and 7 LDO’s to provide
Patch series adding support for ROHM BD71837 PMIC.
BD71837 is a programmable Power Management IC for powering single-core,
dual-core, and quad-core SoC’s such as NXP-i.MX 8M. It is optimized for
low BOM cost and compact solution footprint. It integrates 8 buck
regulators and 7 LDO’s to provide
Hi Neil, Hi Stefan,
On Fri, May 18, 2018 at 03:05:02PM +0200, Neil Armstrong wrote:
> The EC can expose a CEC bus, this patch adds the CEC related definitions
> needed by the cros-ec-cec driver.
> Having a 16 byte mkbp event size makes it possible to send CEC
> messages from the EC to the AP
Hi Neil, Hi Stefan,
On Fri, May 18, 2018 at 03:05:02PM +0200, Neil Armstrong wrote:
> The EC can expose a CEC bus, this patch adds the CEC related definitions
> needed by the cros-ec-cec driver.
> Having a 16 byte mkbp event size makes it possible to send CEC
> messages from the EC to the AP
On 5/23/2018 8:43 PM, Sudeep Holla wrote:
On 19/05/18 18:34, Taniya Das wrote:
Add QCOM cpufreq firmware device bindings for Qualcomm Technology Inc's
SoCs. This is required for managing the cpu frequency transitions which are
controlled by firmware.
Signed-off-by: Taniya Das
On 5/23/2018 8:43 PM, Sudeep Holla wrote:
On 19/05/18 18:34, Taniya Das wrote:
Add QCOM cpufreq firmware device bindings for Qualcomm Technology Inc's
SoCs. This is required for managing the cpu frequency transitions which are
controlled by firmware.
Signed-off-by: Taniya Das
---
Commit-ID: 22916fdb9c50e8fb303bdcedca88fd8798a85844
Gitweb: https://git.kernel.org/tip/22916fdb9c50e8fb303bdcedca88fd8798a85844
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:45 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: 22916fdb9c50e8fb303bdcedca88fd8798a85844
Gitweb: https://git.kernel.org/tip/22916fdb9c50e8fb303bdcedca88fd8798a85844
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:45 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 23 May 2018 10:26:44 -0300
perf
Commit-ID: a1a3a0624e6cd0e2c46a7400800a5e687521a504
Gitweb: https://git.kernel.org/tip/a1a3a0624e6cd0e2c46a7400800a5e687521a504
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:44 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: a1a3a0624e6cd0e2c46a7400800a5e687521a504
Gitweb: https://git.kernel.org/tip/a1a3a0624e6cd0e2c46a7400800a5e687521a504
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:44 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 23 May 2018 10:26:43 -0300
perf
Commit-ID: 15acef6c3727cfe0bc9d1f6b273cca46689e8cd8
Gitweb: https://git.kernel.org/tip/15acef6c3727cfe0bc9d1f6b273cca46689e8cd8
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:41 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: 15acef6c3727cfe0bc9d1f6b273cca46689e8cd8
Gitweb: https://git.kernel.org/tip/15acef6c3727cfe0bc9d1f6b273cca46689e8cd8
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:41 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 23 May 2018 10:26:42 -0300
perf
Commit-ID: b4503cdb67098b2f08320c2c83df758ea72a4431
Gitweb: https://git.kernel.org/tip/b4503cdb67098b2f08320c2c83df758ea72a4431
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:43 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: b4503cdb67098b2f08320c2c83df758ea72a4431
Gitweb: https://git.kernel.org/tip/b4503cdb67098b2f08320c2c83df758ea72a4431
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:43 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 23 May 2018 10:26:43 -0300
perf
Commit-ID: d2c959803c8843f64e419d833dc3722154c82492
Gitweb: https://git.kernel.org/tip/d2c959803c8843f64e419d833dc3722154c82492
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:42 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: d2c959803c8843f64e419d833dc3722154c82492
Gitweb: https://git.kernel.org/tip/d2c959803c8843f64e419d833dc3722154c82492
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:42 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 23 May 2018 10:26:42 -0300
perf
On 24-05-18, 10:48, Taniya Das wrote:
> Hello Rob, Viresh,
>
> Thank you for the comments. If I understand correctly, the device tree nodes
> should look something like the below.
>
> Though I am not sure if any vendor name could be associated in the cpu
> nodes.
Well Rob said Yes to that I
On 24-05-18, 10:48, Taniya Das wrote:
> Hello Rob, Viresh,
>
> Thank you for the comments. If I understand correctly, the device tree nodes
> should look something like the below.
>
> Though I am not sure if any vendor name could be associated in the cpu
> nodes.
Well Rob said Yes to that I
Commit-ID: c9dd1d894958b81a329ec01e7dd03b92eca52789
Gitweb: https://git.kernel.org/tip/c9dd1d894958b81a329ec01e7dd03b92eca52789
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:40 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: c9dd1d894958b81a329ec01e7dd03b92eca52789
Gitweb: https://git.kernel.org/tip/c9dd1d894958b81a329ec01e7dd03b92eca52789
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:40 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 23 May 2018 10:26:41 -0300
perf
Commit-ID: 6e97957d3d30552c415292bb08a0e5f3c459c027
Gitweb: https://git.kernel.org/tip/6e97957d3d30552c415292bb08a0e5f3c459c027
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:39 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: 6e97957d3d30552c415292bb08a0e5f3c459c027
Gitweb: https://git.kernel.org/tip/6e97957d3d30552c415292bb08a0e5f3c459c027
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:39 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 23 May 2018 10:26:41 -0300
perf
Commit-ID: f6838209484d5cfb368ca5c61d150cc4054eef59
Gitweb: https://git.kernel.org/tip/f6838209484d5cfb368ca5c61d150cc4054eef59
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:38 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: f6838209484d5cfb368ca5c61d150cc4054eef59
Gitweb: https://git.kernel.org/tip/f6838209484d5cfb368ca5c61d150cc4054eef59
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:38 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 23 May 2018 10:26:40 -0300
perf
Commit-ID: 5759a6820aadd38b2c8c10e93919eae8e31a9f9a
Gitweb: https://git.kernel.org/tip/5759a6820aadd38b2c8c10e93919eae8e31a9f9a
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:35 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: 787e4da9f95fd44376b3af6fa163ac0b3a48a1fc
Gitweb: https://git.kernel.org/tip/787e4da9f95fd44376b3af6fa163ac0b3a48a1fc
Author: Jin Yao
AuthorDate: Tue, 22 May 2018 19:38:35 +0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 23
Commit-ID: 5759a6820aadd38b2c8c10e93919eae8e31a9f9a
Gitweb: https://git.kernel.org/tip/5759a6820aadd38b2c8c10e93919eae8e31a9f9a
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:35 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 22 May 2018 10:59:22 -0300
perf
Commit-ID: 787e4da9f95fd44376b3af6fa163ac0b3a48a1fc
Gitweb: https://git.kernel.org/tip/787e4da9f95fd44376b3af6fa163ac0b3a48a1fc
Author: Jin Yao
AuthorDate: Tue, 22 May 2018 19:38:35 +0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 23 May 2018 10:26:40 -0300
perf annotate:
Commit-ID: 1c5aae7710bb9ecf82a5cc88e35a028a8b385763
Gitweb: https://git.kernel.org/tip/1c5aae7710bb9ecf82a5cc88e35a028a8b385763
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:36 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: 1c5aae7710bb9ecf82a5cc88e35a028a8b385763
Gitweb: https://git.kernel.org/tip/1c5aae7710bb9ecf82a5cc88e35a028a8b385763
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:36 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 23 May 2018 10:24:08 -0300
perf
Commit-ID: a8ce99b0ee9ad32debad0a9f28d21451ba237cc1
Gitweb: https://git.kernel.org/tip/a8ce99b0ee9ad32debad0a9f28d21451ba237cc1
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:37 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: a8ce99b0ee9ad32debad0a9f28d21451ba237cc1
Gitweb: https://git.kernel.org/tip/a8ce99b0ee9ad32debad0a9f28d21451ba237cc1
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:37 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 23 May 2018 10:26:39 -0300
perf
Commit-ID: 4d004365e25251002935fc3843d80934248ad3ed
Gitweb: https://git.kernel.org/tip/4d004365e25251002935fc3843d80934248ad3ed
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:34 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: 4d004365e25251002935fc3843d80934248ad3ed
Gitweb: https://git.kernel.org/tip/4d004365e25251002935fc3843d80934248ad3ed
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:34 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 22 May 2018 10:55:59 -0300
perf
Commit-ID: 7ebaf4890f63eb90856b76864a0847413cdf6c86
Gitweb: https://git.kernel.org/tip/7ebaf4890f63eb90856b76864a0847413cdf6c86
Author: Jin Yao
AuthorDate: Mon, 21 May 2018 22:57:46 +0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 21
Commit-ID: 7ebaf4890f63eb90856b76864a0847413cdf6c86
Gitweb: https://git.kernel.org/tip/7ebaf4890f63eb90856b76864a0847413cdf6c86
Author: Jin Yao
AuthorDate: Mon, 21 May 2018 22:57:46 +0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 21 May 2018 14:41:25 -0300
perf annotate:
Commit-ID: 9cecca325ea879c84fcd31a5e609a514c1a1dbd1
Gitweb: https://git.kernel.org/tip/9cecca325ea879c84fcd31a5e609a514c1a1dbd1
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:32 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: 9cecca325ea879c84fcd31a5e609a514c1a1dbd1
Gitweb: https://git.kernel.org/tip/9cecca325ea879c84fcd31a5e609a514c1a1dbd1
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:32 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 22 May 2018 10:52:49 -0300
perf
Commit-ID: 4d99e4136580d178e3523281a820be17bf814bf8
Gitweb: https://git.kernel.org/tip/4d99e4136580d178e3523281a820be17bf814bf8
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:33 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: 4d99e4136580d178e3523281a820be17bf814bf8
Gitweb: https://git.kernel.org/tip/4d99e4136580d178e3523281a820be17bf814bf8
Author: Adrian Hunter
AuthorDate: Tue, 22 May 2018 13:54:33 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 22 May 2018 10:54:22 -0300
perf
Commit-ID: a26bb0ba706aef4f42cc9377c0d4e849378574a4
Gitweb: https://git.kernel.org/tip/a26bb0ba706aef4f42cc9377c0d4e849378574a4
Author: Jin Yao
AuthorDate: Mon, 21 May 2018 22:57:45 +0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 21
Commit-ID: a26bb0ba706aef4f42cc9377c0d4e849378574a4
Gitweb: https://git.kernel.org/tip/a26bb0ba706aef4f42cc9377c0d4e849378574a4
Author: Jin Yao
AuthorDate: Mon, 21 May 2018 22:57:45 +0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 21 May 2018 14:41:01 -0300
perf report: Use
On 24.05.2018 07:30, Viresh Kumar wrote:
> On 23-05-18, 19:00, Dmitry Osipenko wrote:
>> PLL_C is running at 600MHz which is significantly higher than the 216MHz
>> of the PLL_P and it is known that PLL_C is always-ON because AHB BUS is
>> running on that PLL. Let's use PLL_C as intermediate clock
On 24.05.2018 07:30, Viresh Kumar wrote:
> On 23-05-18, 19:00, Dmitry Osipenko wrote:
>> PLL_C is running at 600MHz which is significantly higher than the 216MHz
>> of the PLL_P and it is known that PLL_C is always-ON because AHB BUS is
>> running on that PLL. Let's use PLL_C as intermediate clock
Commit-ID: e2bdbe80a0b7dea9ba73582701b8a67c01e1da4f
Gitweb: https://git.kernel.org/tip/e2bdbe80a0b7dea9ba73582701b8a67c01e1da4f
Author: Jin Yao
AuthorDate: Mon, 21 May 2018 22:57:44 +0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 21
Commit-ID: e2bdbe80a0b7dea9ba73582701b8a67c01e1da4f
Gitweb: https://git.kernel.org/tip/e2bdbe80a0b7dea9ba73582701b8a67c01e1da4f
Author: Jin Yao
AuthorDate: Mon, 21 May 2018 22:57:44 +0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 21 May 2018 14:40:54 -0300
perf evlist:
; Merge tag 'perf-core-for-mingo-4.18-20180519' of
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core
> (2018-05-19 13:32:53 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
>
perf-core-for-mingo-4.18-20180519' of
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core
> (2018-05-19 13:32:53 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
> tags/perf-core-fo
After some analysis with Florian (thnx) we found out that the current
implementation is broken:
https://patchwork.ozlabs.org/patch/836538/
https://github.com/torvalds/linux/commit/c499696e7901bda18385ac723b7bd27c3a4af624#diff-a2b6f8d89e18de600e873ac3ac43fa1d
Florians comment:
After some analysis with Florian (thnx) we found out that the current
implementation is broken:
https://patchwork.ozlabs.org/patch/836538/
https://github.com/torvalds/linux/commit/c499696e7901bda18385ac723b7bd27c3a4af624#diff-a2b6f8d89e18de600e873ac3ac43fa1d
Florians comment:
The correct fieldbit value for the NAND PLL reload trigger is 27.
Fixes: commit e120c17a70e5 ("clk: mvebu: support for 98DX3236 SoC")
Signed-off-by: Chris Packham
---
I can't remember where the value of 26 came from. Looking at the lsp source I
have from
The correct fieldbit value for the NAND PLL reload trigger is 27.
Fixes: commit e120c17a70e5 ("clk: mvebu: support for 98DX3236 SoC")
Signed-off-by: Chris Packham
---
I can't remember where the value of 26 came from. Looking at the lsp source I
have from Marvell it's always been 27, so I suspect
On Tue, May 22, 2018 at 08:37:28PM +0200, Michal Hocko wrote:
> So why is this any better than the current code. Sure I am not a great
> fan of GFP_ZONE_TABLE because of how it is incomprehensible but this
> doesn't look too much better, yet we are losing a check for incompatible
> gfp flags. The
On Tue, May 22, 2018 at 08:37:28PM +0200, Michal Hocko wrote:
> So why is this any better than the current code. Sure I am not a great
> fan of GFP_ZONE_TABLE because of how it is incomprehensible but this
> doesn't look too much better, yet we are losing a check for incompatible
> gfp flags. The
Thanks Bjorn for reviewing.
On 5/23/2018 11:56 AM, Bjorn Andersson wrote:
On Sun 13 May 00:01 PDT 2018, Rohit kumar wrote:
--- a/Documentation/devicetree/bindings/remoteproc/qcom,adsp.txt
+++ b/Documentation/devicetree/bindings/remoteproc/qcom,adsp.txt
@@ -10,6 +10,7 @@ on the Qualcomm ADSP
Hello Rob, Viresh,
Thank you for the comments. If I understand correctly, the device tree
nodes should look something like the below.
Though I am not sure if any vendor name could be associated in the cpu
nodes.
Please suggest if my understanding is wrong.
cpu@0 {
qcom,freq-domain
Thanks Bjorn for reviewing.
On 5/23/2018 11:56 AM, Bjorn Andersson wrote:
On Sun 13 May 00:01 PDT 2018, Rohit kumar wrote:
--- a/Documentation/devicetree/bindings/remoteproc/qcom,adsp.txt
+++ b/Documentation/devicetree/bindings/remoteproc/qcom,adsp.txt
@@ -10,6 +10,7 @@ on the Qualcomm ADSP
Hello Rob, Viresh,
Thank you for the comments. If I understand correctly, the device tree
nodes should look something like the below.
Though I am not sure if any vendor name could be associated in the cpu
nodes.
Please suggest if my understanding is wrong.
cpu@0 {
qcom,freq-domain
2018-05-21 20:06 GMT+09:00 Ulf Magnusson :
>>
>> static char *__expand_string(const char **str, bool (*is_end)(const char *))
>> {
>> const char *in, *prev_in, *p;
>> char *new, *out;
>> size_t outlen;
>>
>> out = xmalloc(1);
>> *out =
2018-05-21 20:06 GMT+09:00 Ulf Magnusson :
>>
>> static char *__expand_string(const char **str, bool (*is_end)(const char *))
>> {
>> const char *in, *prev_in, *p;
>> char *new, *out;
>> size_t outlen;
>>
>> out = xmalloc(1);
>> *out = 0;
>>
>> p =
On Wed, May 23, 2018 at 2:09 AM, Peter Zijlstra wrote:
> On Mon, May 21, 2018 at 11:35:38PM -0700, Ivan Babrou wrote:
>> > + TP_printk("path=%s cpu=%d runtime_remaining=%lld",
>> > __get_str(cfs_path),
>> > + __entry->cpu, __entry->runtime_remaining)
>>
On Wed, May 23, 2018 at 2:09 AM, Peter Zijlstra wrote:
> On Mon, May 21, 2018 at 11:35:38PM -0700, Ivan Babrou wrote:
>> > + TP_printk("path=%s cpu=%d runtime_remaining=%lld",
>> > __get_str(cfs_path),
>> > + __entry->cpu, __entry->runtime_remaining)
>> >
>>
>> Can you add
On 2018/05/23 3:54, Michal Hocko wrote:
> On Tue 22-05-18 22:04:23, TSUKADA Koutaro wrote:
>> On 2018/05/22 3:07, Mike Kravetz wrote:
>>> On 05/17/2018 09:27 PM, TSUKADA Koutaro wrote:
Thanks to Mike Kravetz for comment on the previous version patch.
The purpose of this patch-set is
On 2018/05/23 3:54, Michal Hocko wrote:
> On Tue 22-05-18 22:04:23, TSUKADA Koutaro wrote:
>> On 2018/05/22 3:07, Mike Kravetz wrote:
>>> On 05/17/2018 09:27 PM, TSUKADA Koutaro wrote:
Thanks to Mike Kravetz for comment on the previous version patch.
The purpose of this patch-set is
On 23-05-18, 14:25, Sudeep Holla wrote:
> On 23/05/18 13:38, Ilia Lin wrote:
> > +static int __init qcom_cpufreq_kryo_init(void)
> > +{
> > + /*
> > +* Since the driver depends on smem and nvmem drivers, which may
> > +* return EPROBE_DEFER, all the real activity is done in the probe,
>
On 23-05-18, 14:25, Sudeep Holla wrote:
> On 23/05/18 13:38, Ilia Lin wrote:
> > +static int __init qcom_cpufreq_kryo_init(void)
> > +{
> > + /*
> > +* Since the driver depends on smem and nvmem drivers, which may
> > +* return EPROBE_DEFER, all the real activity is done in the probe,
>
(We analyzed the crash and added the result below.)
We report the crash:
"KASAN: use-after-free Read in vgacon_invert_region"
This crash was found in v4.17-rc3. Specifically, memory access (read
operation) is invalid and which is detected by KASAN.
Analysis:
The function "vt_do_resize"
(We analyzed the crash and added the result below.)
We report the crash:
"KASAN: use-after-free Read in vgacon_invert_region"
This crash was found in v4.17-rc3. Specifically, memory access (read
operation) is invalid and which is detected by KASAN.
Analysis:
The function "vt_do_resize"
On 23-05-18, 14:25, Sudeep Holla wrote:
> On 23/05/18 13:38, Ilia Lin wrote:
> > +config ARM_QCOM_CPUFREQ_KRYO
> > + bool "Qualcomm Kryo based CPUFreq"
> > + depends on QCOM_QFPROM
> > + depends on QCOM_SMEM
> > + select PM_OPP
> > + help
> > + This adds the CPUFreq driver for
On 23-05-18, 14:25, Sudeep Holla wrote:
> On 23/05/18 13:38, Ilia Lin wrote:
> > +config ARM_QCOM_CPUFREQ_KRYO
> > + bool "Qualcomm Kryo based CPUFreq"
> > + depends on QCOM_QFPROM
> > + depends on QCOM_SMEM
> > + select PM_OPP
> > + help
> > + This adds the CPUFreq driver for
On 23-05-18, 19:00, Dmitry Osipenko wrote:
> PLL_C is running at 600MHz which is significantly higher than the 216MHz
> of the PLL_P and it is known that PLL_C is always-ON because AHB BUS is
> running on that PLL. Let's use PLL_C as intermediate clock source, making
> CPU snappier a tad during of
On 23-05-18, 19:00, Dmitry Osipenko wrote:
> PLL_C is running at 600MHz which is significantly higher than the 216MHz
> of the PLL_P and it is known that PLL_C is always-ON because AHB BUS is
> running on that PLL. Let's use PLL_C as intermediate clock source, making
> CPU snappier a tad during of
On 23-05-18, 19:00, Dmitry Osipenko wrote:
> PLL_P is known to be always running at 216MHz, hence there is no need to
> query its rate.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/cpufreq/tegra20-cpufreq.c | 12 +---
> 1 file changed, 5 insertions(+), 7
On 23-05-18, 19:00, Dmitry Osipenko wrote:
> PLL_P is known to be always running at 216MHz, hence there is no need to
> query its rate.
>
> Signed-off-by: Dmitry Osipenko
> ---
> drivers/cpufreq/tegra20-cpufreq.c | 12 +---
> 1 file changed, 5 insertions(+), 7 deletions(-)
>
> diff
On 2018/05/22 22:51, Michal Hocko wrote:
> On Fri 18-05-18 13:27:27, TSUKADA Koutaro wrote:
>> The purpose of this patch-set is to make it possible to control whether or
>> not to charge surplus hugetlb pages obtained by overcommitting to memory
>> cgroup. In the future, I am trying to accomplish
On 2018/05/22 22:51, Michal Hocko wrote:
> On Fri 18-05-18 13:27:27, TSUKADA Koutaro wrote:
>> The purpose of this patch-set is to make it possible to control whether or
>> not to charge surplus hugetlb pages obtained by overcommitting to memory
>> cgroup. In the future, I am trying to accomplish
Arnd Bergmann writes:
> On Fri, May 11, 2018 at 2:20 PM, Kalle Valo wrote:
>> Stephen Rothwell writes:
>>
>>> After merging the mac80211-next tree, today's linux-next build (arm_multi
>>> v7_defconfig) produced this warning:
>>>
>>>
On 23-05-18, 12:20, Joe Perches wrote:
> Convert the S_ symbolic permissions to their octal equivalents as
> using octal and not symbolic permissions is preferred by many as more
> readable.
>
> see: https://lkml.org/lkml/2016/8/2/1945
>
> Done with automated conversion via:
> $
Arnd Bergmann writes:
> On Fri, May 11, 2018 at 2:20 PM, Kalle Valo wrote:
>> Stephen Rothwell writes:
>>
>>> After merging the mac80211-next tree, today's linux-next build (arm_multi
>>> v7_defconfig) produced this warning:
>>>
>>> drivers/net/wireless/marvell/mwifiex/uap_event.c: In function
On 23-05-18, 12:20, Joe Perches wrote:
> Convert the S_ symbolic permissions to their octal equivalents as
> using octal and not symbolic permissions is preferred by many as more
> readable.
>
> see: https://lkml.org/lkml/2016/8/2/1945
>
> Done with automated conversion via:
> $
On Wed, May 23, 2018 at 08:59:06PM -0400, Theodore Y. Ts'o wrote:
> On Thu, May 24, 2018 at 10:49:31AM +1000, Dave Chinner wrote:
> >
> > We've learnt this lesson the hard way over and over again: don't
> > parse untrusted input in privileged contexts. How many times do we
> > have to make the
On Wed, May 23, 2018 at 08:59:06PM -0400, Theodore Y. Ts'o wrote:
> On Thu, May 24, 2018 at 10:49:31AM +1000, Dave Chinner wrote:
> >
> > We've learnt this lesson the hard way over and over again: don't
> > parse untrusted input in privileged contexts. How many times do we
> > have to make the
On Wed, May 23, 2018 at 05:54:50PM -0700, Joel Fernandes wrote:
> On Wed, May 23, 2018 at 12:23:49PM -0700, Paul E. McKenney wrote:
> > On Wed, May 23, 2018 at 09:06:17AM -0700, Paul E. McKenney wrote:
> > > On Tue, May 22, 2018 at 11:38:14PM -0700, Joel Fernandes wrote:
> > > > From: "Joel
On Wed, May 23, 2018 at 05:54:50PM -0700, Joel Fernandes wrote:
> On Wed, May 23, 2018 at 12:23:49PM -0700, Paul E. McKenney wrote:
> > On Wed, May 23, 2018 at 09:06:17AM -0700, Paul E. McKenney wrote:
> > > On Tue, May 22, 2018 at 11:38:14PM -0700, Joel Fernandes wrote:
> > > > From: "Joel
scripts/kallsyms.c: function write_src:
"printf", the #1 format specifier "d" need arg type "int",
but the according arg "table_cnt" has type "unsigned int"
scripts/recordmcount.c: function do_file:
"fprintf", the #1 format specifier "d" need arg type "int",
but the according arg
scripts/kallsyms.c: function write_src:
"printf", the #1 format specifier "d" need arg type "int",
but the according arg "table_cnt" has type "unsigned int"
scripts/recordmcount.c: function do_file:
"fprintf", the #1 format specifier "d" need arg type "int",
but the according arg
+static int skl_tplg_get_pvt_data_v4(struct snd_soc_tplg_dapm_widget
*tplg_w,
+ struct skl *skl, struct device *dev,
+ struct skl_module_cfg *mconfig)
+{
+ struct skl_dfw_v4_module *dfw =
+ (struct
+static int skl_tplg_get_pvt_data_v4(struct snd_soc_tplg_dapm_widget
*tplg_w,
+ struct skl *skl, struct device *dev,
+ struct skl_module_cfg *mconfig)
+{
+ struct skl_dfw_v4_module *dfw =
+ (struct
1 - 100 of 2226 matches
Mail list logo