[PATCH v6 0/5] Update LZ4 compressor module

This patchset is for updating the LZ4 compression module to a version based on LZ4 v1.7.3 allowing to use the fast compression algorithm aka LZ4 fast which provides an "acceleration" parameter as a tradeoff between high compression ratio and high compression speed. We want to use LZ4 fast in

[PATCH v6 2/5] lib/decompress_unlz4: Change module to work with new LZ4 module version

This patch updates the unlz4 wrapper to work with the updated LZ4 kernel module version. Signed-off-by: Sven Schmidt <4ssch...@informatik.uni-hamburg.de> --- lib/decompress_unlz4.c | 13 - 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/lib/decompress_unlz4.c

Re: [PATCH V6 3/5] OF: Add missing I/O range exception for indirect-IO devices

On Tue, Jan 24, 2017 at 03:05:23PM +0800, zhichang.yuan wrote: > There are some special ISA/LPC devices that work on a specific I/O range where > it is not correct to specify a 'ranges' property in DTS parent node as cpu > addresses translated from DTS node are only for memory space on some >

Re: [PATCH V6 3/5] OF: Add missing I/O range exception for indirect-IO devices

On Tue, Jan 24, 2017 at 03:05:23PM +0800, zhichang.yuan wrote: > There are some special ISA/LPC devices that work on a specific I/O range where > it is not correct to specify a 'ranges' property in DTS parent node as cpu > addresses translated from DTS node are only for memory space on some >

[HMM v17 06/14] mm/migrate: new memory migration helper for use with device memory v3

This patch add a new memory migration helpers, which migrate memory backing a range of virtual address of a process to different memory (which can be allocated through special allocator). It differs from numa migration by working on a range of virtual address and thus by doing migration in chunk

[HMM v17 06/14] mm/migrate: new memory migration helper for use with device memory v3

This patch add a new memory migration helpers, which migrate memory backing a range of virtual address of a process to different memory (which can be allocated through special allocator). It differs from numa migration by working on a range of virtual address and thus by doing migration in chunk

Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.

Hi! > > > Can I get the copy of the patch? > > > > > > http://www.spinics.net/lists/linux-usb/msg152542.html > > > > > > ...but it is html mangled with no obvious way to unmangle it. > > Bounced it to you. FYI, patchwork.kernel.org should have it too, the > "mbox" option there works the best.

Re: v4.9 to v4.10 regression: oops when USB cable is plugged in.

Hi! > > > Can I get the copy of the patch? > > > > > > http://www.spinics.net/lists/linux-usb/msg152542.html > > > > > > ...but it is html mangled with no obvious way to unmangle it. > > Bounced it to you. FYI, patchwork.kernel.org should have it too, the > "mbox" option there works the best.

[PATCH 3/6] staging: bcm2835-v4l2: Add a build system for the module.

This is derived from the downstream tree's build system, but with just a single Kconfig option. For now the driver only builds on 32-bit arm -- the aarch64 build breaks due to the driver using arm-specific cache flushing functions. Signed-off-by: Eric Anholt ---

[PATCH 3/6] staging: bcm2835-v4l2: Add a build system for the module.

This is derived from the downstream tree's build system, but with just a single Kconfig option. For now the driver only builds on 32-bit arm -- the aarch64 build breaks due to the driver using arm-specific cache flushing functions. Signed-off-by: Eric Anholt --- drivers/staging/media/Kconfig

[PATCH 4/6] staging: bcm2835-v4l2: Add a TODO file for improvements we need.

Signed-off-by: Eric Anholt --- drivers/staging/media/platform/bcm2835/TODO | 39 + 1 file changed, 39 insertions(+) create mode 100644 drivers/staging/media/platform/bcm2835/TODO diff --git a/drivers/staging/media/platform/bcm2835/TODO

[PATCH 4/6] staging: bcm2835-v4l2: Add a TODO file for improvements we need.

Signed-off-by: Eric Anholt --- drivers/staging/media/platform/bcm2835/TODO | 39 + 1 file changed, 39 insertions(+) create mode 100644 drivers/staging/media/platform/bcm2835/TODO diff --git a/drivers/staging/media/platform/bcm2835/TODO

[PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver

Here's my first pass at importing the camera driver. There's a bunch of TODO left to it, most of which is documented, and the rest being standard checkpatch fare. Unfortunately, when I try modprobing it on my pi3, the USB network device dies, consistently. I'm not sure what's going on here yet,

[PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver

Here's my first pass at importing the camera driver. There's a bunch of TODO left to it, most of which is documented, and the rest being standard checkpatch fare. Unfortunately, when I try modprobing it on my pi3, the USB network device dies, consistently. I'm not sure what's going on here yet,

[PATCH 2/6] staging: bcm2835-v4l2: Update the driver to the current VCHI API.

49bec49fd7f2 ("staging: vc04_services: remove vchiq_copy_from_user") removed the flags/msg_handle arguments, which were unused, and pushed the implementation of copying using memcpy vs copy_from_user to the caller. Signed-off-by: Eric Anholt ---

[PATCH 2/6] staging: bcm2835-v4l2: Update the driver to the current VCHI API.

49bec49fd7f2 ("staging: vc04_services: remove vchiq_copy_from_user") removed the flags/msg_handle arguments, which were unused, and pushed the implementation of copying using memcpy vs copy_from_user to the caller. Signed-off-by: Eric Anholt ---

[PATCH 6/6] staging: bcm2835-v4l2: Apply spelling fixes from checkpatch.

Generated with checkpatch.pl --fix-inplace and git add -p out of the results. Signed-off-by: Eric Anholt --- drivers/staging/media/platform/bcm2835/bcm2835-camera.c | 6 +++--- drivers/staging/media/platform/bcm2835/mmal-vchiq.c | 12 ++-- 2 files changed, 9

[PATCH 6/6] staging: bcm2835-v4l2: Apply spelling fixes from checkpatch.

Generated with checkpatch.pl --fix-inplace and git add -p out of the results. Signed-off-by: Eric Anholt --- drivers/staging/media/platform/bcm2835/bcm2835-camera.c | 6 +++--- drivers/staging/media/platform/bcm2835/mmal-vchiq.c | 12 ++-- 2 files changed, 9 insertions(+), 9

[HMM v17 11/14] mm/hmm/mirror: device page fault handler

This handle page fault on behalf of device driver, unlike handle_mm_fault() it does not trigger migration back to system memory for device memory. Signed-off-by: Jérôme Glisse Signed-off-by: Evgeny Baskakov Signed-off-by: John Hubbard

[HMM v17 11/14] mm/hmm/mirror: device page fault handler

This handle page fault on behalf of device driver, unlike handle_mm_fault() it does not trigger migration back to system memory for device memory. Signed-off-by: Jérôme Glisse Signed-off-by: Evgeny Baskakov Signed-off-by: John Hubbard Signed-off-by: Mark Hairgrove Signed-off-by: Sherry Cheung

[HMM v17 07/14] mm/migrate: migrate_vma() unmap page from vma while collecting pages

Common case for migration of virtual address range is page are map only once inside the vma in which migration is taking place. Because we already walk the CPU page table for that range we can directly do the unmap there and setup special migration swap entry. Signed-off-by: Jérôme Glisse

[HMM v17 05/14] mm/migrate: add new boolean copy flag to migratepage() callback

Allow migration without copy in case destination page already have source page content. This is usefull for new dma capable migration where use device dma engine to copy pages. This feature need carefull audit of filesystem code to make sure that no one can write to the source page while it is

[HMM v17 07/14] mm/migrate: migrate_vma() unmap page from vma while collecting pages

Common case for migration of virtual address range is page are map only once inside the vma in which migration is taking place. Because we already walk the CPU page table for that range we can directly do the unmap there and setup special migration swap entry. Signed-off-by: Jérôme Glisse

[HMM v17 05/14] mm/migrate: add new boolean copy flag to migratepage() callback

Allow migration without copy in case destination page already have source page content. This is usefull for new dma capable migration where use device dma engine to copy pages. This feature need carefull audit of filesystem code to make sure that no one can write to the source page while it is

[HMM v17 08/14] mm/hmm: heterogeneous memory management (HMM for short)

HMM provides 3 separate functionality : - Mirroring: synchronize CPU page table and device page table - Device memory: allocating struct page for device memory - Migration: migrating regular memory to device memory This patch introduces some common helpers and definitions to all of

[HMM v17 03/14] mm/ZONE_DEVICE/unaddressable: add support for un-addressable device memory v3

This add support for un-addressable device memory. Such memory is hotpluged only so we can have struct page but we should never map them as such memory can not be accessed by CPU. For that reason it uses a special swap entry for CPU page table entry. This patch implement all the logic from

[HMM v17 08/14] mm/hmm: heterogeneous memory management (HMM for short)

HMM provides 3 separate functionality : - Mirroring: synchronize CPU page table and device page table - Device memory: allocating struct page for device memory - Migration: migrating regular memory to device memory This patch introduces some common helpers and definitions to all of

[HMM v17 03/14] mm/ZONE_DEVICE/unaddressable: add support for un-addressable device memory v3

This add support for un-addressable device memory. Such memory is hotpluged only so we can have struct page but we should never map them as such memory can not be accessed by CPU. For that reason it uses a special swap entry for CPU page table entry. This patch implement all the logic from

[PATCH 1/2] PCI: iproc: allow the MPS to be set

pcie_bus_configure_settings() needs to be called on each of the root ports to allow for the MPS to be configured for all of the children devices. Signed-off-by: Jon Mason --- drivers/pci/host/pcie-iproc.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff

[PATCH 1/2] PCI: iproc: allow the MPS to be set

pcie_bus_configure_settings() needs to be called on each of the root ports to allow for the MPS to be configured for all of the children devices. Signed-off-by: Jon Mason --- drivers/pci/host/pcie-iproc.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git

[PATCH 2/2] PCI: Add quirk entry for NS2 PAXC PCI

The Broadcom Northstar2 SoC has a number of quirks for the PAXC (internal/fake) PCI bus. Specifically, the PCI config space is shared between the root port and the first PF (ie., PF0), and a number of fields are tied to zero (thus preventing them from being set). These cannot be "fixed" in

[PATCH 2/2] PCI: Add quirk entry for NS2 PAXC PCI

The Broadcom Northstar2 SoC has a number of quirks for the PAXC (internal/fake) PCI bus. Specifically, the PCI config space is shared between the root port and the first PF (ie., PF0), and a number of fields are tied to zero (thus preventing them from being set). These cannot be "fixed" in

[PATCH v5 3/13] mmc: sunxi: Always set signal delay to 0 for A64

Experience have shown that the using the autocalibration could severely degrade the performances of the MMC bus. Allwinner is using in its BSP a delay set to 0 for all the modes but HS400. Remove the calibration code for now, and add comments to document our findings. Reviewed-by: Andre

[PATCH v5 3/13] mmc: sunxi: Always set signal delay to 0 for A64

Experience have shown that the using the autocalibration could severely degrade the performances of the MMC bus. Allwinner is using in its BSP a delay set to 0 for all the modes but HS400. Remove the calibration code for now, and add comments to document our findings. Reviewed-by: Andre

[PATCH v5 6/13] mmc: sunxi: Add EMMC (MMC2) controller compatible

The MMC2 controller on the A64 is kind of a special beast. While the general controller design is the same than the other MMC controllers in the SoC, it also has a bunch of features and changes that prevent it to be driven in the same way. It has for example a different bus width limit, a

[PATCH v5 6/13] mmc: sunxi: Add EMMC (MMC2) controller compatible

The MMC2 controller on the A64 is kind of a special beast. While the general controller design is the same than the other MMC controllers in the SoC, it also has a bunch of features and changes that prevent it to be driven in the same way. It has for example a different bus width limit, a

[PATCH v5 2/13] mmc: sunxi: Gate the clock when rate is 0

The MMC core assumes that the code will gate the clock when the bus frequency is set to 0, which we've been ignoring so far. Handle that. Signed-off-by: Maxime Ripard Tested-by: Florian Vaussard --- drivers/mmc/host/sunxi-mmc.c |

[PATCH v5 9/13] arm64: allwinner: a64: Add MMC pinctrl nodes

The A64 only has a single set of pins for each MMC controller. Since we already have boards that require all of them, let's add them to the DTSI. Reviewed-by: Andre Przywara Signed-off-by: Maxime Ripard Tested-by: Florian Vaussard

[PATCH v5 2/13] mmc: sunxi: Gate the clock when rate is 0

The MMC core assumes that the code will gate the clock when the bus frequency is set to 0, which we've been ignoring so far. Handle that. Signed-off-by: Maxime Ripard Tested-by: Florian Vaussard --- drivers/mmc/host/sunxi-mmc.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff

[PATCH v5 9/13] arm64: allwinner: a64: Add MMC pinctrl nodes

The A64 only has a single set of pins for each MMC controller. Since we already have boards that require all of them, let's add them to the DTSI. Reviewed-by: Andre Przywara Signed-off-by: Maxime Ripard Tested-by: Florian Vaussard --- arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 25

[PATCH v5 13/13] arm64: allwinner: add BananaPi-M64 support

From: Andre Przywara The Banana Pi M64 board is a typical single board computer based on the Allwinner A64 SoC. Aside from the usual peripherals it features eMMC storage, which is connected to the 8-bit capable SDHC2 controller. Also it has a soldered WiFi/Bluetooth chip,

[PATCH v5 4/13] mmc: sunxi: Enable the new timings for the A64 MMC controllers

The A64 MMC controllers need to set a "new timings" bit when a new rate is set. The actual meaning of that bit is not clear yet, but not setting it leads to some corner-case issues, like the CMD53 failing, which is used to implement SDIO packet aggregation. Signed-off-by: Maxime Ripard

[PATCH v5 7/13] mmc: sunxi: Add more debug informations

Add a bit more debug messages that can be helpful when debugging the clock setup. Also fill the actual_clock field in struct mmc_host to report properly the current frequency in debugfs. Signed-off-by: Maxime Ripard Tested-by: Florian Vaussard

[PATCH v5 13/13] arm64: allwinner: add BananaPi-M64 support

From: Andre Przywara The Banana Pi M64 board is a typical single board computer based on the Allwinner A64 SoC. Aside from the usual peripherals it features eMMC storage, which is connected to the 8-bit capable SDHC2 controller. Also it has a soldered WiFi/Bluetooth chip, so we enable UART1 and

[PATCH v5 4/13] mmc: sunxi: Enable the new timings for the A64 MMC controllers

The A64 MMC controllers need to set a "new timings" bit when a new rate is set. The actual meaning of that bit is not clear yet, but not setting it leads to some corner-case issues, like the CMD53 failing, which is used to implement SDIO packet aggregation. Signed-off-by: Maxime Ripard

[PATCH v5 7/13] mmc: sunxi: Add more debug informations

Add a bit more debug messages that can be helpful when debugging the clock setup. Also fill the actual_clock field in struct mmc_host to report properly the current frequency in debugfs. Signed-off-by: Maxime Ripard Tested-by: Florian Vaussard --- drivers/mmc/host/sunxi-mmc.c | 23

[PATCH v5 8/13] arm64: allwinner: a64: Add MMC nodes

From: Andre Przywara The A64 has 3 MMC controllers, one of them being especially targeted to eMMC. Among other things, it has a data strobe signal and a 8 bits data width. The two other are more usual controllers that will have a 4 bits width at most and no data strobe

[PATCH v5 8/13] arm64: allwinner: a64: Add MMC nodes

From: Andre Przywara The A64 has 3 MMC controllers, one of them being especially targeted to eMMC. Among other things, it has a data strobe signal and a 8 bits data width. The two other are more usual controllers that will have a 4 bits width at most and no data strobe signal, which limits it

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

Hi Mark, On 01/27/2017 09:38 AM, Mark Rutland wrote: > On Wed, Jan 25, 2017 at 10:52:30AM -0500, Christopher Covington wrote: >> The Qualcomm Datacenter Technologies Falkor v1 CPU may allocate TLB entries >> using an incorrect ASID when TTBRx_EL1 is being updated. When the erratum >> is

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

Hi Mark, On 01/27/2017 09:38 AM, Mark Rutland wrote: > On Wed, Jan 25, 2017 at 10:52:30AM -0500, Christopher Covington wrote: >> The Qualcomm Datacenter Technologies Falkor v1 CPU may allocate TLB entries >> using an incorrect ASID when TTBRx_EL1 is being updated. When the erratum >> is

[HMM v17 13/14] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE

This introduce a simple struct and associated helpers for device driver to use when hotpluging un-addressable device memory as ZONE_DEVICE. It will find a unuse physical address range and trigger memory hotplug for it which allocates and initialize struct page for the device memory.

[HMM v17 13/14] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE

This introduce a simple struct and associated helpers for device driver to use when hotpluging un-addressable device memory as ZONE_DEVICE. It will find a unuse physical address range and trigger memory hotplug for it which allocates and initialize struct page for the device memory.

[PATCH v5 5/13] mmc: sunxi: Mask DATA0 when updating the clock

The A64 MMC controllers need DATA0 to be masked while updating the clock, otherwise any subsequent command will result in a timeout. It's not really clear at this point what DATA0 is exactly, but this behaviour is present in Allwinner's tree, and has been suggested by Allwinner engineers as fixes

[PATCH v5 5/13] mmc: sunxi: Mask DATA0 when updating the clock

The A64 MMC controllers need DATA0 to be masked while updating the clock, otherwise any subsequent command will result in a timeout. It's not really clear at this point what DATA0 is exactly, but this behaviour is present in Allwinner's tree, and has been suggested by Allwinner engineers as fixes

[HMM v17 10/14] mm/hmm/mirror: helper to snapshot CPU page table

This does not use existing page table walker because we want to share same code for our page fault handler. Signed-off-by: Jérôme Glisse Signed-off-by: Evgeny Baskakov Signed-off-by: John Hubbard Signed-off-by: Mark Hairgrove

[HMM v17 09/14] mm/hmm/mirror: mirror process address space on device with HMM helpers

This is a heterogeneous memory management (HMM) process address space mirroring. In a nutshell this provide an API to mirror process address space on a device. This boils down to keeping CPU and device page table synchronize (we assume that both device and CPU are cache coherent like PCIe device

[HMM v17 10/14] mm/hmm/mirror: helper to snapshot CPU page table

This does not use existing page table walker because we want to share same code for our page fault handler. Signed-off-by: Jérôme Glisse Signed-off-by: Evgeny Baskakov Signed-off-by: John Hubbard Signed-off-by: Mark Hairgrove Signed-off-by: Sherry Cheung Signed-off-by: Subhash Gutti ---

[HMM v17 09/14] mm/hmm/mirror: mirror process address space on device with HMM helpers

This is a heterogeneous memory management (HMM) process address space mirroring. In a nutshell this provide an API to mirror process address space on a device. This boils down to keeping CPU and device page table synchronize (we assume that both device and CPU are cache coherent like PCIe device

[HMM v17 04/14] mm/ZONE_DEVICE/x86: add support for un-addressable device memory

It does not need much, just skip populating kernel linear mapping for range of un-addressable device memory (it is pick so that there is no physical memory resource overlapping it). All the logic is in share mm code. Only support x86-64 as this feature doesn't make much sense with constrained

[HMM v17 04/14] mm/ZONE_DEVICE/x86: add support for un-addressable device memory

It does not need much, just skip populating kernel linear mapping for range of un-addressable device memory (it is pick so that there is no physical memory resource overlapping it). All the logic is in share mm code. Only support x86-64 as this feature doesn't make much sense with constrained

[HMM v17 12/14] mm/hmm/migrate: support un-addressable ZONE_DEVICE page in migration

Allow to unmap and restore special swap entry of un-addressable ZONE_DEVICE memory. Signed-off-by: Jérôme Glisse --- include/linux/migrate.h | 2 + mm/migrate.c| 134 +--- mm/rmap.c | 47

[HMM v17 12/14] mm/hmm/migrate: support un-addressable ZONE_DEVICE page in migration

Allow to unmap and restore special swap entry of un-addressable ZONE_DEVICE memory. Signed-off-by: Jérôme Glisse --- include/linux/migrate.h | 2 + mm/migrate.c| 134 +--- mm/rmap.c | 47 + 3 files changed,

[HMM v17 14/14] mm/hmm/devmem: dummy HMM device for ZONE_DEVICE memory v2

This introduce a dummy HMM device class so device driver can use it to create hmm_device for the sole purpose of registering device memory. It is usefull to device driver that want to manage multiple physical device memory under same struct device umbrella. Changed since v1: - Improve commit

[HMM v17 14/14] mm/hmm/devmem: dummy HMM device for ZONE_DEVICE memory v2

This introduce a dummy HMM device class so device driver can use it to create hmm_device for the sole purpose of registering device memory. It is usefull to device driver that want to manage multiple physical device memory under same struct device umbrella. Changed since v1: - Improve commit

[HMM v17 02/14] mm/ZONE_DEVICE/free-page: callback when page is freed v2

When a ZONE_DEVICE page refcount reach 1 it means it is free and nobody is holding a reference on it (only device to which the memory belong do). Add a callback and call it when that happen so device driver can implement their own free page management. Changed since v1: - Do not update

[HMM v17 01/14] mm/memory/hotplug: convert device bool to int to allow for more flags v2

When hotpluging memory we want more informations on the type of memory and its properties. Replace the device boolean flag by an int and define a set of flags. New property for device memory is an opt-in flag to allow page migration from and to a ZONE_DEVICE. Existing user of ZONE_DEVICE are not

[HMM v17 02/14] mm/ZONE_DEVICE/free-page: callback when page is freed v2

When a ZONE_DEVICE page refcount reach 1 it means it is free and nobody is holding a reference on it (only device to which the memory belong do). Add a callback and call it when that happen so device driver can implement their own free page management. Changed since v1: - Do not update

[HMM v17 01/14] mm/memory/hotplug: convert device bool to int to allow for more flags v2

When hotpluging memory we want more informations on the type of memory and its properties. Replace the device boolean flag by an int and define a set of flags. New property for device memory is an opt-in flag to allow page migration from and to a ZONE_DEVICE. Existing user of ZONE_DEVICE are not

[HMM v17 00/14] HMM (Heterogeneous Memory Management) v17

Cliff note: HMM offers 2 things (each standing on its own). First it allows to use device memory transparently inside any process without any modifications to process program code. Second it allows to mirror process address space on a device. Change since v16: - move HMM unaddressable device

[HMM v17 00/14] HMM (Heterogeneous Memory Management) v17

Cliff note: HMM offers 2 things (each standing on its own). First it allows to use device memory transparently inside any process without any modifications to process program code. Second it allows to mirror process address space on a device. Change since v16: - move HMM unaddressable device

Re: [PATCH 06/11] clk: sunxi-ng: Add A80 USB CCU

On Tue, Jan 24, 2017 at 10:32:25AM +0800, Chen-Yu Tsai wrote: > Add support for the USB clock controls found on the A80. > > Signed-off-by: Chen-Yu Tsai > --- > .../devicetree/bindings/clock/sun9i-usb.txt| 24 > drivers/clk/sunxi-ng/Makefile |

Re: [PATCH 06/11] clk: sunxi-ng: Add A80 USB CCU

On Tue, Jan 24, 2017 at 10:32:25AM +0800, Chen-Yu Tsai wrote: > Add support for the USB clock controls found on the A80. > > Signed-off-by: Chen-Yu Tsai > --- > .../devicetree/bindings/clock/sun9i-usb.txt| 24 > drivers/clk/sunxi-ng/Makefile | 1 + >

Re: seccomp: dump core when using SECCOMP_RET_KILL

On Wed, Jan 25, 2017 at 12:05 PM, Kees Cook wrote: > On Tue, Jan 24, 2017 at 4:53 PM, Andrei Vagin wrote: >> Hi, >> >> One of CRIU tests fails with this patch: >> https://github.com/xemul/criu/blob/master/test/zdtm/static/seccomp_filter_tsync.c >> >>

Re: seccomp: dump core when using SECCOMP_RET_KILL

On Wed, Jan 25, 2017 at 12:05 PM, Kees Cook wrote: > On Tue, Jan 24, 2017 at 4:53 PM, Andrei Vagin wrote: >> Hi, >> >> One of CRIU tests fails with this patch: >> https://github.com/xemul/criu/blob/master/test/zdtm/static/seccomp_filter_tsync.c >> >> Before this patch only a thread which called

Re: [PATCH 0/2] PCI: iproc: MPS fix and quirks

The entire patch set looks good to me. Thanks! Acked-by: Ray Jui On 1/27/2017 1:44 PM, Jon Mason wrote: > A patch that corrects an issue where the MPS could not be set, and > another that fixes some quirks in the PAXC > > Jon Mason (2): > PCI: iproc: allow the MPS to be

Re: [PATCH 0/2] PCI: iproc: MPS fix and quirks

The entire patch set looks good to me. Thanks! Acked-by: Ray Jui On 1/27/2017 1:44 PM, Jon Mason wrote: > A patch that corrects an issue where the MPS could not be set, and > another that fixes some quirks in the PAXC > > Jon Mason (2): > PCI: iproc: allow the MPS to be set > PCI: Add

[PATCH v5 12/13] arm64: allwinner: a64: add UART1 pin nodes

From: Andre Przywara On many boards UART1 connects to a Bluetooth chip, so add the pinctrl nodes for the only pins providing access to that UART. That includes those pins for hardware flow control (RTS/CTS). Signed-off-by: Andre Przywara

[PATCH v5 11/13] arm64: allwinner: pine64: add MMC support

From: Andre Przywara All Pine64 boards connect an micro-SD card slot to the first MMC controller. Enable the respective DT node and specify the (always-on) regulator and card-detect pin. As a micro-SD slot does not feature a write-protect switch, we disable this feature.

[PATCH v5 0/13] arm64: allwinner: a64: Enable MMC support

Hi, Here is a new attempt at getting the MMC controllers running, following the work done by Andre. This has been tested on a board with one SDIO device (a Marvell WiFi chip) and a Kingston eMMC with 1.8V IOs. For SDIO, the HS DDR mode works just fine. That serie also enables the SDR104 mode to

[PATCH v5 12/13] arm64: allwinner: a64: add UART1 pin nodes

From: Andre Przywara On many boards UART1 connects to a Bluetooth chip, so add the pinctrl nodes for the only pins providing access to that UART. That includes those pins for hardware flow control (RTS/CTS). Signed-off-by: Andre Przywara Signed-off-by: Maxime Ripard ---

[PATCH v5 11/13] arm64: allwinner: pine64: add MMC support

From: Andre Przywara All Pine64 boards connect an micro-SD card slot to the first MMC controller. Enable the respective DT node and specify the (always-on) regulator and card-detect pin. As a micro-SD slot does not feature a write-protect switch, we disable this feature. Signed-off-by: Andre

[PATCH v5 0/13] arm64: allwinner: a64: Enable MMC support

Hi, Here is a new attempt at getting the MMC controllers running, following the work done by Andre. This has been tested on a board with one SDIO device (a Marvell WiFi chip) and a Kingston eMMC with 1.8V IOs. For SDIO, the HS DDR mode works just fine. That serie also enables the SDR104 mode to

[PATCH v5 1/13] mmc: sunxi: Fix clock frequency change sequence

The SD specification documents that the clock frequency should only be changed once gated (Section 3.2.3 - SD Clock Frequency Change Sequence). The current code first modifies the parent clock, gates it and then modifies the internal divider. This means that since the parent clock rate might be

[PATCH v5 1/13] mmc: sunxi: Fix clock frequency change sequence

The SD specification documents that the clock frequency should only be changed once gated (Section 3.2.3 - SD Clock Frequency Change Sequence). The current code first modifies the parent clock, gates it and then modifies the internal divider. This means that since the parent clock rate might be

[PATCH v5 10/13] arm64: allwinner: a64: Increase the MMC max frequency

The eMMC controller seem to have a maximum frequency of 200MHz, while the regular MMC controllers are capped at 150MHz. Since older SoCs cannot go that high, we cannot change the default maximum frequency, but fortunately for us we have a property for that in the DT. This also has the side

[PATCH v5 10/13] arm64: allwinner: a64: Increase the MMC max frequency

The eMMC controller seem to have a maximum frequency of 200MHz, while the regular MMC controllers are capped at 150MHz. Since older SoCs cannot go that high, we cannot change the default maximum frequency, but fortunately for us we have a property for that in the DT. This also has the side

[PATCH 0/2] PCI: iproc: MPS fix and quirks

A patch that corrects an issue where the MPS could not be set, and another that fixes some quirks in the PAXC Jon Mason (2): PCI: iproc: allow the MPS to be set PCI: Add quirk entry for NS2 PAXC PCI drivers/pci/host/pcie-iproc.c | 5 - drivers/pci/quirks.c | 21

[PATCH 0/2] PCI: iproc: MPS fix and quirks

A patch that corrects an issue where the MPS could not be set, and another that fixes some quirks in the PAXC Jon Mason (2): PCI: iproc: allow the MPS to be set PCI: Add quirk entry for NS2 PAXC PCI drivers/pci/host/pcie-iproc.c | 5 - drivers/pci/quirks.c | 21

[PATCH v2 2/5] userfaultfd: non-cooperative: add event for memory unmaps

When a non-cooperative userfaultfd monitor copies pages in the background, it may encounter regions that were already unmapped. Addition of UFFD_EVENT_UNMAP allows the uffd monitor to track precisely changes in the virtual memory layout. Since there might be different uffd contexts for the

[PATCH v2 2/5] userfaultfd: non-cooperative: add event for memory unmaps

When a non-cooperative userfaultfd monitor copies pages in the background, it may encounter regions that were already unmapped. Addition of UFFD_EVENT_UNMAP allows the uffd monitor to track precisely changes in the virtual memory layout. Since there might be different uffd contexts for the

Re: [PATCH 3/3] perf: Allow kernel filters on cpu events

On 27 January 2017 at 05:31, Alexander Shishkin wrote: > Mathieu Poirier writes: > >> On Thu, Jan 26, 2017 at 11:40:57AM +0200, Alexander Shishkin wrote: >>> +if (!ifh->nr_file_filters) >>> +return; >> >> Is this

Re: [PATCH 3/3] perf: Allow kernel filters on cpu events

On 27 January 2017 at 05:31, Alexander Shishkin wrote: > Mathieu Poirier writes: > >> On Thu, Jan 26, 2017 at 11:40:57AM +0200, Alexander Shishkin wrote: >>> +if (!ifh->nr_file_filters) >>> +return; >> >> Is this mandatory or an optimisation to avoid circling through a list of

Re: [PATCH v4 3/3] p54: convert to sysdata API

On Fri, Jan 27, 2017 at 12:53:38PM -0800, Linus Torvalds wrote: > On Fri, Jan 27, 2017 at 10:23 AM, Luis R. Rodriguez wrote: > >> So I'm really not seeing why you want to make these conversions that > >> just make code worse. > > > > The real goal here was first to actually

Re: [PATCH v4 3/3] p54: convert to sysdata API

On Fri, Jan 27, 2017 at 12:53:38PM -0800, Linus Torvalds wrote: > On Fri, Jan 27, 2017 at 10:23 AM, Luis R. Rodriguez wrote: > >> So I'm really not seeing why you want to make these conversions that > >> just make code worse. > > > > The real goal here was first to actually provide a flexible API

[GIT PULL] MD update for 4.10-rc6

Hi, Please pull MD fixes. This pull fixes several corner cases for raid5 cache, which is merged into this cycle. Thanks, Shaohua The following changes since commit 557ed56cc75e0a33c15ba438734a280bac23bd32: Merge tag 'sound-4.10-rc4' of

Re: [PATCH 1/3] pinctrl: intel: Add support for hardware debouncer

e system] > > url: > https://github.com/0day-ci/linux/commits/Mika-Westerberg/pinctrl-intel-Add-support-for-hardware-debouncer/20170127-181144 > base: > https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git > for-next > config: x86_64-randconfig-s5-0127185

[GIT PULL] MD update for 4.10-rc6

Hi, Please pull MD fixes. This pull fixes several corner cases for raid5 cache, which is merged into this cycle. Thanks, Shaohua The following changes since commit 557ed56cc75e0a33c15ba438734a280bac23bd32: Merge tag 'sound-4.10-rc4' of

Re: [PATCH 1/3] pinctrl: intel: Add support for hardware debouncer

e system] > > url: > https://github.com/0day-ci/linux/commits/Mika-Westerberg/pinctrl-intel-Add-support-for-hardware-debouncer/20170127-181144 > base: > https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git > for-next > config: x86_64-randconfig-s5-0127185

Re: [PATCH] IB/cma: Fix reversed test

On Fri, 2017-01-27 at 14:15 +0100, Christophe JAILLET wrote: > This test looks reverted. > We should log an error message only if 'ib_attach_mcast()' fails. > > Signed-off-by: Christophe JAILLET > --- > drivers/infiniband/core/cma.c | 2 +- > 1 file changed, 1

Re: [PATCH] IB/cma: Fix reversed test

On Fri, 2017-01-27 at 14:15 +0100, Christophe JAILLET wrote: > This test looks reverted. > We should log an error message only if 'ib_attach_mcast()' fails. > > Signed-off-by: Christophe JAILLET > --- > drivers/infiniband/core/cma.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >

<    1   2   3   4   5   6   7   8   9   10   >