Re: [PATCH 4/6] irqchip: irq-mvebu-icu: new driver for Marvell ICU

Hi Thomas, Very small comment, On Tue, May 30, 2017 at 11:16:09AM +0200, Thomas Petazzoni wrote: > diff --git a/drivers/irqchip/irq-mvebu-icu.c b/drivers/irqchip/irq-mvebu-icu.c [...] > +#define ICU_INT_CFG(x) (0x100 + 4 * x) You should use (x) here, to be safe. Thanks! Antoine --

[PATCH V1 05/15] spmi: pmic-arb: cleanup unrequested irqs

From: Abhijeet Dharmapurikar We see a unmapped irqs trigger right around bootup. This could likely be because the bootloader exited leaving the interrupts in an unknown or unhandled state. Ack and mask the interrupt if one is found. A request_irq later will unmask it

Re: [PATCH 3/3] livepatch: force transition process to finish

On Mon, May 29, 2017 at 02:28:13PM +0200, Petr Mladek wrote: > On Fri 2017-05-26 12:37:56, Josh Poimboeuf wrote: > > On Thu, May 25, 2017 at 06:03:07PM +0200, Petr Mladek wrote: > > > On Thu 2017-05-25 14:59:55, Miroslav Benes wrote: > > > > > > > > > > > In fact, I would suggest to take

[PATCH V1 12/15] spmi-pmic-arb: fix a possible null pointer dereference

From: Abhijeet Dharmapurikar If "core" memory resource is not specified, the driver could end up dereferencing a null pointer. Fix this by returning -EINVAL when core resource is missing. Signed-off-by: Abhijeet Dharmapurikar Signed-off-by:

Re: [PATCH 2/2] xen/input: add multi-touch support

Hi, Dmitry! On 05/30/2017 08:51 AM, Dmitry Torokhov wrote: On Fri, Apr 21, 2017 at 09:40:36AM +0300, Oleksandr Andrushchenko wrote: Hi, Dmitry! On 04/21/2017 05:10 AM, Dmitry Torokhov wrote: Hi Oleksandr, On Thu, Apr 13, 2017 at 02:38:04PM +0300, Oleksandr Andrushchenko wrote: From:

Re: [PATCH v8] mfd: Add Cherry Trail Whiskey Cove PMIC driver

On Tue, 2017-05-30 at 13:20 +0100, Lee Jones wrote: > On Tue, 30 May 2017, Andy Shevchenko wrote: > > > On Tue, May 30, 2017 at 12:02 PM, Lee Jones > > wrote: > > > On Tue, 23 May 2017, Hans de Goede wrote: > > > > +static const struct i2c_device_id cht_wc_i2c_id[] = { > >

Re: [PATCH 4/6] irqchip: irq-mvebu-icu: new driver for Marvell ICU

On 30/05/17 13:05, Thomas Petazzoni wrote: > Hello, > > On Tue, 30 May 2017 12:10:29 +0100, Marc Zyngier wrote: > >> Thanks for that, looks pretty interesting. A couple of comments below. > > Thanks again for the review! > >>> +/* GICP registers */ >>> +#define GICP_SETSPI_NSR_OFFSET 0x0

Re: [PATCH] KVM: x86: update master clock before computing kvmclock_offset

On Tue, May 16, 2017 at 10:50:00PM +0200, Radim Krčmář wrote: > kvm master clock usually has a different frequency than the kernel boot > clock. This is not a problem until the master clock is updated; > update uses the current kernel boot clock to compute new kvm clock, > which erases any kvm

Re: [PATCH v2 1/3] mfd: lp87565: Add lp87565 PMIC support

On Tuesday 30 May 2017 03:42 PM, Lee Jones wrote: > On Tue, 30 May 2017, Keerthy wrote: > >> >> >> On Tuesday 30 May 2017 02:53 PM, Lee Jones wrote: >>> On Tue, 23 May 2017, Keerthy wrote: >>> The LP87565 chip is a power management IC for Portable Navigation Systems and Tablet

Re: [PATCH v2] [media] vb2: core: Lower the log level of debug outputs

On Tue, 2017-05-30 at 18:49 +0900, Hirokazu Honda wrote: > Some debug output whose log level is set 1 flooded the log. > Their log level is lowered to find the important log easily. Maybe use pr_debug instead? Perhaps it would be better to change the level to a bitmap so these can be more

Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE

On Tue, May 30, 2017 at 09:44:08AM +0200, Michal Hocko wrote: > On Wed 24-05-17 17:27:36, Mike Rapoport wrote: > > On Wed, May 24, 2017 at 01:18:00PM +0200, Michal Hocko wrote: > [...] > > > Why cannot khugepaged simply skip over all VMAs which have userfault > > > regions registered? This would

Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever

/* +* Avoid configuration and syncing commands if controller is already +* being removed and queues have been killed. +*/ + if (ctrl->state == NVME_CTRL_DELETING || ctrl->state == NVME_CTRL_DEAD) + return; + Hey Rakesh, Christoph, Given

Re: [PATCH] macintosh: move mac_hid driver to input/mouse.

Hi Michal, On May 30 2017 or thereabouts, Michal Suchánek wrote: > On Mon, 29 May 2017 22:06:06 -0700 > Dmitry Torokhov wrote: > > > On Mon, May 29, 2017 at 08:03:25PM +0200, Michal Suchánek wrote: > > > On Sun, 28 May 2017 10:55:40 -0700 > > > Dmitry Torokhov

Re: [PATCH v2] LSM: Convert security_hook_heads into explicit array of struct list_head

On Mon, 29 May 2017, Tetsuo Handa wrote: > Igor proposed a sealable memory allocator, and the LSM hooks > ("struct security_hook_heads security_hook_heads" and > "struct security_hook_list ...[]") will benefit from that allocator via > protection using set_memory_ro()/set_memory_rw(), and that

[PATCH V2 2/3] net-next: dsa: add multi cpu port support

Some boards have two CPU interfaces connected to the switch, e.g. WiFi access points, with 1 port labeled WAN, 4 ports labeled lan1-lan4, and two port connected to the SoC. This patch extends DSA to allows both CPU ports to be used. The "cpu" node in the DSA tree can now have a phandle to the

Re: [PATCH v2] powerpc/fadump: return error when fadump registration fails

Mahesh Jagannath Salgaonkar writes: > On 05/27/2017 09:16 PM, Michal Suchanek wrote: >> - log an error message when registration fails and no error code listed >> in the switch is returned >> - translate the hv error code to posix error code and return it from >>

Re: [PATCH v13 9/9] arm64: dts: qcom: msm8916: Add debug unit

Hi Andy, David, [ + Nico ] On Fri, May 26, 2017 at 12:04:13AM +0800, Leo Yan wrote: > Add debug unit on Qualcomm msm8916 based platforms, including the > DragonBoard 410c board. Could you take a look for this patch? After get your ACK I think Mathieu could help pick up this patch through

[PATCH V2 1/3] Documentation: devicetree: add multiple cpu port DSA binding

Extend the DSA binding documentation, adding the new property required when there is more than one CPU port attached to the switch. Cc: Rob Herring Cc: devicet...@vger.kernel.org Signed-off-by: John Crispin ---

[PATCH V2 3/3] net-next: dsa: mt7530: add multi cpu port support

MT7530 switches have 2 CPU ports. Inside an MT7623a these are connected to GMAC1 and GMAC2. The code currently has the CPU hard coded to 6. Change this to using the new dsa_port_upstream_port() api. In case port 5 is not setup as a cpu port, we configure the RGMII passthrough mode allowing GMAC2

[PATCH] gpio: xra1403: select REGMAP_SPI

Without the regmap code, we get a link error: drivers/gpio/built-in.o: In function `xra1403_probe': (.text+0x132e0): undefined reference to `__devm_regmap_init_spi' Fixes: 5704520d7880 ("gpio: xra1403: Add EXAR XRA1403 SPI GPIO expander driver") Signed-off-by: Arnd Bergmann ---

Re: [Linux-ima-devel] [PATCH v2 3/5] tpm: pass multiple digests to tpm_pcr_extend()

On Tue, 2017-05-30 at 09:28 +0200, Roberto Sassu wrote: > On 5/30/2017 5:29 AM, Mimi Zohar wrote: > > On Fri, 2017-05-05 at 16:21 +0200, Roberto Sassu wrote: > >> @@ -876,29 +925,46 @@ static int tpm1_pcr_extend(struct tpm_chip *chip, > >> int pcr_idx, const u8 *hash, > >> * isn't, protect

[RFC 1/3] WhiteEgret: Add WhiteEgret core functions.

This RFC provides implementation of WhiteEgret. Signed-off-by: Masanobu Koike --- security/Kconfig | 7 +- security/Makefile | 2 + security/whiteegret/Kconfig| 21 ++ security/whiteegret/Makefile | 7 +

[RFC 3/3] WhiteEgret: Add an example of user application.

A user application is required to use WhiteEgret. This RFC provides a sample user application program. Usage sample-we-user This sample user application always returns "not permit" for the executable specified by the argument , otherwise always returns "permit". Set the absolute path of an

[PATCH 2/2 v2] backlight: gpio: delete pdata inversion

The option to invert the output of the GPIO (active low) is not used by the only platform still using platform data to set up a GPIO backlight (one SH board). Delete the option as we do not expect to expand the use of board files for this driver, and GPIO descriptors intrinsically keep track of

Re: [PATCH 4/6] irqchip: irq-mvebu-icu: new driver for Marvell ICU

I see we're still duplicating work. Yes, I know you'll reply with your "your tree is a private tree" blah blah, which is fine if you want to keep re-doing work that others have done, but it's incredibly inefficient. What you call my private tree is the public ARM git tree - hardly private. It's

Re: [PATCH 1/2] xen/input: use string constants from PV protocol

Hi, Dmitry! On 04/21/2017 05:11 AM, Dmitry Torokhov wrote: On Thu, Apr 13, 2017 at 02:38:03PM +0300, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko Xen input para-virtual protocol defines string constants used by both back and frontend. Use

[RFC, PATCH] imx: serial: Take tty->files_lock opportunistically

Trying to load a serdev driver agains a tty port on i.MX6Q results in the following lockdep warning: kworker/u8:1/100 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire: (&(>files_lock)->rlock){+.+...}, at: [] imx_startup+0x2c0/0x50c and this task is already holding: (_lock_key){-.}, at: []

Re: [-next] memory hotplug regression

On Tue, May 30, 2017 at 02:18:06PM +0200, Michal Hocko wrote: > > So ZONE_DMA ends within ZONE_NORMAL. This shouldn't be possible, unless > > this restriction is gone? > > The patch below should help. It does fix this specific problem, but introduces a new one: # echo online_movable >

[PATCH V1 07/15] spmi: pmic-arb: clear the latched status of the interrupt

From: Abhijeet Dharmapurikar PMIC interrupts each have an internal latched status bit which is not visible from any register. This status bit is set as soon as the conditions specified in the interrupt type and polarity registers are met even if the interrupt is not

[PATCH V1 03/15] spmi: pmic-arb: fix inconsistent use of apid and chan

From: Abhijeet Dharmapurikar The driver currently uses "apid" and "chan" to mean apid. Remove the use of chan and use only apid. On a SPMI bus there is allocation to manage up to 4K peripherals. However, in practice only few peripherals are instantiated and only few

[PATCH V1 02/15] spmi: pmic-arb: rename spmi_pmic_arb_dev to spmi_pmic_arb

From: Abhijeet Dharmapurikar Usually *_dev best used for structures that embed a struct device in them. spmi_pmic_arb_dev doesn't embed one. It is simply a driver data structure. Use an appropriate name for it. Also there are many places in the driver that left shift

Re: [PATCH 09/10] KVM: arm/arm64: vgic: Implement forwarding setting

Hi, On 25/05/2017 21:19, Marc Zyngier wrote: > On Wed, May 24 2017 at 10:13:22 pm BST, Eric Auger > wrote: >> Implements kvm_vgic_[set|unset]_forwarding. >> >> Handle low-level VGIC programming and consistent irqchip >> programming. >> >> Signed-off-by: Eric Auger

Re: [PATCH 1/2] gpio: mvebu: fix blink counter register selection

Hi Richard, On mar., mai 30 2017, Richard Genoud wrote: > The blink counter A was always selected because 0 was forced in the > blink select counter register. > The variable 'set' was obviously there to be used as the register value, > selecting the B counter when

Re: [PATCH 1/2] gpio: mvebu: fix blink counter register selection

Hi again, On mar., mai 30 2017, Gregory CLEMENT wrote: > Hi Richard, > > On mar., mai 30 2017, Richard Genoud wrote: > >> The blink counter A was always selected because 0 was forced in the >> blink select counter register. >>

Re: [PATCH 4/6] irqchip: irq-mvebu-icu: new driver for Marvell ICU

Hello, On Tue, 30 May 2017 13:56:43 +0100, Russell King - ARM Linux wrote: > > The problem is that you do tons of work on your side, but never submit > > anything. Or when you submit something, it's enormous patch series that > > hardly get reviewed because they are too big. > > The choice is

[PATCH v3] mfd: lp87565: Add lp87565 PMIC support

The LP87565 chip is a power management IC for Portable Navigation Systems and Tablet Computing devices. It contains the following components: - Configurable Bucks(Single and multi-phase). - Configurable General Purpose Output Signals (GPO). The LP87565-Q1 variant device uses two

linux-next: build failure after merge of the rtc tree

gt;client->irq > 0 || ^ Caused by commit 345b89453dda ("rtc: rtc-ds1307: enable support for mcp794xx as a wakeup source without IRQ") interacting with commit 11e5890b5342 ("rtc: ds1307: convert driver to regmap") I have used t

Re: [PATCH] macintosh: move mac_hid driver to input/mouse.

On Tue, May 30, 2017 at 02:56:18PM +0200, Michal Suchánek wrote: > > > > I concede userspace doesn't have the feature, but you should > > > > really have a look at libinput (i.e. open a bug on > > > > bugs.freedesktop.org) and request the feature here. > > > > > > > > > > > > > > > >

Re: [PATCH 4/4] ARM: multi_v7_defconfig: Switch AXP20x driver from module to built-in

Maxime Ripard writes: > Hi Kevin, > > On Thu, May 18, 2017 at 11:59:50AM -0700, Kevin Hilman wrote: >> On Fri, Mar 17, 2017 at 10:39 AM, Kevin Hilman wrote: >> > On Fri, Feb 10, 2017 at 12:42 AM, Maxime Ripard >> >

Re: [PATCH v6 3/6] drm/i915/gvt: Frame buffer decoder support for GVT-g

On 2017.05.27 16:38:49 +0800, Xiaoguang Chen wrote: > decode frambuffer attributes of primary, cursor and sprite plane > > Signed-off-by: Xiaoguang Chen > --- > drivers/gpu/drm/i915/gvt/Makefile | 3 +- > drivers/gpu/drm/i915/gvt/display.c| 2 +- >

[PATCH] PCI: qcom: ix spelling mistake: "asser" -> "assert"

From: Colin Ian King Trivial fix to spelling mistake in dev_err message Signed-off-by: Colin Ian King --- drivers/pci/dwc/pcie-qcom.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pci/dwc/pcie-qcom.c

[PATCH][V2] PCI: qcom: fix spelling mistake: "asser" -> "assert"

From: Colin Ian King Trivial fix to spelling mistake in dev_err message Signed-off-by: Colin Ian King --- drivers/pci/dwc/pcie-qcom.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pci/dwc/pcie-qcom.c

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Tue, May 30, 2017 at 05:16:56PM +0300, Andrey Ryabinin wrote: > On 05/29/2017 06:29 PM, Dmitry Vyukov wrote: > > Joonsoo, > > > > I guess mine (and Andrey's) main concern is the amount of additional > > complexity (I am still struggling to understand how it all works) and > > more

Re: [GIT PULL] Immutable branch between MFD, GPIO, Thermal and X86 due for the v4.13 merge window

Sorry, its a mistake from my end. It looks like typec wcove driver got merged recently and I missed to add it to my cleanup patch set. Lee, I have created a patch to fix this issue. Do you want me to send the entire series again with this fix or just send the fix alone. On Tue, May 30, 2017

Re: [GIT PULL] Immutable branch between MFD, GPIO, Thermal and X86 due for the v4.13 merge window

Hi All, On Tue, May 30, 2017 at 8:38 PM, Stephen Rothwell wrote: > Hi all, > > On Tue, 30 May 2017 09:53:06 +0100 Lee Jones wrote: >> >> Dear fellow Maintainers, >> >> Enjoy! >> >> The following changes since commit

Re: [PATCH] iscsi-target: Fix initial login PDU asynchronous socket close OOPs

Hey MNC, On Fri, 2017-05-26 at 22:14 -0500, Mike Christie wrote: > Thanks for the patch. > Btw, after running DATERA's internal longevity and scale tests across ~20 racks on v4.1.y with this patch over the long weekend, there haven't been any additional regressions. > On 05/26/2017 12:32 AM,

Re: [PATCH v3] scripts/gdb: make lx-dmesg command work (reliably)

Hi André, Jan, Andrew, On 26/05/17 20:28, Jan Kiszka wrote: > On 2017-05-26 13:22, André Draszik wrote: >> lx-dmesg needs access to the log_buf symbol from printk.c. >> Unfortunately, the symbol log_buf also exists in BPF's >> verifier.c and hence gdb can pick one or the other. If it >> happens

[PATCH v4 1/9] mfd: intel_soc_pmic_bxtwc: fix TMU interrupt index

From: Kuppuswamy Sathyanarayanan TMU interrupts are registered as a separate interrupt chip, and hence it should start its interrupt index(BXTWC_TMU_IRQ) number from 0. But currently, BXTWC_TMU_IRQ is defined as part of enum bxtwc_irqs_level2 and its

Re: [RFC PATCH v2] ASoC: Intel: sst: Delete sst_shim_regs64; saved regs are never used

On Tue, May 30, 2017 at 08:06:38PM +0300, Andy Shevchenko wrote: > On Tue, May 30, 2017 at 7:51 PM, Douglas Anderson > wrote: > > In commit 9a075265c6dc ("ASoC: Intel: sst: Remove unused function > > sst_restore_shim64()"), we deleted the sst_restore_shim64() since it > >

Re: [RFC PATCH] vmalloc: show more detail info in vmallocinfo for clarify

Hi Tim, Thanks for comment! On 2017/5/31 8:56, Tim Chen wrote: > On 05/19/2017 11:47 PM, Yisheng Xie wrote: >> When ioremap a 67112960 bytes vm_area with the vmallocinfo: >> [..] >> 0xec79b000-0xec7fa000 389120 ftl_add_mtd+0x4d0/0x754 pages=94 vmalloc >> 0xec80-0xecbe1000 4067328

Re: [PATCH v6 2/6] drm/i915/gvt: OpRegion support for GVT-g

On 2017.05.27 16:38:48 +0800, Xiaoguang Chen wrote: > OpRegion is needed to support display related operation for > intel vgpu. > > A vfio device region is added to intel vgpu to deliver the > host OpRegion information to user space so user space can > construct the OpRegion for vgpu. > >

[PATCH v4 2/9] mfd: intel_soc_pmic_bxtwc: remove thermal second level irqs

From: Kuppuswamy Sathyanarayanan Since all second level thermal irqs are consumed by the same device(bxt_wcove_thermal), there is no need to expose them as separate interrupts. We can just export only the first level irqs for thermal and let the

[PATCH v4 4/9] mfd: intel_soc_pmic_bxtwc: remove second level irq for gpio device

From: Kuppuswamy Sathyanarayanan Currently all PMIC GPIO domain irqs are consumed by the same device(bxt_wcove_gpio), so there is no need to export them as separate interrupts. We can just export only the first level GPIO irq(BXTWC_GPIO_LVL1_IRQ) as an

[PATCH v4 5/9] gpio: gpio-wcove: use first level PMIC GPIO irq

From: Kuppuswamy Sathyanarayanan PMIC mfd driver only exports first level irq for GPIO device. But currently we are reading the irqs from the second level irq chip, So this patch fixes this issue by adding support to use first level PMIC GPIO irq.

[PATCH v4 6/9] mfd: intel_soc_pmic_bxtwc: utilize devm_* functions in driver probe

From: Kuppuswamy Sathyanarayanan Cleanup the resource allocation/free code in probe function by using devm_* calls. Signed-off-by: Kuppuswamy Sathyanarayanan Acked-for-MFD-by: Lee Jones

[PATCH v4 0/9] WCOVE chained IRQ fix

From: Kuppuswamy Sathyanarayanan Following patch set fixes the chained IRQ issue observed in WCOVE PMIC driver. Changes since v3: * Added fix for typec wcove driver. Kuppuswamy Sathyanarayanan (9): mfd: intel_soc_pmic_bxtwc: fix TMU interrupt

[PATCH v4 9/9] usb: typec: typec_wcove: Use charger irq chip to get usbc virq

From: Kuppuswamy Sathyanarayanan Currently, in Whiskey cove PMIC driver, USBC IRQ is moved under charger level2 irq chip. So use irq_chip_data_chgr to get the USBC virtual IRQ number. Signed-off-by: Kuppuswamy Sathyanarayanan

[PATCH v4 8/9] platform: x86: intel_bxtwc_tmu: remove first level irq unmask

From: Kuppuswamy Sathyanarayanan Currently in WCOVE PMIC mfd driver, all second level irq chips are chained to the respective first level irqs. So there is no need for explicitly unmasking the first level irq in this driver. This patches removes this

[PATCH v4 3/9] thermal: intel_bxt_pmic_thermal: use first level PMIC thermal irq

From: Kuppuswamy Sathyanarayanan PMIC mfd driver only exports first level irq for thermal device. But currently we are reading the irqs from the second level irq chip, So this patch fixes this issue by adding support to use first level PMIC thermal

[PATCH v4 7/9] mfd: intel_soc_pmic_bxtwc: use chained irqs for second level irq chips

From: Kuppuswamy Sathyanarayanan Whishkey cove PMIC has support to mask/unmask interrupts at two levels. At first level we can mask/unmask interrupt domains like TMU, GPIO, ADC, CHGR, BCU THERMAL and PWRBTN and at second level, it provides facility to

linux-next: Tree for May 31

Hi all, Changes since 20170530: The mfd tree gained a build failure so I used the version from next-20170530. The drivers-x86 tree gained the same build failure as the mfd tree so I used the version from next-20170530. The rtc tree gained a build failure so I used the version from next

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

tch removes member client from struct ds1307. Rgds, Heiner > > Caused by commit > > 345b89453dda ("rtc: rtc-ds1307: enable support for mcp794xx as a wakeup > source without IRQ") > > interacting with commit > > 11e5890b5342 ("rtc: ds1307: convert driver to regmap") > > I have used the rtc tree from next-20170530 for today. >

Re: [PATCH] mm,oom: add tracepoints for oom reaper-related events

On Tue, May 30, 2017 at 02:34:16PM +0200, Michal Hocko wrote: > On Tue 30-05-17 13:05:32, Roman Gushchin wrote: > > Add tracepoints to simplify the debugging of the oom reaper code. > > > > Trace the following events: > > 1) a process is marked as an oom victim, > > 2) a process is added to the

Re: [PATCH 4/6] irqchip: irq-mvebu-icu: new driver for Marvell ICU

Hello, On Tue, 30 May 2017 15:27:35 +0200, Andrew Lunn wrote: > > Given the number of patch sets that I have, that is simply an > > impossibility to do on a continual basis - I have close to 500 > > patches, and there's simply no way to post that number of patches. > > So you don't expect to

Re: [PATCH v6 1/4] gpio: mvebu: Add limited PWM support

Hi Ralph and Linus, I resurrect this thread following the series post by Richard Genoud: http://lists.infradead.org/pipermail/linux-arm-kernel/2017-May/509461.html On lun., avril 24 2017, Linus Walleij wrote: > On Fri, Apr 14, 2017 at 5:40 PM, Ralph Sennhauser >

Re: [PATCH v1 1/1] mux: mux-intel-usb: Add Intel USB Multiplexer driver

On 2017-05-30 02:47, sathyanarayanan.kuppusw...@linux.intel.com wrote: > From: Kuppuswamy Sathyanarayanan > > In some Intel SOCs, a single USB port is shared between USB device and > host controller and an internal mux is used to control the selection

Re: [PATCH 1/2] perf/x86/intel: enable CPU ref_cycles for GP counter

On Tue, May 30, 2017 at 11:25:23AM +0200, Peter Zijlstra wrote: > On Sun, May 28, 2017 at 01:31:09PM -0700, Stephane Eranian wrote: > > Ultimately, I would like to see the watchdog move out of the PMU. That > > is the only sensible solution. > > You just need a resource able to interrupt on NMI or

Re: [PATCH 3/6] irqchip: irq-mvebu-gicp: new driver for Marvell GICP

On 30/05/17 10:16, Thomas Petazzoni wrote: > This commit adds a simple driver for the Marvell GICP, a hardware unit > that converts memory writes into GIC SPI interrupts. The driver doesn't > do anything but clear all interrupts at boot time, to avoid spurious > interrupts left by the firmware. >

Re: [PATCH 6/6] arm64: dts: marvell: enable GICP and ICU on Armada 7K/8K

On 30/05/17 10:16, Thomas Petazzoni wrote: > This commit modifies the Marvell EBU Armada 7K and 8K Device Tree files > to describe the ICU and GICP units, and use ICU interrupts for all > devices in the CP110 blocks. > > Signed-off-by: Thomas Petazzoni > ---

Re: [PATCH 4/6] irqchip: irq-mvebu-icu: new driver for Marvell ICU

1;4601;0cOn Tue, May 30, 2017 at 02:42:26PM +0100, Russell King - ARM Linux wrote: > On Tue, May 30, 2017 at 03:27:35PM +0200, Andrew Lunn wrote: > > So you don't expect to every have your 500 patches merged? > > Correct. > > > What might help is that you ask for help getting them merged. I

Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE

On Tue, May 30, 2017 at 12:39:30PM +0200, Michal Hocko wrote: > On Tue 30-05-17 13:19:22, Mike Rapoport wrote: > > On Tue, May 30, 2017 at 09:44:08AM +0200, Michal Hocko wrote: > > > On Wed 24-05-17 17:27:36, Mike Rapoport wrote: > > > > On Wed, May 24, 2017 at 01:18:00PM +0200, Michal Hocko

Re: [PATCH 0/6] Add support for the ICU unit in Marvell Armada 7K/8K

Hi Thomas, On 30/05/17 10:16, Thomas Petazzoni wrote: > Hello, > > The Marvell Armada 7K/8K SoCs are composed of two parts: the AP (which > contains the CPU cores) and the CP (which contains most > peripherals). The 7K SoCs have one CP, while the 8K SoCs have two CPs, > doubling the number of

Re: [PATCH 6/6] arm64: dts: marvell: enable GICP and ICU on Armada 7K/8K

Hello, On Tue, 30 May 2017 15:02:34 +0100, Marc Zyngier wrote: > > @@ -221,13 +229,13 @@ > > cps_crypto: crypto@80 { > > compatible = "inside-secure,safexcel-eip197"; > > reg = <0x80 0x20>; > > -

Re: [RFC] KVM: SVM: do not drop VMCB CPL to 0 if SS is not present

On 19/05/2017 18:14, Roman Penyaev wrote: > 2. A bit complicated, which makes sure the CPL field is preserved across >KVM_GET/SET_SREGS calls and makes svm_set_segment() and svm_get_segment() >functionality symmethric: I think I prefer this solution. >KVM SVM side: >

Re: [lkp-robot] [block] c4e7d723f3: WARNING:at_block/blk-merge.c:#attempt_merge

On Sun, 2017-05-28 at 13:33 +0800, kernel test robot wrote: > [ 207.874416] WARNING: CPU: 0 PID: 419 at block/blk-merge.c:674 > attempt_merge+0xd1/0x11a6 I will fix this by adding if (!q->mq_ops) in front of the lockdep_assert_held() statement in attempt_merge(). Bart.

Re: [PATCH 3/6] irqchip: irq-mvebu-gicp: new driver for Marvell GICP

Hello, On Tue, 30 May 2017 14:55:57 +0100, Marc Zyngier wrote: > > + for (i = 0; i < GICP_INT_COUNT; i++) > > + writel(i, regs + GICP_CLRSPI_NSR_OFFSET); > > What does this do on an edge interrupt? I guess nothing. What the ICU does is: * For level interrupts: when the

Re: [PATCH net-next 0/7] net: dsa: tagger simplification

On Tue, May 30, 2017 at 10:21:24AM -0400, Vivien Didelot wrote: > The DSA layer has a dsa_device_ops structure containing two members to > tag and untag the proprietary switch header, called xmit and rcv. > > The switch tree and slave private structures respectively hold a useless > copy of the

Re: [PATCH net-next 3/7] net: dsa: remove unused arguments of tagger rcv

On Tue, May 30, 2017 at 10:21:27AM -0400, Vivien Didelot wrote: > The struct dsa_device_ops defines the rcv function with 2 unused > arguments struct packet_type *pt, and struct net_device *orig_dev. > > This patch removes them from the definition and implementations. > > Signed-off-by: Vivien

Re: [PATCH 1/2] gpio: mvebu: fix blink counter register selection

Hi Richard On Tue, 30 May 2017 14:28:47 +0200 Richard Genoud wrote: > The blink counter A was always selected because 0 was forced in the > blink select counter register. > The variable 'set' was obviously there to be used as the register > value, selecting the B

Re: [PATCH net-next 4/7] net: dsa: free orig skb on rcv if reallocated

On Tue, May 30, 2017 at 10:21:28AM -0400, Vivien Didelot wrote: > If the receive function of a tagger reallocated the SKB, the original > SKB is currently not freed. Fix this and free it on both copy or error. I don't see any of the receive functions reallocate the skb. It might be better to just

Re: [PATCH 3/6] irqchip: irq-mvebu-gicp: new driver for Marvell GICP

Hello, On Tue, 30 May 2017 16:17:41 +0100, Marc Zyngier wrote: > > Indeed. But do we care? Can an edge interrupt be left pending from the > > firmware? > > I cannot see why not. It is just as likely as a level interrupt. OK. > > I'm not sure how to use this irq_set_irqchip_state() API. I

Re: [PATCH 2/2] nvme: Quirk APST on Intel 600P/P3100 devices

On Wed, May 24, 2017 at 03:06:31PM -0700, Andy Lutomirski wrote: > They have known firmware bugs. A fix is apparently in the works -- > once fixed firmware is available, someone from Intel (Hi, Keith!) > can adjust the quirk accordingly. Here's the latest firmware with all the known fixes:

Re: [RFC] KVM: SVM: ignore type when setting segment registers

On Tue, May 30, 2017 at 02:54:21PM +0200, Radim Krčmář wrote: > 2017-05-29 15:24+0200, Gioh Kim: > > Current code sets unusable as 1 if present is 1 and type is 0. > > In Long mode, type value in segment descriptor is ignored. > > So I think type should be ignored when setting the segment

Re: [PATCH 09/10] KVM: arm/arm64: vgic: Implement forwarding setting

Hi Marc, On 30/05/2017 15:17, Marc Zyngier wrote: > On 30/05/17 13:54, Auger Eric wrote: >> Hi, >> >> On 25/05/2017 21:19, Marc Zyngier wrote: >>> On Wed, May 24 2017 at 10:13:22 pm BST, Eric Auger >>> wrote: Implements kvm_vgic_[set|unset]_forwarding.

[PATCH] staging: android: uapi: drop definitions of removed ION_IOC_{FREE,SHARE} ioctls

This problem was found by strace ioctl list generator. Fixes: 15c6098cfec5 ("staging: android: ion: Remove ion_handle and ion_client") Signed-off-by: Gleb Fotengauer-Malinovskiy --- drivers/staging/android/uapi/ion.h | 18 -- 1 file changed, 18 deletions(-)

Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever

On Tue, May 30, 2017 at 01:18:55PM +0300, Sagi Grimberg wrote: > > > /* > > +* Avoid configuration and syncing commands if controller is already > > +* being removed and queues have been killed. > > +*/ > > + if (ctrl->state == NVME_CTRL_DELETING || ctrl->state ==

[PATCH net-next 3/7] net: dsa: remove unused arguments of tagger rcv

The struct dsa_device_ops defines the rcv function with 2 unused arguments struct packet_type *pt, and struct net_device *orig_dev. This patch removes them from the definition and implementations. Signed-off-by: Vivien Didelot --- net/dsa/dsa.c | 2

[PATCH net-next 0/7] net: dsa: tagger simplification

The DSA layer has a dsa_device_ops structure containing two members to tag and untag the proprietary switch header, called xmit and rcv. The switch tree and slave private structures respectively hold a useless copy of the rcv and xmit functions. The tagging implementations use useless goto labels

Re: [PATCH] x86/KASLR: use the right memcpy

On Tue, May 30, 2017 at 3:56 PM, Baoquan He wrote: > On 05/30/17 at 11:14am, Arnd Bergmann wrote: >> The decompressor has its own implementation of the string functions, >> but has to include the right header to get those, while implicitly >> including linux/string.h may result

Re: [PATCH] LSM: Convert security_hook_heads into explicit array of struct list_head

James Morris wrote: > On Sun, 28 May 2017, Tetsuo Handa wrote: > > > can afford enabling". And we know that we cannot merge all security modules > > into mainline. Thus, allowing LKM-based LSM modules is inevitable. > > Nope, it's not inevitable. The LSM API only caters to in-tree users. > >

Re: [PATCH 4/6] irqchip: irq-mvebu-icu: new driver for Marvell ICU

On Tue, May 30, 2017 at 04:03:20PM +0200, Andrew Lunn wrote: > Linux has a long history of reworking stuff in tree, when it has been > shown to be inadequate in its first version. So long as the device > tree binding does not need incompatible changes, this reworking is not > an issue. My guess

[PATCH] pinctrl: stm32: Fix bad function call

In stm32_pconf_parse_conf function, stm32_pmx_gpio_set_direction is called with wrong parameter value. Indeed, using NULL value for range will raise an oops. Fixes: aceb16dc2da5 ("pinctrl: Add STM32 MCUs support") Reported-by: Dan Carpenter Signed-off-by: Alexandre

Re: [PATCH v6 1/4] gpio: mvebu: Add limited PWM support

On Tue, 30 May 2017 15:40:00 +0200 Gregory CLEMENT wrote: > Hi Ralph and Linus, > > I resurrect this thread following the series post by Richard Genoud: > http://lists.infradead.org/pipermail/linux-arm-kernel/2017-May/509461.html > > On lun., avril 24 2017,

Re: [PATCH 3/3] mm, memory_hotplug: move movable_node to the hotplug proper

On Mon, May 29, 2017 at 01:41:41PM +0200, Michal Hocko wrote: movable_node_is_enabled is defined in memblock proper while it is initialized from the memory hotplug proper. This is quite messy and it makes a dependency between the two so move movable_node along with the helper functions to

Re: [PATCH] KVM: SVM: ignore type when setting segment registers

2017-05-30 15:24+0200, Gioh Kim: > This patch is based on linux-next v4.12.0-rc3. (I'd omit this.) > Signed-off-by: Gioh Kim > --- Reviewed-by: Radim Krčmář

Re: [PATCH 4/6] irqchip: irq-mvebu-icu: new driver for Marvell ICU

On Tue, May 30, 2017 at 03:39:02PM +0100, Russell King - ARM Linux wrote: > On Tue, May 30, 2017 at 03:27:35PM +0200, Andrew Lunn wrote: > > What might help is that you ask for help getting them merged. I know > > of at least 4 groups of people interested in your devlink and 10G PHY > > code. If

Re: [PATCH net-next 1/7] net: dsa: hide dsa_uses_tagged_protocol code

On Tue, May 30, 2017 at 10:21:25AM -0400, Vivien Didelot wrote: > Hide the implementation of dsa_uses_tagged_protocol in dsa.c since this > helper will be extended to access the opaque dsa_device_ops structure. > > At the same time, fix the checkpatch comparison check: > > CHECK: Comparison

Re: [PATCH 3/6] irqchip: irq-mvebu-gicp: new driver for Marvell GICP

On 30/05/17 15:54, Thomas Petazzoni wrote: > Hello, > > On Tue, 30 May 2017 14:55:57 +0100, Marc Zyngier wrote: > >>> + for (i = 0; i < GICP_INT_COUNT; i++) >>> + writel(i, regs + GICP_CLRSPI_NSR_OFFSET); >> >> What does this do on an edge interrupt? > > I guess nothing. What the

Re: [PATCH 15/16] platform/x86: wmi-mof: New driver to expose embedded WMI MOF metadata

On Sat, 2017-05-27 at 14:07 -0700, Andy Lutomirski wrote: > On Sat, May 27, 2017 at 4:14 AM, Pali Rohár > wrote: > > > Quite a few laptops (and maybe servers?) have embedded WMI MOF > > > > Not "a few", but "lots of" :-) Aren't they are synonyms ("quite a few" vs "lots

Re: [PATCH net-next 6/7] net: dsa: remove useless copy of tagger xmit

On Tue, May 30, 2017 at 10:21:30AM -0400, Vivien Didelot wrote: > The dsa_slave_priv structure holds a copy of the dsa_device_ops xmit > function. It is always assigned to the switch tree xmit function. > > Remove this useless copy. > > Signed-off-by: Vivien Didelot

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