[PATCH] PCI: thunder-pem: Add support for cn81xx and cn83xx SoCs.

From: David Daney The pci-thunder-pem driver was initially developed for cn88xx SoCs. The cn81xx and cn83xx members of the same family of SoCs has a slightly different configuration of interrupt resources in the PEM hardware, which prevents the INTA legacy interrupt

Re: net/atm: warning in alloc_tx/__might_sleep

On Tue, 2017-01-10 at 23:47 +0100, Francois Romieu wrote: > Eric Dumazet : > > On Tue, Jan 10, 2017 at 9:35 AM, Cong Wang wrote: > > > On Mon, Jan 9, 2017 at 9:20 AM, Andrey Konovalov > > > wrote: > > > > > > The fix should

Re: [PATCH] PCI/MSI: pci-xgene-msi: Fix CPU hotplug registration handling

On Wed, Jan 11, 2017 at 2:26 AM, Marc Zyngier wrote: > The conversion to the new hotplug state machine introduced a regression > where a successful hotplug registration would be treated as an error, > effectively disabling the MSI driver forever. > > Fix it by doing the

Re: [PATCH v1 1/1] serial: 8250_dw: Allow hardware flow control to be used

On Tue, Dec 06, 2016 at 02:34:03PM -0800, Jason Uy wrote: > In the most common use case, the Synopsys DW UART driver does not > set the set_termios callback function. This prevents UPSTAT_AUTOCTS > from being set when the UART flag CRTSCTS is set. As a result, the > driver will use software flow

RE: [PATCH 1/3] ARM: at91: flush the L2 cache before entering cpu idle

Hi Jean-Jacques, > -Original Message- > From: Jean-Jacques Hiblot [mailto:jjhib...@gmail.com] > Sent: 2017年1月11日 0:51 > To: Alexandre Belloni > Cc: Wenyou Yang - A41535 ; Mark Rutland > ; devicetree

Re: [PATCH v8 2/5] i2c: Add STM32F4 I2C driver

Hello Cedric, On Thu, Jan 05, 2017 at 10:07:23AM +0100, M'boumba Cedric Madianga wrote: > +/* > + * In standard mode: > + * SCL period = SCL high period = SCL low period = CCR * I2C parent clk > period > + * > + * In fast mode: > + * If Duty = 0; SCL high period = 1 * CCR * I2C parent clk

Re: [PATCH 32/62] watchdog: meson_gxbb_wdt: Convert to use device managed functions and other improvements

On 01/11/2017 01:44 AM, Guenter Roeck wrote: > Use device managed functions to simplify error handling, reduce > source code size, improve readability, and reduce the likelyhood of bugs. > Other improvements as listed below. > > The conversion was done automatically with coccinelle using the >

Re: [PATCH] doc: add note on usleep_range range

On Tue, Jan 10, 2017 at 10:25:29PM +0100, Pavel Machek wrote: > Hi! > > > > "to have zero jitter" at least. I believe it is "does not". > > > > > > I don't see how atomic vs. non-atomic context makes difference. There > > > are sources of jitter that affect atomic context... > > > > The

Re: [PATCH 0/5 v3] adv7511 EDID probing improvements

Hi, On 01/04/2017 01:11 AM, John Stultz wrote: Hope everyone had a good newyears! Wanted to re-send out v3 of this patch set improving the EDID probing on the adv7511 used on HiKey, for consideration for merging for 4.11 The first three patches are fixups that are hopefully straight forward,

Re: [PATCH] docs: Make CodingStyle and SubmittingPatches symlinks

On Wed, 11 Jan 2017, Joe Perches wrote: > Make these files symlinks to the .rst equivalents If we're going to do this (and I really don't mind either way), then please add Fixes: 08a9a8d44c1c ("doc: re-add CodingStyle and SubmittingPatches") and queue to v4.10-rc. BR, Jani.

Re: [PATCH] clk: qcom: gdsc: Fix handling of hw control enable/disable

Hi Sricharan, On 01/10/2017 09:29 PM, Sricharan wrote: > Hi stan, > >> -Original Message- >> From: linux-arm-msm-ow...@vger.kernel.org >> [mailto:linux-arm-msm-ow...@vger.kernel.org] On Behalf Of Stanimir Varbanov >> Sent: Tuesday, January 10, 2017 10:14 PM >> To: Rajendra Nayak

[PATCH 1/4] platform/x86: fujitsu-laptop: decrease indentation in acpi_fujitsu_hotkey_notify()

acpi_fujitsu_hotkey_notify() is pretty deeply nested, which hurts readability. Strip off one level of indentation by returning early when the event code supplied as argument is not ACPI_FUJITSU_NOTIFY_CODE1. Signed-off-by: Michał Kępień --- Changes introduced by this patch

[PATCH 4/4] platform/x86: fujitsu-laptop: make hotkey handling functions more similar

Make two minor tweaks to acpi_fujitsu_hotkey_press() to make it more similar to acpi_fujitsu_hotkey_release(): * call vdbg_printk() after reporting the input event, * return immediately when kfifo_in_locked() fails. Signed-off-by: Michał Kępień ---

[PATCH 3/4] platform/x86: fujitsu-laptop: break up complex loop condition

The loop condition in acpi_fujitsu_hotkey_release() includes an assignment, a four-argument function call and a comparison, making it hard to read. Separate the assignment from the comparison to improve readability. Signed-off-by: Michał Kępień ---

[PATCH 0/4] fujitsu-laptop: acpi_fujitsu_hotkey_notify() cleanup

I am currently preparing a patch series which makes fujitsu-laptop use a sparse keymap for hotkey handling. Before that will happen, though, acpi_fujitsu_hotkey_notify() could use a revamp because it is pretty hard to read as it is. To avoid posting everything at once, here are a few patches

Re: [PATCH v2 2/2] media: rc: add driver for IR remote receiver on MT7623 SoC

On Tue, 2017-01-10 at 17:23 +, Sean Young wrote: > Hi Sean, > > > > > > > The kernel guarantees that calls to the interrupt handler are serialised, > > > no need to disable the interrupt in the handler. > > > > agreed. I will save the mtk irq disable/enable and retest again. > > > > > >

Re: [PATCH net-next] bridge: multicast to unicast

> > Exactly. My point is that this is breaking the expectation that > > hosts are actually able to drop such packets. > > [readding CCs I removed earlier] > > Ah! Thanks. I was worried about creating packetloss :D. Ah, well, no - at least not in this case. > Hm, for this other other way

[PATCH] perf/x86/intel: fix integer overflow when shifting 32 places

From: Colin Ian King When x86_pmu.num_counters is set to INTEL_PMC_MAX_GENERIC we end up with the 32 bit integer constant 1 being shifted 32 places leading to undefined behaviour. Fix this by shifting 1ULL instead of 1. Fixes CoverityScan CID#1192105 ("Bad bit shift

[PATCH] ASoC: rt5651: use msleep for large delays

config + SND_SOC=m SND_SOC_INTEL_BYTCR_RT5651_MACH=m (implies CONFIG_SND_SOC_RT5651) Patch is aginast 4.10-rc3 (localversion-next is next-20170111) sound/soc/codecs/rt5651.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sound/soc/codecs/rt5651.c b/sound/soc/codecs/rt5651.c

Re: imx: RS-485 problems during TX, maybe DMA related

Hi Clemens, On Tue, Jan 10, 2017 at 10:33 PM, Clemens Gruber wrote: > Hi Fabio, > > On Sun, Jan 08, 2017 at 07:46:29PM -0200, Fabio Estevam wrote: >> > What's the revision of the i.MX6Q on your board? Mine is 1.5 (TO 1.3) >> >> Mine is a mx6solo rev1.1. > > Could it

[PATCH 1/1] iommu/arm-smmu: Fix for ThunderX erratum #27704

The goal of erratum #27704 workaround was to make sure that ASIDs and VMIDs are unique across all SMMU instances on affected Cavium systems. Currently, the workaround code partitions ASIDs and VMIDs by increasing global cavium_smmu_context_count which in turn becomes the base ASID and VMID value

Re: [PATCH v2 2/2] Support for DW CSI-2 Host IPK

Hi Ramiro, See my review comments below: On 12/12/16 16:00, Ramiro Oliveira wrote: Add support for the DesignWare CSI-2 Host IP Prototyping Kit Signed-off-by: Ramiro Oliveira --- MAINTAINERS | 7 + drivers/media/platform/Kconfig

Re: [PATCH] ASoC: rt5651: use msleep for large delays

On Wed, 2017-01-11 at 12:49 +0100, Nicholas Mc Guire wrote: > ulseep_range() uses hrtimers and provides no advantage over msleep() > for larger delays. Fix up the 75/85ms delays here to use msleep() and > reduce the load on the hrtimer subsystem. If this is useful, why not convert all the large

Crypto Fixes for 4.10

Hi Linus: This push fixes a regression in aesni that renders it useless if it's built-in with a modular pcbc configuration. Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus Herbert Xu (1): crypto: aesni - Fix failure when built-in with modular

Re: [PATCH v7 1/7] perf/amd/iommu: Misc fix up perf_iommu_read

On Mon, Jan 09, 2017 at 09:33:41PM -0600, Suravee Suthikulpanit wrote: > This patch contains the following minor fixup: > * Fixed overflow handling since u64 delta would lose the MSB sign bit. Please explain.. afaict this actually introduces a bug. > diff --git a/arch/x86/events/amd/iommu.c

Re: [PATCH 0/4] fujitsu-laptop: acpi_fujitsu_hotkey_notify() cleanup

On Wed, Jan 11, 2017 at 09:59:29AM +0100, Micha?? K??pie?? wrote: > I am currently preparing a patch series which makes fujitsu-laptop use a > sparse keymap for hotkey handling. Before that will happen, though, > acpi_fujitsu_hotkey_notify() could use a revamp because it is pretty > hard to read

[PATCH v5] lib/scatterlist: Introduce and export __sg_alloc_table_from_pages

From: Tvrtko Ursulin Drivers like i915 benefit from being able to control the maxium size of the sg coallesced segment while building the scatter- gather list. Introduce and export the __sg_alloc_table_from_pages function which will allow it that control. v2: Reorder

[PATCH v6] drm/i915: Use __sg_alloc_table_from_pages for userptr allocations

From: Tvrtko Ursulin With the addition of __sg_alloc_table_from_pages we can control the maximum coallescing size and eliminate a separate path for allocating backing store here. Similar to 871dfbd67d4e ("drm/i915: Allow compaction upto SWIOTLB max segment size") this

Re: [PATCH v6] x86: fix kaslr and memmap collision

On Tue, 10 Jan 2017, Dave Jiang wrote: > +unsigned long simple_strtoul(const char *cp, char **endp, unsigned int base); > +long simple_strtol(const char *cp, char **endp, unsigned int base); What are those functions for? They are not used in that patch at all. > +static void

[PATCH v4] lib/scatterlist: Avoid potential scatterlist entry overflow

From: Tvrtko Ursulin Since the scatterlist length field is an unsigned int, make sure that sg_alloc_table_from_pages does not overflow it while coallescing pages to a single entry. v2: Drop reference to future use. Use UINT_MAX. v3: max_segment must be page aligned.

Re: [PATCH] ASoC: rt5651: use msleep for large delays

On Wed, Jan 11, 2017 at 03:55:49AM -0800, Joe Perches wrote: > On Wed, 2017-01-11 at 12:49 +0100, Nicholas Mc Guire wrote: > > ulseep_range() uses hrtimers and provides no advantage over msleep() > > for larger delays. Fix up the 75/85ms delays here to use msleep() and > > reduce the load on the

Re: [PATCH v8 1/3] dt-bindings: Add support for samsung s6e3ha2 panel binding

Hi Hoegeun, 2017-01-11 15:33 GMT+09:00 Hoegeun Kwon : > The Samsung s6e3ha2 is a 5.7" 1440x2560 AMOLED panel connected > using MIPI-DSI interfaces. > > Signed-off-by: Donghwa Lee > Signed-off-by: Hyungwon Hwang >

[PATCH 4/5] PCI: dwc: dra7xx: Enable MSI and legacy interrupts simultaneously

pci-dra7xx driver had a bug in that if CONFIG_PCI_MSI config is enabled, it doesn't support legacy interrupt. Fix it here so that both MSI and legacy interrupts can be enabled simultaneously and the interrupt mechanism supported by the endpoint device will be used. Signed-off-by: Kishon Vijay

[PATCH 1/5] PCI: dwc: Add COMPILE_TEST to all designware based drivers

Add COMPILE_TEST to all designware based drivers so that it is possible to perform compile test even when a particular architecture specific config symbol is not set. Signed-off-by: Kishon Vijay Abraham I --- drivers/pci/dwc/Kconfig | 16 1 file changed, 8

[PATCH 5/5] PCI: dwc: dra7xx: Group phy API invocations

No functional change. Phy APIs like phy_init/phy_power_on is being invoked from multiple places. Group all the phy APIs in dra7xx_pcie_enable_phy() and dra7xx_pcie_disable_phy() and use these functions for enabling or disabling the phy. Signed-off-by: Kishon Vijay Abraham I ---

[PATCH 2/5] PCI: dwc: dra7xx: Simplify the probe code

No functional change. Use the new devm_gpiod_get_optional() to simplify the probe code. Signed-off-by: Kishon Vijay Abraham I --- drivers/pci/dwc/pci-dra7xx.c | 21 + 1 file changed, 5 insertions(+), 16 deletions(-) diff --git a/drivers/pci/dwc/pci-dra7xx.c

Re: [PATCH] vme: Fix wrong pointer utilization in ca91cx42_slave_get

On 10 January 2017 at 10:45, Augusto Mecking Caringi wrote: > In ca91cx42_slave_get function, the value pointed by vme_base pointer is > set through: > > *vme_base = ioread32(bridge->base + CA91CX42_VSI_BS[i]); > > So it must be dereferenced to be used in calculation of

[PATCH v8 11/18] iommu/arm-smmu-v3: Implement reserved region get/put callbacks

iommu/arm-smmu: Implement reserved region get/put callbacks The get() populates the list with the MSI IOVA reserved window. At the moment an arbitray MSI IOVA window is set at 0x800 of size 1MB. This will allow to report those info in iommu-group sysfs. Signed-off-by: Eric Auger

[PATCH v8 15/18] irqchip/gicv3-its: Sets IRQ_DOMAIN_FLAG_MSI_REMAP

The GICv3 ITS is MSI remapping capable. Let's advertise this property so that VFIO passthrough can assess IRQ safety. Signed-off-by: Eric Auger Reviewed-by: Marc Zyngier --- v7 -> v8: - added Marc's R-b --- drivers/irqchip/irq-gic-v3-its.c | 1 +

[PATCH v8 12/18] irqdomain: Add irq domain MSI and MSI_REMAP flags

We introduce two new enum values for the irq domain flag: - IRQ_DOMAIN_FLAG_MSI indicates the irq domain corresponds to an MSI domain - IRQ_DOMAIN_FLAG_MSI_REMAP indicates the irq domain has MSI remapping capabilities. Those values will be useful to check all MSI irq domains have MSI

[PATCH v8 17/18] vfio/type1: Check MSI remapping at irq domain level

In case the IOMMU translates MSI transactions (typical case on ARM), we check MSI remapping capability at IRQ domain level. Otherwise it is checked at IOMMU level. At this stage the arm-smmu-(v3) still advertise the IOMMU_CAP_INTR_REMAP capability at IOMMU level. This will be removed in

[PATCH v8 02/18] iommu: Rename iommu_dm_regions into iommu_resv_regions

We want to extend the callbacks used for dm regions and use them for reserved regions. Reserved regions can be - directly mapped regions - regions that cannot be iommu mapped (PCI host bridge windows, ...) - MSI regions (because they belong to another address space or because they are not

[PATCH v8 03/18] iommu: Add a new type field in iommu_resv_region

We introduce a new field to differentiate the reserved region types and specialize the apply_resv_region implementation. Legacy direct mapped regions have IOMMU_RESV_DIRECT type. We introduce 2 new reserved memory types: - IOMMU_RESV_MSI will characterize MSI regions that are mapped -

[PATCH v8 07/18] iommu: Implement reserved_regions iommu-group sysfs file

A new iommu-group sysfs attribute file is introduced. It contains the list of reserved regions for the iommu-group. Each reserved region is described on a separate line: - first field is the start IOVA address, - second is the end IOVA address, - third is the type. Signed-off-by: Eric Auger

[PATCH v8 09/18] iommu/amd: Declare MSI and HT regions as reserved IOVA regions

This patch registers the MSI and HT regions as non mappable reserved regions. They will be exposed in the iommu-group sysfs. For direct-mapped regions let's also use iommu_alloc_resv_region(). Signed-off-by: Eric Auger --- v6 -> v7: - use IOMMU_RESV_RESERVED v5:

[PATCH v8 01/18] iommu/dma: Allow MSI-only cookies

From: Robin Murphy IOMMU domain users such as VFIO face a similar problem to DMA API ops with regard to mapping MSI messages in systems where the MSI write is subject to IOMMU translation. With the relevant infrastructure now in place for managed DMA domains, it's actually

Re: [PATCH v4 2/8] PCI: Allow runtime PM on Thunderbolt ports

On Sun, Jan 08, 2017 at 09:41:45AM +0100, Lukas Wunner wrote: > Currently PCIe ports are only allowed to go to D3 if the BIOS is dated > 2015 or newer to avoid potential issues with old chipsets. However for > Thunderbolt we know that even the oldest controller, Light Ridge (2010), > is able to

Re: 174cc7187e6f ACPICA: Tables: Back port acpi_get_table_with_size() and early_acpi_os_unmap_memory() from Linux kernel

On Wed, Jan 11, 2017 at 01:51:56AM -0800, Paul E. McKenney wrote: > Yes, you could make RCU expedited grace periods go back to using the > requesting task, and that would allow expedited grace periods to run early > in the boot process. But that causes problems with signals and the like > unless

Re: lkp: make.cross: old aarch64-gcc has been removed

Ping? BTW, I found that the old toolchain is archived in release.linaro.org. So I made a patch for that. Thank you, On Fri, 30 Dec 2016 07:43:45 +0900 Masami Hiramatsu wrote: > Hi Fengguang, > > Recently I tried to build a cross-build environment ( >

[PATCH v4] ARM64: dts: meson-gx: Add reserved memory zone and usable memory range

The Amlogic Meson GXBB/GXL/GXM secure monitor uses part of the memory space, this patch adds this reserved zone and redefines the usable memory range. The memory node is also moved from the dtsi files into the proper dts files to handle variants memory sizes. This patch also fixes the memory

[PATCH] arm64: Add support for DMA_ATTR_SKIP_CPU_SYNC attribute to swiotlb

From: Takeshi Kihara This patch adds support for DMA_ATTR_SKIP_CPU_SYNC attribute for dma_{un}map_{page,sg} functions family to swiotlb. DMA_ATTR_SKIP_CPU_SYNC allows platform code to skip synchronization of the CPU cache for the given buffer assuming that it has

[PATCH v2 2/3] MAINTAINERS: add zx2967 thermal drivers to ARM ZTE architecture

Add the zx2967 thermal drivers as maintained by ARM ZTE architecture maintainers, as they're parts of the core IP. Signed-off-by: Baoyou Xie --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 64f04df..2593296 100644 ---

[PATCH v2 3/3] thermal: zx2967: add thermal driver for ZTE's zx2967 family

This patch adds thermal driver for ZTE's zx2967 family. Signed-off-by: Baoyou Xie --- drivers/thermal/Kconfig | 6 + drivers/thermal/Makefile | 1 + drivers/thermal/zx2967_thermal.c | 247 +++ 3 files changed, 254

[PATCH v2 1/3] dt: bindings: add documentation for zx2967 family thermal sensor

This patch adds dt-binding documentation for zx2967 family thermal sensor. Signed-off-by: Baoyou Xie --- .../devicetree/bindings/thermal/zx2967-thermal.txt | 21 + 1 file changed, 21 insertions(+) create mode 100644

Re: [PATCH v6 02/14] irqchip: gic-v3-its: keep the head file include in alphabetic order

On 02/01/17 14:31, Hanjun Guo wrote: The head file is strictly in alphabetic order now, so let's be the rule breaker. As acpi_iort.h includes acpi.h so remove the duplidate acpi.h inclusion as well. Sounds strange, maybe someting like: Rearrange header file includes to alphabetic order. As

Re: [PATCH v8 3/3] arm64: dts: exynos: Add support for S6E3HA2 panel device on TM2 board

On 01/11/2017 04:46 PM, Andrzej Hajda wrote: On 11.01.2017 07:33, Hoegeun Kwon wrote: From: Hyungwon Hwang This patch add the panel device tree node for S6E3HA2 display controller to TM2 dts. Signed-off-by: Hyungwon Hwang Signed-off-by:

Re: [PATCH v6 02/14] irqchip: gic-v3-its: keep the head file include in alphabetic order

On 02/01/17 14:31, Hanjun Guo wrote: The head file is strictly in alphabetic order now, so let's be the rule breaker. As acpi_iort.h includes acpi.h so remove the duplidate acpi.h inclusion as well. Sounds strange, maybe someting like: Rearrange header file includes to alphabetic order. As

Re: [PATCH v8 3/3] arm64: dts: exynos: Add support for S6E3HA2 panel device on TM2 board

On 11.01.2017 11:23, hoegeun kwon wrote: > > On 01/11/2017 06:39 PM, Andrzej Hajda wrote: >> On 11.01.2017 09:40, Inki Dae wrote: >>> 2017년 01월 11일 16:46에 Andrzej Hajda 이(가) 쓴 글: On 11.01.2017 07:33, Hoegeun Kwon wrote: > From: Hyungwon Hwang > > This

Re: [PATCH] PCI/MSI: pci-xgene-msi: Fix CPU hotplug registration handling

On 2017-01-11 10:26:47 [+], Marc Zyngier wrote: > The conversion to the new hotplug state machine introduced a regression > where a successful hotplug registration would be treated as an error, > effectively disabling the MSI driver forever. > > Fix it by doing the proper check on the return

Re: [PATCH v7 1/7] perf/amd/iommu: Misc fix up perf_iommu_read

On Mon, Jan 09, 2017 at 09:33:41PM -0600, Suravee Suthikulpanit wrote: > This patch contains the following minor fixup: For the future: never say "this patch" in the commit message - just explain *why* the patch is needed. > * Fixed overflow handling since u64 delta would lose the MSB sign

mm, vmscan: commit makes PAE kernel crash nightly (bisected)

Hi! I have biected a nightly oom-killer flood and crash/hang on one of the boxes I admin. It doesn't crash on Fedora 23/24 4.7.10 kernel but does on any 4.8 Fedora kernel. I did a vanilla bisect and the bug is here: commit b2e18757f2c9d1cdd746a882e9878852fdec9501 Author: Mel Gorman

Re: Dell XPS13 does not suspend with Linux 4.10-rc3

On Wed, Jan 11, 2017 at 09:53:38AM +0100, Paul Menzel wrote: > Dear Linux folks, > > > On 01/10/17 23:24, Jan Niehusmann wrote: > > On Tue, Jan 10, 2017 at 09:43:31PM +0100, Jan Niehusmann wrote: > > > And I bisected the issue to commit 7279b238ba, "mei: send OS type to the > > > FW" > > > >

Re: [PATCH v8 3/3] arm64: dts: exynos: Add support for S6E3HA2 panel device on TM2 board

On 11.01.2017 09:40, Inki Dae wrote: > > 2017년 01월 11일 16:46에 Andrzej Hajda 이(가) 쓴 글: >> On 11.01.2017 07:33, Hoegeun Kwon wrote: >>> From: Hyungwon Hwang >>> >>> This patch add the panel device tree node for S6E3HA2 display >>> controller to TM2 dts. >>> >>>

[PATCH v8 14/18] irqdomain: irq_domain_check_msi_remap

This new function checks whether all MSI irq domains implement IRQ remapping. This is useful to understand whether VFIO passthrough is safe with respect to interrupts. On ARM typically an MSI controller can sit downstream to the IOMMU without preventing VFIO passthrough. As such any assigned

[PATCH v8 16/18] vfio/type1: Allow transparent MSI IOVA allocation

When attaching a group to the container, check the group's reserved regions and test whether the IOMMU translates MSI transactions. If yes, we initialize an IOVA allocator through the iommu_get_msi_cookie API. This will allow the MSI IOVAs to be transparently allocated on MSI controller's

[PATCH v8 13/18] genirq/msi: Set IRQ_DOMAIN_FLAG_MSI on MSI domain creation

Now we have a flag value indicating an IRQ domain implements MSI, let's set it on msi_create_irq_domain(). Signed-off-by: Eric Auger Reviewed-by: Marc Zyngier --- v7 -> v8 - Added Marc's R-b v6: new --- kernel/irq/msi.c | 4 ++-- 1 file changed,

[PATCH v8 18/18] iommu/arm-smmu: Do not advertise IOMMU_CAP_INTR_REMAP anymore

IOMMU_CAP_INTR_REMAP has been advertised in arm-smmu(-v3) although on ARM this property is not attached to the IOMMU but rather is implemented in the MSI controller (GICv3 ITS). Now vfio_iommu_type1 checks MSI remapping capability at MSI controller level, let's correct this. Signed-off-by: Eric

[PATCH v8 10/18] iommu/arm-smmu: Implement reserved region get/put callbacks

The get() populates the list with the MSI IOVA reserved window. At the moment an arbitray MSI IOVA window is set at 0x800 of size 1MB. This will allow to report those info in iommu-group sysfs. Signed-off-by: Eric Auger --- v3 -> v4: - do not handle PCI host bridge

[PATCH v8 00/18] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions

Following LPC discussions, we now report reserved regions through the iommu-group sysfs reserved_regions attribute file. Reserved regions are populated through the IOMMU get_resv_region callback (former get_dm_regions), now implemented by amd-iommu, intel-iommu and arm-smmu: - the intel-iommu

[PATCH v8 05/18] iommu: Only map direct mapped regions

As we introduced new reserved region types which do not require mapping, let's make sure we only map direct mapped regions. Signed-off-by: Eric Auger --- v3 -> v4: - use region's type and reword commit message and title --- drivers/iommu/iommu.c | 3 +++ 1 file changed,

[PATCH v8 04/18] iommu: iommu_alloc_resv_region

Introduce a new helper serving the purpose to allocate a reserved region. This will be used in iommu driver implementing reserved region callbacks. Signed-off-by: Eric Auger --- v3 -> v4: - add INIT_LIST_HEAD(>list) - use int for prot param and add int type param -

[PATCH v8 06/18] iommu: iommu_get_group_resv_regions

Introduce iommu_get_group_resv_regions whose role consists in enumerating all devices from the group and collecting their reserved regions. The list is sorted and overlaps between regions of the same type are handled by merging the regions. Signed-off-by: Eric Auger ---

Re: [PATCH] docs: Make CodingStyle and SubmittingPatches symlinks

On Wed, 11 Jan 2017, Joe Perches wrote: > On Wed, 2017-01-11 at 10:54 +0200, Jani Nikula wrote: >> On Wed, 11 Jan 2017, Joe Perches wrote: >> > Make these files symlinks to the .rst equivalents >> >> If we're going to do this (and I really don't mind either

[PATCH v8 08/18] iommu/vt-d: Implement reserved region get/put callbacks

This patch registers the [FEE0_h - FEF0_000h] 1MB MSI range as a reserved region and RMRR regions as direct regions. This will allow to report those reserved regions in the iommu-group sysfs. Signed-off-by: Eric Auger --- v6 -> v7: - report RMRR regions as direct

Re: 174cc7187e6f ACPICA: Tables: Back port acpi_get_table_with_size() and early_acpi_os_unmap_memory() from Linux kernel

On Wed, Jan 11, 2017 at 04:42:16AM +0100, Rafael J. Wysocki wrote: > Let's try the attached one. Works, thanks. Lemme give you the tags :) Reported-and-tested-by: Borislav Petkov Fixes: 174cc7187e6f ("ACPICA: Tables: Back port acpi_get_table_with_size() and

[PATCH v3] ARM64: dts: meson-gx: Add reserved memory zone and usable memory range

The Amlogic Meson GXBB/GXL/GXM secure monitor uses part of the memory space, this patch adds this reserved zone and redefines the usable memory range. The memory node is also moved from the dtsi files into the proper dts files to handle variants memory sizes. This patch also fixes the memory

[tip:timers/urgent] nohz: Fix collision between tick and other hrtimers

Commit-ID: 24b91e360ef521a2808771633d76ebc68bd5604b Gitweb: http://git.kernel.org/tip/24b91e360ef521a2808771633d76ebc68bd5604b Author: Frederic Weisbecker AuthorDate: Wed, 4 Jan 2017 15:12:04 +0100 Committer: Thomas Gleixner CommitDate: Wed, 11

RE: Dell XPS13 does not suspend with Linux 4.10-rc3

> Subject: Re: Dell XPS13 does not suspend with Linux 4.10-rc3 > > On 01/11/17 10:36, Greg Kroah-Hartman wrote: > > On Wed, Jan 11, 2017 at 09:53:38AM +0100, Paul Menzel wrote: > > >> On 01/10/17 23:24, Jan Niehusmann wrote: > >>> On Tue, Jan 10, 2017 at 09:43:31PM +0100, Jan Niehusmann wrote:

Re: Dell XPS13 does not suspend with Linux 4.10-rc3

On 01/11/17 10:36, Greg Kroah-Hartman wrote: On Wed, Jan 11, 2017 at 09:53:38AM +0100, Paul Menzel wrote: On 01/10/17 23:24, Jan Niehusmann wrote: On Tue, Jan 10, 2017 at 09:43:31PM +0100, Jan Niehusmann wrote: And I bisected the issue to commit 7279b238ba, "mei: send OS type to the FW"

Re: 174cc7187e6f ACPICA: Tables: Back port acpi_get_table_with_size() and early_acpi_os_unmap_memory() from Linux kernel

On Wed, Jan 11, 2017 at 10:21:06AM +0100, Borislav Petkov wrote: > On Mon, Jan 09, 2017 at 09:51:29PM -0800, Paul E. McKenney wrote: > > Definitely. > > Btw, we have more breakage from RCU expedited using workqueues: > https://bugzilla.kernel.org/show_bug.cgi?id=192111 > > I've added you to CC

[PATCH RESEND] splice: introduce FMODE_SPLICE_READ and FMODE_SPLICE_WRITE

Introduce FMODE_SPLICE_READ and FMODE_SPLICE_WRITE. These modes check whether it is legal to read or write a file using splice. Both get automatically set on regular files and are not checked when a 'struct fileoperations' includes the splice_{read,write} methods. Suggested-by: Linus Torvalds

[RESEND PATCH v3] ARM64: dts: meson-gx: Add reserved memory zone and usable memory range

The Amlogic Meson GXBB/GXL/GXM secure monitor uses part of the memory space, this patch adds this reserved zone and redefines the usable memory range. The memory node is also moved from the dtsi files into the proper dts files to handle variants memory sizes. This patch also fixes the memory

Re: [PATCH tip/master v4] kprobes: extable: Identify kprobes' insn-slots as kernel text area

On Tue, 10 Jan 2017 15:42:07 -0600 Josh Poimboeuf wrote: > On Tue, Jan 10, 2017 at 09:59:23AM +0100, Peter Zijlstra wrote: > > On Mon, Jan 09, 2017 at 11:36:48AM -0600, Josh Poimboeuf wrote: > > > BTW, I think we'll have more problems with generated code if/when we > > >

Re: [PATCH v4 3/8] PCI: Don't block runtime PM for Thunderbolt host hotplug ports

On Sun, Jan 08, 2017 at 09:41:45AM +0100, Lukas Wunner wrote: > Hotplug ports generally block their parents from suspending to D3hot as > otherwise their interrupts couldn't be delivered. > > An exception are Thunderbolt host controllers: They have a separate > GPIO pin to side-band signal plug

RE: [PATCH v4 1/8] PCI: Recognize Thunderbolt devices

> > On Sun, Jan 08, 2017 at 10:23:03AM +, Winkler, Tomas wrote: > > > We're about to allow runtime PM on Thunderbolt ports in > > > pci_bridge_d3_possible() and unblock runtime PM for Thunderbolt host > > > hotplug ports in pci_dev_check_d3cold(). In both cases we need to > > > uniquely

Re: [tpmdd-devel] [PATCH RFC 0/4] RFC: in-kernel resource manager

Am 10.01.2017 um 21:05 schrieb Jason Gunthorpe: On Tue, Jan 10, 2017 at 01:16:35AM +0200, Jarkko Sakkinen wrote: On Wed, Jan 04, 2017 at 10:12:41AM -0600, Dr. Greg Wettstein wrote: The kernel needs a resource manager. Everyone needs to think VERY hard and VERY, VERY carefully about what gets

Re: [tpmdd-devel] [PATCH RFC 0/4] RFC: in-kernel resource manager

Am 09.01.2017 um 23:39 schrieb Jarkko Sakkinen: On Thu, Jan 05, 2017 at 03:52:02PM +, Fuchs, Andreas wrote: Great to see this coming along so well. Thanks a lot to Jarkko ! I just wanted to point out a few things I deem important at this point: - Number of virtual handles: From what I see

Re: [PATCHv3 3/8] rtc: add STM32 RTC driver

Hi Alexandre, On 01/11/2017 01:08 AM, Alexandre Belloni wrote: Looks good to me, however... On 05/01/2017 at 14:43:24 +0100, Amelie Delaunay wrote : +struct stm32_rtc { + struct rtc_device *rtc_dev; + void __iomem *base; + struct clk *ck_rtc; + spinlock_t lock; /*

Re: [PATCH v3 12/15] livepatch: store function sizes

On Thursday 08 December 2016 11:38 PM, Josh Poimboeuf wrote: For the consistency model we'll need to know the sizes of the old and new functions to determine if they're on the stacks of any tasks. Signed-off-by: Josh Poimboeuf Reviewed-by: Kamalesh Babulal

[PATCH] lpfc: avoid double free of resource identifiers

From: Roberto Sassu Set variables initialized in lpfc_sli4_alloc_resource_identifiers() to NULL if an error occurred. Otherwise, lpfc_sli4_driver_resource_unset() attempts to free the memory again. Signed-off-by: Roberto Sassu Signed-off-by: Johannes Thumshirn

Re: [PATCHv3 3/8] rtc: add STM32 RTC driver

On 11/01/2017 at 11:07:16 +0100, Amelie DELAUNAY wrote : > > This will never happen, tm is already checked multiple times (up to > > three) in the core before this function can be called. > > > You're right. I'll remove all rtc_valid_tm calls. You can keep the one in read_time -- Alexandre

Re: net/atm: warning in alloc_tx/__might_sleep

On Tue, Jan 10, 2017 at 6:40 PM, Eric Dumazet wrote: > On Tue, Jan 10, 2017 at 9:35 AM, Cong Wang wrote: >> On Mon, Jan 9, 2017 at 9:20 AM, Andrey Konovalov >> wrote: >> >> The fix should be straight-forward. Mind to try the

Re: [char-misc for 4.10-rc4 V2] mei: bus: enable OS version only for SPT and newer

Dear Tomas, On 01/11/17 10:24, Winkler, Tomas wrote: On Wed, Jan 11, 2017 at 01:27:21AM +0200, Tomas Winkler wrote: On older platforms the command should be just ignored by the firmware but some older platforms misbehave so it's safer to send the command only if required. Thanks! This

Re: 174cc7187e6f ACPICA: Tables: Back port acpi_get_table_with_size() and early_acpi_os_unmap_memory() from Linux kernel

On Wed, Jan 11, 2017 at 11:03:23AM +0100, Borislav Petkov wrote: > On Wed, Jan 11, 2017 at 01:51:56AM -0800, Paul E. McKenney wrote: > > Yes, you could make RCU expedited grace periods go back to using the > > requesting task, and that would allow expedited grace periods to run early > > in the

Re: [PATCH v8 3/3] arm64: dts: exynos: Add support for S6E3HA2 panel device on TM2 board

On 01/11/2017 06:39 PM, Andrzej Hajda wrote: On 11.01.2017 09:40, Inki Dae wrote: 2017년 01월 11일 16:46에 Andrzej Hajda 이(가) 쓴 글: On 11.01.2017 07:33, Hoegeun Kwon wrote: From: Hyungwon Hwang This patch add the panel device tree node for S6E3HA2 display controller to

Re: [PATCH v8 3/3] arm64: dts: exynos: Add support for S6E3HA2 panel device on TM2 board

On 01/11/2017 06:51 PM, hoegeun kwon wrote: On 01/11/2017 04:46 PM, Andrzej Hajda wrote: On 11.01.2017 07:33, Hoegeun Kwon wrote: From: Hyungwon Hwang This patch add the panel device tree node for S6E3HA2 display controller to TM2 dts. Signed-off-by: Hyungwon

Re: [RFC] drm: Parse HDMI 2.0 YCbCr 4:2:0 VDB and VCB

Hi Ville, On 10-01-2017 17:21, Ville Syrjälä wrote: [snip] >> But we already have color_formats field in drm_display_info >> struct, right? Shouldn't we instead create for example a helper >> which returns the best output colorspace? According to what you >> said it would be something like: >>

[PATCH] PCI/MSI: pci-xgene-msi: Fix CPU hotplug registration handling

The conversion to the new hotplug state machine introduced a regression where a successful hotplug registration would be treated as an error, effectively disabling the MSI driver forever. Fix it by doing the proper check on the return value. Fixes: 9c248f8896e6 ("PCI/xgene-msi: Convert to

Re: [PATCH] perf/x86/intel/uncore: Initialize with correct logical package ID

On Tue, 3 Jan 2017, Prarit Bhargava wrote: > On multi-socket Intel v3 processor systems (aka Haswell) kdump can fail with: > > BUG: unable to handle kernel paging request at 006563a1 > IP: [] hswep_uncore_cpu_init+0x52/0xa0 > PGD 0 [2.313897] > Oops: [#1] SMP > Modules linked

Re: [PATCH v6 04/14] irqchip: gicv3-its: platform-msi: refactor its_pmsi_prepare()

On 02/01/17 14:31, Hanjun Guo wrote: Adding ACPI support for platform MSI, we need to retrieve the dev id in ACPI way instead of device tree, we already have a well formed function its_pmsi_prepare() to get the dev id but it's OF dependent, so collect OF related code and put them into a single

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