linaro-kernel

linaro-kernel@lists.linaro.org

10095 discussions

master build: 0 failures 3 warnings (v4.9-rc4-194-g86e4ee7)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.9-rc4-194-g86e4ee7 Commit: 86e4ee760e Merge tag 'acpi-4.9-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm Build Time: 86 min 34 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 3 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 3 warnings 0 mismatches : arm64-allmodconfig 2 warnings 0 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 3 2 ../sound/soc/qcom/lpass-platform.c:83:29: warning: 'dma_ch' may be used uninitialized in this function [-Wmaybe-uninitialized] 2 ../drivers/iio/temperature/maxim_thermocouple.c:141:5: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized] 1 ../include/linux/kernel.h:739:16: warning: comparison of distinct pointer types lacks a cast =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : PASS, 0 errors, 3 warnings, 0 section mismatches Warnings: ../include/linux/kernel.h:739:16: warning: comparison of distinct pointer types lacks a cast ../sound/soc/qcom/lpass-platform.c:83:29: warning: 'dma_ch' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/iio/temperature/maxim_thermocouple.c:141:5: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 2 warnings, 0 section mismatches Warnings: ../sound/soc/qcom/lpass-platform.c:83:29: warning: 'dma_ch' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/iio/temperature/maxim_thermocouple.c:141:5: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig

8 years, 10 months

master build: 0 failures 3 warnings (v4.9-rc4-171-g5f3a5cb)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.9-rc4-171-g5f3a5cb Commit: 5f3a5cb8e7 Merge branch 'for-linus' of git://git.kernel.dk/linux-block Build Time: 87 min 20 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 3 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 3 warnings 0 mismatches : arm64-allmodconfig 2 warnings 0 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 3 2 ../sound/soc/qcom/lpass-platform.c:83:29: warning: 'dma_ch' may be used uninitialized in this function [-Wmaybe-uninitialized] 2 ../drivers/iio/temperature/maxim_thermocouple.c:141:5: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized] 1 ../include/linux/kernel.h:739:16: warning: comparison of distinct pointer types lacks a cast =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : PASS, 0 errors, 3 warnings, 0 section mismatches Warnings: ../include/linux/kernel.h:739:16: warning: comparison of distinct pointer types lacks a cast ../sound/soc/qcom/lpass-platform.c:83:29: warning: 'dma_ch' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/iio/temperature/maxim_thermocouple.c:141:5: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 2 warnings, 0 section mismatches Warnings: ../sound/soc/qcom/lpass-platform.c:83:29: warning: 'dma_ch' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/iio/temperature/maxim_thermocouple.c:141:5: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig

8 years, 10 months

master build: 0 failures 3 warnings (v4.9-rc4-107-g015ed94)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.9-rc4-107-g015ed94 Commit: 015ed9433b Merge branch 'maybe-uninitialized' (patches from Arnd) Build Time: 87 min 22 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 3 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 3 warnings 0 mismatches : arm64-allmodconfig 2 warnings 0 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 3 2 ../sound/soc/qcom/lpass-platform.c:83:29: warning: 'dma_ch' may be used uninitialized in this function [-Wmaybe-uninitialized] 2 ../drivers/iio/temperature/maxim_thermocouple.c:141:5: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized] 1 ../include/linux/kernel.h:739:16: warning: comparison of distinct pointer types lacks a cast =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : PASS, 0 errors, 3 warnings, 0 section mismatches Warnings: ../sound/soc/qcom/lpass-platform.c:83:29: warning: 'dma_ch' may be used uninitialized in this function [-Wmaybe-uninitialized] ../include/linux/kernel.h:739:16: warning: comparison of distinct pointer types lacks a cast ../drivers/iio/temperature/maxim_thermocouple.c:141:5: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 2 warnings, 0 section mismatches Warnings: ../sound/soc/qcom/lpass-platform.c:83:29: warning: 'dma_ch' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/iio/temperature/maxim_thermocouple.c:141:5: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig

8 years, 10 months

master build: 0 failures 1 warnings (v4.9-rc4-79-gc5e4ca6)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.9-rc4-79-gc5e4ca6 Commit: c5e4ca6da9 Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs Build Time: 87 min 4 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 1 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 1 warnings 0 mismatches : arm64-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 1 1 ../include/linux/kernel.h:739:16: warning: comparison of distinct pointer types lacks a cast =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../include/linux/kernel.h:739:16: warning: comparison of distinct pointer types lacks a cast ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

8 years, 10 months

next-20161111 build: 0 failures 0 warnings (next-20161111)

by Build bot for Mark Brown

Tree/Branch: next-20161111 Git describe: next-20161111 Commit: 37634f05ef Add linux-next specific files for 20161111 Build Time: 87 min 29 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 0 Section Mismatches: 4 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 0 warnings 2 mismatches : arm64-allmodconfig 0 warnings 2 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Section Mismatch Summary: 4 1 WARNING: vmlinux.o(.text+0x79ba1c): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() 1 WARNING: vmlinux.o(.text+0x548320): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() 1 WARNING: drivers/built-in.o(.text+0x1a356c): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() 1 WARNING: drivers/built-in.o(.text+0x1105d8): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : PASS, 0 errors, 0 warnings, 2 section mismatches Section Mismatches: WARNING: drivers/built-in.o(.text+0x1a356c): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() WARNING: vmlinux.o(.text+0x79ba1c): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 0 warnings, 2 section mismatches Section Mismatches: WARNING: drivers/built-in.o(.text+0x1105d8): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() WARNING: vmlinux.o(.text+0x548320): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig

8 years, 10 months

[Discussion] Performance levels of power domains

by Viresh Kumar

Hi Guys, I wanted to involve you guys to get a discussion going for a problem we want to solve, and so this mail. Platform details: Some of the Qualcom SoCs have the option to configure the performance level of their Power Domains. The performance levels are identified by integer values (lets say 0-9, 0 being the lowest). Another M3 core handles the *real* voltage scaling based on the input received (from software) in terms of these performance levels. The M3 core translates the levels into a range of voltages (corners) and selects the right one by itself. Software needs to provide the performance level for the entire domain to the M3 core and so software also needs to handle performance requests from all the devices that lie in the domain X and find a Performance Level P, which can satisfy all the devices (normally the highest requrested level). Problem statement: As we aren't dealing with Voltages here, we can't really get the benefits of the Regulators framework. The regulators are managed internally by the M3 core. All we need is a way for software to comeout with inputs for the M3 core. The OPP framework can be used to include performance levels for each OPP (frequency) entry. But what framework can be used to select performance level of power domains ? By name, power-domain or genpd looks to be the right choice, but until now it is only managing power-on and power-off of devices and domains. Should we extend that (along with runtime PM), or do something else? Qualcomm guys, please correct my understanding of the hardware in case, something wasn't explained correctly. -- viresh

8 years, 10 months

next-20161110 build: 0 failures 1 warnings (next-20161110)

by Build bot for Mark Brown

Tree/Branch: next-20161110 Git describe: next-20161110 Commit: 6e637d6fd5 Add linux-next specific files for 20161110 Build Time: 88 min 18 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 1 Section Mismatches: 4 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 0 warnings 2 mismatches : arm64-allmodconfig 1 warnings 2 mismatches : arm-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 1 1 ../drivers/tty/serial/pxa.c:944:1: warning: 'serial_pxa_init' is deprecated [-Wdeprecated-declarations] Section Mismatch Summary: 4 1 WARNING: vmlinux.o(.text+0x78c114): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() 1 WARNING: vmlinux.o(.text+0x544400): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() 1 WARNING: drivers/built-in.o(.text+0x1a2564): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() 1 WARNING: drivers/built-in.o(.text+0x10fa98): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : PASS, 0 errors, 0 warnings, 2 section mismatches Section Mismatches: WARNING: drivers/built-in.o(.text+0x1a2564): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() WARNING: vmlinux.o(.text+0x78c114): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() ------------------------------------------------------------------------------- arm-allmodconfig : PASS, 0 errors, 1 warnings, 2 section mismatches Warnings: ../drivers/tty/serial/pxa.c:944:1: warning: 'serial_pxa_init' is deprecated [-Wdeprecated-declarations] Section Mismatches: WARNING: drivers/built-in.o(.text+0x10fa98): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() WARNING: vmlinux.o(.text+0x544400): Section mismatch in reference from the function fsl_guts_probe() to the function .init.text:of_flat_dt_get_machine_name() ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig

8 years, 10 months

[PATCH V2 0/8] PM / OPP: Multiple regulator support

by Viresh Kumar

Hi, Some platforms (like TI) have complex DVFS configuration for CPU devices, where multiple regulators are required to be configured to change DVFS state of the device. This was explained well by Nishanth earlier [1]. Some thoughts went into it few months back but then it all got lost. I am trying to get that back on track with this thread. One of the major complaints around multiple regulators case was that the DT isn't responsible in any way to represent the ordering in which multiple supplies need to be programmed, before or after frequency change. It was considered in this patch and such information is left to the platform specific OPP driver now, which can register its own opp_set_rate() callback with the OPP core and the OPP core will then call it during DVFS. The patches are tested on Exynos5250 (Dual A15). I have hacked around DT and code to pass values for multiple regulators and verified that they are all properly read by the kernel (using debugfs interface). Though more testing on real (TI) platforms would be useful. This is rebased over: linux-next branch in the PM tree. V1->V2: - Ack from Rob for 1st patch - Moved the supplies structure to pm_opp.h (Dave) - Fixed an compilation warning. -- viresh [1] https://marc.info/?l=linux-pm&m=145684495832764&w=2 Viresh Kumar (8): PM / OPP: Reword binding supporting multiple regulators per device PM / OPP: Don't use OPP structure outside of rcu protected section PM / OPP: Manage supply's voltage/current in a separate structure PM / OPP: Pass struct dev_pm_opp_supply to _set_opp_voltage() PM / OPP: Add infrastructure to manage multiple regulators PM / OPP: Separate out _generic_opp_set_rate() PM / OPP: Allow platform specific custom opp_set_rate() callbacks PM / OPP: Don't WARN on multiple calls to dev_pm_opp_set_regulators() Documentation/devicetree/bindings/opp/opp.txt | 25 +- drivers/base/power/opp/core.c | 501 ++++++++++++++++++++------ drivers/base/power/opp/debugfs.c | 48 ++- drivers/base/power/opp/of.c | 104 ++++-- drivers/base/power/opp/opp.h | 20 +- drivers/cpufreq/cpufreq-dt.c | 9 +- include/linux/pm_opp.h | 49 ++- 7 files changed, 574 insertions(+), 182 deletions(-) -- 2.7.1.410.g6faf27b

8 years, 10 months

master build: 0 failures 1 warnings (v4.9-rc4-58-g27bcd37)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.9-rc4-58-g27bcd37 Commit: 27bcd37e02 Merge tag 'sound-4.9-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound Build Time: 86 min 44 sec Passed: 10 / 10 (100.00 %) Failed: 0 / 10 ( 0.00 %) Errors: 0 Warnings: 1 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 1 warnings 0 mismatches : arm64-allmodconfig ------------------------------------------------------------------------------- Warnings Summary: 1 1 ../include/linux/kernel.h:739:16: warning: comparison of distinct pointer types lacks a cast =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../include/linux/kernel.h:739:16: warning: comparison of distinct pointer types lacks a cast ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm-multi_v4t_defconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

8 years, 10 months

v4.4.30-rt41 build: 0 failures 0 warnings (v4.4.30-rt41)

by Build bot for Mark Brown

Tree/Branch: v4.4.30-rt41 Git describe: v4.4.30-rt41 Commit: 4db7ec2e7b Linux 4.4.30-rt41 Build Time: 131 min 18 sec Passed: 9 / 9 (100.00 %) Failed: 0 / 9 ( 0.00 %) Errors: 0 Warnings: 0 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): ------------------------------------------------------------------------------- =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm64-allmodconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig arm64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

8 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel