[PATCH v4 1/2] PCI: Add tango MSI controller support

The MSI controller in Tango supports 256 message-signaled interrupts, and a single doorbell address. Signed-off-by: Marc Gonzalez --- drivers/pci/host/pcie-tango.c | 232 ++ 1 file changed, 232

[PATCH v4 0/2] Tango PCIe controller support

Hello, This patch was split in two, to ease review of two orthogonal parts (MSI controller and host bridge). NB: the patch is just split in two where host bridge support starts. Changes from v3 to v4 In the MSI part: - Support 256 MSIs instead of only 32 - Define tango_{ack,mask,unmask}

[PATCH v4 2/2] PCI: Add tango PCIe host bridge support

This driver is required to work around several hardware bugs in the PCIe controller. NB: Revision 1 does not support legacy interrupts, or IO space. Signed-off-by: Marc Gonzalez --- Documentation/devicetree/bindings/pci/tango-pcie.txt | 32

Re: [PATCH] timer: fix timer_migration to accept only 0 and 1

On Wed, 19 Apr 2017, Myungho Jung wrote: > Error is not shown by setting invalid value to timer_migration. Valid > values for timer_migration should be restricted to 0 and 1. Testcase for > this bug is ltp/runpwtests06. While I agree with the change, I disagree with the changelog. Where is the

Re: [LTP] [lkp-robot] [KEYS] bdf7c0f8bf: ltp.add_key02.fail

Hi! > > commit: bdf7c0f8bf282ba44827ce3c7fd7936c8e90a18a ("KEYS: fix dereferencing > > NULL payload with nonzero length") > > url: > > https://github.com/0day-ci/linux/commits/Eric-Biggers/KEYS-fix-dereferencing-NULL-payload-with-nonzero-length/20170403-102013 > > base: > >

Re: [PATCH v5 1/4] printk/nmi: generic solution for safe printk in NMI

On Thu 2017-04-20 12:31:12, Sergey Senozhatsky wrote: > Hello Steven, > > On (04/19/17 13:13), Steven Rostedt wrote: > > > printk() takes some locks and could not be used a safe way in NMI context. > > > > I just found a problem with this solution. It kills ftrace dumps from > > NMI context :-(

[PATCH v2 9/9] MAINTAINERS: add Gilad BY as ccree maintainer

I work for Arm on maintaining the TrustZone CryptoCell driver. Signed-off-by: Gilad Ben-Yossef --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 676c139..f21caa1 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -3066,6

[PATCH v2 3/9] staging: ccree: add skcipher support

Add CryptoCell skcipher support Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/Kconfig |8 + drivers/staging/ccree/Makefile |2 +- drivers/staging/ccree/cc_crypto_ctx.h | 21 + drivers/staging/ccree/ssi_buffer_mgr.c | 147

[tip:timers/core] arm64/arch_timer: Mark errata handlers as __maybe_unused

Commit-ID: eb64522100a1d4adc89bce11b935a30c4401e234 Gitweb: http://git.kernel.org/tip/eb64522100a1d4adc89bce11b935a30c4401e234 Author: Arnd Bergmann AuthorDate: Wed, 19 Apr 2017 19:37:09 +0200 Committer: Thomas Gleixner CommitDate: Thu, 20 Apr 2017

[tip:timers/core] MIPS/Malta: Probe gic-timer via devicetree

Commit-ID: 4287adec7212d48fb878a45400fd7e11a198462c Gitweb: http://git.kernel.org/tip/4287adec7212d48fb878a45400fd7e11a198462c Author: Matt Redfearn AuthorDate: Wed, 19 Apr 2017 13:26:45 +0100 Committer: Thomas Gleixner CommitDate: Thu, 20

Re: [PATCH] mmc: sdio: Fix sdio wait busy implement limitation

On 17 April 2017 at 10:09, wrote: > From: Jiajie Hao > > The host may issue an I/O abort by writing to the CCCR at any time > during I/O read operation via CMD52. And host may need suspend > transcation during write busy stage in SDIO

Re: [PATCH] mm/madvise: Dont poison entire HugeTLB page for single page errors

Hi Anshuman, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc7 next-20170420] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Anshuman-Khandual/mm-madvise-Dont-poison

Re: [PATCH] tools: iio: add ability to pass kernel headers

On Tuesday 18 April 2017 03:42 PM, Sekhar Nori wrote: > Hi Jonathan, Randy, > > On Friday 14 April 2017 08:53 PM, Jonathan Cameron wrote: >> On 14/04/17 16:23, Randy Dunlap wrote: >>> On 04/14/17 07:42, Jonathan Cameron wrote: On 11/04/17 12:06, Sekhar Nori wrote: > Very often,

[PATCH] iommu/ipmmu-vmsa: Fix pgsize_bitmap semicolon typo

From: Magnus Damm Fix comman-instead-of-semicolon typo error present in the latest version of the IPMMU driver. Will in the future be rolled into next driver update. Signed-off-by: Magnus Damm --- Applies on top of

Re: [PATCH v4 02/11] clk: sunxi-ng: add support for DE2 CCU

On Sun, Apr 16, 2017 at 08:08:40PM +0800, Icenowy Zheng wrote: > The "Display Engine 2.0" in Allwinner newer SoCs contains a clock > management unit for its subunits, like the DE CCU in A80. > > Add a sunxi-ng style driver for it. > > Signed-off-by: Icenowy Zheng > --- >

[PATCH] goldfish_pipe: An implementation of more parallel pipe

From: Jin Qian This is a driver code for a redesigned android pipe. Currently it works for x86 and x64 emulators with the following performance results: ADB push to /dev/null, Ubuntu, 400 MB file, times are for (1 / 10 / 100) parallel adb commands x86 adb push:

[tip:x86/cpu] x86/intel_rdt: Fix padding when resource is enabled via mount

Commit-ID: adcbdd70309dba5a12a9d8158deb6a62a6d5fc98 Gitweb: http://git.kernel.org/tip/adcbdd70309dba5a12a9d8158deb6a62a6d5fc98 Author: Vikas Shivappa AuthorDate: Wed, 19 Apr 2017 16:50:02 -0700 Committer: Thomas Gleixner CommitDate:

[tip:x86/cpu] x86/intel_rdt: Trim whitespace while parsing schemata input

Commit-ID: 634b0e0491d6f6e882b922eb41c278d01a743bab Gitweb: http://git.kernel.org/tip/634b0e0491d6f6e882b922eb41c278d01a743bab Author: Vikas Shivappa AuthorDate: Wed, 19 Apr 2017 16:50:03 -0700 Committer: Thomas Gleixner CommitDate:

Re: RFC: WMI Enhancements

With Andy's conversion of WMI to the driver model the GUIDs should be our device ids. Which means WMI can support the dynamic device ID model, where you can echo a id to sysfs to bind an id - that way people could add the GUIDs on demand to the pass through driver if they need them even with the

Re: [PATCH v8 5/6] i2c: designware: add SLAVE mode functions

On 20-Apr-17 13:50, Jarkko Nikula wrote: > On 04/12/2017 07:47 PM, Luis Oliveira wrote: >> - Changes in Kconfig to enable I2C_DESIGNWARE_SLAVE support >> - Slave functions added to core library file >> - Slave abort sources added to common source file >> - New driver: i2c-designware-slave added >>

Re: [PATCH] nl80211: fix enumeration type

On 2017-04-20 00:22, Johannes Berg wrote: > On Wed, 2017-04-19 at 23:55 -0700, Stefan Agner wrote: >> Use type enum nl80211_rate_info for bitrate information. This fixes >> a warning when compiling with clang: >>   warning: implicit conversion from enumeration type 'enum >> nl80211_rate_info' >>  

Re: [PATCH 3.18 000/124] 3.18.50-stable review

On Thu, Apr 20, 2017 at 06:46:11AM -0700, Guenter Roeck wrote: > On 04/19/2017 11:34 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.18.50 release. > > There are 124 patches in this series, all will be posted as a response > > to this one. If anyone has

Re: Heads-up: two regressions in v4.11-rc series

On Thu, Apr 20, 2017 at 11:00:42AM +0200, Jesper Dangaard Brouer wrote: > Hi Linus, > > Just wanted to give a heads-up on two regressions in 4.11-rc series. > > (1) page allocator optimization revert > > Mel Gorman and I have been playing with optimizing the page allocator, > but Tariq spotted

Re: [PATCH v8 5/6] i2c: designware: add SLAVE mode functions

On 04/12/2017 07:47 PM, Luis Oliveira wrote: - Changes in Kconfig to enable I2C_DESIGNWARE_SLAVE support - Slave functions added to core library file - Slave abort sources added to common source file - New driver: i2c-designware-slave added - Changes in the Makefile to compile the

Re: [PATCH] RFC: serial: core: Dynamic minor support

On Thu, Apr 20, 2017 at 02:44:18PM +0200, Sjoerd Simons wrote: > On Thu, 2017-04-20 at 14:15 +0200, Greg Kroah-Hartman wrote: > > On Thu, Apr 20, 2017 at 02:03:57PM +0200, Sjoerd Simons wrote: > > > --- a/include/linux/serial_core.h > > > +++ b/include/linux/serial_core.h > > > @@ -31,6 +31,8 @@ >

[PATCH] platform/x86: INT33FE: add i2c dependency

With CONFIG_I2C=m and CONFIG_INTEL_CHT_INT33FE=y we see the following link errors: drivers/built-in.o: In function 'cht_int33fe_remove': intel_cht_int33fe.c:(.text+0x391f6e): undefined reference to 'i2c_unregister_device' intel_cht_int33fe.c:(.text+0x391f76): undefined reference to

[PATCH v2 6/9] staging: ccree: add FIPS support

Add FIPS mode support to CryptoCell driver Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/Kconfig |9 + drivers/staging/ccree/Makefile |1 + drivers/staging/ccree/ssi_aead.c|6 + drivers/staging/ccree/ssi_cipher.c |

[PATCH v2 0/9] staging: ccree: add Arm TrustZone CryptoCell REE driver

Arm TrustZone CryptoCell 700 is a family of cryptographic hardware accelerators. It is supported by a long lived series of out of tree drivers, which I am now in the process of unifying and upstreaming. This is the first drop, supporting the new CryptoCell 712 REE. The code still needs some

Re: [v6 PATCH 09/21] x86/insn-eval: Add functions to get default operand and address sizes

On Tue, Mar 07, 2017 at 04:32:42PM -0800, Ricardo Neri wrote: > These functions read the default values of the address and operand sizes > as specified in the segment descriptor. This information is determined > from the D and L bits. Hence, it can be used for both IA-32e 64-bit and > 32-bit

[PATCH v2 7/9] staging: ccree: add TODO list

Add TODO list for moving out of staging tree for ccree crypto driver Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/TODO | 28 1 file changed, 28 insertions(+) create mode 100644 drivers/staging/ccree/TODO diff --git

[PATCH v2 8/9] staging: ccree: add DT bindings for Arm CryptoCell

This adds DT bindings for the Arm TrustZone CryptoCell cryptographic accelerator IP. Signed-off-by: Gilad Ben-Yossef --- .../devicetree/bindings/crypto/arm-cryptocell.txt | 27 ++ 1 file changed, 27 insertions(+) create mode 100644

[PATCH v2] net: arc_emac: switch to phy_start()/phy_stop()

Currently driver use phy_start_aneg() in arc_emac_open() to bring up PHY. But phy_start() function is more appropriate for this purposes. Besides that it call phy_start_aneg() as part of PHY startup sequence it also can correctly bring up PHY from error and suspended states. So the patch replace

Re: [PATCH v2 0/9] staging: ccree: add Arm TrustZone CryptoCell REE driver

On Thu, Apr 20, 2017 at 4:30 PM, Greg Kroah-Hartman wrote: > On Thu, Apr 20, 2017 at 04:12:54PM +0300, Gilad Ben-Yossef wrote: >> Arm TrustZone CryptoCell 700 is a family of cryptographic hardware >> accelerators. It is supported by a long lived series of out of tree

Re: [PATCH v2] dt-bindings: input: add bindings document for ar1021_i2c driver

On Fri, Apr 14, 2017 at 08:11:38AM +0200, Martin Kepplinger wrote: > Add a simple binding document describing the supported devices and the > I2C bus address. > > Signed-off-by: Martin Kepplinger > --- > > revision history > > v2: fixed subject

Re: WARNING: kernel stack regs at ffffc9000024fea8 in udevadm:92 has bad 'bp' value 00007fffc4614d30

On Thu, Apr 20, 2017 at 08:30:21AM -0500, Josh Poimboeuf wrote: > On Thu, Apr 20, 2017 at 01:06:10PM +0200, Borislav Petkov wrote: > > Hi, > > > > the splat below started appearing on one of the boxes here with > > rc7+tip/master from yesterday. > > > > Ideas? > > Thanks for reporting it. This

[PATCH 2/2] ring-buffer: Have ring_buffer_iter_empty() return true when empty

From: "Steven Rostedt (VMware)" I noticed that reading the snapshot file when it is empty no longer gives a status. It suppose to show the status of the snapshot buffer as well as how to allocate and use it. For example: ># cat snapshot # tracer: nop # # # * Snapshot

[PATCH 1/2] tracing: Allocate the snapshot buffer before enabling probe

From: "Steven Rostedt (VMware)" Currently the snapshot trigger enables the probe and then allocates the snapshot. If the probe triggers before the allocation, it could cause the snapshot to fail and turn tracing off. It's best to allocate the snapshot buffer first, and then

Re: [PATCH v4 01/11] dt-bindings: add binding for the Allwinner DE2 CCU

On Sun, Apr 16, 2017 at 08:08:39PM +0800, Icenowy Zheng wrote: > Allwinner "Display Engine 2.0" contains some clock controls in it. > > In order to add them as clock drivers, we need a device tree binding. > Add the binding here. > > Signed-off-by: Icenowy Zheng > --- > Changes

[PATCH 0/2] [GIT PULL] tracing: Two more small fixes

Linus, While continuing my development, I uncovered two more small bugs. One is a race condition when enabling the snapshot function probe trigger. It enables the probe before allocating the snapshot, and if the probe triggers first, it stops tracing with a warning that the snapshot buffer was

Re: [PATCH v4 03/11] dt-bindings: add bindings for DE2 on V3s SoC

On Sun, Apr 16, 2017 at 08:08:41PM +0800, Icenowy Zheng wrote: > Allwinner V3s SoC have a display engine which have a different pipeline > with older SoCs. > > Add document for it (new compatibles and the new "mixer" part). > > Signed-off-by: Icenowy Zheng > --- > Changes in

[PATCH v2 01/16] doc: fpga: update documents for the FPGA API

The FPGA manager has been simplified to have a single fpga_mgr_load function which replaces the three fpga_mgr_*load* functions. The parameters presenting the FPGA image have been added to struct fpga_image_info. Additional functions have been added to alloc/free fpga_image_info. Getting a FPGA

Re: [PATCH] ligtnvm: fix double blk_put_queue on same queue

On Thu, Apr 20 2017, Matias Bjørling wrote: > On 04/19/2017 11:47 PM, Rakesh Pandit wrote: > >On an error path in NVM_DEV_CREATE ioctl blk_put_queue is being called > >twice: one via blk_cleanup_queue and another via put_disk. Straight fix > >seems to remove queue pointer so that disk_release

Re: [PATCH] ligtnvm: fix double blk_put_queue on same queue

On 04/20/2017 04:09 PM, Jens Axboe wrote: On Thu, Apr 20 2017, Matias Bjørling wrote: On 04/19/2017 11:47 PM, Rakesh Pandit wrote: On an error path in NVM_DEV_CREATE ioctl blk_put_queue is being called twice: one via blk_cleanup_queue and another via put_disk. Straight fix seems to remove

Re: [RFC 1/2] dt-bindings: add mmio-based syscon mux controller DT bindings

On 2017-04-20 15:32, Peter Rosin wrote: > On 2017-04-20 00:09, Rob Herring wrote: >> On Thu, Apr 13, 2017 at 05:48:11PM +0200, Philipp Zabel wrote: >>> This adds device tree binding documentation for mmio-based syscon >>> multiplexers controlled by a single bitfield in a syscon register >>> range.

[tip:irq/core] irqchip/mips-gic: Replace static map with dynamic

Commit-ID: 8ada00a650ec7ec639fb72964f0e4eba928786f8 Gitweb: http://git.kernel.org/tip/8ada00a650ec7ec639fb72964f0e4eba928786f8 Author: Matt Redfearn AuthorDate: Thu, 20 Apr 2017 10:07:36 +0100 Committer: Thomas Gleixner CommitDate: Thu, 20

Re: [PATCH] ligtnvm: fix double blk_put_queue on same queue

On Thu, Apr 20 2017, Matias Bjørling wrote: > On 04/20/2017 04:09 PM, Jens Axboe wrote: > >On Thu, Apr 20 2017, Matias Bjørling wrote: > >>On 04/19/2017 11:47 PM, Rakesh Pandit wrote: > >>>On an error path in NVM_DEV_CREATE ioctl blk_put_queue is being called > >>>twice: one via blk_cleanup_queue

Re: [PATCH] ALSA: firewire-motu: mark trace helpers as __maybe_unused

On Thu, 20 Apr 2017 14:52:13 +0200, Takashi Sakamoto wrote: > > Hi, > > On 2017年04月20日 19:51, Takashi Iwai wrote: > > On Wed, 19 Apr 2017 19:51:29 +0200, > > Arnd Bergmann wrote: > >> > >> Two functions were introduced for the purpose of tracing but cause warnings > >> when tracing is disabled:

[PATCH] fs:orangefs:orangefs-debug, orangefs-kernel: Fixing warning issues and use ARRAY_SIZE

Fix warning issues produced by kbuild test and use a ARRAY_SIZE kernel defined macro more safe and remove unnecessary cast when __KERNEL__ is defined. Signed-off-by: Karim Eshapa --- fs/orangefs/orangefs-debug.h | 6 ++ fs/orangefs/orangefs-kernel.h | 2 ++ 2 files

Re: [PATCH] Revert "cpuidle: Replace ktime_get() with local_clock()"

On Thu, Apr 20, 2017 at 03:44:47PM +0300, ville.syrj...@linux.intel.com wrote: > From: Ville Syrjälä > > This reverts commit e93e59ce5b85e6c2b444f09fd1f707274ec066dc. > > The TSC stops in deeper C states, On some old hardware (Core2 era and before) only. You've

[PATCH v2 4/9] staging: ccree: add IV generation support

Add CryptoCell IV hardware generation support. This patch adds the needed support to drive the HW but does not expose the ability via the kernel crypto API yet. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/Makefile | 2 +-

Re: [PATCH v4 02/21] linux/io.h: add PCI config space remap interface

On Thu, Apr 20, 2017 at 5:51 AM, Lorenzo Pieralisi wrote: > [+ Michael] > > On Wed, Apr 19, 2017 at 05:48:51PM +0100, Lorenzo Pieralisi wrote: >> The PCI specifications (Rev 3.0, 3.2.5 "Transaction Ordering and >> Posting") mandate non-posted configuration transactions.

Re: [PATCH v2] mdio_bus: Issue GPIO RESET to PHYs.

On Thu, Apr 20, 2017 at 11:39:20AM +0300, Roger Quadros wrote: > Some boards [1] leave the PHYs at an invalid state > during system power-up or reset thus causing unreliability > issues with the PHY which manifests as PHY not being detected > or link not functional. To fix this, these PHYs need to

[PATCH v2 2/9] staging: ccree: add ahash support

Add CryptoCell async. hash and HMAC support. Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/Kconfig |6 + drivers/staging/ccree/Makefile |2 +- drivers/staging/ccree/cc_crypto_ctx.h | 22 + drivers/staging/ccree/hash_defs.h | 78

Re: linux-next: manual merge of the scsi-mkp tree with the char-misc tree

On 04/07/2017 10:50 PM, Bart Van Assche wrote: > On Fri, 2017-04-07 at 13:29 -0600, Logan Gunthorpe wrote: >> On 07/04/17 09:49 AM, Bart Van Assche wrote: >>> Sorry that I had not yet noticed Logan's patch series. Should my two >>> patches that conflict with Logan's patch series be dropped and

[tip:x86/irq] x86/irq: Optimize free vector check in the CPU offline path

Commit-ID: c0edbd4a1693600d6eb9e2faad452638c35391f7 Gitweb: http://git.kernel.org/tip/c0edbd4a1693600d6eb9e2faad452638c35391f7 Author: Chen Yu AuthorDate: Sun, 16 Apr 2017 23:43:30 +0800 Committer: Thomas Gleixner CommitDate: Thu, 20 Apr 2017

Re: [PATCH] of: introduce event tracepoints for dynamic device_node lifecyle

On Wed, 19 Apr 2017 22:24:58 -0700 Tyrel Datwyler wrote: > On 04/19/2017 07:33 PM, Steven Rostedt wrote: > > On Wed, 19 Apr 2017 16:27:10 -0700 > > Tyrel Datwyler wrote: > > > >> # echo stacktrace >

Re: [PATCH 3.18 049/124] tty/serial: atmel: fix race condition (TX+DMA)

On Thu, Apr 20, 2017 at 09:46:03AM +0200, Richard Genoud wrote: > On 20/04/2017 08:35, Greg Kroah-Hartman wrote: > > 3.18-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Richard Genoud > > > > commit

Re: [PATCH v2 1/9] staging: ccree: introduce CryptoCell HW driver

On Thu, Apr 20, 2017 at 4:33 PM, Greg Kroah-Hartman wrote: > On Thu, Apr 20, 2017 at 04:12:55PM +0300, Gilad Ben-Yossef wrote: >> +++ b/drivers/staging/ccree/bsp.h >> @@ -0,0 +1,21 @@ >> +/* >> + * Copyright (C) 2012-2016 ARM Limited or its affiliates. >> + * >> + *

Re: [PATCH v2 3/3] mmc: sdio: mediatek: Support SDIO feature

On 18 April 2017 at 12:13, Yong Mao wrote: > From: yong mao > > 1. Add irqlock to protect accessing the shared register > 2. Implement enable_sdio_irq interface > 3. Add msdc_recheck_sdio_irq mechanism to make sure all interrupts >can be

Re: [PATCH v2 1/2] dt-binding: regulator: anatop: make regulator name property required

On Fri, Apr 14, 2017 at 10:30:33PM +0800, Dong Aisheng wrote: > We actually can't allow the missing of the regualor name, thus update > the binding doc to make regulator-name property to be required. > > Cc: Rob Herring > Cc: Mark Rutland > Cc:

Re: [PATCH] mmc: dw_mmc: hide clock message when card is resuming

> 20 апр. 2017 г., в 13:06, Jaehoon Chung написал(а): > > I think you are not using the latest kernel. which version do you use? > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ce69e2fea093b7fa3991c87849c4955cd47796c9 > > Could you

Re: [PATCH v2] mdio_bus: Issue GPIO RESET to PHYs.

On 20/04/17 16:13, Andrew Lunn wrote: > On Thu, Apr 20, 2017 at 11:39:20AM +0300, Roger Quadros wrote: >> Some boards [1] leave the PHYs at an invalid state >> during system power-up or reset thus causing unreliability >> issues with the PHY which manifests as PHY not being detected >> or link not

Re: [PATCH v2 1/9] staging: ccree: introduce CryptoCell HW driver

On Thu, Apr 20, 2017 at 04:40:56PM +0300, Gilad Ben-Yossef wrote: > On Thu, Apr 20, 2017 at 4:33 PM, Greg Kroah-Hartman > wrote: > > On Thu, Apr 20, 2017 at 04:12:55PM +0300, Gilad Ben-Yossef wrote: > >> +++ b/drivers/staging/ccree/bsp.h > >> @@ -0,0 +1,21 @@ > >> +/*

[tip:irq/urgent] genirq/affinity: Fix calculating vectors to assign

Commit-ID: b72f8051f34b8164a62391e3676edc34523c5952 Gitweb: http://git.kernel.org/tip/b72f8051f34b8164a62391e3676edc34523c5952 Author: Keith Busch AuthorDate: Wed, 19 Apr 2017 19:51:10 -0400 Committer: Thomas Gleixner CommitDate: Thu, 20 Apr

[tip:x86/cpu] x86/intel_rdt: Return error for incorrect resource names in schemata

Commit-ID: 4797b7dfdfcf457075c36743d71e2b0feeaaa20f Gitweb: http://git.kernel.org/tip/4797b7dfdfcf457075c36743d71e2b0feeaaa20f Author: Vikas Shivappa AuthorDate: Wed, 19 Apr 2017 16:50:04 -0700 Committer: Thomas Gleixner CommitDate:

[PATCH][-next] block, bfq: don't dereference bic before null checking it

From: Colin Ian King The call to bfq_check_ioprio_change will dereference bic, however, the null check for bic is after this call. Move the the null check on bic to before the call to avoid any potential null pointer dereference issues. Detected by CoverityScan,

[tip:irq/core] irqchip/mips-gic: Remove device IRQ domain

Commit-ID: b87281e7f205eda08c911fdacd27d4d2f01daa09 Gitweb: http://git.kernel.org/tip/b87281e7f205eda08c911fdacd27d4d2f01daa09 Author: Paul Burton AuthorDate: Thu, 20 Apr 2017 10:07:35 +0100 Committer: Thomas Gleixner CommitDate: Thu, 20 Apr

Re: [PATCH 22/29] dt-bindings: Clarify compatible property for rockchip timers

On Sun, Apr 16, 2017 at 10:27:12PM +0200, Daniel Lezcano wrote: > From: Alexander Kochetkov > > Make all properties description in form '"rockchip,-timer", > "rockchip,rk3288-timer"' for all chips found in linux kernel. > > Suggested-by: Heiko Stübner >

[tip:irq/core] irqchip/mips-gic: Separate IPI reservation & usage tracking

Commit-ID: f8dcd9e81797ae24acc44c84f0eb3b9e6cee9791 Gitweb: http://git.kernel.org/tip/f8dcd9e81797ae24acc44c84f0eb3b9e6cee9791 Author: Paul Burton AuthorDate: Thu, 20 Apr 2017 10:07:34 +0100 Committer: Thomas Gleixner CommitDate: Thu, 20 Apr

[PATCH v2 08/16] fpga: region: check for child regions before allocing image info

During a device tree overlay pre-apply notification, the check for child FPGA regions can happen slightly earlier. This saves us from allocating the FPGA image info that just gets thrown away. This is a baby step in refactoring the FPGA region code to separate out common FPGA region code from

Re: [PATCH v4 1/1] pwm: pca9685: fix gpio-only operation.

> Taking above into consideration perhaps sleep is not quite good word > at all. By functional description it sounds like latency tolerance to > me. That's true, but the bit description in the chip datasheet is 'SLEEP'. (its real function is suspend/low power, but the chip designers called it

[PATCH v3 net-next] mdio_bus: Issue GPIO RESET to PHYs.

Some boards [1] leave the PHYs at an invalid state during system power-up or reset thus causing unreliability issues with the PHY which manifests as PHY not being detected or link not functional. To fix this, these PHYs need to be RESET via a GPIO connected to the PHY's RESET pin. Some boards

[PATCH v2 07/16] fpga: region: get mgr early on

Get the FPGA manager during region creation. This is a baby step in refactoring the FPGA region code to separate out common FPGA region code from FPGA region Device Tree overlay support. Signed-off-by: Alan Tull --- v2: split out from another patch ---

[PATCH v2 09/16] fpga: region: fix slow warning with more than one overlay

Prevent applying more than one overlay to a region. This fixes a slow warning that happens when more than one overlay is applied and then removed. Signed-off-by: Alan Tull --- v2: split out from another patch --- drivers/fpga/fpga-region.c | 5 + 1 file changed, 5

[PATCH v2 12/16] fpga: region: add fpga-region.h header

* Create fpga-region.h. * Export fpga_region_program_fpga. * Move struct fpga_region and other things to the header. This is a step in separating FPGA region common code from Device Tree support. Signed-off-by: Alan Tull --- v2: split out from another patch update author

[PATCH v2 06/16] fpga: region: remove unneeded of_node_get and put

Remove of_node_get/put in fpga_region_get/put. Not needed and will get in the way when I separate out the common FPGA region code from Device Tree support code. Signed-off-by: Alan Tull --- v2: split out from another patch --- drivers/fpga/fpga-region.c | 3 --- 1 file

Re: [PATCH v3 03/12] dt-bindings: make AXP20X compatible strings one per line

On Mon, Apr 17, 2017 at 07:57:38PM +0800, Icenowy Zheng wrote: > In the binding documentation of AXP20X mfd, the compatible strings used > to be listed for three per line, which leads to some mess when trying to > add AXP803 compatible string (as we have already AXP806 and AXP809 > compatibles,

Re: [PATCH v3] sched: Have do_idle() call __schedule() without enabling preemption

On Fri, 14 Apr 2017 20:48:07 +0200 (CEST) Thomas Gleixner wrote: > On Fri, 14 Apr 2017, Steven Rostedt wrote: > > > > Acked-by: "Paul E. McKenney" > > Signed-off-by: Steven Rostedt (VMware) > > Reviewed-by: Thomas

Re: MMC block addressing mode.

On 13 April 2017 at 21:49, Steven J. Hill wrote: > Uffe, > > The Cavium hardware requires knowledge of the card addressing mode. > We need to either restore mmc_card_blockaddr(), or create another > way to generate the same information. You previously suggested use > of

Re: linux-next: build failure after merge of the rcu tree

On Thu, Apr 20, 2017 at 03:36:47PM +1000, Stephen Rothwell wrote: > Hi Paul, > > [Also reported by Michael elsewhere] > > After merging the rcu tree, today's linux-next build (powerpc > pseries_le_defconfig) failed like this: > > arch/powerpc/kvm/book3s_hv_rmhandlers.S: Assembler messages: >

Re: [PATCH v4 1/1] pwm: pca9685: fix gpio-only operation.

On Thu, Apr 20, 2017 at 06:07:37PM +0300, Andy Shevchenko wrote: > On Thu, Apr 20, 2017 at 5:12 PM, Sven Van Asbroeck > wrote: > >> Taking above into consideration perhaps sleep is not quite good word > >> at all. By functional description it sounds like latency tolerance to

Re: [PATCH 0/5] nvme APST fixes/improvements for 4.11

On Wed, Apr 19, 2017 at 10:19 PM, Christoph Hellwig wrote: > On Wed, Apr 19, 2017 at 09:52:17PM -0700, Andy Lutomirski wrote: >> > I can make it so that force_apst=0 means no APST and force_apst=1 mean >> > yes APST and we could try again with a quirk list for 4.12. There's a >> >

Re: [PATCH 2/2] tick: Make sure tick timer is active when bypassing reprogramming

On Thu, 2017-04-20 at 17:30 +0200, Frederic Weisbecker wrote: > So far we have run into too much troubles with the optimization path > that skips reprogramming the clock on IRQ exit when the expiration > deadline hasn't changed. If by accident the cached deadline happens > to > be out of sync with

Re: [PATCH 1/2] nohz: Fix again collision between tick and other hrtimers

On Thu, 2017-04-20 at 17:30 +0200, Frederic Weisbecker wrote: > (This restores commit 24b91e360ef521a2808771633d76ebc68bd5604b that > got > reverted by commit 558e8e27e73f53f8a512485be538b07115fe5f3c due to a > regression where CPUs spuriously stopped ticking. The issue happened > when a tick

Re: [PATCH v6 1/6] dt-bindings: power: supply: add AXP20X/AXP22X battery DT binding

On Tue, Apr 18, 2017 at 09:34:16AM +0200, Quentin Schulz wrote: > The X-Powers AXP20X and AXP22X PMICs can have a battery as power supply. > > This patch adds the DT binding documentation for the battery power > supply which gets various data from the PMIC, such as the battery status > (charging,

Re: [PATCH v6 4/4] net: dsa: LAN9303: add MDIO managed mode support

On Tue, Apr 18, 2017 at 10:48:27AM +0200, Juergen Borleis wrote: > When the LAN9303 device is in MDIO manged mode, all register accesses must > be done via MDIO. > > Please note: this code is compile time tested only due to the absence of such > configured hardware. It is based on a patch from

Re: [PATCH v6 3/4] net: dsa: LAN9303: add I2C managed mode support

On Tue, Apr 18, 2017 at 10:48:26AM +0200, Juergen Borleis wrote: > In this mode the switch device and the internal phys will be managed via > I2C interface. The MDIO interface is still supported, but for the > (emulated) CPU port only. > > Signed-off-by: Juergen Borleis >

Re: [PATCH 3/3] iio: tools: generic_buffer: increase trigger length

On Wed, Apr 19, 2017 at 11:20 AM, Eugen Hristev wrote: > Increased trigger length to 50 in order to cope with trigger names like > fc03.adc-dev0-external-rising > > Signed-off-by: Eugen Hristev > --- > tools/iio/iio_utils.h | 2 +- >

[PATCH v4 6/8] ARM: dts: stm32: Enable OV2640 camera support of STM32F429-EVAL board

Enable OV2640 camera support of STM32F429-EVAL board. Signed-off-by: Hugues Fruchet --- arch/arm/boot/dts/stm32429i-eval.dts | 30 ++ 1 file changed, 30 insertions(+) diff --git a/arch/arm/boot/dts/stm32429i-eval.dts

[PATCH v4 1/8] dt-bindings: Document STM32 DCMI bindings

This adds documentation of device tree bindings for the STM32 DCMI (Digital Camera Memory Interface). Acked-by: Rob Herring Signed-off-by: Hugues Fruchet --- .../devicetree/bindings/media/st,stm32-dcmi.txt| 46 ++ 1 file changed,

Re: [PATCH v4 1/1] pwm: pca9685: fix gpio-only operation.

On Thu, 2017-04-20 at 11:50 -0400, Sven Van Asbroeck wrote: > > Thus, I would suggest: int sleep -> bool enable (or alike). > > > > Would we agree on that? > > I would. Perhaps also: > set_sleep_mode(int sleep) -> enable_sleep_mode(bool enable) ? I'm okay with a such (don't forget to change 0/1

[PATCH v4 7/8] ARM: configs: stm32: STMPE1600 GPIO expander

Enable STMPE1600 GPIO expander. Signed-off-by: Hugues Fruchet --- arch/arm/configs/stm32_defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/configs/stm32_defconfig b/arch/arm/configs/stm32_defconfig index a9d8e3c..84adc88 100644 ---

[PATCHv5 9/9] x86/mm: Allow to have userspace mappings above 47-bits

On x86, 5-level paging enables 56-bit userspace virtual address space. Not all user space is ready to handle wide addresses. It's known that at least some JIT compilers use higher bits in pointers to encode their information. It collides with valid pointers with 5-level paging and leads to

[PATCHv5 6/9] x86/mm: Make kernel_physical_mapping_init() support 5-level paging

Populate additional page table level if CONFIG_X86_5LEVEL is enabled. Signed-off-by: Kirill A. Shutemov --- arch/x86/mm/init_64.c | 69 --- 1 file changed, 60 insertions(+), 9 deletions(-) diff --git

Re: [Xen-devel] [PATCH RFC] x86/smpboot: Set safer __max_logical_packages limit

Boris Ostrovsky writes: > On 04/20/2017 11:40 AM, Vitaly Kuznetsov wrote: >> Peter Zijlstra writes: >> >>> On Thu, Apr 20, 2017 at 03:24:53PM +0200, Vitaly Kuznetsov wrote: In this patch I suggest we set __max_logical_packages based on the

[PATCHv5 4/9] x86/boot/64: Add support of additional page table level during early boot

This patch adds support for 5-level paging during early boot. It generalizes boot for 4- and 5-level paging on 64-bit systems with compile-time switch between them. Signed-off-by: Kirill A. Shutemov --- arch/x86/boot/compressed/head_64.S | 23

[PATCHv5 1/9] x86/asm: Fix comment in return_from_SYSCALL_64

On x86-64 __VIRTUAL_MASK_SHIFT depends on paging mode now. Signed-off-by: Kirill A. Shutemov --- arch/x86/entry/entry_64.S | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S index

Re: [PATCH v2 0/2] nvme APST quirk updates, take two

On Thu, Apr 20, 2017 at 07:15:15PM +0300, Sagi Grimberg wrote: > > > > Hi Jens- > > > > > > These are just the quirk updates, split out. The patches are > > > unchanged. > > > > > > I think that, even if we want to apply a broader quirk for 4.11, we > > > should still apply these so that we

[PATCHv5 7/9] x86/mm: Add support for 5-level paging for KASLR

With 5-level paging randomization happens on P4D level instead of PUD. Maximum amount of physical memory also bumped to 52-bits for 5-level paging. Signed-off-by: Kirill A. Shutemov --- arch/x86/mm/kaslr.c | 81

[PATCHv5 3/9] x86/boot/64: Rename init_level4_pgt and early_level4_pgt

With CONFIG_X86_5LEVEL=y, level 4 is no longer top level of page tables. Let's give these variable more generic names: init_top_pgt and early_top_pgt. Signed-off-by: Kirill A. Shutemov --- arch/x86/include/asm/pgtable.h | 2 +-

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