[RFC v3 02/10] KVM: arm/arm64: Move cntvoff to each timer context

Make cntvoff per each timer context. This is helpful to abstract kvm timer functions to work with timer context without considering timer types (e.g. physical timer or virtual timer). This also would pave the way for ever doing adjustments of the cntvoff on a per-CPU basis if that should ever

[RFC v3 02/10] KVM: arm/arm64: Move cntvoff to each timer context

Make cntvoff per each timer context. This is helpful to abstract kvm timer functions to work with timer context without considering timer types (e.g. physical timer or virtual timer). This also would pave the way for ever doing adjustments of the cntvoff on a per-CPU basis if that should ever

[RFC v3 08/10] KVM: arm/arm64: Set up a background timer for the physical timer emulation

Set a background timer for the EL1 physical timer emulation while VMs are running, so that VMs get the physical timer interrupts in a timely manner. Schedule the background timer on entry to the VM and cancel it on exit. This would not have any performance impact to the guest OSes that currently

[RFC v3 08/10] KVM: arm/arm64: Set up a background timer for the physical timer emulation

Set a background timer for the EL1 physical timer emulation while VMs are running, so that VMs get the physical timer interrupts in a timely manner. Schedule the background timer on entry to the VM and cancel it on exit. This would not have any performance impact to the guest OSes that currently

[RFC v3 05/10] KVM: arm/arm64: Initialize the emulated EL1 physical timer

Initialize the emulated EL1 physical timer with the default irq number. Signed-off-by: Jintack Lim --- arch/arm/kvm/reset.c | 9 - arch/arm64/kvm/reset.c | 9 - include/kvm/arm_arch_timer.h | 3 ++- virt/kvm/arm/arch_timer.c| 9

[RFC v3 05/10] KVM: arm/arm64: Initialize the emulated EL1 physical timer

Initialize the emulated EL1 physical timer with the default irq number. Signed-off-by: Jintack Lim --- arch/arm/kvm/reset.c | 9 - arch/arm64/kvm/reset.c | 9 - include/kvm/arm_arch_timer.h | 3 ++- virt/kvm/arm/arch_timer.c| 9 +++-- 4 files changed, 25

Re: [PATCH v3 1/2] iio: distance: add dt binding for devantech-srf04

On Tue, Jan 31, 2017 at 07:03:06PM +0100, Andreas Klinger wrote: > This patch adds dt binding for devantech ultrasonic ranger srf04. > > The vendor "devantech" was already added to the vendor list with > "[PATCH v4 1/3] iio: distance: srf08: add trivial DT binding" > > Signed-off-by:

Re: [PATCH v3 1/2] iio: distance: add dt binding for devantech-srf04

On Tue, Jan 31, 2017 at 07:03:06PM +0100, Andreas Klinger wrote: > This patch adds dt binding for devantech ultrasonic ranger srf04. > > The vendor "devantech" was already added to the vendor list with > "[PATCH v4 1/3] iio: distance: srf08: add trivial DT binding" > > Signed-off-by:

[PATCH] efi: fdt: avoid FDT manipulation after ExitBootServices()

Some AArch64 UEFI implementations disable the MMU in ExitBootServices(), after which unaligned accesses to RAM are no longer supported. Commit abfb7b686a3e ("efi/libstub/arm*: Pass latest memory map to the kernel") fixed an issue in the memory map handling of the stub FDT code, but inadvertently

[GIT PULL] EFI urgent fix for v4.10

The following changes since commit 090abfc9dc7faf3f84799f956158c8c3af149a81: x86/efi: Always map first physical page into EFI pagetables (2017-01-27 20:20:01 +) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-urgent for you to

[PATCH] efi: fdt: avoid FDT manipulation after ExitBootServices()

Some AArch64 UEFI implementations disable the MMU in ExitBootServices(), after which unaligned accesses to RAM are no longer supported. Commit abfb7b686a3e ("efi/libstub/arm*: Pass latest memory map to the kernel") fixed an issue in the memory map handling of the stub FDT code, but inadvertently

[GIT PULL] EFI urgent fix for v4.10

The following changes since commit 090abfc9dc7faf3f84799f956158c8c3af149a81: x86/efi: Always map first physical page into EFI pagetables (2017-01-27 20:20:01 +) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-urgent for you to

[RFC v3 06/10] KVM: arm/arm64: Update the physical timer interrupt level

Now that we maintain the EL1 physical timer register states of VMs, update the physical timer interrupt level along with the virtual one. Signed-off-by: Jintack Lim --- virt/kvm/arm/arch_timer.c | 4 1 file changed, 4 insertions(+) diff --git

[RFC v3 06/10] KVM: arm/arm64: Update the physical timer interrupt level

Now that we maintain the EL1 physical timer register states of VMs, update the physical timer interrupt level along with the virtual one. Signed-off-by: Jintack Lim --- virt/kvm/arm/arch_timer.c | 4 1 file changed, 4 insertions(+) diff --git a/virt/kvm/arm/arch_timer.c

[RFC v3 04/10] KVM: arm/arm64: Add the EL1 physical timer context

Add the EL1 physical timer context. Signed-off-by: Jintack Lim --- include/kvm/arm_arch_timer.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/kvm/arm_arch_timer.h b/include/kvm/arm_arch_timer.h index f46fa3b..6445a3d 100644 ---

[RFC v3 04/10] KVM: arm/arm64: Add the EL1 physical timer context

Add the EL1 physical timer context. Signed-off-by: Jintack Lim --- include/kvm/arm_arch_timer.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/kvm/arm_arch_timer.h b/include/kvm/arm_arch_timer.h index f46fa3b..6445a3d 100644 --- a/include/kvm/arm_arch_timer.h +++

[RFC v3 09/10] KVM: arm64: Add the EL1 physical timer access handler

KVM traps on the EL1 phys timer accesses from VMs, but it doesn't handle those traps. This results in terminating VMs. Instead, set a handler for the EL1 phys timer access, and inject an undefined exception as an intermediate step. Signed-off-by: Jintack Lim ---

[RFC v3 09/10] KVM: arm64: Add the EL1 physical timer access handler

KVM traps on the EL1 phys timer accesses from VMs, but it doesn't handle those traps. This results in terminating VMs. Instead, set a handler for the EL1 phys timer access, and inject an undefined exception as an intermediate step. Signed-off-by: Jintack Lim --- arch/arm64/kvm/sys_regs.c | 34

[RFC v3 10/10] KVM: arm/arm64: Emulate the EL1 phys timer registers

Emulate read and write operations to CNTP_TVAL, CNTP_CVAL and CNTP_CTL. Now VMs are able to use the EL1 physical timer. Signed-off-by: Jintack Lim --- arch/arm64/kvm/sys_regs.c| 37 ++--- include/kvm/arm_arch_timer.h | 2 ++

[RFC v3 10/10] KVM: arm/arm64: Emulate the EL1 phys timer registers

Emulate read and write operations to CNTP_TVAL, CNTP_CVAL and CNTP_CTL. Now VMs are able to use the EL1 physical timer. Signed-off-by: Jintack Lim --- arch/arm64/kvm/sys_regs.c| 37 ++--- include/kvm/arm_arch_timer.h | 2 ++ virt/kvm/arm/arch_timer.c| 2

Re: [PATCH v3 6/7] dt-bindings: Add Multi-Inno MI0283QT binding

On Tue, Jan 31, 2017 at 05:03:18PM +0100, Noralf Trønnes wrote: > Add device-tree binding documentation for the MI0283QT display panel. > > Signed-off-by: Noralf Trønnes > --- > > Datasheet: https://cdn-shop.adafruit.com/datasheets/MI0283QT-11+V1.1.PDF > >

Re: [PATCH v3 6/7] dt-bindings: Add Multi-Inno MI0283QT binding

On Tue, Jan 31, 2017 at 05:03:18PM +0100, Noralf Trønnes wrote: > Add device-tree binding documentation for the MI0283QT display panel. > > Signed-off-by: Noralf Trønnes > --- > > Datasheet: https://cdn-shop.adafruit.com/datasheets/MI0283QT-11+V1.1.PDF > >

[RFC v3 01/10] KVM: arm/arm64: Abstract virtual timer context into separate structure

Abstract virtual timer context into a separate structure and change all callers referring to timer registers, irq state and so on. No change in functionality. This is about to become very handy when adding the EL1 physical timer. Signed-off-by: Jintack Lim Acked-by:

[RFC v3 01/10] KVM: arm/arm64: Abstract virtual timer context into separate structure

Abstract virtual timer context into a separate structure and change all callers referring to timer registers, irq state and so on. No change in functionality. This is about to become very handy when adding the EL1 physical timer. Signed-off-by: Jintack Lim Acked-by: Christoffer Dall Acked-by:

[RFC v3 07/10] KVM: arm/arm64: Set a background timer to the earliest timer expiration

When scheduling a background timer, consider both of the virtual and physical timer and pick the earliest expiration time. Signed-off-by: Jintack Lim --- arch/arm/kvm/arm.c| 3 ++- virt/kvm/arm/arch_timer.c | 53 +++

[RFC v3 00/10] Provide the EL1 physical timer to the VM

The ARM architecture defines the EL1 physical timer and the virtual timer, and it is reasonable for an OS to expect to be able to access both. However, the current KVM implementation does not provide the EL1 physical timer to VMs but terminates VMs on access to the timer. This patch series

[RFC v3 00/10] Provide the EL1 physical timer to the VM

The ARM architecture defines the EL1 physical timer and the virtual timer, and it is reasonable for an OS to expect to be able to access both. However, the current KVM implementation does not provide the EL1 physical timer to VMs but terminates VMs on access to the timer. This patch series

[RFC v3 07/10] KVM: arm/arm64: Set a background timer to the earliest timer expiration

When scheduling a background timer, consider both of the virtual and physical timer and pick the earliest expiration time. Signed-off-by: Jintack Lim --- arch/arm/kvm/arm.c| 3 ++- virt/kvm/arm/arch_timer.c | 53 +++ 2 files changed, 42

Re: [REGRESSION] EFI mixed mode patch triggers boot failure

On 01/30/2017 05:10 AM, Jiri Kosina wrote: > On Sat, 28 Jan 2017, Laura Abbott wrote: > Was out for a few days, reporter says the below patch does not work. There was some confusion with secure boot so I've asked them to re-test with efi=old_map and secure boot off. >>> >>> FYI,

Re: [REGRESSION] EFI mixed mode patch triggers boot failure

On 01/30/2017 05:10 AM, Jiri Kosina wrote: > On Sat, 28 Jan 2017, Laura Abbott wrote: > Was out for a few days, reporter says the below patch does not work. There was some confusion with secure boot so I've asked them to re-test with efi=old_map and secure boot off. >>> >>> FYI,

Re: [PATCH v4 2/4] arm64: Work around Falkor erratum 1003

On Wed, Feb 01, 2017 at 05:36:09PM +, Catalin Marinas wrote: > On Wed, Feb 01, 2017 at 04:33:58PM +, Will Deacon wrote: > > On Wed, Feb 01, 2017 at 11:29:22AM -0500, Christopher Covington wrote: > > > On 01/31/2017 12:56 PM, Marc Zyngier wrote: > > > > Given that all ARMv8 CPUs can support

Re: [PATCH v3 5/7] dt-bindings: display: Add common rotation property

On Tue, Jan 31, 2017 at 05:03:17PM +0100, Noralf Trønnes wrote: > Display panels can be oriented many ways, especially in the embedded > world. The rotation property is a way to describe this orientation. > The counter clockwise direction is chosen because that's what fbdev > and drm use. The h/w

Re: [PATCH v4 2/4] arm64: Work around Falkor erratum 1003

On Wed, Feb 01, 2017 at 05:36:09PM +, Catalin Marinas wrote: > On Wed, Feb 01, 2017 at 04:33:58PM +, Will Deacon wrote: > > On Wed, Feb 01, 2017 at 11:29:22AM -0500, Christopher Covington wrote: > > > On 01/31/2017 12:56 PM, Marc Zyngier wrote: > > > > Given that all ARMv8 CPUs can support

Re: [PATCH v3 5/7] dt-bindings: display: Add common rotation property

On Tue, Jan 31, 2017 at 05:03:17PM +0100, Noralf Trønnes wrote: > Display panels can be oriented many ways, especially in the embedded > world. The rotation property is a way to describe this orientation. > The counter clockwise direction is chosen because that's what fbdev > and drm use. The h/w

[PATCH 6/9] irqchip/gic-v3-its: Prevent its init ordering dependencies

Right now its_init() must be called before pci and platform init. Remove ordering dependencies to allow all initialization functions being called with the same initcall type. Signed-off-by: Robert Richter --- drivers/irqchip/irq-gic-v3-its-pci-msi.c | 4 +++-

[PATCH 6/9] irqchip/gic-v3-its: Prevent its init ordering dependencies

Right now its_init() must be called before pci and platform init. Remove ordering dependencies to allow all initialization functions being called with the same initcall type. Signed-off-by: Robert Richter --- drivers/irqchip/irq-gic-v3-its-pci-msi.c | 4 +++-

[PATCH 7/9] irqchip/gic-v3-its: Initialize its nodes later

Use an initcall to initialize its. This allows us to use the device framework during initialization that is up at this point. We use subsys_initcall() here since we need the arch to be initialized first. It is before pci and platform device probe where devices are bound to msi interrupts.

[PATCH 7/9] irqchip/gic-v3-its: Initialize its nodes later

Use an initcall to initialize its. This allows us to use the device framework during initialization that is up at this point. We use subsys_initcall() here since we need the arch to be initialized first. It is before pci and platform device probe where devices are bound to msi interrupts.

[PATCH 9/9] irqchip, gicv3-its, cma: Use CMA for allocation of large device tables

The gicv3-its device table may have a size of up to 16MB. With 4k pagesize the maximum size of memory allocation is 4MB. Use CMA for allocation of large tables. We use the device managed version of dma_alloc_coherent(). Thus, we don't need to release it manually on device removal. Signed-off-by:

[PATCH 5/9] irqchip/gic-v3-its: Decouple its initialization from gic

This patch separates its initialization from the gic. Probing and initialization of its nodes is separate now. There is an own cpu notifier for its now. Signed-off-by: Robert Richter --- drivers/irqchip/irq-gic-v3-its.c | 55 ++

[PATCH 9/9] irqchip, gicv3-its, cma: Use CMA for allocation of large device tables

The gicv3-its device table may have a size of up to 16MB. With 4k pagesize the maximum size of memory allocation is 4MB. Use CMA for allocation of large tables. We use the device managed version of dma_alloc_coherent(). Thus, we don't need to release it manually on device removal. Signed-off-by:

[PATCH 5/9] irqchip/gic-v3-its: Decouple its initialization from gic

This patch separates its initialization from the gic. Probing and initialization of its nodes is separate now. There is an own cpu notifier for its now. Signed-off-by: Robert Richter --- drivers/irqchip/irq-gic-v3-its.c | 55 ++ drivers/irqchip/irq-gic-v3.c

[PATCH 8/9] irqchip/gic-v3-its: Handle its nodes as kernel devices

Manage its nodes as kernel devices. We can then use the kernel's device resource management for memory allocation. Freeing memory becomes much easier now. This also allows us to use CMA for the allocation of large its tables. Signed-off-by: Robert Richter ---

[PATCH 8/9] irqchip/gic-v3-its: Handle its nodes as kernel devices

Manage its nodes as kernel devices. We can then use the kernel's device resource management for memory allocation. Freeing memory becomes much easier now. This also allows us to use CMA for the allocation of large its tables. Signed-off-by: Robert Richter --- drivers/irqchip/irq-gic-v3-its.c |

[PATCH 3/9] irqchip/gic-v3-its: Initialize MSIs with subsys_initcalls

This allows us to use kernel core functionality (e.g. cma) for ITS initialization. MSIs must be up before the device_initcalls (pci and platform device probe) and after arch_initcalls (dma init), so subsys_initcall is fine. Signed-off-by: Robert Richter ---

[PATCH 4/9] irqchip/gic-v3-its: Split probing from its node initialization

To initialize the its nodes at a later point during boot, we need to split probing from initialization. Collect all information required for initialization in struct its_node. We can then use the its node list for initialization. Signed-off-by: Robert Richter ---

[PATCH 3/9] irqchip/gic-v3-its: Initialize MSIs with subsys_initcalls

This allows us to use kernel core functionality (e.g. cma) for ITS initialization. MSIs must be up before the device_initcalls (pci and platform device probe) and after arch_initcalls (dma init), so subsys_initcall is fine. Signed-off-by: Robert Richter ---

[PATCH 4/9] irqchip/gic-v3-its: Split probing from its node initialization

To initialize the its nodes at a later point during boot, we need to split probing from initialization. Collect all information required for initialization in struct its_node. We can then use the its node list for initialization. Signed-off-by: Robert Richter ---

[PATCH 2/9] irqchip/gic-v3-its: Initialize its nodes in probe order

ATM the last discovered node is initialized first. Though this order should work too, change the initialization of nodes to probe order as one would expect it. Signed-off-by: Robert Richter --- drivers/irqchip/irq-gic-v3-its.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 2/9] irqchip/gic-v3-its: Initialize its nodes in probe order

ATM the last discovered node is initialized first. Though this order should work too, change the initialization of nodes to probe order as one would expect it. Signed-off-by: Robert Richter --- drivers/irqchip/irq-gic-v3-its.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/9] irqchip/gic-v3-its: Fix command buffer allocation

The its command buffer must be page aligned, but kzalloc() is not guaranteed to be (though it is mostly when allocating 64k). Use __get_free_pages() as this is used for other buffers as well. Signed-off-by: Robert Richter --- drivers/irqchip/irq-gic-v3-its.c | 3 ++- 1 file

[PATCH 1/9] irqchip/gic-v3-its: Fix command buffer allocation

The its command buffer must be page aligned, but kzalloc() is not guaranteed to be (though it is mostly when allocating 64k). Use __get_free_pages() as this is used for other buffers as well. Signed-off-by: Robert Richter --- drivers/irqchip/irq-gic-v3-its.c | 3 ++- 1 file changed, 2

Re: [PATCH 1/3] arc: vdk: Disable halt on reset

On 02/01/2017 09:14 AM, Alexey Brodkin wrote: >>> -# CONFIG_ARC_TIMERS_64BIT is not set >> >> Are you sure abut this part. Ater the timers driver rework, this would >> enable GFRC >> for SMP builds and AFAIKR there were some issues with time with GFRC + nSIM >> etc.. > > Not anymore :) > >

Re: [PATCH 1/3] arc: vdk: Disable halt on reset

On 02/01/2017 09:14 AM, Alexey Brodkin wrote: >>> -# CONFIG_ARC_TIMERS_64BIT is not set >> >> Are you sure abut this part. Ater the timers driver rework, this would >> enable GFRC >> for SMP builds and AFAIKR there were some issues with time with GFRC + nSIM >> etc.. > > Not anymore :) > >

Re: Build failure with v4.9-rc1 and GCC trunk -- compiler weirdness

On 1 February 2017 at 16:58, Laura Abbott wrote: > On 10/19/2016 09:22 AM, Will Deacon wrote: >> On Wed, Oct 19, 2016 at 09:01:33AM -0700, Linus Torvalds wrote: >>> On Wed, Oct 19, 2016 at 8:56 AM, Markus Trippelsdorf >>> wrote: On 2016.10.19 at

Re: Build failure with v4.9-rc1 and GCC trunk -- compiler weirdness

On 1 February 2017 at 16:58, Laura Abbott wrote: > On 10/19/2016 09:22 AM, Will Deacon wrote: >> On Wed, Oct 19, 2016 at 09:01:33AM -0700, Linus Torvalds wrote: >>> On Wed, Oct 19, 2016 at 8:56 AM, Markus Trippelsdorf >>> wrote: On 2016.10.19 at 08:55 -0700, Linus Torvalds wrote: >

Re: [PATCH v4 2/4] arm64: Work around Falkor erratum 1003

On Wed, Feb 01, 2017 at 04:33:58PM +, Will Deacon wrote: > On Wed, Feb 01, 2017 at 11:29:22AM -0500, Christopher Covington wrote: > > On 01/31/2017 12:56 PM, Marc Zyngier wrote: > > > Given that all ARMv8 CPUs can support SW_PAN, it is more likely to be > > > enabled than the ARMv8.1 PAN. I'd

Re: [PATCH v4 2/4] arm64: Work around Falkor erratum 1003

On Wed, Feb 01, 2017 at 04:33:58PM +, Will Deacon wrote: > On Wed, Feb 01, 2017 at 11:29:22AM -0500, Christopher Covington wrote: > > On 01/31/2017 12:56 PM, Marc Zyngier wrote: > > > Given that all ARMv8 CPUs can support SW_PAN, it is more likely to be > > > enabled than the ARMv8.1 PAN. I'd

Re: [PATCH linux v5 5/6] hwmon: occ: Add hwmon implementation for the P8 OCC

On Tue, Jan 31, 2017 at 09:43:56AM -0600, eaja...@linux.vnet.ibm.com wrote: > From: "Edward A. James" > > Add code to tie the hwmon sysfs code and the POWER8 OCC code together, as > well as probe the entire driver from the I2C bus. I2C is the communication > method between

Re: [PATCH 0/3] Updates for ARC VDK platform

Hi Vineet, On Wed, 2017-02-01 at 09:22 -0800, Vineet Gupta wrote: > On 02/01/2017 09:16 AM, Alexey Brodkin wrote: > > > > Hi Vineet, > > > > On Wed, 2017-02-01 at 09:13 -0800, Vineet Gupta wrote: > > > > > > On 02/01/2017 08:43 AM, Alexey Brodkin wrote: > > > > > > > > This series improves

Re: [PATCH linux v5 5/6] hwmon: occ: Add hwmon implementation for the P8 OCC

On Tue, Jan 31, 2017 at 09:43:56AM -0600, eaja...@linux.vnet.ibm.com wrote: > From: "Edward A. James" > > Add code to tie the hwmon sysfs code and the POWER8 OCC code together, as > well as probe the entire driver from the I2C bus. I2C is the communication > method between the BMC and the P8

Re: [PATCH 0/3] Updates for ARC VDK platform

Hi Vineet, On Wed, 2017-02-01 at 09:22 -0800, Vineet Gupta wrote: > On 02/01/2017 09:16 AM, Alexey Brodkin wrote: > > > > Hi Vineet, > > > > On Wed, 2017-02-01 at 09:13 -0800, Vineet Gupta wrote: > > > > > > On 02/01/2017 08:43 AM, Alexey Brodkin wrote: > > > > > > > > This series improves

[PATCH v3 1/4] device property: export code duplicating array of property entries

When augmenting ACPI-enumerated devices with additional property data based on DMI info, a module has often several potential property sets, with only one being active on a given box. In order to save memory it should be possible to mark everything and __initdata or __initconst, execute DMI match

Re: [PATCH 3/8] Documentation: dt-bindings: Add STM32 pinctrl driver DT bindings

On Tue, Jan 31, 2017 at 02:14:20PM +0100, Alexandre TORGUE wrote: > Add compatible sting for stm32h743 MCU. Also, you can drop "Documentation: " from the subject as it is redundant. > > Signed-off-by: Alexandre TORGUE > > diff --git

[PATCH v3 3/4] driver property: constify property arrays values

Data that is fed into property arrays should not be modified, so let's mark relevant pointers as const. This will allow us making source arrays as const/__initconst. Also fix memory leaks on errors in property_entry_copy(). Signed-off-by: Dmitry Torokhov ---

[PATCH v3 1/4] device property: export code duplicating array of property entries

When augmenting ACPI-enumerated devices with additional property data based on DMI info, a module has often several potential property sets, with only one being active on a given box. In order to save memory it should be possible to mark everything and __initdata or __initconst, execute DMI match

Re: [PATCH 3/8] Documentation: dt-bindings: Add STM32 pinctrl driver DT bindings

On Tue, Jan 31, 2017 at 02:14:20PM +0100, Alexandre TORGUE wrote: > Add compatible sting for stm32h743 MCU. Also, you can drop "Documentation: " from the subject as it is redundant. > > Signed-off-by: Alexandre TORGUE > > diff --git

[PATCH v3 3/4] driver property: constify property arrays values

Data that is fed into property arrays should not be modified, so let's mark relevant pointers as const. This will allow us making source arrays as const/__initconst. Also fix memory leaks on errors in property_entry_copy(). Signed-off-by: Dmitry Torokhov --- drivers/base/property.c | 66

[PATCH] jbd2: Fix use after free in kjournald2()

Below is the synchronization issue between unmount and kjournald2 contexts, which results into use after free issue in kjournald2(). Fix this issue by using journal->j_state_lock to synchronize the wait_event() done in journal_kill_thread() and the wake_up() done in kjournald2(). TASK 1: umount

[PATCH] jbd2: Fix use after free in kjournald2()

Below is the synchronization issue between unmount and kjournald2 contexts, which results into use after free issue in kjournald2(). Fix this issue by using journal->j_state_lock to synchronize the wait_event() done in journal_kill_thread() and the wake_up() done in kjournald2(). TASK 1: umount

[Patch v6 0/2] Support ARM SMCC SoC vendor quirks

At least one SoC vendor (Qualcomm) requires additional processing done during ARM SMCCC calls. As such, an additional parameter to the arm_smccc_smc is required to be able to handle SoC specific quirks. The Qualcomm quirk is necessary due to the fact that the scm call can be interrupted on

[Patch v6 0/2] Support ARM SMCC SoC vendor quirks

At least one SoC vendor (Qualcomm) requires additional processing done during ARM SMCCC calls. As such, an additional parameter to the arm_smccc_smc is required to be able to handle SoC specific quirks. The Qualcomm quirk is necessary due to the fact that the scm call can be interrupted on

Re: [PATCH 3/8] Documentation: dt-bindings: Add STM32 pinctrl driver DT bindings

On Tue, Jan 31, 2017 at 02:14:20PM +0100, Alexandre TORGUE wrote: > Add compatible sting for stm32h743 MCU. > > Signed-off-by: Alexandre TORGUE > > diff --git a/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.txt >

[Patch v6 2/2] firmware: qcom: scm: Fix interrupted SCM calls

This patch adds a Qualcomm specific quirk to the arm_smccc_smc call. On Qualcomm ARM64 platforms, the SMC call can return before it has completed. If this occurs, the call can be restarted, but it requires using the returned session ID value from the interrupted SMC call. The quirk stores off

[PATCH v3 4/4] i2c: allow specify device properties in i2c_board_info

With many drivers converting to using generic device properties, it is useful to provide array of device properties when instantiating new i2c client via i2c_board_info and have them automatically added to the device in question. Signed-off-by: Dmitry Torokhov ---

[Patch v6 1/2] arm: kernel: Add SMC structure parameter

This patch adds a quirk parameter to the arm_smccc_(smc/hvc) calls. The quirk structure allows for specialized SMC operations due to SoC specific requirements. The current arm_smccc_(smc/hvc) is renamed and macros are used instead to specify the standard arm_smccc_(smc/hvc) or the

[Patch v6 2/2] firmware: qcom: scm: Fix interrupted SCM calls

This patch adds a Qualcomm specific quirk to the arm_smccc_smc call. On Qualcomm ARM64 platforms, the SMC call can return before it has completed. If this occurs, the call can be restarted, but it requires using the returned session ID value from the interrupted SMC call. The quirk stores off

[PATCH v3 4/4] i2c: allow specify device properties in i2c_board_info

With many drivers converting to using generic device properties, it is useful to provide array of device properties when instantiating new i2c client via i2c_board_info and have them automatically added to the device in question. Signed-off-by: Dmitry Torokhov --- drivers/i2c/i2c-core.c | 16

[Patch v6 1/2] arm: kernel: Add SMC structure parameter

This patch adds a quirk parameter to the arm_smccc_(smc/hvc) calls. The quirk structure allows for specialized SMC operations due to SoC specific requirements. The current arm_smccc_(smc/hvc) is renamed and macros are used instead to specify the standard arm_smccc_(smc/hvc) or the

Re: [PATCH 3/8] Documentation: dt-bindings: Add STM32 pinctrl driver DT bindings

On Tue, Jan 31, 2017 at 02:14:20PM +0100, Alexandre TORGUE wrote: > Add compatible sting for stm32h743 MCU. > > Signed-off-by: Alexandre TORGUE > > diff --git a/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.txt > b/Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.txt >

[PATCH v3 2/4] device property: allow to constify properties

There is no reason why statically defined properties should be modifiable, so let's make device_add_properties() and the rest of pset_*() functions to take const pointers to properties. This will allow us to mark properties as const/__initconst at definition sites. Reviewed-by: Mika Westerberg

[PATCH v3 2/4] device property: allow to constify properties

There is no reason why statically defined properties should be modifiable, so let's make device_add_properties() and the rest of pset_*() functions to take const pointers to properties. This will allow us to mark properties as const/__initconst at definition sites. Reviewed-by: Mika Westerberg

[PATCH v3 0/4] Export APIs to copy device properties & more

Hi, Here is the refreshed series exporting APIs to copy statically declared device properties. The reason is that we want to augment ACPI-based devices with properties, and drivers usually have a largish DMI table for multiple models, so it is desirable to mark everything as

[PATCH v3 0/4] Export APIs to copy device properties & more

Hi, Here is the refreshed series exporting APIs to copy statically declared device properties. The reason is that we want to augment ACPI-based devices with properties, and drivers usually have a largish DMI table for multiple models, so it is desirable to mark everything as

Re: [PATCH v3 5/8] ASoC: codecs: Add sun8i-a33 binding documentation

On Tue, Jan 31, 2017 at 11:05:49AM +0100, Mylène Josserand wrote: > Add the documentation for dt-binding of the digital audio codec driver > and the audio card driver for Sun8i-a33 SoCs. > > Signed-off-by: Mylène Josserand > --- >

Re: [PATCH v3 5/8] ASoC: codecs: Add sun8i-a33 binding documentation

On Tue, Jan 31, 2017 at 11:05:49AM +0100, Mylène Josserand wrote: > Add the documentation for dt-binding of the digital audio codec driver > and the audio card driver for Sun8i-a33 SoCs. > > Signed-off-by: Mylène Josserand > --- > .../devicetree/bindings/sound/sun8i-a33-codec.txt | 75 >

Re: [PATCH 7/9] md: use kvmalloc rather than opencoded variant

On Mon, 30 Jan 2017, Michal Hocko wrote: > From: Michal Hocko > > copy_params uses kmalloc with vmalloc fallback. We already have a helper > for that - kvmalloc. This caller requires GFP_NOIO semantic so it hasn't > been converted with many others by previous patches. All we

Re: [PATCH 7/9] md: use kvmalloc rather than opencoded variant

On Mon, 30 Jan 2017, Michal Hocko wrote: > From: Michal Hocko > > copy_params uses kmalloc with vmalloc fallback. We already have a helper > for that - kvmalloc. This caller requires GFP_NOIO semantic so it hasn't > been converted with many others by previous patches. All we need to > achieve

Re: [PATCH v3 1/8] ASoC: sun4i-i2s: Update binding documentation to include A31

On Tue, Jan 31, 2017 at 11:05:45AM +0100, Mylène Josserand wrote: > Add a new compatible for sun4i-i2s driver to handle some > SoCs that have a reset line that must be asserted/deasserted. > > This new compatible, "allwinner,sun6i-a31-i2s", requires the > property "resets" which should be a

Re: [PATCH v3 1/8] ASoC: sun4i-i2s: Update binding documentation to include A31

On Tue, Jan 31, 2017 at 11:05:45AM +0100, Mylène Josserand wrote: > Add a new compatible for sun4i-i2s driver to handle some > SoCs that have a reset line that must be asserted/deasserted. > > This new compatible, "allwinner,sun6i-a31-i2s", requires the > property "resets" which should be a

Re: [PATCH] Input: uinput - fix crash when mixing old and new init style

On Wed, Feb 01, 2017 at 09:49:25AM +0100, Benjamin Tissoires wrote: > On Jan 31 2017 or thereabouts, Dmitry Torokhov wrote: > > If user tries to initialize uinput device mixing old and new style > > initialization (i.e. using old UI_SET_ABSBIT instead of UI_ABS_SETUP, > > we forget to allocate

Re: [PATCH] Input: uinput - fix crash when mixing old and new init style

On Wed, Feb 01, 2017 at 09:49:25AM +0100, Benjamin Tissoires wrote: > On Jan 31 2017 or thereabouts, Dmitry Torokhov wrote: > > If user tries to initialize uinput device mixing old and new style > > initialization (i.e. using old UI_SET_ABSBIT instead of UI_ABS_SETUP, > > we forget to allocate

Re: kernel 4.10-rcx iio helper question

On 1 February 2017 05:50:12 GMT+00:00, Peter Rosin wrote: >On 2017-02-01 01:42, Ken.Lin wrote: >> >> >>> -Original Message- >>> From: Peter Rosin [mailto:p...@axentia.se] >>> Sent: Tuesday, January 31, 2017 1:10 PM >>> To: Ken.Lin; ji...@kernel.org >>> Cc:

Re: kernel 4.10-rcx iio helper question

On 1 February 2017 05:50:12 GMT+00:00, Peter Rosin wrote: >On 2017-02-01 01:42, Ken.Lin wrote: >> >> >>> -Original Message- >>> From: Peter Rosin [mailto:p...@axentia.se] >>> Sent: Tuesday, January 31, 2017 1:10 PM >>> To: Ken.Lin; ji...@kernel.org >>> Cc: knaac...@gmx.de;

Re: [RFC PATCH v2] Input: gpio_keys - add dt abs/rel button support

On Tue, Jan 31, 2017 at 08:55:19AM +0100, Hans Holmberg wrote: > This change adds support for specifying device tree buttons emitting > abs/rel events. > > ABS events were previously supported, but only via platform data, so add > the missing device tree property to allow axis values to be

Re: [RFC PATCH v2] Input: gpio_keys - add dt abs/rel button support

On Tue, Jan 31, 2017 at 08:55:19AM +0100, Hans Holmberg wrote: > This change adds support for specifying device tree buttons emitting > abs/rel events. > > ABS events were previously supported, but only via platform data, so add > the missing device tree property to allow axis values to be

Re: [PATCH v3 13/24] drm/rockchip: dw-mipi-dsi: fix escape clock rate

On Mon, 30 Jan 2017 15:25:10 -0500, Sean Paul wrote: > On Sun, Jan 29, 2017 at 01:24:33PM +, John Keeping wrote: > > This clock rate is derived from the PHY PLL, so it should be calculated > > dynamically. Use the same calculation as the vendor kernel to derive > > the escape clock speed. >

Re: [PATCH v3 13/24] drm/rockchip: dw-mipi-dsi: fix escape clock rate

On Mon, 30 Jan 2017 15:25:10 -0500, Sean Paul wrote: > On Sun, Jan 29, 2017 at 01:24:33PM +, John Keeping wrote: > > This clock rate is derived from the PHY PLL, so it should be calculated > > dynamically. Use the same calculation as the vendor kernel to derive > > the escape clock speed. >

Re: [PATCH 0/3] Updates for ARC VDK platform

On 02/01/2017 09:16 AM, Alexey Brodkin wrote: > Hi Vineet, > > On Wed, 2017-02-01 at 09:13 -0800, Vineet Gupta wrote: >> On 02/01/2017 08:43 AM, Alexey Brodkin wrote: >>> This series improves ARC VDK support in upstream Linux kernel by: >>> 1) Removal of UP configuration which is no longer

Re: [PATCH 0/3] Updates for ARC VDK platform

On 02/01/2017 09:16 AM, Alexey Brodkin wrote: > Hi Vineet, > > On Wed, 2017-02-01 at 09:13 -0800, Vineet Gupta wrote: >> On 02/01/2017 08:43 AM, Alexey Brodkin wrote: >>> This series improves ARC VDK support in upstream Linux kernel by: >>> 1) Removal of UP configuration which is no longer

<    3   4   5   6   7   8   9   10   11   12   >