[PATCH v5 2/9] Input: goodix - use actual config length for each device type

Each of the Goodix devices supported by this driver has a fixed size for the configuration information registers. The size varies depending on the device and is specified in the datasheet. Use the proper configuration length as specified in the datasheet for each device model, so we do not read

Re: [PATCH v2 2/2] leds: leds-ipaq-micro: Fix coding style issues

Hi Muhammad, On 09/07/2015 04:13 PM, Muhammad Falak R Wani wrote: Spaces at the starting of a line are removed, indentation using tab, instead of space. Also, warnings related to line width of more than 80 characters is also taken care of. Two warnings have been left alone to aid better

Re: [PATCH v4 0/3] mtd: nand: jz4780: Add NAND and BCH drivers

On 06/09/2015 21:38, Ezequiel Garcia wrote: > On 27 Jul 02:50 PM, Alex Smith wrote: >> Hi, >> >> This series adds support for the BCH controller and NAND devices on >> the Ingenic JZ4780 SoC. >> >> Tested on the MIPS Creator Ci20 board. All dependencies are now in >> mainline so it should be

RE: [PATCH] powerpc32: memcpy: only use dcbz once cache is enabled

From: Christophe Leroy > Sent: 07 September 2015 15:25 ... > diff --git a/arch/powerpc/lib/copy_32.S b/arch/powerpc/lib/copy_32.S > index 2ef50c6..05b3096 100644 > --- a/arch/powerpc/lib/copy_32.S > +++ b/arch/powerpc/lib/copy_32.S > @@ -172,7 +172,16 @@ _GLOBAL(memcpy) > mtctr r0 >

Re: [PATCH 2/2] rcu: Fix up timeouts for forcing the quiescent state

On Fri 2015-09-04 16:49:46, Paul E. McKenney wrote: > On Fri, Sep 04, 2015 at 02:11:30PM +0200, Petr Mladek wrote: > > The deadline to force the quiescent state (jiffies_force_qs) is currently > > updated only when the previous timeout passed. But the timeout used for > > wait_event() is always

Re: [PATCH] ARM: fix bug which lowmem size is limited to 760MB

On Mon, 7 Sep 2015, Arnd Bergmann wrote: > Given how much more common 1GB hardware configurations are compared to 768MB > configuration, we could however think about adding a VMSPLIT_3G_OPT option > that x86 has (also VMSPLIT_2_75G on ARCH_TILE), to allow using the entire > 1GB of lowmem without

[PATCH v4 09/20] xen/biomerge: Don't allow biovec's to be merged when Linux is not using 4KB pages

On ARM all dma-capable devices on a same platform may not be protected by an IOMMU. The DMA requests have to use the BFN (i.e MFN on ARM) in order to use correctly the device. While the DOM0 memory is allocated in a 1:1 fashion (PFN == MFN), grant mapping will screw this contiguous mapping. When

[PATCH v4 00/20] xen/arm64: Add support for 64KB page in Linux

Hi all, ARM64 Linux is supporting both 4KB and 64KB page granularity. Although, Xen hypercall interface and PV protocol are always based on 4KB page granularity. Any attempt to boot a Linux guest with 64KB pages enabled will result to a guest crash. This series is a first attempt to allow those

[PATCH v4 07/20] block/xen-blkfront: Store a page rather a pfn in the grant structure

All the usage of the field pfn are done using the same idiom: pfn_to_page(grant->pfn) This will return always the same page. Store directly the page in the grant to clean up the code. Signed-off-by: Julien Grall Acked-by: Roger Pau Monné

Re: [PATCH 5/6] sched/fair: Get rid of scaling utilization by capacity_orig

On 04/09/15 00:51, Steve Muckle wrote: > Hi Morten, Dietmar, > > On 08/14/2015 09:23 AM, Morten Rasmussen wrote: > ... >> + * cfs_rq.avg.util_avg is the sum of running time of runnable tasks plus the >> + * recent utilization of currently non-runnable tasks on a CPU. It >> represents >> + * the

[PATCH v4 04/20] xen/grant: Introduce helpers to split a page into grant

Currently, a grant is always based on the Xen page granularity (i.e 4KB). When Linux is using a different page granularity, a single page will be split between multiple grants. The new helpers will be in charge of splitting the Linux page into grants and call a function given by the caller on

[PATCH v4 05/20] xen/grant: Add helper gnttab_page_grant_foreign_access_ref_one

Many PV drivers contain the idiom: pfn = page_to_gfn(...) /* Or similar */ gnttab_grant_foreign_access_ref Replace it by a new helper. Note that when Linux is using a different page granularity than Xen, the helper only gives access to the first 4KB grant. This is useful where drivers are

Re: [RFC PATCH 0/3] Implement IRQ stack on ARM64

On Sep 7, 2015, at 11:33 PM, James Morse wrote: > On 04/09/15 15:23, Jungseok Lee wrote: >> ARM64 kernel allocates 16KB kernel stack when creating a process. In case >> of low memory platforms with tough workloads on userland, this order-2 >> allocation request reaches to memory pressure and

[PATCH v4 0/4] cpufreq-dt: add suspend frequency support

Hi, This patch series adds suspend frequency support (using opp-v2 bindings and suspend-opp functionality) to cpufreq-dt driver and then adds suspend opp for Exynos4412 based boards. This patch series fixes suspend/resume support on Exynos4412 based Trats2 board and reboot hang on Exynos4412

Re: [PATCH 2/3] selftests: add membarrier syscall test

- On Sep 3, 2015, at 11:36 PM, Michael Ellerman m...@ellerman.id.au wrote: > On Thu, 2015-09-03 at 15:47 +, Mathieu Desnoyers wrote: >> - On Sep 3, 2015, at 5:33 AM, Michael Ellerman m...@ellerman.id.au wrote: >> >> > On Tue, 2015-09-01 at 11:32 -0700, Andy Lutomirski wrote: >> >> On

[PATCH v2 1/9] [picked] powerpc: allocate sys_membarrier system call number

Allow it to be used from SPU, since it should not have unwanted side-effects. [ Picked-by: Michael Ellerman ] Signed-off-by: Mathieu Desnoyers CC: Andrew Morton CC: linux-...@vger.kernel.org CC: Benjamin

[PATCH v3 2/2] leds: leds-ipaq-micro: Fix coding style issues

Spaces at the starting of a line are removed, indentation using tab, instead of space. Also, line width of more than 80 characters is also taken care of. Two warnings are left alone to aid better readability. Signed-off-by: Muhammad Falak R Wani ---

Re: [PATCH 1/2] ASoC: atmel-classd: add the Audio Class D Amplifier code

On Sun, Sep 06, 2015 at 05:44:21PM +0800, Wu, Songjun wrote: > On 9/3/2015 19:37, Mark Brown wrote: > >On Tue, Sep 01, 2015 at 01:41:40PM +0800, Songjun Wu wrote: > >>+static const char * const eqcfg_bass_text[] = { > >>+ "-12 dB", "-6 dB", "0 dB", "+6 dB", "+12 dB" > >>+}; > > > >>+static

Re: [PATCH v4 4/5] irqchip, gicv3-its: Add HW revision detection and configuration

Hi Robert, On 14/08/15 19:28, Robert Richter wrote: > From: Robert Richter > > Some GIC revisions require an individual configuration to esp. add > workarounds for HW bugs. This patch implements generic code to parse > the hw revision provided by an IIDR register value and

Re: [PATCH 2/2] ASoC: atmel-classd: DT binding for Class D audio amplifier driver

On Sun, Sep 06, 2015 at 05:44:30PM +0800, Wu, Songjun wrote: > On 9/3/2015 19:43, Mark Brown wrote: > >Why is this a separate DT node? It seems that this IP is entirely self > >contained so I'm not clear why we need a separate node for the card, the > >card is usually a separate node because it

[GIT PULL] regmap updates for v4.3

The following changes since commit 64291f7db5bd8150a74ad2036f1037e6a0428df2: Linux 4.2 (2015-08-30 11:34:09 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v4.3 for you to fetch changes up to

[PATCH v4 02/20] arm/xen: Drop pte_mfn and mfn_pte

They are not used in common code expect in one place in balloon.c which is only compiled when Linux is using PV MMU. It's not the case on ARM. Rather than worrying how to handle the 64KB case, drop them. Signed-off-by: Julien Grall Reviewed-by: Stefano Stabellini

[PATCH v4 08/20] block/xen-blkfront: split get_grant in 2

Prepare the code to support 64KB page granularity. The first implementation will use a full Linux page per indirect and persistent grant. When non-persistent grant is used, each page of a bio request may be split in multiple grant. Furthermore, the field page of the grant structure is only used

[PATCH v4 03/20] xen: Add Xen specific page definition

The Xen hypercall interface is always using 4K page granularity on ARM and x86 architecture. With the incoming support of 64K page granularity for ARM64 guest, it won't be possible to re-use the Linux page definition in Xen drivers. Introduce Xen page definition helpers based on the Linux page

[PATCH v4 01/20] net/xen-netback: xenvif_gop_frag_copy: move GSO check out of the loop

The skb doesn't change within the function. Therefore it's only necessary to check if we need GSO once at the beginning. Signed-off-by: Julien Grall Acked-by: Wei Liu --- Cc: Ian Campbell Cc: net...@vger.kernel.org

[PATCH v4 11/20] tty/hvc: xen: Use xen page definition

The console ring is always based on the page granularity of Xen. Signed-off-by: Julien Grall Reviewed-by: Stefano Stabellini --- Cc: Greg Kroah-Hartman Cc: Jiri Slaby Cc: David Vrabel

[PATCH v4 19/20] xen/privcmd: Add support for Linux 64KB page granularity

The hypercall interface (as well as the toolstack) is always using 4KB page granularity. When the toolstack is asking for mapping a series of guest PFN in a batch, it expects to have the page map contiguously in its virtual memory. When Linux is using 64KB page granularity, the privcmd driver

[PATCH v4 3/4] cpufreq-dt: add suspend frequency support

Add suspend frequency support and if needed set it to the frequency obtained from the suspend opp (can be defined using opp-v2 bindings and is optional). Cc: Viresh Kumar Cc: Thomas Abraham Cc: Javier Martinez Canillas Cc:

[PATCH v4 4/4] ARM: dts: add suspend opp to exynos4412

Mark 800MHz OPP as a suspend opp for Exynos4412 based boards so effectively cpufreq-dt driver behavior w.r.t. suspend frequency matches what the old exynos-cpufreq driver has been doing. This patch fixes suspend/resume support on Exynos4412 based Trats2 board and reboot hang on Exynos4412 based

Re: [PATCH] ARM: fix bug which lowmem size is limited to 760MB

On Monday 07 September 2015 11:34:36 Nicolas Pitre wrote: > > That shifts the risk to user space though. But if there is a regression > there, it will manifest itself on all systems and not only with some > particular hardware. I'd consider that a good thing, as it makes it easier to test

Re: [PATCH] arm64: kernel: Use a separate stack for irq interrupts.

On Sep 7, 2015, at 11:36 PM, James Morse wrote: Hi James, > Having to handle interrupts on top of an existing kernel stack means the > kernel stack must be large enough to accomodate both the maximum kernel > usage, and the maximum irq handler usage. Switching to a different stack > when

Re: [RFC PATCH 1/3] arm64: entry: Remove unnecessary calculation for S_SP in EL1h

On Sep 7, 2015, at 11:56 PM, Mark Rutland wrote: Hi Mark, > On Fri, Sep 04, 2015 at 03:23:05PM +0100, Jungseok Lee wrote: >> Under EL1h, S_SP data is not seen in kernel_exit. Thus, x21 calculation >> is not needed in kernel_entry. Currently, S_SP information is vaild only >> when sp_el0 is used.

[PATCH v1] usb: core: driver: Use kmalloc_array

Use kmalloc_array instead of kmalloc to allocate memory for an array. Also, remove the dev_warn for a memory leak, making the if check more sleek. Signed-off-by: Muhammad Falak R Wani --- On suggestion by Joe Perches Changes since v0 -remove

[PATCH v2 0/1] Corsair Vengeance K90 driver

I removed the k90_profile class completely. I cannot write a good enough ABI with what I know of the keyboard so I am leaving that part out of the kernel. If I change my mind in the future, it will be done in another patch. I also fixed a bug I had when unregistering the led device. Work was

Re: [PATCH] arm64: kernel: Use a separate stack for irq interrupts.

On 07/09/15 16:48, Jungseok Lee wrote: > On Sep 7, 2015, at 11:36 PM, James Morse wrote: > > Hi James, > >> Having to handle interrupts on top of an existing kernel stack means the >> kernel stack must be large enough to accomodate both the maximum kernel >> usage, and the maximum irq handler

Re: [PATCH] virtio-blk: use VIRTIO_BLK_F_WCE and VIRTIO_BLK_F_CONFIG_WCE in virtio1

On 22/08/2015 00:53, Paolo Bonzini wrote: > VIRTIO_BLK_F_CONFIG_WCE is important in order to achieve good performance > (up to 2x, though more realistically +30-40%) in latency-bound workloads. > However, it was removed by mistake together with VIRTIO_BLK_F_FLUSH. > > It will be restored in the

[RFC PATCH v2 7/9] arm64: allocate sys_membarrier system call number

arm64 sys_membarrier number is already wired for arm64 through asm-generic/unistd.h, but needs to be allocated separately for the 32-bit compability layer of arm64. [ Untested on this architecture. To try it out: fetch linux-next/akpm, apply this patch, build/run a membarrier-enabled kernel,

[RFC PATCH v2 8/9] ia64: allocate sys_membarrier system call number

[ Untested on this architecture. To try it out: fetch linux-next/akpm, apply this patch, build/run a membarrier-enabled kernel, and do make kselftest. ] Signed-off-by: Mathieu Desnoyers CC: Andrew Morton CC:

[RFC PATCH v2 9/9] s390/s390x: allocate sys_membarrier system call number

[ Untested on this architecture. To try it out: fetch linux-next/akpm, apply this patch, build/run a membarrier-enabled kernel, and do make kselftest. ] Signed-off-by: Mathieu Desnoyers CC: Andrew Morton CC:

[RFC PATCH v2 5/9] alpha: allocate sys_membarrier system call number

[ Untested on this architecture. To try it out: fetch linux-next/akpm, apply this patch, build/run a membarrier-enabled kernel, and do make kselftest. ] Signed-off-by: Mathieu Desnoyers CC: Andrew Morton CC:

[PATCH v2 3/9] sparc/sparc64: allocate sys_membarrier system call number

Signed-off-by: Mathieu Desnoyers Acked-by: "David S. Miller" CC: Andrew Morton CC: linux-...@vger.kernel.org CC: sparcli...@vger.kernel.org --- arch/sparc/include/uapi/asm/unistd.h | 3 ++-

[PATCH v2 4/9] parisc: allocate sys_membarrier system call number

Signed-off-by: Mathieu Desnoyers Tested-by: Helge Deller CC: Andrew Morton CC: linux-...@vger.kernel.org CC: "James E.J. Bottomley" CC: linux-par...@vger.kernel.org ---

Re: [PATCH] arm64: kernel: Use a separate stack for irq interrupts.

On Sep 8, 2015, at 1:06 AM, James Morse wrote: > On 07/09/15 16:48, Jungseok Lee wrote: >> On Sep 7, 2015, at 11:36 PM, James Morse wrote: >> >> Hi James, >> >>> Having to handle interrupts on top of an existing kernel stack means the >>> kernel stack must be large enough to accomodate both the

Re: [PATCH v4 5/5] irqchip, gicv3-its: Workaround for Cavium ThunderX errata 22375, 24313

On 14/08/15 19:28, Robert Richter wrote: > From: Robert Richter > > This implements two gicv3-its errata workarounds for ThunderX. Both > with small impact affecting only ITS table allocation. > > erratum 22375: only alloc 8MB table size > erratum 24313: ignore memory

Re: [RFC PATCH v1 2/4] irqchip: GICv3: set non-percpu irqs status with _IRQ_MOVE_PCNTXT

On 2015/9/7 22:56, Marc Zyngier wrote: > Hi Thomas, > > On 07/09/15 14:24, Thomas Gleixner wrote: >> On Mon, 7 Sep 2015, Marc Zyngier wrote: >>> On 06/09/15 06:56, Jiang Liu wrote: On 2015/9/6 12:23, Yang Yingliang wrote: > Use irq_settings_set_move_pcntxt() helper irqs status with >

Re: [PATCH v2 1/5] ACPI: add in a bad_madt_entry() function to eventually replace the macro

Hi Al, On 19/08/15 23:07, Al Stone wrote: I finally got a chance to try this series on Juno. Well it exposed a firmware bug in MADT table :) [..] acpi_tbl_entry_handler handler, @@ -245,6 +484,8 @@ acpi_parse_entries(char *id, unsigned long table_size,

[PATCH v4 06/20] block/xen-blkfront: Split blkif_queue_request in 2

Currently, blkif_queue_request has 2 distinct execution path: - Send a discard request - Send a read/write request The function is also allocating grants to use for generating the request. Although, this is only used for read/write request. Rather than having a function with 2 distinct

[PATCH v4 18/20] net/xen-netback: Make it running on 64KB page granularity

The PV network protocol is using 4KB page granularity. The goal of this patch is to allow a Linux using 64KB page granularity working as a network backend on a non-modified Xen. It's only necessary to adapt the ring size and break skb data in small chunk of 4KB. The rest of the code is relying on

[PATCH v4 17/20] net/xen-netfront: Make it running on 64KB page granularity

The PV network protocol is using 4KB page granularity. The goal of this patch is to allow a Linux using 64KB page granularity using network device on a non-modified Xen. It's only necessary to adapt the ring size and break skb data in small chunk of 4KB. The rest of the code is relying on the

[PATCH v4 15/20] block/xen-blkfront: Make it running on 64KB page granularity

The PV block protocol is using 4KB page granularity. The goal of this patch is to allow a Linux using 64KB page granularity using block device on a non-modified Xen. The block API is using segment which should at least be the size of a Linux page. Therefore, the driver will have to break the page

[PATCH v4 20/20] arm/xen: Add support for 64KB page granularity

The hypercall interface is always using 4KB page granularity. This is requiring to use xen page definition macro when we deal with hypercall. Note that pfn_to_gfn is working with a Xen pfn (i.e 4KB). We may want to rename pfn_gfn to make this explicit. We also allocate a 64KB page for the shared

[PATCH v4 16/20] block/xen-blkback: Make it running on 64KB page granularity

The PV block protocol is using 4KB page granularity. The goal of this patch is to allow a Linux using 64KB page granularity behaving as a block backend on a non-modified Xen. It's only necessary to adapt the ring size and the number of request per indirect frames. The rest of the code is relying

[PATCH v4 12/20] xen/balloon: Don't rely on the page granularity is the same for Xen and Linux

For ARM64 guests, Linux is able to support either 64K or 4K page granularity. Although, the hypercall interface is always based on 4K page granularity. With 64K page granularity, a single page will be spread over multiple Xen frame. To avoid splitting the page into 4K frame, take advantage of

[PATCH v4 13/20] xen/events: fifo: Make it running on 64KB granularity

Only use the first 4KB of the page to store the events channel info. It means that we will waste 60KB every time we allocate page for: * control block: a page is allocating per CPU * event array: a page is allocating everytime we need to expand it I think we can reduce the memory waste

[PATCH v4 10/20] xen/xenbus: Use Xen page definition

All the ring (xenstore, and PV rings) are always based on the page granularity of Xen. Signed-off-by: Julien Grall Reviewed-by: David Vrabel Reviewed-by: Stefano Stabellini --- Cc: Konrad Rzeszutek Wilk

[PATCH v4 14/20] xen/grant-table: Make it running on 64KB granularity

The Xen interface is using 4KB page granularity. This means that each grant is 4KB. The current implementation allocates a Linux page per grant. On Linux using 64KB page granularity, only the first 4KB of the page will be used. We could decrease the memory wasted by sharing the page with

[PATCH v4 2/4] cpufreq: allow cpufreq_generic_suspend() to work without suspend frequency

Some cpufreq drivers may set suspend frequency only for selected setups but still would like to use the generic suspend handler. Thus don't treat !policy->suspend_freq condition as an incorrect one. Cc: Viresh Kumar Cc: Thomas Abraham Cc: Javier

[PATCH v4 1/4] PM / OPP: add dev_pm_opp_get_suspend_opp() helper

Add dev_pm_opp_get_suspend_opp() helper to obtain suspend opp. Cc: Viresh Kumar Cc: Thomas Abraham Cc: Javier Martinez Canillas Cc: Krzysztof Kozlowski Cc: Marek Szyprowski

Re: [PATCH] ARM: fix bug which lowmem size is limited to 760MB

On Mon, 7 Sep 2015, Arnd Bergmann wrote: > On Monday 07 September 2015 11:34:36 Nicolas Pitre wrote: > > > > That shifts the risk to user space though. But if there is a regression > > there, it will manifest itself on all systems and not only with some > > particular hardware. > > I'd

[PATCH v4 RESEND] x86/asm/entry/32, selftests: Add 'test_syscall_vdso' test

This new test checks that all x86 registers are preserved across 32-bit syscalls. It tests syscalls through VDSO (if available) and through INT 0x80, normally and under ptrace. If kernel is a 64-bit one, high registers (r8..r15) are poisoned before the syscall is called and are checked

[PATCH v2 1/1] Add Corsair Vengeance K90 driver

This patch implements a HID driver for the Corsair Vengeance K90 keyboard. It fixes the behaviour of the keys using incorrect HID usage codes and exposes the macro playback mode and current profile to the user space through sysfs attributes. It also adds two LED class devices controlling the

Re: [PATCH 1/5] acpi: Add basic device probing infrastructure

[+M.Salter] On Fri, Sep 04, 2015 at 06:06:48PM +0100, Marc Zyngier wrote: > IRQ controllers and timers are the two types of device the kernel > requires before being able to use the device driver model. > > ACPI so far lacks a proper probing infrastructure similar to the one > we have with DT,

Re: [PATCH v4 0/3] mtd: nand: jz4780: Add NAND and BCH drivers

On 7 September 2015 at 11:54, Alex Smith wrote: > On 06/09/2015 21:38, Ezequiel Garcia wrote: >> On 27 Jul 02:50 PM, Alex Smith wrote: >>> Hi, >>> >>> This series adds support for the BCH controller and NAND devices on >>> the Ingenic JZ4780 SoC. >>> >>> Tested on the MIPS

[PATCH v2 2/9] mips: allocate sys_membarrier system call number

Signed-off-by: Mathieu Desnoyers Acked-by: Ralf Baechle CC: Andrew Morton CC: linux-...@vger.kernel.org CC: linux-m...@linux-mips.org --- arch/mips/include/uapi/asm/unistd.h | 15 +--

[RFC PATCH v2 6/9] arm: allocate sys_membarrier system call number

[ Untested on this architecture. To try it out: fetch linux-next/akpm, apply this patch, build/run a membarrier-enabled kernel, and do make kselftest. ] Signed-off-by: Mathieu Desnoyers CC: Andrew Morton CC:

[PATCH v2 0/9] Allocate sys_membarrier on main architectures

Following feedback from architecture maintainers, this is v2 of this patchset. Status: * Picked into maintainer's tree: - powerpc * Ready to be picked into maintainer's tree (acked/tested): - mips, sparc/sparc64, parisc, * Awaiting feedback/testing: - arm, arm64, ia64, s390/s390x Thanks,

Re: [PATCH 5/6] sched/fair: Get rid of scaling utilization by capacity_orig

On 7 September 2015 at 17:37, Dietmar Eggemann wrote: > On 04/09/15 00:51, Steve Muckle wrote: >> Hi Morten, Dietmar, >> >> On 08/14/2015 09:23 AM, Morten Rasmussen wrote: >> ... >>> + * cfs_rq.avg.util_avg is the sum of running time of runnable tasks plus >>> the >>> +

[PATCH] ARM: dts: omap3-igep: Move eth IRQ pinmux to IGEPv2 common dtsi

Only the IGEPv2 boards have a LAN9221i chip connected to the GPMC so the pinmux configuration for the GPIO connected to the IRQ line of the LAN chip should not be defined in the IGEP common dtsi but in the one common to the IGEPv2 boards. While there, use the OMAP3_CORE1_IOPAD() macro for the

Re: [PATCH v4 0/5] irqchip, gicv3: Updates and Cavium ThunderX errata workarounds

Hi Robert, On 14/08/15 19:28, Robert Richter wrote: > From: Robert Richter > > This patch series adds gicv3 updates and workarounds for HW errata in > Cavium's ThunderX GICV3. > > The first one is an unchanged resubmission of a patch from a gicv3 > series I sent a while

[PATCH v5 4/5] thermal: power_allocator: don't require tzp to be present for the thermal zone

Thermal zones created using thermal_zone_device_create() may not have tzp. As the governor gets its parameters from there, allocate it while the governor is bound to the thermal zone so that it can operate in it. In this case, tzp is freed when the thermal zone switches to another governor. Cc:

[PATCH v5 3/5] thermal: power_allocator: relax the requirement of two passive trip points

The power allocator governor currently requires that the thermal zone has at least two passive trip points. If there aren't, the governor refuses to bind to the thermal zone. This commit relaxes that requirement. Now the governor will bind to all thermal zones regardless of how many trip points

[PATCH v5 1/5] thermal: Add a function to get the minimum power

The thermal core already has a function to get the maximum power of a cooling device: power_actor_get_max_power(). Add a function to get the minimum power of a cooling device. Cc: Zhang Rui Cc: Eduardo Valentin Signed-off-by: Javi Merino

[PATCH v5 0/5] Let the power allocator thermal governor run on any thermal zone

Relax the thermal governor requirements of sustainable_power and at least two trip points so that it can be bound to any thermal zone. Its behavior won't be optimal, it would be the best possible with the data provided. Changes since v4: - Fix crash when a thermal zone with no trip points has

Re: [PATCH] virtio-gpu: fix compilation warnings

On Mi, 2015-09-02 at 12:30 +0300, Mike Rapoport wrote: > Update snprintf format in virtgpu_fence.c and virtgpu_debugfs.c to fix the > following compilation warnings: > > C [M] drivers/gpu/drm/virtio/virtgpu_fence.o > drivers/gpu/drm/virtio/virtgpu_fence.c: In function >

[PATCH v2 0/6] kselftest improvement and cleanup

This is my second attempt for improving the kselftest for arm/arm64 architecture. Eventually, we hope we could build(in an cross compile environment) and run all the kselftest cases automatically(successful of courses). The first version is here[1]. In this series, I try to make all the testcases

[PATCH 1/4] hv: add helpers to handle hv_util device state

The callbacks in kvp, vss and fcopy code are called the main thread and also from interrupt context. If a state change is done by the main thread it is not immediately seen by the interrupt. As a result the state machine gets out of sync. Force propagation of state changes via get/set helpers

[PATCH 0/4] hv: utils: propagate state to interrupt thread

The Copy-VMFile cmdlet on the host may fail because the guest fcopy driver state machine gets out of sync. This happens because the ->state and ->context variables are accessed by the main thread and from interrupt context. If an interrupt happens between fcopy_respond_to_host and hv_poll_channel

[PATCH 4/4] hv: vss: use wrapper to propate state

The .state is used by several threads of execution. Propagate the state to make changes visible. Also propagate context change in vss_on_msg. Signed-off-by: Olaf Hering --- drivers/hv/hv_snapshot.c | 37 - 1 file changed, 20 insertions(+), 17

[PATCH 3/4] hv: kvp: use wrapper to propate state

The .state is used by several threads of execution. Propagate the state to make changes visible. Also propagate context change in kvp_on_msg. Signed-off-by: Olaf Hering --- drivers/hv/hv_kvp.c | 38 +- 1 file changed, 21 insertions(+), 17

[PATCH] btrfs: memset cur_trans->delayed_refs to zero

Use memset() to null out the btrfs_delayed_ref_root of btrfs_transaction instead of setting all the members to 0 by hand. Signed-off-by: Alexandru Moise <00moses.alexande...@gmail.com> --- Rather than setting each member of ->delayed_refs by hand we should adhere to the practice of using memset()

[PATCH v5 3/9] Input: goodix - reset device at init

After power on, it is recommended that the driver resets the device. The reset procedure timing is described in the datasheet and is used at device init (before writing device configuration) and for power management. It is a sequence of setting the interrupt and reset pins high/low at specific

[PATCH v5 1/9] Input: goodix - sort includes alphabetically

Signed-off-by: Irina Tirdea --- drivers/input/touchscreen/goodix.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/input/touchscreen/goodix.c b/drivers/input/touchscreen/goodix.c index e36162b..6ae28c5 100644 ---

[PATCH v5 0/9] Goodix touchscreen enhancements

Add several enhancements to the Goodix touchscreen driver. This version adds runtime power management and includes some cleanup. Thanks, Irina Changes in v5: - add some more style cleanup (reorder includes, use error instead of ret for return values) - add runtime power management patch

similar files: fusbh200-hcd.c and fotg210-hcd.c

I executed a clone detection tool* on drivers source code and I found that the files drivers/usb/host/fusbh200-hcd.c and drivers/usb/host/fotg210-hcd.c are very similar. The main difference between the two files are replacing the string 'USBH20' by 'OTG21' and some white space fixes. Some

Re: [PATCH v4 3/3] mtd: nand: jz4780: driver for NAND devices on JZ4780 SoCs

Hi, On 06/09/2015 22:21, Ezequiel Garcia wrote: > On 27 Jul 03:21 PM, Alex Smith wrote: >> Add a driver for NAND devices connected to the NEMC on JZ4780 SoCs, as >> well as the hardware BCH controller. DMA is not currently implemented. >> >> While older 47xx SoCs also have a BCH controller, they

Re: [PATCH] powerpc32: memcpy: only use dcbz once cache is enabled

On Mon, Sep 07 2015, Christophe Leroy wrote: > memcpy() uses instruction dcbz to speed up copy by not wasting time > loading cache line with data that will be overwritten. > Some platform like mpc52xx do no have cache active at startup and > can therefore not use memcpy(). Allthough no part of the

Re: [RFC PATCH 1/3] arm64: entry: Remove unnecessary calculation for S_SP in EL1h

On Fri, Sep 04, 2015 at 03:23:05PM +0100, Jungseok Lee wrote: > Under EL1h, S_SP data is not seen in kernel_exit. Thus, x21 calculation > is not needed in kernel_entry. Currently, S_SP information is vaild only > when sp_el0 is used. I don't think this is true. The generic BUG implementation will

Re: [RFC PATCH v1 2/4] irqchip: GICv3: set non-percpu irqs status with _IRQ_MOVE_PCNTXT

Hi Thomas, On 07/09/15 14:24, Thomas Gleixner wrote: > On Mon, 7 Sep 2015, Marc Zyngier wrote: >> On 06/09/15 06:56, Jiang Liu wrote: >>> On 2015/9/6 12:23, Yang Yingliang wrote: Use irq_settings_set_move_pcntxt() helper irqs status with _IRQ_MOVE_PCNTXT. So that it can do set affinity

[PATCH v2] 9p: trans_fd, bail out if recv fcall if missing

req->rc is pre-allocated early on with p9_tag_alloc and shouldn't be missing Signed-off-by: Dominique Martinet --- net/9p/trans_fd.c | 13 ++--- 1 file changed, 6 insertions(+), 7 deletions(-) Feel free to adapt error code/message if you can think of

[PATCH] tty: don't leak cdev in tty_cdev_add()

Commit a3a10ce3429e ("Avoid usb reset crashes by making tty_io cdevs truly dynamic") which mixes using cdev_alloc() and cdev_init() is problematic. Subsequent call to cdev_init() after cdev_alloc() sets kobj release method from cdev_dynamic_release() to cdev_default_release() and thus makes it

Re: [RFC v0 2/9] suspend: Add getter function to report if freezing is active

On Monday, September 07, 2015 10:55:43 AM Daniel Wagner wrote: > On 09/05/2015 04:11 AM, Rafael J. Wysocki wrote: > > On Friday, September 04, 2015 03:34:55 PM Daniel Wagner wrote: > >> Instead encode the FREEZE state via the CPU state we allow the > >> interesting subsystems (MCE, microcode) to

Re: [PATCH 0/5] New Atmel PIO4 pinctrl/gpio driver

Hi Sascha, Any comments about this version? Maybe you missed it since you answered me on the RFC version. Of course I'll do the changes you requested for the next version (remove gpio_request_*() stuff and add macros for gpio muxing case). Thanks Ludovic On Tue, Aug 11, 2015 at 10:28:00AM

Re: [PATCH 0/6] sched/fair: Compute capacity invariant load/utilization tracking

On Mon, Sep 07, 2015 at 02:42:20PM +0200, Peter Zijlstra wrote: > I'm of a mind to apply these patches; with two patches on top, which > I'll post shortly. --- Subject: sched: Optimize __update_load_avg() From: Peter Zijlstra Date: Mon Sep 7 15:09:15 CEST 2015 Prior to

[PATCH] input: fix data race __ps2_command

The data race happens on ps2dev->cmdcnt and ps2dev->cmdbuf contents. __ps2_command reads that data concurrently with the interrupt handler. As the result, for example, if a response arrives just after the timeout, __ps2_command can copy out garbage from ps2dev->cmdbuf but then see that

Re: [PATCH 4/5] [media] uvcvideo: create pad links after subdev registration

Hello, On 09/03/2015 06:00 PM, Javier Martinez Canillas wrote: > The uvc driver creates the pads links before the media entity is > registered with the media device. This doesn't work now that obj > IDs are used to create links so the media_device has to be set. > > Move entities registration

[PATCH v2 2/2] leds: leds-ipaq-micro: Fix coding style issues

Spaces at the starting of a line are removed, indentation using tab, instead of space. Also, warnings related to line width of more than 80 characters is also taken care of. Two warnings have been left alone to aid better readability. Signed-off-by: Muhammad Falak R Wani

[PATCH v2 1/2] leds: leds-ipaq-micro: Use devm_led_classdev_register

Use of resource-managed function devm_led_classdev_register instead of led_classdev_register is preferred, consequently remove redundant function micro_leds_remove. Signed-off-by: Muhammad Falak R Wani --- drivers/leds/leds-ipaq-micro.c | 9 + 1 file changed, 1

Re: [V9fs-developer] [PATCH] 9p: trans_fd, initialize recv fcall properly if not set

I thought the nature of trans_fd would have prevented any sort of true zero copy, but I suppose one less is always welcome :) -eric On Sun, Sep 6, 2015 at 1:55 AM, Dominique Martinet wrote: > Eric Van Hensbergen wrote on Sat, Sep 05, 2015: >> On Thu, Sep 3,

[PATCH v2 0/2] leds: leds-ipaq-micro: Use resource managed functions and fix coding style.

Hi, Based on the suggestion from Jaeck, the orginal patch is split into two, one patch fixes the coding style issues, and the other uses resource managed function, devm_led_classdev_register. Muhammad Falak R Wani (2): leds: leds-ipaq-micro: Use devm_led_classdev_register leds:

Re: [PATCH] [s390]: Use .rept directive to store/load fpu registers

On Tue, Sep 01, 2015 at 09:51:32AM +0200, Christian Borntraeger wrote: > Am 28.08.2015 um 15:49 schrieb Alexander Kuleshov: > > arch/s390/kernel/swsusp.S | 49 > > --- > > 1 file changed, 17 insertions(+), 32 deletions(-) > > > > diff --git

<    4   5   6   7   8   9   10   11   12   >