linaro-kernel August 2014

linaro-kernel@lists.linaro.org

78 participants
244 discussions

[PATCH] arm: Fix DEBUG_LL for multi-platform kernels (without PL01X)

by Daniel Thompson

When building a multi_v7_defconfig kernel it is not possible to configure DEBUG_LL to use any serial device except a ARM Primecell PL01X, or more accurately and worse, it is possible to configure a different serial device but KConfig does not honour this request. The happens because the multi-platform mode may include ARCH_SPEAR13XX and this forcibly engages DEBUG_UART_PL01X to provide some kind of compatibility with single platform builds (SPEAr supports both single and multi-platform). This in turn causes DEBUG_LL_INCLUDE to wedge at debug/pl01x.S. Problem is fixed by only deploying the compatibility options for SPEAr when ARCH_MULTIPLATFORM is not set. Signed-off-by: Daniel Thompson <daniel.thompson(a)linaro.org> --- arch/arm/Kconfig.debug | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug index 0531da8..f10c784 100644 --- a/arch/arm/Kconfig.debug +++ b/arch/arm/Kconfig.debug @@ -991,9 +991,9 @@ config DEBUG_LL_INCLUDE config DEBUG_UART_PL01X def_bool ARCH_EP93XX || \ ARCH_INTEGRATOR || \ - ARCH_SPEAR3XX || \ - ARCH_SPEAR6XX || \ - ARCH_SPEAR13XX || \ + (ARCH_SPEAR3XX && !ARCH_MULTIPLATFORM) || \ + (ARCH_SPEAR6XX && !ARCH_MULTIPLATFORM) || \ + (ARCH_SPEAR13XX && !ARCH_MULTIPLATFORM) || \ ARCH_VERSATILE # Compatibility options for 8250 -- 1.9.0

9 years, 7 months

[RFC 0/8] kgdb: NMI/FIQ support for ARM

by Daniel Thompson

This patchset makes it possible to use the kgdb NMI infrastructure on ARM platforms. The kgdb NMI infrastructure works by re-routing an UARTs interrupt signal from IRQ to FIQ. The UART will no longer function normally and will instead be managed by kgdb using the polled I/O functions. Any character delivered to the UART causes the kgdb handler function to be called. Each serial driver explicitly consents (or not) to this abuse by calling the appropriate registration functions. [PATCH 1/8] arm: fiq: Allow EOI to be communicated to the intc [PATCH 2/8] irqchip: gic: Provide support for interrupt grouping Both these patches lay the ground work to allow modern ARM interrupt controllers to support FIQ correctly. [PATCH 3/8] ARM: Move some macros from entry-armv to entry-header [PATCH 4/8] ARM: Add KGDB/KDB FIQ debugger generic code This is the heart of the patch series, allowing FIQs to be registered with KGDB and handled by KGDB. [PATCH 5/8] serial: amba-pl011: Pass on FIQ information to KGDB. [PATCH 6/8] serial: asc: Add support for KGDB's FIQ/NMI mode Extend to UART drivers to allow the register the appropriate FIQ (implicitly promising to behave properly when their own IRQ handler is cut off). [PATCH 7/8] ARM: VIC: Add vic_set_fiq function to select if an... [PATCH 8/8] arm: fiq: Hack FIQ routing backdoors into GIC and VIC Here we hit the serious request-for-comment section. It is not clear what the best way to get the interrupt controller to re-route an interrupt source from the IRQ signal to the FIQ signal. Clearly the approach here is wrong but it has been enough for me to test my work so far. Anton Vorontsov (2): ARM: Move some macros from entry-armv to entry-header ARM: Add KGDB/KDB FIQ debugger generic code Arve Hjønnevåg (1): ARM: VIC: Add vic_set_fiq function to select if an interrupt should generate an IRQ or FIQ Daniel Thompson (5): arm: fiq: Allow EOI to be communicated to the intc irqchip: gic: Provide support for interrupt grouping serial: amba-pl011: Pass on FIQ information to KGDB. serial: asc: Add support for KGDB's FIQ/NMI mode arm: fiq: Hack FIQ routing backdoors into GIC and VIC arch/arm/Kconfig | 2 + arch/arm/Kconfig.debug | 18 ++++ arch/arm/boot/dts/stih416.dtsi | 2 +- arch/arm/boot/dts/vexpress-v2m-rs1.dtsi | 2 +- arch/arm/include/asm/fiq.h | 1 + arch/arm/include/asm/kgdb.h | 7 ++ arch/arm/kernel/Makefile | 1 + arch/arm/kernel/entry-armv.S | 151 +---------------------------- arch/arm/kernel/entry-header.S | 164 ++++++++++++++++++++++++++++++++ arch/arm/kernel/fiq.c | 50 ++++++++++ arch/arm/kernel/kgdb_fiq.c | 117 +++++++++++++++++++++++ arch/arm/kernel/kgdb_fiq_entry.S | 87 +++++++++++++++++ drivers/irqchip/irq-gic.c | 62 +++++++++++- drivers/irqchip/irq-vic.c | 23 +++++ drivers/tty/serial/amba-pl011.c | 18 +++- drivers/tty/serial/st-asc.c | 25 +++++ include/linux/irqchip/arm-gic.h | 3 + include/linux/irqchip/arm-vic.h | 1 + 18 files changed, 576 insertions(+), 158 deletions(-) create mode 100644 arch/arm/kernel/kgdb_fiq.c create mode 100644 arch/arm/kernel/kgdb_fiq_entry.S -- 1.9.0

9 years, 7 months

[PATCH V3 00/10] CPUFreq: cpufreq-cpu0 updates for 3.{17|18 ?}

by Viresh Kumar

Hi Rafael, I am sending this again, but without the controversial part this time. I have dropped last two patches which were about detecting clock sharing among CPUs. Would fix up that later once other Maintainers get in sync about the bindings. So, what's left here ? These are mostly updates/reorders which can be applied the patches which I have dropped now. These are all well reviewed and tested by others. Getting them in shouldn't break anything, I believe. Its better people start using the updates we already have, otherwise they will keep on sending fixes they get (The way Pramod Gurav tried it today). Can we please get them in 3.17 if its still allowed? Or -next otherwise. V2: https://lkml.org/lkml/2014/7/1/358 Rebased over: 3.17-rc2 git://git.linaro.org/people/viresh.kumar/linux.git cpufreq/cpu0-updates-v3 V2->V3: Dropped few patches, nothing much. -- Thanks Viresh Viresh Kumar (10): cpufreq: Add support for per-policy driver data cpufreq: cpu0: Update Module Author cpufreq: cpu0: don't validate clock on clk_put() cpufreq: cpu0: print relevant error when we defer probe cpufreq: cpu0: use dev_{err|warn|dbg} instead of pr_{err|warn|debug} cpufreq: cpu0: Move per-cluster initialization code to ->init() cpufreq: cpu0: try regulators with name "cpu-supply" cpufreq: cpu0: Make allocate_resources() work for any CPU cpufreq: cpu0: rename driver and internals to 'cpufreq_generic' cpufreq: generic: set platform_{driver|device} '.name' to 'cpufreq-generic' .../{cpufreq-cpu0.txt => cpufreq-generic.txt} | 8 +- arch/arm/mach-imx/imx27-dt.c | 2 +- arch/arm/mach-imx/mach-imx51.c | 2 +- arch/arm/mach-omap2/pm.c | 2 +- arch/arm/mach-shmobile/board-ape6evm-reference.c | 2 +- arch/arm/mach-shmobile/cpufreq.c | 2 +- arch/arm/mach-shmobile/setup-sh73a0.c | 4 +- arch/arm/mach-zynq/common.c | 2 +- drivers/cpufreq/Kconfig | 10 +- drivers/cpufreq/Kconfig.arm | 2 +- drivers/cpufreq/Makefile | 2 +- drivers/cpufreq/cpufreq-cpu0.c | 248 -------------- drivers/cpufreq/cpufreq-generic.c | 363 +++++++++++++++++++++ drivers/cpufreq/exynos4210-cpufreq.c | 2 +- drivers/cpufreq/exynos4x12-cpufreq.c | 2 +- drivers/cpufreq/exynos5250-cpufreq.c | 2 +- drivers/cpufreq/highbank-cpufreq.c | 6 +- drivers/cpufreq/s5pv210-cpufreq.c | 2 +- include/linux/cpufreq.h | 3 + 19 files changed, 392 insertions(+), 274 deletions(-) rename Documentation/devicetree/bindings/cpufreq/{cpufreq-cpu0.txt => cpufreq-generic.txt} (85%) delete mode 100644 drivers/cpufreq/cpufreq-cpu0.c create mode 100644 drivers/cpufreq/cpufreq-generic.c -- 2.0.3.693.g996b0fd

9 years, 7 months

[PATCH] irq: gic-v3: Tag all low level accessors __maybey_unused

by Mark Brown

From: Mark Brown <broonie(a)linaro.org> This is only really needed for gic_write_sgi1r in the !SMP case since it is only referenced in the SMP initialisation code but it seems better to have these functions all next to each other and declared consistently. Signed-off-by: Mark Brown <broonie(a)linaro.org> --- drivers/irqchip/irq-gic-v3.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c index 41b98ba7ffd1..f1ba38f11f7a 100644 --- a/drivers/irqchip/irq-gic-v3.c +++ b/drivers/irqchip/irq-gic-v3.c @@ -104,7 +104,7 @@ static void gic_redist_wait_for_rwp(void) } /* Low level accessors */ -static u64 gic_read_iar(void) +static u64 __maybe_unused gic_read_iar(void) { u64 irqstat; @@ -112,24 +112,24 @@ static u64 gic_read_iar(void) return irqstat; } -static void gic_write_pmr(u64 val) +static void __maybe_unused gic_write_pmr(u64 val) { asm volatile("msr_s " __stringify(ICC_PMR_EL1) ", %0" : : "r" (val)); } -static void gic_write_ctlr(u64 val) +static void __maybe_unused gic_write_ctlr(u64 val) { asm volatile("msr_s " __stringify(ICC_CTLR_EL1) ", %0" : : "r" (val)); isb(); } -static void gic_write_grpen1(u64 val) +static void __maybe_unused gic_write_grpen1(u64 val) { asm volatile("msr_s " __stringify(ICC_GRPEN1_EL1) ", %0" : : "r" (val)); isb(); } -static void gic_write_sgi1r(u64 val) +static void __maybe_unused gic_write_sgi1r(u64 val) { asm volatile("msr_s " __stringify(ICC_SGI1R_EL1) ", %0" : : "r" (val)); } -- 2.0.1

9 years, 7 months

[PATCH] irqchip: gic-v3: Only define gic_peek_irq() when building SMP

by Mark Brown

From: Mark Brown <broonie(a)linaro.org> If building with CONFIG_SMP disbled (for example, with allnoconfig) then GCC complains that the static function gic_peek_irq() is defined but not used since the only reference is in the SMP initialisation code. Fix this by moving the function definition inside the ifdef. Signed-off-by: Mark Brown <broonie(a)linaro.org> --- drivers/irqchip/irq-gic-v3.c | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c index 81519bae0453..30130f955151 100644 --- a/drivers/irqchip/irq-gic-v3.c +++ b/drivers/irqchip/irq-gic-v3.c @@ -200,19 +200,6 @@ static void gic_poke_irq(struct irq_data *d, u32 offset) rwp_wait(); } -static int gic_peek_irq(struct irq_data *d, u32 offset) -{ - u32 mask = 1 << (gic_irq(d) % 32); - void __iomem *base; - - if (gic_irq_in_rdist(d)) - base = gic_data_rdist_sgi_base(); - else - base = gic_data.dist_base; - - return !!(readl_relaxed(base + offset + (gic_irq(d) / 32) * 4) & mask); -} - static void gic_mask_irq(struct irq_data *d) { gic_poke_irq(d, GICD_ICENABLER); @@ -401,6 +388,19 @@ static void gic_cpu_init(void) } #ifdef CONFIG_SMP +static int gic_peek_irq(struct irq_data *d, u32 offset) +{ + u32 mask = 1 << (gic_irq(d) % 32); + void __iomem *base; + + if (gic_irq_in_rdist(d)) + base = gic_data_rdist_sgi_base(); + else + base = gic_data.dist_base; + + return !!(readl_relaxed(base + offset + (gic_irq(d) / 32) * 4) & mask); +} + static int gic_secondary_init(struct notifier_block *nfb, unsigned long action, void *hcpu) { -- 2.0.1

9 years, 8 months

Re: [PATCH v9 4/6] ARM: Exynos: switch to using generic cpufreq driver for Exynos4210/5250/5420

by Kevin Hilman

Tomasz Figa <tomasz.figa(a)gmail.com> writes: > Kukjin, > > On 31.07.2014 20:32, Kukjin Kim wrote: >> On 07/30/14 17:07, Thomas Abraham wrote: >>> The new CPU clock type allows the use of generic CPUfreq drivers. So for >>> Exynos4210/5250, switch to using generic cpufreq driver. For Exynos5420, >>> which did not have CPUfreq driver support, enable the use of generic >>> CPUfreq driver. >>> >>> Suggested-by: Tomasz Figa<t.figa(a)samsung.com> >>> Cc: Kukjin Kim<kgene.kim(a)samsung.com> >> >> Looks good to me, >> >> Acked-by: Kukjin Kim <kgene.kim(a)samsung.com> >> >> BTW, who will handle this series? I hope see this series in 3.17. > > This series consists mostly of clock changes and it likely depends on > patches already in my for-next, so I would be inclined toward taking it > through samsung-clk tree. So has this series been picked up anywhere? I don't see it in your samsung-clk tree, nor in Kukjin's for-next. Also, I'm curious whether or how this is has been tested on big.LITTLE SoCs. I'm trying it on the 5800/Chromebook2 and it's not terribly stable. I'm testing along with CPUidle, so there may be some untested interactions there as it seems a bit more stable without CPUidle enabled. I'd love to hear from anyone else that's testing CPUidle and CPUfreq together big.LITTLE 5420/5800, with or without the switcher. Also, the patch below[2] is needed for 5800. FWIW, I have a temporary branch[1] based on the v3.17-rc branch of the exynos-reference tree where I've added the DT patch needed for CPUidle, this series (and it's dependencies) which is what I'm using for testing. Kevin [1] git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux.git wip/exynos/integ [2] >From 72ee00246c0fbdcf5dbb0bf910b8a427da4ac002 Mon Sep 17 00:00:00 2001 From: Kevin Hilman <khilman(a)linaro.org> Date: Fri, 22 Aug 2014 16:04:11 -0700 Subject: [PATCH] ARM: Exynos: use generic cpufreq driver for Exynos5800 As a derivative of the 5420, the 5800 SoC should use the generic big.LITTLE driver for Exynos5800 as well. Signed-off-by: Kevin Hilman <khilman(a)linaro.org> --- arch/arm/mach-exynos/exynos.c | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos/exynos.c index 8923d37c3e85..debe50bf736a 100644 --- a/arch/arm/mach-exynos/exynos.c +++ b/arch/arm/mach-exynos/exynos.c @@ -283,6 +283,7 @@ static void __init exynos_init_irq(void) static const struct of_device_id exynos_cpufreq_matches[] = { { .compatible = "samsung,exynos5420", .data = "arm-bL-cpufreq-dt" }, + { .compatible = "samsung,exynos5800", .data = "arm-bL-cpufreq-dt" }, { .compatible = "samsung,exynos5250", .data = "cpufreq-cpu0" }, { .compatible = "samsung,exynos4210", .data = "cpufreq-cpu0" }, { .compatible = "samsung,exynos5440", .data = "exynos5440-cpufreq" }, -- 1.9.2

9 years, 8 months

[PATCH v5 0/5] ARM: EXYNOS: cpuidle: fix AFTR mode on boards with secure firmware enabled

by Bartlomiej Zolnierkiewicz

Hi, This patch series adds support for AFTR idle mode on boards with secure firmware enabled and allows EXYNOS cpuidle driver usage on Exynos4x12 SoCs. It has been tested on Trats2 board (using Exynos4412 SoC with secure firmware enabled) on which AFTR mode reduces power consumption by ~12% when EXYNOS cpuidle driver is enabled (in both cases the default exynos_defconfig config is used and CPU1-3 are offlined). Depends on: - next-20140804 branch of linux-next kernel tree - [PATCH v5][next-20140804] ARM: EXYNOS: Fix suspend/resume sequences (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg35262.html) - [PATCH v2 0/2] Firmware-assisted suspend/resume of Exynos SoCs (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg34282.html) Changes since v4: - rebased on top of next-20140804 + [PATCH v5][next-20140804] ARM: EXYNOS: Fix suspend/resume sequences (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg35262.html) [PATCH v2 0/2] Firmware-assisted suspend/resume of Exynos SoCs (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg34282.html) - call exynos_save_cp15() only on A9 type core (this is needed for the future Exynos3250 SoC support) Changes since v3: - rebased on top of next-20140804 + [PATCH v4][next-20140804] ARM: EXYNOS: Fix suspend/resume sequences (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg35192.html) [PATCH v2 0/2] Firmware-assisted suspend/resume of Exynos SoCs (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg34282.html) - (re-)added patch fixing S5P_CENTRAL_SEQ_OPTION register setup Changes since v2: - rebased on top of next-20140708 + [PATCH 5/6] ARM: EXYNOS: Fix suspend/resume sequencies (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg32809.html) [with rejects fixed] [PATCH 6/6] ARM: EXYNOS: Register cpuidle device only on Exynos4210 and 5250 (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg32808.html) [PATCH 0/2] Firmware-assisted suspend/resume of Exynos SoCs (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg32991.html) [with rejects fixed in patch #2] - addressed review comments from Tomasz Figa and Daniel Lezcano Changes since v1: - synced against next-20140602 - added missing Acked-by-s Best regards, -- Bartlomiej Zolnierkiewicz Samsung R&D Institute Poland Samsung Electronics Bartlomiej Zolnierkiewicz (5): ARM: EXYNOS: PM: replace EXYNOS_BOOT_VECTOR_* macros by static inlines ARM: EXYNOS: add AFTR mode support to firmware do_idle method ARM: EXYNOS: cpuidle: add secure firmware support to AFTR mode code ARM: EXYNOS: PM: fix register setup for AFTR mode code ARM: EXYNOS: cpuidle: allow driver usage on Exynos4x12 SoCs arch/arm/include/asm/firmware.h | 2 +- arch/arm/mach-exynos/common.h | 5 ++++ arch/arm/mach-exynos/exynos.c | 4 ++- arch/arm/mach-exynos/firmware.c | 34 ++++++++++++++++------- arch/arm/mach-exynos/pm.c | 60 ++++++++++++++++++++++++----------------- 5 files changed, 70 insertions(+), 35 deletions(-) -- 1.8.2.3

9 years, 8 months

[PATCH] ARM: configs: Enable cpufreq-cpu0 for multi_v7_defconfig

by Mark Brown

Many boards share the cpufreq-cpu0 driver meaning that if we enable it in multi_v7_defconfig we can get a reasonable amount of functional utility for systems and test coverage for a fairly small increase in kernel size. Signed-off-by: Mark Brown <broonie(a)kernel.org> --- arch/arm/configs/multi_v7_defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig index 05c0e7c789df..9799e9d2e222 100644 --- a/arch/arm/configs/multi_v7_defconfig +++ b/arch/arm/configs/multi_v7_defconfig @@ -414,3 +414,5 @@ CONFIG_DEBUG_FS=y CONFIG_MAGIC_SYSRQ=y CONFIG_LOCKUP_DETECTOR=y CONFIG_CRYPTO_DEV_TEGRA_AES=y +CONFIG_CPU_FREQ=y +CONFIG_GENERIC_CPUFREQ_CPU0=y -- 2.1.0

9 years, 8 months

[PATCH] ARM: configs: Remove REGULATOR_VIRTUAL_CONSUMER from defconfigs

by Mark Brown

The virtual consumer is a test device intended to be used while developing regulator drivers, it should never be used in production. Remove it from all defconfigs to avoid confusion among users. Signed-off-by: Mark Brown <broonie(a)kernel.org> --- arch/arm/configs/bcm_defconfig | 1 - arch/arm/configs/ezx_defconfig | 1 - arch/arm/configs/imote2_defconfig | 1 - arch/arm/configs/multi_v7_defconfig | 1 - arch/arm/configs/pxa3xx_defconfig | 1 - arch/arm/configs/sunxi_defconfig | 1 - arch/arm/configs/tegra_defconfig | 1 - 7 files changed, 7 deletions(-) diff --git a/arch/arm/configs/bcm_defconfig b/arch/arm/configs/bcm_defconfig index fbebcbce1e8c..bc614f44b33d 100644 --- a/arch/arm/configs/bcm_defconfig +++ b/arch/arm/configs/bcm_defconfig @@ -83,7 +83,6 @@ CONFIG_I2C_CHARDEV=y CONFIG_MFD_BCM590XX=y CONFIG_REGULATOR=y CONFIG_REGULATOR_FIXED_VOLTAGE=y -CONFIG_REGULATOR_VIRTUAL_CONSUMER=y CONFIG_REGULATOR_USERSPACE_CONSUMER=y CONFIG_REGULATOR_BCM590XX=y diff --git a/arch/arm/configs/ezx_defconfig b/arch/arm/configs/ezx_defconfig index d95763d5f0d8..eb440aae4283 100644 --- a/arch/arm/configs/ezx_defconfig +++ b/arch/arm/configs/ezx_defconfig @@ -230,7 +230,6 @@ CONFIG_POWER_SUPPLY=y CONFIG_EZX_PCAP=y CONFIG_REGULATOR=y CONFIG_REGULATOR_DEBUG=y -CONFIG_REGULATOR_VIRTUAL_CONSUMER=y CONFIG_REGULATOR_USERSPACE_CONSUMER=y CONFIG_REGULATOR_PCAP=y CONFIG_MEDIA_SUPPORT=y diff --git a/arch/arm/configs/imote2_defconfig b/arch/arm/configs/imote2_defconfig index fd996bb13022..182e54692664 100644 --- a/arch/arm/configs/imote2_defconfig +++ b/arch/arm/configs/imote2_defconfig @@ -208,7 +208,6 @@ CONFIG_POWER_SUPPLY=y CONFIG_PMIC_DA903X=y CONFIG_REGULATOR=y CONFIG_REGULATOR_DEBUG=y -CONFIG_REGULATOR_VIRTUAL_CONSUMER=y CONFIG_REGULATOR_USERSPACE_CONSUMER=y CONFIG_REGULATOR_DA903X=y CONFIG_MEDIA_SUPPORT=y diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig index 7cfa5fa5f7ac..05c0e7c789df 100644 --- a/arch/arm/configs/multi_v7_defconfig +++ b/arch/arm/configs/multi_v7_defconfig @@ -259,7 +259,6 @@ CONFIG_MFD_PALMAS=y CONFIG_MFD_TPS65090=y CONFIG_MFD_TPS6586X=y CONFIG_MFD_TPS65910=y -CONFIG_REGULATOR_VIRTUAL_CONSUMER=y CONFIG_REGULATOR_AB8500=y CONFIG_REGULATOR_AS3722=y CONFIG_REGULATOR_BCM590XX=y diff --git a/arch/arm/configs/pxa3xx_defconfig b/arch/arm/configs/pxa3xx_defconfig index 60e313834b3f..5f337d7ceb5b 100644 --- a/arch/arm/configs/pxa3xx_defconfig +++ b/arch/arm/configs/pxa3xx_defconfig @@ -77,7 +77,6 @@ CONFIG_BATTERY_DA9030=y CONFIG_PMIC_DA903X=y CONFIG_REGULATOR=y CONFIG_REGULATOR_DEBUG=y -CONFIG_REGULATOR_VIRTUAL_CONSUMER=y CONFIG_REGULATOR_DA903X=y CONFIG_FB=y CONFIG_FB_PXA=y diff --git a/arch/arm/configs/sunxi_defconfig b/arch/arm/configs/sunxi_defconfig index 6c037f956e36..c1a4ca4f6e6d 100644 --- a/arch/arm/configs/sunxi_defconfig +++ b/arch/arm/configs/sunxi_defconfig @@ -75,7 +75,6 @@ CONFIG_POWER_RESET_SUN6I=y CONFIG_WATCHDOG=y CONFIG_SUNXI_WATCHDOG=y CONFIG_MFD_AXP20X=y -CONFIG_REGULATOR_VIRTUAL_CONSUMER=y CONFIG_REGULATOR_GPIO=y CONFIG_USB=y CONFIG_USB_EHCI_HCD=y diff --git a/arch/arm/configs/tegra_defconfig b/arch/arm/configs/tegra_defconfig index 2b8be4850347..b448f58f621a 100644 --- a/arch/arm/configs/tegra_defconfig +++ b/arch/arm/configs/tegra_defconfig @@ -168,7 +168,6 @@ CONFIG_MFD_TPS6586X=y CONFIG_MFD_TPS65910=y CONFIG_REGULATOR=y CONFIG_REGULATOR_FIXED_VOLTAGE=y -CONFIG_REGULATOR_VIRTUAL_CONSUMER=y CONFIG_REGULATOR_AS3722=y CONFIG_REGULATOR_GPIO=y CONFIG_REGULATOR_MAX8907=y -- 2.1.0

9 years, 8 months

mainline boot: 83 boots: 82 pass, 0 fail, 1 offline (v3.17-rc2-246-g81bbadc)

by Kevin's boot bot

Status report database: http://status.armcloud.us/boot/all/job/mainline/kernel/v3.17-rc2-246-g81bba… Tree/Branch: mainline Git describe: v3.17-rc2-246-g81bbadc Offline boards (unable to connect to serial console) ==================================================== at91-sama5d3_xplained: OFFLINE: arm-sama5_defconfig Full Report =========== arm-shmobile_defconfig ---------------------- emev2-kzm9d 0 min 23.5 sec: PASS arm-davinci_all_defconfig ------------------------- legacy,dm365evm 0 min 17.2 sec: PASS da850-evm 0 min 15.3 sec: PASS arm-tegra_defconfig ------------------- tegra124-jetson-tk1 0 min 21.5 sec: PASS tegra30-beaver 0 min 17.3 sec: PASS arm64-defconfig --------------- legacy,qemu-aarch64 0 min 4.9 sec: PASS arm-multi_v7_defconfig+CONFIG_ARM_LPAE=y ---------------------------------------- tegra124-jetson-tk1 0 min 20.6 sec: PASS sun7i-a20-cubieboard2 0 min 11.8 sec: PASS exynos5420-arndale-octa 0 min 44.8 sec: PASS armada-xp-openblocks-ax3-4 0 min 24.1 sec: PASS exynos5410-smdk5410 0 min 21.2 sec: PASS exynos5800-peach-pi 0 min 29.9 sec: PASS omap5-uevm 0 min 53.5 sec: PASS (Warnings: 1) exynos5250-arndale 0 min 41.9 sec: PASS vexpress-v2p-ca15 0 min 4.8 sec: PASS arm-mvebu_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y ---------------------------------------------- armada-xp-openblocks-ax3-4 0 min 22.6 sec: PASS armada-370-mirabox 0 min 17.6 sec: PASS arm-versatile_defconfig ----------------------- legacy,versatilepb 0 min 2.8 sec: PASS arm-multi_v7_defconfig ---------------------- am335x-boneblack 0 min 23.6 sec: PASS sun7i-a20-cubieboard2 0 min 11.8 sec: PASS sun4i-a10-cubieboard 0 min 18.3 sec: PASS omap3-overo-tobi 0 min 24.9 sec: PASS am335x-bone 0 min 26.2 sec: PASS tegra124-jetson-tk1 0 min 20.7 sec: PASS armada-370-mirabox 0 min 18.8 sec: PASS exynos5410-smdk5410 0 min 21.2 sec: PASS omap4-panda 0 min 56.7 sec: PASS imx6q-wandboard 0 min 17.3 sec: PASS imx6dl-wandboard,wand-dual 0 min 18.3 sec: PASS vexpress-v2p-ca15 0 min 4.6 sec: PASS ste-snowball 0 min 24.6 sec: PASS tegra30-beaver 0 min 16.9 sec: PASS omap5-uevm 0 min 56.1 sec: PASS (Warnings: 1) qcom-apq8074-dragonboard 0 min 18.0 sec: PASS bcm28155-ap 0 min 27.4 sec: PASS exynos5800-peach-pi 0 min 30.0 sec: PASS imx6dl-wandboard,wand-solo 0 min 18.5 sec: PASS omap3-overo-storm-tobi 0 min 29.2 sec: PASS omap3-beagle-xm 0 min 53.7 sec: PASS exynos5420-arndale-octa 0 min 44.6 sec: PASS armada-xp-openblocks-ax3-4 0 min 24.1 sec: PASS vexpress-v2p-ca9 0 min 3.7 sec: PASS omap3-beagle 0 min 32.7 sec: PASS omap3-n900 0 min 17.6 sec: PASS omap4-panda-es 0 min 56.4 sec: PASS exynos5250-arndale 0 min 42.0 sec: PASS zynq-zc702 0 min 19.3 sec: PASS arm-vexpress_defconfig ---------------------- vexpress-v2p-ca9 0 min 4.9 sec: PASS vexpress-v2p-ca15 0 min 5.8 sec: PASS legacy,vexpress-v2p-ca9 0 min 4.7 sec: PASS arm-multi_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y ---------------------------------------------- armada-xp-openblocks-ax3-4 0 min 25.4 sec: PASS armada-370-mirabox 0 min 19.2 sec: PASS arm-qcom_defconfig ------------------ qcom-apq8074-dragonboard 0 min 16.9 sec: PASS arm-bcm_defconfig ----------------- bcm28155-ap 0 min 23.8 sec: PASS arm-exynos_defconfig -------------------- exynos5420-arndale-octa 0 min 29.2 sec: PASS (Warnings: 1) exynos5250-arndale 0 min 30.7 sec: PASS exynos5410-smdk5410 0 min 20.6 sec: PASS exynos5800-peach-pi 0 min 26.5 sec: PASS arm-imx_v6_v7_defconfig ----------------------- imx6dl-wandboard,wand-dual 0 min 18.0 sec: PASS imx6dl-wandboard,wand-solo 0 min 18.1 sec: PASS imx6q-wandboard 0 min 16.6 sec: PASS arm-u8500_defconfig ------------------- ste-snowball 0 min 24.4 sec: PASS arm-omap2plus_defconfig ----------------------- legacy,3730xm 0 min 54.9 sec: PASS am335x-boneblack 0 min 24.0 sec: PASS omap3-beagle-xm 1 min 2.5 sec: PASS legacy,3530beagle 0 min 34.7 sec: PASS (Warnings: 1) omap4-panda 1 min 6.7 sec: PASS omap3-overo-tobi 0 min 23.7 sec: PASS am335x-bone 0 min 30.7 sec: PASS omap3-overo-storm-tobi 0 min 23.4 sec: PASS omap5-uevm 1 min 9.9 sec: PASS (Warnings: 1) omap3-n900 0 min 18.0 sec: PASS legacy,n900 0 min 18.3 sec: PASS (Warnings: 2) omap4-panda-es 1 min 5.4 sec: PASS legacy,3730storm 0 min 24.5 sec: PASS omap3-beagle 0 min 34.8 sec: PASS legacy,3530overo 0 min 21.7 sec: PASS (Warnings: 1) arm-sunxi_defconfig ------------------- sun7i-a20-cubieboard2 0 min 11.5 sec: PASS sun4i-a10-cubieboard 0 min 13.6 sec: PASS arm-mvebu_v7_defconfig ---------------------- armada-xp-openblocks-ax3-4 0 min 22.8 sec: PASS armada-370-mirabox 0 min 20.2 sec: PASS arm-sama5_defconfig ------------------- sama5d35ek 0 min 16.6 sec: PASS at91-sama5d3_xplained 0 min 31.6 sec: OFFLINE

9 years, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel August 2014