linaro-kernel June 2013

linaro-kernel@lists.linaro.org

89 participants
86 discussions

by Viresh Kumar

Hi Rafael, The following changes since commit 9e895ace5d82df8929b16f58e9f515f6d54ab82d: Linux 3.10-rc7 (2013-06-22 09:47:31 -1000) are available in the git repository at: git://git.linaro.org/people/vireshk/linux.git cpufreq-next for you to fetch changes up to 166b9addd83aaf6eb22d9db7dc015f81913c9a0e: cpufreq: s3c2416: fix forgotten driver_data conversions (2013-06-24 11:22:33 +0530) ---------------------------------------------------------------- Heiko Stübner (1): cpufreq: s3c2416: fix forgotten driver_data conversions drivers/cpufreq/s3c2416-cpufreq.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

10 years, 10 months

[PATCH] arm64: Add support to pass earlyprintk argument via device tree

by Pranavkumar Sawargaonkar

This patch adds support for defining and passing earlyprintk related information i.e. device and address information via device tree by adding it inside "chosen" node. This will help user to just specify "earlyprintk" from bootargs without actually knowing the address and device to enable earlyprintk. Mechanism: One can just append earlyprintk=device-type,address (same as we pass through command line) in "/chosen" node to notify kernel which is the earlyprintk device and what is its address. Backward Compatibility: This patch also allows existing method of specifying earlyprintk parameter via bootargs. Existing method i.e. passing via bootargs will still have precedence over device tree i.e. if one specifies earlyprintk=device-type,address in bootargs then kernel will use information from bootargs instead of device tree. If user just specifies earlyprintk (without =...) then kernel will look for device tree earlyprintk parameter. Signed-off-by: Pranavkumar Sawargaonkar <pranavkumar(a)linaro.org> Signed-off-by: Anup Patel <anup.patel(a)linaro.org> --- arch/arm64/kernel/early_printk.c | 7 +++++++ arch/arm64/kernel/setup.c | 21 ++++++++++++++++++++- 2 files changed, 27 insertions(+), 1 deletion(-) diff --git a/arch/arm64/kernel/early_printk.c b/arch/arm64/kernel/early_printk.c index fbb6e18..4e6f845 100644 --- a/arch/arm64/kernel/early_printk.c +++ b/arch/arm64/kernel/early_printk.c @@ -29,6 +29,8 @@ static void __iomem *early_base; static void (*printch)(char ch); +extern char *earlyprintk_dt_args; + /* * PL011 single character TX. */ @@ -116,6 +118,11 @@ static int __init setup_early_printk(char *buf) phys_addr_t paddr = 0; if (!buf) { + /* Try to check if Device Tree has this argument or not ? */ + buf = earlyprintk_dt_args; + } + + if (!buf) { pr_warning("No earlyprintk arguments passed.\n"); return 0; } diff --git a/arch/arm64/kernel/setup.c b/arch/arm64/kernel/setup.c index 6a9a532..fb2d56f 100644 --- a/arch/arm64/kernel/setup.c +++ b/arch/arm64/kernel/setup.c @@ -60,6 +60,8 @@ EXPORT_SYMBOL(processor_id); unsigned int elf_hwcap __read_mostly; EXPORT_SYMBOL_GPL(elf_hwcap); +char *earlyprintk_dt_args; + static const char *cpu_name; static const char *machine_name; phys_addr_t __fdt_pointer __initdata; @@ -122,6 +124,23 @@ static void __init setup_processor(void) elf_hwcap = 0; } +int __init early_init_dt_scan_chosen_arm64(unsigned long node, + const char *uname, + int depth, void *data) +{ + char *prop; + + /* Check if this is chosen node */ + if (early_init_dt_scan_chosen(node, uname, depth, data) == 0) + return 0; + + prop = of_get_flat_dt_prop(node, "earlyprintk", NULL); + if (prop) + earlyprintk_dt_args = prop; + + return 1; +} + static void __init setup_machine_fdt(phys_addr_t dt_phys) { struct boot_param_header *devtree; @@ -165,7 +184,7 @@ static void __init setup_machine_fdt(phys_addr_t dt_phys) pr_info("Machine: %s\n", machine_name); /* Retrieve various information from the /chosen node */ - of_scan_flat_dt(early_init_dt_scan_chosen, boot_command_line); + of_scan_flat_dt(early_init_dt_scan_chosen_arm64, boot_command_line); /* Initialize {size,address}-cells info */ of_scan_flat_dt(early_init_dt_scan_root, NULL); /* Setup memory, calling early_init_dt_add_memory_arch */ -- 1.7.9.5

10 years, 10 months

[RFC patch 0/2] ARM: at91: cpuidle: move driver to drivers/cpuidle

by Daniel Lezcano

The number of cpuidle drivers is increasing more and more. Today we have in total 24 drivers. A lot of the code is duplicated, at least for the initialization. A work of consolidation has been done during this year: * a lot of code cleanup in all the drivers * time keeping is now part of the framework * timer broadcast is now part of the framework * a WFI state function for ARM is defined and used in the drivers * an init function has been proposed to factor out the initialization across the drivers (patchset pending) What has been observed is a lot of code duplicationis, modification made in the framework takes awhile before reaching the driver which uses an old API, duplicate routine and bugs, etc ... It appears the drivers are belonging to different trees, the cpuidle framework is under linux-pm, the drivers are per SoC tree. The communication is made difficult because of the different mailing lists where the cpuidle are submitted. After this work, it is time to prevent all these problems to occur again. I propose to move the cpuidle drivers to the drivers/cpuidle directory, hence having one single submission path for cpuidle in order to have the cpuidle framework and the different drivers synced. This series move the AT91 cpuidle driver under drivers/cpuidle. That does not change the rule to have the patches acked-by the author of the driver. Note the calxeda and kirkwood drivers are now in drivers/cpuidle. Daniel Lezcano (2): ARM: at91: cpuidle: encapsulate the standby code ARM: at91: cpuidle: move the driver to drivers/cpuidle directory arch/arm/mach-at91/Makefile | 1 - arch/arm/mach-at91/cpuidle.c | 66 ------------------------------------------ arch/arm/mach-at91/pm.c | 8 ++++- drivers/cpuidle/Makefile | 1 + drivers/cpuidle/at91.c | 55 +++++++++++++++++++++++++++++++++++ 5 files changed, 63 insertions(+), 68 deletions(-) delete mode 100644 arch/arm/mach-at91/cpuidle.c create mode 100644 drivers/cpuidle/at91.c -- 1.7.9.5

10 years, 10 months

[PATCH] tick: fix tick_broadcast_pending_mask not cleared

by Daniel Lezcano

The recent modification in the cpuidle framework consolidated the timer broadcast code across the different drivers by setting a new flag in the idle state. It tells the cpuidle core code to enter/exit to the broadcast mode for the cpu when entering a deep idle state. The broadcast timer enter/exit is no longer handled by the back-end driver. This change made the local interrupt to be enabled *before* calling CLOCK_EVENT_NOTIFY_EXIT. bad or not (see below) ? On a tegra114, a four cores system, when the flag has been introduced in the driver, the following warning appeared: [ 25.629559] WARNING: CPU: 2 PID: 0 at kernel/time/tick-broadcast.c:578 tick_broadcast_oneshot_control +0x1a4/0x1d0() [ 25.629565] Modules linked in: [ 25.629574] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 3.10.0-rc3-next-20130529+ #15 [ 25.629601] [<c00148f4>] (unwind_backtrace+0x0/0xf8) from [<c0011040>] (show_stack+0x10/0x14) [ 25.629616] [<c0011040>] (show_stack+0x10/0x14) from [<c0504248>] (dump_stack+0x80/0xc4) [ 25.629633] [<c0504248>] (dump_stack+0x80/0xc4) from [<c00231ac>] (warn_slowpath_common+0x64/0x88) [ 25.629646] [<c00231ac>] (warn_slowpath_common+0x64/0x88) from [<c00231ec>] (warn_slowpath_null+0x1c/0x24) [ 25.629657] [<c00231ec>] (warn_slowpath_null+0x1c/0x24) from [<c00667f8>] (tick_broadcast_oneshot_control+0x1a4/0x1d0) [ 25.629670] [<c00667f8>] (tick_broadcast_oneshot_control+0x1a4/0x1d0) from [<c0065cd0>] (tick_notify+0x240/0x40c) [ 25.629685] [<c0065cd0>] (tick_notify+0x240/0x40c) from [<c0044724>] (notifier_call_chain+0x44/0x84) [ 25.629699] [<c0044724>] (notifier_call_chain+0x44/0x84) from [<c0044828>] (raw_notifier_call_chain+0x18/0x20) [ 25.629712] [<c0044828>] (raw_notifier_call_chain+0x18/0x20) from [<c00650cc>] (clockevents_notify+0x28/0x170) [ 25.629726] [<c00650cc>] (clockevents_notify+0x28/0x170) from [<c033f1f0>] (cpuidle_idle_call+0x11c/0x168) [ 25.629739] [<c033f1f0>] (cpuidle_idle_call+0x11c/0x168) from [<c000ea94>] (arch_cpu_idle+0x8/0x38) [ 25.629755] [<c000ea94>] (arch_cpu_idle+0x8/0x38) from [<c005ea80>] (cpu_startup_entry+0x60/0x134) [ 25.629767] [<c005ea80>] (cpu_startup_entry+0x60/0x134) from [<804fe9a4>] (0x804fe9a4) [ 25.629772] ---[ end trace 5484e77e2531bccc ]--- I don't have the hardware, so I wasn't able to reproduce the warning but after looking a while in the code, I deduced the following: 1. the CPU2 enters a deep idle state and sets the broadcast timer 2. the timer expires, the tick_handle_oneshot_broadcast function is called, setting the tick_broadcast_pending_mask and waking up the idle cpu CPU2 3. the CPU2 exits idle and invokes tick_broadcast_oneshot_control with CLOCK_EVENT_NOTIFY_EXIT with the following code: [...] if (dev->next_event.tv64 == KTIME_MAX) goto out; if (cpumask_test_and_clear_cpu(cpu, tick_broadcast_pending_mask)) goto out; [...] 4. if there is no next event planned for CPU2, we fulfil the first condition and we jump to the 'out' section without clearing the tick_broadcast_pending_mask 5. CPU2 goes to deep idle again and calls tick_broadcast_oneshot_control with CLOCK_NOTIFY_EVENT_ENTER but with the tick_broadcast_pending_mask set for CPU2, leading to the WARNING. Above, it is mentionned the change moved the CLOCK_EVENT_NOTIFY_EXIT after the local interrupt were enabled. If it is before, this warning does not occur. My hypothesis is the code path described before does not happen because when a broadcast timer expires, dev->next_event.tv64 is always different from KTIME_MAX because the timer handler did not set the value yet (local interrupt are still disabled). I don't see anywhere in the code, a clockevents_notify(ENTER/EXIT) block must be done with the local interrupt disabled in between, furthermore the function uses 'raw_spin_lock_irqsave' which make me think, we don't care about that. Invert the conditions and make the tick broadcast code immune from the local interrupts context. Signed-off-by: Daniel Lezcano <daniel.lezcano(a)linaro.org> Reported-by: Joseph Lo <josephl(a)nvidia.com> --- kernel/time/tick-broadcast.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c index d067c01..58d88e8 100644 --- a/kernel/time/tick-broadcast.c +++ b/kernel/time/tick-broadcast.c @@ -610,8 +610,6 @@ void tick_broadcast_oneshot_control(unsigned long reason) } else { if (cpumask_test_and_clear_cpu(cpu, tick_broadcast_oneshot_mask)) { clockevents_set_mode(dev, CLOCK_EVT_MODE_ONESHOT); - if (dev->next_event.tv64 == KTIME_MAX) - goto out; /* * The cpu which was handling the broadcast * timer marked this cpu in the broadcast @@ -625,6 +623,8 @@ void tick_broadcast_oneshot_control(unsigned long reason) tick_broadcast_pending_mask)) goto out; + if (dev->next_event.tv64 == KTIME_MAX) + goto out; /* * If the pending bit is not set, then we are * either the CPU handling the broadcast -- 1.7.9.5

10 years, 10 months

[PATCH] arm: l2x0: add support for prefetch and pwr control register configuration

by Chander Kashyap

This patch adds support to configure prefetch and pwr control registers of pl310 cache controllor. Signed-off-by: Chander Kashyap <chander.kashyap(a)linaro.org> --- Documentation/devicetree/bindings/arm/l2cc.txt | 6 ++++ arch/arm/include/asm/hardware/cache-l2x0.h | 23 +++++++++++++ arch/arm/mm/cache-l2x0.c | 44 ++++++++++++++++++++++++ 3 files changed, 73 insertions(+) diff --git a/Documentation/devicetree/bindings/arm/l2cc.txt b/Documentation/devicetree/bindings/arm/l2cc.txt index cbef09b..66876b6 100644 --- a/Documentation/devicetree/bindings/arm/l2cc.txt +++ b/Documentation/devicetree/bindings/arm/l2cc.txt @@ -34,6 +34,12 @@ Optional properties: - arm,filter-ranges : <start length> Starting address and length of window to filter. Addresses in the filter window are directed to the M1 port. Other addresses will go to the M0 port. +- arm,prefetch-control : Prefetch related configurations. Specifies 8 cells of + prefetch-offset, not-same-ID-on-exclusive-sequence-en, incr-double-Linefill-en, + prefetch-drop-en, data-prefetch-en, instruction-prefetch-en and + double-linefill-en. +- arm,pwr-control : Operting mode clock and power mode selection. Specifies two + cells of standby-mode-en and dynamic_clk_gating_en. - interrupts : 1 combined interrupt. - cache-id-part: cache id part number to be used if it is not present on hardware diff --git a/arch/arm/include/asm/hardware/cache-l2x0.h b/arch/arm/include/asm/hardware/cache-l2x0.h index 3b2c40b..188f4da 100644 --- a/arch/arm/include/asm/hardware/cache-l2x0.h +++ b/arch/arm/include/asm/hardware/cache-l2x0.h @@ -106,6 +106,29 @@ #define L2X0_WAY_SIZE_SHIFT 3 +#define L2X0_PREFETCH_CTRL_OFFSET_SHIFT 0 +#define L2X0_PREFETCH_CTRL_NOT_SAME_ID_SHIFT 21 +#define L2X0_PREFETCH_CTRL_INC_DOUBLE_LINEFILL_SHIFT 23 +#define L2X0_PREFETCH_CTRL_PREFETCH_DROP_SHIFT 24 +#define L2X0_PREFETCH_CTRL_DOUBLE_LINEFILL_WR_SHIFT 27 +#define L2X0_PREFETCH_CTRL_DATA_PREFETCH_EN_SHIFT 28 +#define L2X0_PREFETCH_CTRL_INSTR_PREFETCH_EN_SHIFT 29 +#define L2X0_PREFETCH_CTRL_DOUBLE_LINEFILL_EN_SHIFT 30 + +#define PREFETCH_R2P0_MASK (~(1 << L2X0_PREFETCH_CTRL_OFFSET_SHIFT)) +#define PREFETCH_R3P0_MASK \ + (~((1 << L2X0_PREFETCH_CTRL_NOT_SAME_ID_SHIFT) | \ + (1 << L2X0_PREFETCH_CTRL_INC_DOUBLE_LINEFILL_SHIFT) | \ + (1 << L2X0_PREFETCH_CTRL_PREFETCH_DROP_SHIFT) | \ + (1 << L2X0_PREFETCH_CTRL_DATA_PREFETCH_EN_SHIFT) | \ + (1 << L2X0_PREFETCH_CTRL_INSTR_PREFETCH_EN_SHIFT) | \ + (1 << L2X0_PREFETCH_CTRL_DOUBLE_LINEFILL_EN_SHIFT))) +#define PREFETCH_R3P1_MASK \ + (~(1 << L2X0_PREFETCH_CTRL_DOUBLE_LINEFILL_WR_SHIFT)) + +#define L2X0_PWR_CTRL_STANDBY_MODE_EN_SHIFT 0 +#define L2X0_PWR_CTRL_DYNAMIC_CLK_GATE_EN_SHIFT 1 + #ifndef __ASSEMBLY__ extern void __init l2x0_init(void __iomem *base, u32 aux_val, u32 aux_mask); #if defined(CONFIG_CACHE_L2X0) && defined(CONFIG_OF) diff --git a/arch/arm/mm/cache-l2x0.c b/arch/arm/mm/cache-l2x0.c index c465fac..490e182 100644 --- a/arch/arm/mm/cache-l2x0.c +++ b/arch/arm/mm/cache-l2x0.c @@ -563,6 +563,11 @@ static void __init pl310_of_setup(const struct device_node *np, u32 data[3] = { 0, 0, 0 }; u32 tag[3] = { 0, 0, 0 }; u32 filter[2] = { 0, 0 }; + u32 prefetch[8] = { 0, 0, 0, 0, 0, 0, 0, 0 }; + u32 prefetch_val; + u32 pwr[2] = { 0, 0 }; + u32 l2x0_revision = readl_relaxed(l2x0_base + L2X0_CACHE_ID) & + L2X0_CACHE_ID_RTL_MASK; of_property_read_u32_array(np, "arm,tag-latency", tag, ARRAY_SIZE(tag)); if (tag[0] && tag[1] && tag[2]) @@ -589,6 +594,45 @@ static void __init pl310_of_setup(const struct device_node *np, writel_relaxed((filter[0] & ~(SZ_1M - 1)) | L2X0_ADDR_FILTER_EN, l2x0_base + L2X0_ADDR_FILTER_START); } + + if (l2x0_revision >= L2X0_CACHE_ID_RTL_R2P0) { + of_property_read_u32_array(np, "arm,prefetch-control", + prefetch, ARRAY_SIZE(prefetch)); + prefetch_val = readl_relaxed(l2x0_base + L2X0_PREFETCH_CTRL); + prefetch_val &= PREFETCH_R2P0_MASK; + prefetch_val |= prefetch[0] << L2X0_PREFETCH_CTRL_OFFSET_SHIFT; + if (l2x0_revision >= L2X0_CACHE_ID_RTL_R3P0) { + prefetch_val &= PREFETCH_R3P0_MASK; + prefetch_val |= + ((prefetch[1]) << + L2X0_PREFETCH_CTRL_NOT_SAME_ID_SHIFT) | + ((prefetch[2]) << + L2X0_PREFETCH_CTRL_INC_DOUBLE_LINEFILL_SHIFT) | + ((prefetch[3]) << + L2X0_PREFETCH_CTRL_PREFETCH_DROP_SHIFT) | + ((prefetch[5]) << + L2X0_PREFETCH_CTRL_DATA_PREFETCH_EN_SHIFT) | + ((prefetch[6]) << + L2X0_PREFETCH_CTRL_INSTR_PREFETCH_EN_SHIFT) | + ((prefetch[7]) << + L2X0_PREFETCH_CTRL_DOUBLE_LINEFILL_EN_SHIFT); + if (l2x0_revision >= L2X0_CACHE_ID_RTL_R3P1) { + prefetch_val &= PREFETCH_R3P1_MASK; + prefetch_val |= + ((prefetch[4]) << + L2X0_PREFETCH_CTRL_DOUBLE_LINEFILL_WR_SHIFT); + } + writel_relaxed(prefetch_val, + l2x0_base + L2X0_PREFETCH_CTRL); + + of_property_read_u32_array(np, "arm,pwr-control", + pwr, ARRAY_SIZE(pwr)); + writel_relaxed( + ((pwr[0]) << L2X0_PWR_CTRL_STANDBY_MODE_EN_SHIFT) | + ((pwr[1]) << L2X0_PWR_CTRL_DYNAMIC_CLK_GATE_EN_SHIFT), + l2x0_base + L2X0_POWER_CTRL); + } + } } static void __init pl310_save(void) -- 1.7.9.5

10 years, 10 months

[PATCH V4 00/11] USB: OHCI:Properly handle ohci_suspend()routine in bus glue

by Manjunath Goudar

Suspend scenario in case of ohci bus glue was not properly handled as it was not suspending generic part of ohci controller. Calling explicitly the ohci_suspend()routine will ensure proper handling of suspend scenario. V2: -Incase ohci_suspend() fails, return right away without executing further. V3: -New patch 1/11 added, for generic ohci-hcd suspend code. V4: -Properly aligned "do_wakeup" and "ret" variables. Manjunath Goudar (11): USB: OHCI: Properly handle OHCI controller suspend USB: OHCI: Properly handle ohci-at91 suspend USB: OHCI: Properly handle ohci-s3c2410 suspend USB: OHCI: Properly handle ohci-da8xx suspend USB: OHCI: Properly handle ohci-ep93xx suspend USB: OHCI: Properly handle ohci-exynos suspend USB: OHCI: Properly handle ohci-omap suspend USB: OHCI: Properly handle ohci-platform suspend USB: OHCI: Properly handle ohci-pxa27x suspend USB: OHCI: Properly handle ohci-sm501 suspend USB: OHCI: Properly handle ohci-spear suspend drivers/usb/host/ohci-at91.c | 10 ++++++++-- drivers/usb/host/ohci-da8xx.c | 15 +++++++++++---- drivers/usb/host/ohci-ep93xx.c | 9 ++++++++- drivers/usb/host/ohci-exynos.c | 20 +++++--------------- drivers/usb/host/ohci-hcd.c | 9 ++++++++- drivers/usb/host/ohci-omap.c | 13 ++++++++++--- drivers/usb/host/ohci-platform.c | 9 ++++++++- drivers/usb/host/ohci-pxa27x.c | 8 +++++++- drivers/usb/host/ohci-s3c2410.c | 19 ++++--------------- drivers/usb/host/ohci-sm501.c | 11 +++++++++-- drivers/usb/host/ohci-spear.c | 12 +++++++++--- 11 files changed, 87 insertions(+), 48 deletions(-) -- 1.7.9.5

10 years, 10 months

[PATCH 0/7] KVM: arm-vgic: Implement save/restore of VGIC state

by Christoffer Dall

This patch series adds support for user space save/restore of the VGIC state. Instead of expanding the ONE_REG interface, which works on VCPUs, we first introduce support for the new KVM device control API and the VGIC. Now, instead of calling KVM_CREATE_IRQCHIP, user space can call KVM_CREATE_DEVICE and perform operations on the device fd, such as KVM_SET_DEVICE_ATTR to set a device attribute. We leverage the KVM_{SET/GET}_DEVICE_ATTR API to export the state of the VGIC to user space. Instead of coming up with our own custom format for exporting the VGIC state, we simply export all the state visible to an emulated guest, which must contain the full GIC state to provide save/restore of the GIC state for power management purposes. This further provides the benefit of being able to re-use the MMIO emulation code for the distributor for save/restore. However, the need to save/restore cpu-specific state demands that user space can save/restore state accessible through the CPU interface, and we therefore add an emulation interface for the CPU-specific interface. This is considered a first attempt, and I am not married to the device control API. If there are good technical arguments to take another approach, I am of course willing to discuss this. However, my attempts with the ONE_REG interface did not look very nice. [ WARINING: The patch set core functionality is completely untested; the basic KVM system has been briefly tested on TC2 and it doesn't seem like I've broken existing functionality. ] I wanted to get this out early to get feedback on the overall API and idea, and I'm writing some user QEMU for the user space side to test the new functionality meanwhile. Patches are against kvm-arm-next and also available here: git://git.linaro.org/people/cdall/linux-kvm-arm.git vgic-migrate Christoffer Dall (7): KVM: arm-vgic: Support KVM_CREATE_DEVICE for VGIC KVM: arm-vgic: Set base addr through device API irqchip: arm-gic: Define additional MMIO offsets and masks KVM: arm-vgic: Make vgic mmio functions more generic KVM: arm-vgic: Add vgic reg access from dev attr KVM: arm-vgic: Add GICD_SPENDSGIR and GICD_CPENDSGIR handlers KVM: arm-vgic: Support CPU interface reg access Documentation/virtual/kvm/api.txt | 5 +- Documentation/virtual/kvm/devices/arm-vgic.txt | 52 +++ arch/arm/include/uapi/asm/kvm.h | 8 + arch/arm/kvm/arm.c | 3 +- include/kvm/arm_vgic.h | 2 +- include/linux/irqchip/arm-gic.h | 14 + include/linux/kvm_host.h | 1 + include/uapi/linux/kvm.h | 1 + virt/kvm/arm/vgic.c | 452 +++++++++++++++++++++++- virt/kvm/kvm_main.c | 4 + 10 files changed, 522 insertions(+), 20 deletions(-) create mode 100644 Documentation/virtual/kvm/devices/arm-vgic.txt -- 1.7.9.5

10 years, 10 months

[PATCH V3 00/11] USB: OHCI:Properly handle ohci_suspend()routine in bus glue

by Manjunath Goudar

Suspend scenario in case of ohci bus glue was not properly handled as it was not suspending generic part of ohci controller. Calling explicitly the ohci_suspend()routine will ensure proper handling of suspend scenario. V2: -Incase ohci_suspend() fails, return right away without executing further. V3: -New patch 1/11 added, for generic ohci-hcd suspend code. Manjunath Goudar (11): USB: OHCI: Properly handle OHCI controller suspend USB: OHCI: Properly handle ohci-at91 suspend USB: OHCI: Properly handle ohci-s3c2410 suspend USB: OHCI: Properly handle ohci-da8xx suspend USB: OHCI: Properly handle ohci-ep93xx suspend USB: OHCI: Properly handle ohci-exynos suspend USB: OHCI: Properly handle ohci-omap suspend USB: OHCI: Properly handle ohci-platform suspend USB: OHCI: Properly handle ohci-pxa27x suspend USB: OHCI: Properly handle ohci-sm501 suspend USB: OHCI: Properly handle ohci-spear suspend drivers/usb/host/ohci-at91.c | 10 ++++++++-- drivers/usb/host/ohci-da8xx.c | 17 ++++++++++++----- drivers/usb/host/ohci-ep93xx.c | 10 +++++++++- drivers/usb/host/ohci-exynos.c | 24 +++++++----------------- drivers/usb/host/ohci-hcd.c | 9 ++++++++- drivers/usb/host/ohci-omap.c | 13 ++++++++++--- drivers/usb/host/ohci-platform.c | 9 ++++++++- drivers/usb/host/ohci-pxa27x.c | 8 +++++++- drivers/usb/host/ohci-s3c2410.c | 19 ++++--------------- drivers/usb/host/ohci-sm501.c | 11 +++++++++-- drivers/usb/host/ohci-spear.c | 12 +++++++++--- 11 files changed, 91 insertions(+), 51 deletions(-) -- 1.7.9.5

10 years, 10 months

[GIT PULL] CPUFreq Kconfig Fixes: Select CPU_FREQ_TABLE

by Viresh Kumar

Hi Rafael, The following changes since commit 7d132055814ef17a6c7b69f342244c410a5e000f: Linux 3.10-rc6 (2013-06-15 11:51:07 -1000) are available in the git repository at: git://git.linaro.org/people/vireshk/linux.git cpufreq-kconfig-fixes for you to fetch changes up to dbcc9f845efc604564f34a5fa62f939c2bebfff6: cpufreq: X86_AMD_FREQ_SENSITIVITY: select CPU_FREQ_TABLE (2013-06-18 13:53:11 +0530) ---------------------------------------------------------------- Viresh Kumar (11): cpufreq: blackfin: enable driver for CONFIG_BFIN_CPU_FREQ cpufreq: cris: select CPU_FREQ_TABLE cpufreq: davinci: select CPU_FREQ_TABLE cpufreq: exynos: select CPU_FREQ_TABLE cpufreq: highbank: remove select CPU_FREQ_TABLE cpufreq: imx: select CPU_FREQ_TABLE cpufreq: powerpc: CBE_RAS: select CPU_FREQ_TABLE cpufreq: pxa: select CPU_FREQ_TABLE cpufreq: S3C2416/S3C64XX: select CPU_FREQ_TABLE cpufreq: tegra: create CONFIG_ARM_TEGRA_CPUFREQ cpufreq: X86_AMD_FREQ_SENSITIVITY: select CPU_FREQ_TABLE arch/arm/mach-davinci/Kconfig | 1 + arch/arm/mach-pxa/Kconfig | 3 +++ arch/arm/mach-tegra/Kconfig | 3 --- arch/cris/Kconfig | 2 ++ drivers/cpufreq/Kconfig.arm | 14 +++++++++++++- drivers/cpufreq/Kconfig.powerpc | 1 + drivers/cpufreq/Kconfig.x86 | 1 + drivers/cpufreq/Makefile | 4 ++-- 8 files changed, 23 insertions(+), 6 deletions(-) -- viresh

10 years, 10 months

[PATCH 1/2] sched/nohz: add sysctl control over sched_tick_max_deferment

by Kevin Hilman

Allow sysctl override of sched_tick_max_deferment in order to ease finding/fixing the remaining issues with full nohz. The value to be written is in jiffies, and -1 means the max deferment is disabled (scheduler_tick_max_deferment() returns KTIME_MAX.) Cc: Frederic Weisbecker <fweisbec(a)gmail.com> Signed-off-by: Kevin Hilman <khilman(a)linaro.org> --- include/linux/sched/sysctl.h | 3 +++ kernel/sched/core.c | 6 +++++- kernel/sched/debug.c | 1 + kernel/sysctl.c | 9 +++++++++ 4 files changed, 18 insertions(+), 1 deletion(-) diff --git a/include/linux/sched/sysctl.h b/include/linux/sched/sysctl.h index bf8086b..2ad07bb 100644 --- a/include/linux/sched/sysctl.h +++ b/include/linux/sched/sysctl.h @@ -57,6 +57,9 @@ extern unsigned int sysctl_sched_nr_migrate; extern unsigned int sysctl_sched_time_avg; extern unsigned int sysctl_timer_migration; extern unsigned int sysctl_sched_shares_window; +#ifdef CONFIG_NO_HZ_FULL +extern unsigned int sysctl_sched_tick_max_deferment; +#endif int sched_proc_update_handler(struct ctl_table *table, int write, void __user *buffer, size_t *length, diff --git a/kernel/sched/core.c b/kernel/sched/core.c index e1a27f9..b5d3f99 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -2751,12 +2751,16 @@ void scheduler_tick(void) * balancing, etc... continue to move forward, even * with a very low granularity. */ +unsigned int sysctl_sched_tick_max_deferment = HZ; u64 scheduler_tick_max_deferment(void) { struct rq *rq = this_rq(); unsigned long next, now = ACCESS_ONCE(jiffies); - next = rq->last_sched_tick + HZ; + if (sysctl_sched_tick_max_deferment == -1) + return KTIME_MAX; + + next = rq->last_sched_tick + sysctl_sched_tick_max_deferment; if (time_before_eq(next, now)) return 0; diff --git a/kernel/sched/debug.c b/kernel/sched/debug.c index 75024a6..f445ab9 100644 --- a/kernel/sched/debug.c +++ b/kernel/sched/debug.c @@ -374,6 +374,7 @@ static void sched_debug_header(struct seq_file *m) PN(sysctl_sched_wakeup_granularity); P(sysctl_sched_child_runs_first); P(sysctl_sched_features); + P(sysctl_sched_tick_max_deferment); #undef PN #undef P diff --git a/kernel/sysctl.c b/kernel/sysctl.c index 9edcf45..fb0b7d8 100644 --- a/kernel/sysctl.c +++ b/kernel/sysctl.c @@ -393,6 +393,15 @@ static struct ctl_table kern_table[] = { .proc_handler = proc_dointvec, }, #endif /* CONFIG_NUMA_BALANCING */ +#ifdef CONFIG_NO_HZ_FULL + { + .procname = "sched_tick_max_deferment", + .data = &sysctl_sched_tick_max_deferment, + .maxlen = sizeof(unsigned int), + .mode = 0644, + .proc_handler = proc_dointvec, + }, +#endif /* CONFIG_NO_HZ_FULL */ #endif /* CONFIG_SCHED_DEBUG */ { .procname = "sched_rt_period_us", -- 1.8.3

10 years, 10 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel June 2013