Re: [PATCH V3 1/9] PM / OPP: Reword binding supporting multiple regulators per device

On 09-11-16, 14:58, Mark Brown wrote: > On Wed, Oct 26, 2016 at 12:02:56PM +0530, Viresh Kumar wrote: > > > + Entries for multiple regulators shall be provided in the same field > > separated > > + by angular brackets <>. The OPP binding doesn't provide any provisions to > > + relate the

Re: [PATCH V3 1/9] PM / OPP: Reword binding supporting multiple regulators per device

On 09-11-16, 14:58, Mark Brown wrote: > On Wed, Oct 26, 2016 at 12:02:56PM +0530, Viresh Kumar wrote: > > > + Entries for multiple regulators shall be provided in the same field > > separated > > + by angular brackets <>. The OPP binding doesn't provide any provisions to > > + relate the

Re: [PATCH] drivers: tca8418: Change the interrupt type

Hi Maxime, On Wed, Nov 09, 2016 at 09:02:35AM +0100, Maxime Ripard wrote: > Hello Dmitry, > > On Tue, Nov 08, 2016 at 04:04:00PM -0800, Dmitry Torokhov wrote: > > On Mon, Nov 07, 2016 at 03:40:24PM +0100, Maxime Ripard wrote: > > > The TCA8418 interrupt has a level trigger, not a edge one. > > >

Re: [PATCH] drivers: tca8418: Change the interrupt type

Hi Maxime, On Wed, Nov 09, 2016 at 09:02:35AM +0100, Maxime Ripard wrote: > Hello Dmitry, > > On Tue, Nov 08, 2016 at 04:04:00PM -0800, Dmitry Torokhov wrote: > > On Mon, Nov 07, 2016 at 03:40:24PM +0100, Maxime Ripard wrote: > > > The TCA8418 interrupt has a level trigger, not a edge one. > > >

Re: [PATCH] x86/cpuid: Deal with broken firmware once more

On 11/09/2016 06:35 PM, Thomas Gleixner wrote: > Both ACPI and MP specifications require that the APIC id in the respective > tables must be the same as the APIC id in CPUID. > > The kernel retrieves the physical package id from the APIC id during the > ACPI/MP table scan and builds the physical

Re: [PATCH] x86/cpuid: Deal with broken firmware once more

On 11/09/2016 06:35 PM, Thomas Gleixner wrote: > Both ACPI and MP specifications require that the APIC id in the respective > tables must be the same as the APIC id in CPUID. > > The kernel retrieves the physical package id from the APIC id during the > ACPI/MP table scan and builds the physical

Re: [v16, 0/7] Fix eSDHC host version register bug

On Wed, 2016-11-09 at 19:27 +0100, Ulf Hansson wrote: > - i2c-list > > On 9 November 2016 at 04:14, Yangbo Lu wrote: > > > > This patchset is used to fix a host version register bug in the T4240- > > R1.0-R2.0 > > eSDHC controller. To match the SoC version and revision, 15

Re: [v16, 0/7] Fix eSDHC host version register bug

On Wed, 2016-11-09 at 19:27 +0100, Ulf Hansson wrote: > - i2c-list > > On 9 November 2016 at 04:14, Yangbo Lu wrote: > > > > This patchset is used to fix a host version register bug in the T4240- > > R1.0-R2.0 > > eSDHC controller. To match the SoC version and revision, 15 previous > > version

[PATCH] r8152: Fix error path in open function

If usb_submit_urb() called from the open function fails, the following crash may be observed. r8152 8-1:1.0 eth0: intr_urb submit failed: -19 ... r8152 8-1:1.0 eth0: v1.08.3 Unable to handle kernel paging request at virtual address 6b6b6b6b6b6b6b7b pgd = ffc0e7305000 [6b6b6b6b6b6b6b7b]

[PATCH] r8152: Fix error path in open function

If usb_submit_urb() called from the open function fails, the following crash may be observed. r8152 8-1:1.0 eth0: intr_urb submit failed: -19 ... r8152 8-1:1.0 eth0: v1.08.3 Unable to handle kernel paging request at virtual address 6b6b6b6b6b6b6b7b pgd = ffc0e7305000 [6b6b6b6b6b6b6b7b]

linux-next: Tree for Nov 10

Hi all, Changes since 20161109: The asm-generic tree gained a conflict against Linus' tree. The net-next tree gained conflicts against the net and netfilter trees. The drm-misc tree lost its build failure. The sound-asoc tree lost its build failure. The mmc tree gained a conflict against

linux-next: Tree for Nov 10

Hi all, Changes since 20161109: The asm-generic tree gained a conflict against Linus' tree. The net-next tree gained conflicts against the net and netfilter trees. The drm-misc tree lost its build failure. The sound-asoc tree lost its build failure. The mmc tree gained a conflict against

[PATCH] arm64: dts: Add ARM PMU node for exynos7

This patch adds ARM Performance Monitor Unit dt node for exynos7. PMU provides various statistics on the operation of the CPU and memory system at runtime, which are very useful when debugging or profiling code. This enables the same. Signed-off-by: Alim Akhtar ---

[PATCH] arm64: dts: Add ARM PMU node for exynos7

This patch adds ARM Performance Monitor Unit dt node for exynos7. PMU provides various statistics on the operation of the CPU and memory system at runtime, which are very useful when debugging or profiling code. This enables the same. Signed-off-by: Alim Akhtar ---

[PATCH v10 03/10] kexec_file: Factor out kexec_locate_mem_hole from kexec_add_buffer.

kexec_locate_mem_hole will be used by the PowerPC kexec_file_load implementation to find free memory for the purgatory stack. Signed-off-by: Thiago Jung Bauermann Acked-by: Dave Young --- include/linux/kexec.h | 1 + kernel/kexec_file.c | 25

[PATCH v10 06/10] powerpc: Implement kexec_file_load.

Add arch-specific functions needed by the generic kexec_file code. Signed-off-by: Josh Sklar Signed-off-by: Thiago Jung Bauermann --- arch/powerpc/Kconfig| 14 ++ arch/powerpc/include/asm/systbl.h | 1 +

[PATCH v10 03/10] kexec_file: Factor out kexec_locate_mem_hole from kexec_add_buffer.

kexec_locate_mem_hole will be used by the PowerPC kexec_file_load implementation to find free memory for the purgatory stack. Signed-off-by: Thiago Jung Bauermann Acked-by: Dave Young --- include/linux/kexec.h | 1 + kernel/kexec_file.c | 25 - 2 files changed, 21

[PATCH v10 06/10] powerpc: Implement kexec_file_load.

Add arch-specific functions needed by the generic kexec_file code. Signed-off-by: Josh Sklar Signed-off-by: Thiago Jung Bauermann --- arch/powerpc/Kconfig| 14 ++ arch/powerpc/include/asm/systbl.h | 1 + arch/powerpc/include/asm/unistd.h | 2 +-

[PATCH v10 05/10] powerpc: Change places using CONFIG_KEXEC to use CONFIG_KEXEC_CORE instead.

Commit 2965faa5e03d ("kexec: split kexec_load syscall from kexec core code") introduced CONFIG_KEXEC_CORE so that CONFIG_KEXEC means whether the kexec_load system call should be compiled-in and CONFIG_KEXEC_FILE means whether the kexec_file_load system call should be compiled-in. These options can

[PATCH v10 10/10] powerpc: Enable CONFIG_KEXEC_FILE in powerpc server defconfigs.

Enable CONFIG_KEXEC_FILE in powernv_defconfig, ppc64_defconfig and pseries_defconfig. It depends on CONFIG_CRYPTO_SHA256=y, so add that as well. Signed-off-by: Thiago Jung Bauermann --- arch/powerpc/configs/powernv_defconfig | 2 ++

[PATCH v10 07/10] powerpc: Add functions to read ELF files of any endianness.

A little endian kernel might need to kexec a big endian kernel (the opposite is less likely but could happen as well), so we can't just cast the buffer with the binary to ELF structs and use them as is done elsewhere. This patch adds functions which do byte-swapping as necessary when populating

[PATCH v10 05/10] powerpc: Change places using CONFIG_KEXEC to use CONFIG_KEXEC_CORE instead.

Commit 2965faa5e03d ("kexec: split kexec_load syscall from kexec core code") introduced CONFIG_KEXEC_CORE so that CONFIG_KEXEC means whether the kexec_load system call should be compiled-in and CONFIG_KEXEC_FILE means whether the kexec_file_load system call should be compiled-in. These options can

[PATCH v10 10/10] powerpc: Enable CONFIG_KEXEC_FILE in powerpc server defconfigs.

Enable CONFIG_KEXEC_FILE in powernv_defconfig, ppc64_defconfig and pseries_defconfig. It depends on CONFIG_CRYPTO_SHA256=y, so add that as well. Signed-off-by: Thiago Jung Bauermann --- arch/powerpc/configs/powernv_defconfig | 2 ++ arch/powerpc/configs/ppc64_defconfig | 2 ++

[PATCH v10 07/10] powerpc: Add functions to read ELF files of any endianness.

A little endian kernel might need to kexec a big endian kernel (the opposite is less likely but could happen as well), so we can't just cast the buffer with the binary to ELF structs and use them as is done elsewhere. This patch adds functions which do byte-swapping as necessary when populating

[PATCH v10 04/10] kexec_file: Add support for purgatory built as PIE.

powerpc's purgatory.ro has 12 relocation types when built as a relocatable object. To implement support for them requires arch_kexec_apply_relocations_add to duplicate a lot of code with module_64.c:apply_relocate_add. When built as a Position Independent Executable there are only 4 relocation

[PATCH v10 08/10] powerpc: Add support for loading ELF kernels with kexec_file_load.

This uses all the infrastructure built up by the previous patches in the series to load an ELF vmlinux file and an initrd. It uses the flattened device tree at initial_boot_params as a base and adjusts memory reservations and its /chosen node for the next kernel. [a...@linux-foundation.org:

[PATCH v10 02/10] kexec_file: Change kexec_add_buffer to take kexec_buf as argument.

This is done to simplify the kexec_add_buffer argument list. Adapt all callers to set up a kexec_buf to pass to kexec_add_buffer. In addition, change the type of kexec_buf.buffer from char * to void *. There is no particular reason for it to be a char *, and the change allows us to get rid of 3

RE: [PATCH 3/3] clk: qcom: Set BRANCH_HALT_DELAY flags for venus core0/1 clks

Hi Rajendra, > >>> >>> The proper sequence sounds like it should be: >>> >>> 1. Enable GDSC for main domain >>> 2. Enable clocks for main domain (video_{core,maxi,ahb,axi}_clk) >>> 3. Write the two registers to assert hw signal for subdomains >>> 4. Enable GDSCs for two subdomains

[PATCH v10 09/10] powerpc: Add purgatory for kexec_file_load implementation.

This purgatory implementation comes from kexec-tools and was trimmed down a bit. It uses the memset, memcpy and memcmp implementations from lib/string.c. It's not straightforward to #include "lib/string.c" so we simply copy those functions. The changes made to the purgatory code relative to the

[PATCH v10 04/10] kexec_file: Add support for purgatory built as PIE.

powerpc's purgatory.ro has 12 relocation types when built as a relocatable object. To implement support for them requires arch_kexec_apply_relocations_add to duplicate a lot of code with module_64.c:apply_relocate_add. When built as a Position Independent Executable there are only 4 relocation

[PATCH v10 08/10] powerpc: Add support for loading ELF kernels with kexec_file_load.

This uses all the infrastructure built up by the previous patches in the series to load an ELF vmlinux file and an initrd. It uses the flattened device tree at initial_boot_params as a base and adjusts memory reservations and its /chosen node for the next kernel. [a...@linux-foundation.org:

[PATCH v10 02/10] kexec_file: Change kexec_add_buffer to take kexec_buf as argument.

This is done to simplify the kexec_add_buffer argument list. Adapt all callers to set up a kexec_buf to pass to kexec_add_buffer. In addition, change the type of kexec_buf.buffer from char * to void *. There is no particular reason for it to be a char *, and the change allows us to get rid of 3

RE: [PATCH 3/3] clk: qcom: Set BRANCH_HALT_DELAY flags for venus core0/1 clks

Hi Rajendra, > >>> >>> The proper sequence sounds like it should be: >>> >>> 1. Enable GDSC for main domain >>> 2. Enable clocks for main domain (video_{core,maxi,ahb,axi}_clk) >>> 3. Write the two registers to assert hw signal for subdomains >>> 4. Enable GDSCs for two subdomains

[PATCH v10 09/10] powerpc: Add purgatory for kexec_file_load implementation.

This purgatory implementation comes from kexec-tools and was trimmed down a bit. It uses the memset, memcpy and memcmp implementations from lib/string.c. It's not straightforward to #include "lib/string.c" so we simply copy those functions. The changes made to the purgatory code relative to the

[PATCH v10 00/10] kexec_file_load implementation for PowerPC

Hello, [ Andrew, you might want to wait until the kexec maintainers say whether they agree with patch 4 before picking up this version. ] v10 addresses two requests from Michael Ellerman: build the purgatory as a Position Independent Executable binary to reduce the number of relocation types

[PATCH v10 00/10] kexec_file_load implementation for PowerPC

Hello, [ Andrew, you might want to wait until the kexec maintainers say whether they agree with patch 4 before picking up this version. ] v10 addresses two requests from Michael Ellerman: build the purgatory as a Position Independent Executable binary to reduce the number of relocation types

[PATCH v10 01/10] kexec_file: Allow arch-specific memory walking for kexec_add_buffer

Allow architectures to specify a different memory walking function for kexec_add_buffer. x86 uses iomem to track reserved memory ranges, but PowerPC uses the memblock subsystem. Signed-off-by: Thiago Jung Bauermann Acked-by: Dave Young Acked-by:

[PATCH v10 01/10] kexec_file: Allow arch-specific memory walking for kexec_add_buffer

Allow architectures to specify a different memory walking function for kexec_add_buffer. x86 uses iomem to track reserved memory ranges, but PowerPC uses the memblock subsystem. Signed-off-by: Thiago Jung Bauermann Acked-by: Dave Young Acked-by: Balbir Singh --- include/linux/kexec.h | 29

Re: [PATCH 1/4] x86/cpufeature: Add User-Mode Instruction Prevention definitions

On Wed, 2016-11-09 at 03:02 -0800, Andy Lutomirski wrote: > On Tue, Nov 8, 2016 at 8:25 PM, Ricardo Neri > wrote: > > On Tue, 2016-11-08 at 07:32 -0800, Andy Lutomirski wrote: > >> > diff --git a/arch/x86/include/asm/disabled-features.h > >>

Re: [PATCH 1/4] x86/cpufeature: Add User-Mode Instruction Prevention definitions

On Wed, 2016-11-09 at 03:02 -0800, Andy Lutomirski wrote: > On Tue, Nov 8, 2016 at 8:25 PM, Ricardo Neri > wrote: > > On Tue, 2016-11-08 at 07:32 -0800, Andy Lutomirski wrote: > >> > diff --git a/arch/x86/include/asm/disabled-features.h > >> b/arch/x86/include/asm/disabled-features.h > >> > index

Re: [PATCH V11 1/1] usb:serial: Add Fintek F81532/534 driver

Hi Johan, Johan Hovold 於 2016/11/2 下午 08:37 寫道: On Fri, Oct 14, 2016 at 04:20:46PM +0800, Ji-Ze Hong (Peter Hong) wrote: Reviewed-by: Johan Hovold You must never add other peoples' Reviewed-by tags unless you've explicitly been given permission to do so (e.g. "fix this

Re: [PATCH V11 1/1] usb:serial: Add Fintek F81532/534 driver

Hi Johan, Johan Hovold 於 2016/11/2 下午 08:37 寫道: On Fri, Oct 14, 2016 at 04:20:46PM +0800, Ji-Ze Hong (Peter Hong) wrote: Reviewed-by: Johan Hovold You must never add other peoples' Reviewed-by tags unless you've explicitly been given permission to do so (e.g. "fix this minor thing up and

Re: [PATCH v2 2/6] mfd: dt: Add bindings for the Aspeed SoC Display Controller (GFX)

On Thu, Nov 10, 2016 at 4:56 AM, Rob Herring wrote: > On Thu, Nov 03, 2016 at 01:07:57AM +1030, Andrew Jeffery wrote: >> The Aspeed SoC Display Controller is presented as a syscon device to >> arbitrate access by display and pinmux drivers. Video pinmux >> configuration on fifth

Re: [PATCH v2 2/6] mfd: dt: Add bindings for the Aspeed SoC Display Controller (GFX)

On Thu, Nov 10, 2016 at 4:56 AM, Rob Herring wrote: > On Thu, Nov 03, 2016 at 01:07:57AM +1030, Andrew Jeffery wrote: >> The Aspeed SoC Display Controller is presented as a syscon device to >> arbitrate access by display and pinmux drivers. Video pinmux >> configuration on fifth generation SoCs

Re: [RFC] mem-hotplug: shall we skip unmovable node when doing numa balance?

On 2016/11/9 19:58, Mel Gorman wrote: > On Tue, Nov 08, 2016 at 12:43:17PM +0800, Xishi Qiu wrote: >> On mem-hotplug system, there is a problem, please see the following case. >> >> memtester xxG, the memory will be alloced on a movable node. And after numa >> balancing, the memory may be

Re: [RFC] mem-hotplug: shall we skip unmovable node when doing numa balance?

On 2016/11/9 19:58, Mel Gorman wrote: > On Tue, Nov 08, 2016 at 12:43:17PM +0800, Xishi Qiu wrote: >> On mem-hotplug system, there is a problem, please see the following case. >> >> memtester xxG, the memory will be alloced on a movable node. And after numa >> balancing, the memory may be

Re: [PATCH] iio: cros_ec_sensors_core: fix unsigned compared less than zero on status

On Wed, Nov 9, 2016 at 3:12 PM, Colin King wrote: > From: Colin Ian King > > status is a u8 hence the check if status is less than zero has no effect. > Fix this by replacing status with int ret so the less than zero compare > will correctly

Re: [PATCH] iio: cros_ec_sensors_core: fix unsigned compared less than zero on status

On Wed, Nov 9, 2016 at 3:12 PM, Colin King wrote: > From: Colin Ian King > > status is a u8 hence the check if status is less than zero has no effect. > Fix this by replacing status with int ret so the less than zero compare > will correctly detect errors. > > Issue found with static analysis

Re: linux-next: build warning after merge of the akpm-current tree

Hi Andrew, On Wed, 9 Nov 2016 13:21:53 -0800 Andrew Morton wrote: > > On Wed, 9 Nov 2016 15:18:24 +0800 Huang Shijie wrote: > > > On Wed, Nov 09, 2016 at 03:10:06PM +1100, Stephen Rothwell wrote: > > Hi Stephen, > > > Hi Andrew, > > > > > >

[PATCH v4] i2c: designware: Implement support for SMBus block read and write

From: Tin Huynh Free and Open IPMI use SMBUS BLOCK Read/Write to support SSIF protocol. However, I2C Designware Core Driver doesn't handle the case at the moment. The below patch supports this feature. Signed-off-by: Tin Huynh --- Change from V3: - Correct

Re: linux-next: build warning after merge of the akpm-current tree

Hi Andrew, On Wed, 9 Nov 2016 13:21:53 -0800 Andrew Morton wrote: > > On Wed, 9 Nov 2016 15:18:24 +0800 Huang Shijie wrote: > > > On Wed, Nov 09, 2016 at 03:10:06PM +1100, Stephen Rothwell wrote: > > Hi Stephen, > > > Hi Andrew, > > > > > > After merging the akpm-current tree, today's

[PATCH v4] i2c: designware: Implement support for SMBus block read and write

From: Tin Huynh Free and Open IPMI use SMBUS BLOCK Read/Write to support SSIF protocol. However, I2C Designware Core Driver doesn't handle the case at the moment. The below patch supports this feature. Signed-off-by: Tin Huynh --- Change from V3: - Correct coding conventions - Make clean

Re: [PATCH] phy: rockchip-inno-usb2: correct 480MHz output clock stable time

Hi Doug, 在 2016年11月10日 04:54, Doug Anderson 写道: Hi, On Mon, Nov 7, 2016 at 5:00 AM, William Wu wrote: We found that the system crashed due to 480MHz output clock of USB2 PHY was unstable after clock had been enabled by gpu module. Theoretically, 1 millisecond is a

Re: [PATCH] phy: rockchip-inno-usb2: correct 480MHz output clock stable time

Hi Doug, 在 2016年11月10日 04:54, Doug Anderson 写道: Hi, On Mon, Nov 7, 2016 at 5:00 AM, William Wu wrote: We found that the system crashed due to 480MHz output clock of USB2 PHY was unstable after clock had been enabled by gpu module. Theoretically, 1 millisecond is a critical value for 480MHz

Re: [PATCH v4] KVM: x86: emulate FXSAVE and FXRSTOR

-next] [also build test ERROR on v4.9-rc4 next-20161109] [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/Radim-Kr-m/KVM-x86-emulate-FXSAVE-and-FXRSTOR/20161110-021048 base: https://git.kernel.org

Re: [PATCH v4] KVM: x86: emulate FXSAVE and FXRSTOR

-next] [also build test ERROR on v4.9-rc4 next-20161109] [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/Radim-Kr-m/KVM-x86-emulate-FXSAVE-and-FXRSTOR/20161110-021048 base: https://git.kernel.org

Re: [PATCH v5] Net Driver: Add Cypress GX3 VID=04b4 PID=3610.

From: Date: Tue, 8 Nov 2016 16:08:01 -0600 > From: Allan Chou > > Add support for Cypress GX3 SuperSpeed to Gigabit Ethernet > Bridge Controller (Vendor=04b4 ProdID=3610). > > Patch verified on x64 linux kernel 4.7.4, 4.8.6, 4.9-rc4 systems > with the

Re: [PATCH v5] Net Driver: Add Cypress GX3 VID=04b4 PID=3610.

From: Date: Tue, 8 Nov 2016 16:08:01 -0600 > From: Allan Chou > > Add support for Cypress GX3 SuperSpeed to Gigabit Ethernet > Bridge Controller (Vendor=04b4 ProdID=3610). > > Patch verified on x64 linux kernel 4.7.4, 4.8.6, 4.9-rc4 systems > with the Kensington SD4600P USB-C Universal Dock

Re: [PATCH V6 2/3] ACPI: Add support for ResourceSource/IRQ domain mapping

Hi Marc, Rafael, Lorenzo, Since we agreed to add a probe deferral if we failed to get irq resources which mirroring the DT does (patch 1 in this patch set), I think the last blocker to make things work both for Agustin and me [1] is this patch, which makes the interrupt producer and consumer

Re: [PATCH V6 2/3] ACPI: Add support for ResourceSource/IRQ domain mapping

Hi Marc, Rafael, Lorenzo, Since we agreed to add a probe deferral if we failed to get irq resources which mirroring the DT does (patch 1 in this patch set), I think the last blocker to make things work both for Agustin and me [1] is this patch, which makes the interrupt producer and consumer

Re: [PATCH 3/3] clk: qcom: Set BRANCH_HALT_DELAY flags for venus core0/1 clks

[].. >> >> The proper sequence sounds like it should be: >> >> 1. Enable GDSC for main domain >> 2. Enable clocks for main domain (video_{core,maxi,ahb,axi}_clk) >> 3. Write the two registers to assert hw signal for subdomains >> 4. Enable GDSCs for two subdomains >> 5.

Re: [PATCH 3/3] clk: qcom: Set BRANCH_HALT_DELAY flags for venus core0/1 clks

[].. >> >> The proper sequence sounds like it should be: >> >> 1. Enable GDSC for main domain >> 2. Enable clocks for main domain (video_{core,maxi,ahb,axi}_clk) >> 3. Write the two registers to assert hw signal for subdomains >> 4. Enable GDSCs for two subdomains >> 5.

Re: [PATCH] f2fs: support multiple devices

At 11/10/2016 06:57 AM, Andreas Dilger wrote: On Nov 9, 2016, at 1:56 PM, Jaegeuk Kim wrote: This patch implements multiple devices support for f2fs. Given multiple devices by mkfs.f2fs, f2fs shows them entirely as one big volume under one f2fs instance. Internal block

Re: [PATCH] f2fs: support multiple devices

At 11/10/2016 06:57 AM, Andreas Dilger wrote: On Nov 9, 2016, at 1:56 PM, Jaegeuk Kim wrote: This patch implements multiple devices support for f2fs. Given multiple devices by mkfs.f2fs, f2fs shows them entirely as one big volume under one f2fs instance. Internal block management is very

Re: [PATCH 4/4] dts: arm64: enable mmc3 for supporting sdio feature

On Tue, 2016-11-08 at 14:09 +0800, Yong Mao wrote: > From: yong mao > > Add description of mmc3 for supporting sdio feature > > Signed-off-by: Yong Mao > Signed-off-by: Chaotian Jing > --- >

Re: [PATCH 4/4] dts: arm64: enable mmc3 for supporting sdio feature

On Tue, 2016-11-08 at 14:09 +0800, Yong Mao wrote: > From: yong mao > > Add description of mmc3 for supporting sdio feature > > Signed-off-by: Yong Mao > Signed-off-by: Chaotian Jing > --- > arch/arm64/boot/dts/mediatek/mt8173-evb.dts | 82 > +++ > 1 file changed,

Re: [PATCH v3 8/9] media: venus: add Makefiles and Kconfig files

On 11/07, Stanimir Varbanov wrote: > diff --git a/drivers/media/platform/qcom/Kconfig > b/drivers/media/platform/qcom/Kconfig > new file mode 100644 > index ..bf4d2fcce924 > --- /dev/null > +++ b/drivers/media/platform/qcom/Kconfig > @@ -0,0 +1,7 @@ > + > +menuconfig VIDEO_QCOM_VENUS

Re: [PATCH v3 8/9] media: venus: add Makefiles and Kconfig files

On 11/07, Stanimir Varbanov wrote: > diff --git a/drivers/media/platform/qcom/Kconfig > b/drivers/media/platform/qcom/Kconfig > new file mode 100644 > index ..bf4d2fcce924 > --- /dev/null > +++ b/drivers/media/platform/qcom/Kconfig > @@ -0,0 +1,7 @@ > + > +menuconfig VIDEO_QCOM_VENUS

[PATCH] PM / wakeirq: forward declare 'struct device'

Drivers might include this header without . Signed-off-by: Brian Norris --- include/linux/pm_wakeirq.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/linux/pm_wakeirq.h b/include/linux/pm_wakeirq.h index cd5b62db9084..49c2220fb245 100644 ---

[PATCH] PM / wakeirq: forward declare 'struct device'

Drivers might include this header without . Signed-off-by: Brian Norris --- include/linux/pm_wakeirq.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/linux/pm_wakeirq.h b/include/linux/pm_wakeirq.h index cd5b62db9084..49c2220fb245 100644 --- a/include/linux/pm_wakeirq.h +++

Re: Summary of LPC guest MSI discussion in Santa Fe

On Wed, Nov 09, 2016 at 05:55:17PM -0700, Alex Williamson wrote: > On Thu, 10 Nov 2016 01:14:42 +0100 > Auger Eric wrote: > > On 10/11/2016 00:59, Alex Williamson wrote: > > > On Wed, 9 Nov 2016 23:38:50 + > > > Will Deacon wrote: > > >> On Wed,

Re: Summary of LPC guest MSI discussion in Santa Fe

On Wed, Nov 09, 2016 at 05:55:17PM -0700, Alex Williamson wrote: > On Thu, 10 Nov 2016 01:14:42 +0100 > Auger Eric wrote: > > On 10/11/2016 00:59, Alex Williamson wrote: > > > On Wed, 9 Nov 2016 23:38:50 + > > > Will Deacon wrote: > > >> On Wed, Nov 09, 2016 at 04:24:58PM -0700, Alex

Re: [PATCH v3] PM / sleep: don't suspend parent when async child suspend_{noirq,late} fails

On Thu, Nov 10, 2016 at 02:53:20AM +0100, Rafael J. Wysocki wrote: > On Thu, Nov 10, 2016 at 2:21 AM, Brian Norris > wrote: > > diff --git a/drivers/base/power/main.c b/drivers/base/power/main.c > > index c58563581345..57a8ca4bc8ab 100644 > > ---

Re: [PATCH v3] PM / sleep: don't suspend parent when async child suspend_{noirq,late} fails

On Thu, Nov 10, 2016 at 02:53:20AM +0100, Rafael J. Wysocki wrote: > On Thu, Nov 10, 2016 at 2:21 AM, Brian Norris > wrote: > > diff --git a/drivers/base/power/main.c b/drivers/base/power/main.c > > index c58563581345..57a8ca4bc8ab 100644 > > --- a/drivers/base/power/main.c > > +++

[PATCH] gpio: Guard devm_* functions behind CONFIG_GPIO_DEVRES not CONFIG_GPIOLIB

These functions are defined in devres.c, which only gets compiled with CONFIG_GPIO_DEVRES (in addition to CONFIG_GPIOLIB). However, in the header files, the difference between the declaration and the inline stub was only guarded by CONFIG_GPIOLIB, not CONFIG_GPIO_DEVRES, causing undefined symbol

[PATCH] gpio: Guard devm_* functions behind CONFIG_GPIO_DEVRES not CONFIG_GPIOLIB

These functions are defined in devres.c, which only gets compiled with CONFIG_GPIO_DEVRES (in addition to CONFIG_GPIOLIB). However, in the header files, the difference between the declaration and the inline stub was only guarded by CONFIG_GPIOLIB, not CONFIG_GPIO_DEVRES, causing undefined symbol

Re: [PATCH v2 2/3] dt-binding: remoteproc: venus rproc dt binding document

On 11/07, Stanimir Varbanov wrote: > diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,venus.txt > b/Documentation/devicetree/bindings/remoteproc/qcom,venus.txt > new file mode 100644 > index ..06a2db60fa38 > --- /dev/null > +++

Re: [PATCH v2 2/3] dt-binding: remoteproc: venus rproc dt binding document

On 11/07, Stanimir Varbanov wrote: > diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,venus.txt > b/Documentation/devicetree/bindings/remoteproc/qcom,venus.txt > new file mode 100644 > index ..06a2db60fa38 > --- /dev/null > +++

Re: [PATCH v3] PM / sleep: don't suspend parent when async child suspend_{noirq,late} fails

On Thu, Nov 10, 2016 at 2:21 AM, Brian Norris wrote: > Consider two devices, A and B, where B is a child of A, and B utilizes > asynchronous suspend (it does not matter whether A is sync or async). If > B fails to suspend_noirq() or suspend_late(), or is interrupted by a

[PATCH] um: Fix compile failure due to current_text_address() definition

Fixes the following link error: ``` /usr/bin/ld: net/built-in.o: relocation R_X86_64_32S against `.text' can not be used when making a shared object; recompile with -fPIC ``` This is the same definition used on some other architectures. Signed-off-by: Keno Fischer --- I

Re: [PATCH v3] PM / sleep: don't suspend parent when async child suspend_{noirq,late} fails

On Thu, Nov 10, 2016 at 2:21 AM, Brian Norris wrote: > Consider two devices, A and B, where B is a child of A, and B utilizes > asynchronous suspend (it does not matter whether A is sync or async). If > B fails to suspend_noirq() or suspend_late(), or is interrupted by a > wakeup

[PATCH] um: Fix compile failure due to current_text_address() definition

Fixes the following link error: ``` /usr/bin/ld: net/built-in.o: relocation R_X86_64_32S against `.text' can not be used when making a shared object; recompile with -fPIC ``` This is the same definition used on some other architectures. Signed-off-by: Keno Fischer --- I am not sure this is the

Re: [PATCH v2 1/3] firmware: qcom: scm: add a video command for state setting

On 11/07, Stanimir Varbanov wrote: > diff --git a/drivers/firmware/qcom_scm.c b/drivers/firmware/qcom_scm.c > index d95c70227c05..7e364691a87c 100644 > --- a/drivers/firmware/qcom_scm.c > +++ b/drivers/firmware/qcom_scm.c > @@ -320,6 +320,22 @@ bool qcom_scm_is_available(void) > } >

Re: [PATCH v2 1/3] firmware: qcom: scm: add a video command for state setting

On 11/07, Stanimir Varbanov wrote: > diff --git a/drivers/firmware/qcom_scm.c b/drivers/firmware/qcom_scm.c > index d95c70227c05..7e364691a87c 100644 > --- a/drivers/firmware/qcom_scm.c > +++ b/drivers/firmware/qcom_scm.c > @@ -320,6 +320,22 @@ bool qcom_scm_is_available(void) > } >

Re: Proposal: HAVE_SEPARATE_IRQ_STACK?

On 11/09/2016 01:27 PM, Jason A. Donenfeld wrote: Hi folks, I do some ECC crypto in a kthread. A fast 32bit implementation usually uses around 2k - 3k bytes of stack. Since kernel threads get 8k, I figured this would be okay. And for the most part, it is. However, everything falls apart on

Re: Proposal: HAVE_SEPARATE_IRQ_STACK?

On 11/09/2016 01:27 PM, Jason A. Donenfeld wrote: Hi folks, I do some ECC crypto in a kthread. A fast 32bit implementation usually uses around 2k - 3k bytes of stack. Since kernel threads get 8k, I figured this would be okay. And for the most part, it is. However, everything falls apart on

Re: [PATCH 1/1] arm64: dts: msm8996: Add SCM DT node

On 10/28, Sarangdhar Joshi wrote: > Add SCM DT node to enable SCM functionality on MSM8996. > > Signed-off-by: Sarangdhar Joshi > --- Reviewed-by: Stephen Boyd -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux

Re: [PATCH 1/1] arm64: dts: msm8996: Add SCM DT node

On 10/28, Sarangdhar Joshi wrote: > Add SCM DT node to enable SCM functionality on MSM8996. > > Signed-off-by: Sarangdhar Joshi > --- Reviewed-by: Stephen Boyd -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

Re: [PATCH v2 1/3] dt-bindings: firmware: scm: Add MSM8996 DT bindings

On 11/03, Sarangdhar Joshi wrote: > Add SCM DT bindings for Qualcomm's MSM8996 platform. > > Acked-by: Rob Herring > Signed-off-by: Sarangdhar Joshi > --- Reviewed-by: Stephen Boyd -- Qualcomm Innovation Center, Inc. is a member

Re: [PATCH v2 1/3] dt-bindings: firmware: scm: Add MSM8996 DT bindings

On 11/03, Sarangdhar Joshi wrote: > Add SCM DT bindings for Qualcomm's MSM8996 platform. > > Acked-by: Rob Herring > Signed-off-by: Sarangdhar Joshi > --- Reviewed-by: Stephen Boyd -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

Re: [PATCH v2 3/3] firmware: qcom: scm: Return PTR_ERR when devm_clk_get fails

On 11/03, Sarangdhar Joshi wrote: > When devm_clk_get fails for core clock, the failure was ignored > and the core_clk was explicitly set to NULL so that other > remaining clocks can be queried. However, now that we have a > cleaner way of expressing the clock dependency, return failure > when

Re: [PATCH v2 3/3] firmware: qcom: scm: Return PTR_ERR when devm_clk_get fails

On 11/03, Sarangdhar Joshi wrote: > When devm_clk_get fails for core clock, the failure was ignored > and the core_clk was explicitly set to NULL so that other > remaining clocks can be queried. However, now that we have a > cleaner way of expressing the clock dependency, return failure > when

Re: Proposal: HAVE_SEPARATE_IRQ_STACK?

On Thu, Nov 10, 2016 at 1:17 AM, David Daney wrote: > Easiest thing to do would be to select 16K page size in your .config, I > think that will give you a similar sized stack. I didn't realize that was possible... I'm mostly concerned about the best way to deal with

Re: Proposal: HAVE_SEPARATE_IRQ_STACK?

On Thu, Nov 10, 2016 at 1:17 AM, David Daney wrote: > Easiest thing to do would be to select 16K page size in your .config, I > think that will give you a similar sized stack. I didn't realize that was possible... I'm mostly concerned about the best way to deal with systems that have a limited

Re: [PATCH v2 2/3] firmware: qcom: scm: Remove core, iface and bus clocks dependency

On 11/03, Sarangdhar Joshi wrote: > diff --git a/drivers/firmware/qcom_scm.c b/drivers/firmware/qcom_scm.c > index d79fecd..844e90d 100644 > --- a/drivers/firmware/qcom_scm.c > +++ b/drivers/firmware/qcom_scm.c > @@ -380,32 +384,40 @@ EXPORT_SYMBOL(qcom_scm_is_available); > static int

Re: [PATCH v2 2/3] firmware: qcom: scm: Remove core, iface and bus clocks dependency

On 11/03, Sarangdhar Joshi wrote: > diff --git a/drivers/firmware/qcom_scm.c b/drivers/firmware/qcom_scm.c > index d79fecd..844e90d 100644 > --- a/drivers/firmware/qcom_scm.c > +++ b/drivers/firmware/qcom_scm.c > @@ -380,32 +384,40 @@ EXPORT_SYMBOL(qcom_scm_is_available); > static int

Re: task isolation discussion at Linux Plumbers

On Wed, Nov 9, 2016 at 9:38 AM, Paul E. McKenney wrote: Are you planning on changing rcu_nmi_enter()? It would make it easier to figure out how they interact if I could see the code. > diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c > index

Re: task isolation discussion at Linux Plumbers

On Wed, Nov 9, 2016 at 9:38 AM, Paul E. McKenney wrote: Are you planning on changing rcu_nmi_enter()? It would make it easier to figure out how they interact if I could see the code. > diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c > index dbf20b058f48..342c8ee402d6 100644 > ---

Re: [PATCH] [RFC] drivers: dma-coherent: use MEMREMAP_WB instead of MEMREMAP_WC

Hi On 2016년 11월 09일 19:23, Brian Starkey wrote: > Hi, > > On Wed, Nov 09, 2016 at 06:47:26PM +0900, Jaewon Kim wrote: >> >> >> On 2016년 11월 09일 18:27, Brian Starkey wrote: >>> Hi Jaewon, >>> >>> On Wed, Nov 09, 2016 at 06:10:09PM +0900, Jaewon Kim wrote: Commit 6b03ae0d42bf (drivers:

Re: [PATCH] [RFC] drivers: dma-coherent: use MEMREMAP_WB instead of MEMREMAP_WC

Hi On 2016년 11월 09일 19:23, Brian Starkey wrote: > Hi, > > On Wed, Nov 09, 2016 at 06:47:26PM +0900, Jaewon Kim wrote: >> >> >> On 2016년 11월 09일 18:27, Brian Starkey wrote: >>> Hi Jaewon, >>> >>> On Wed, Nov 09, 2016 at 06:10:09PM +0900, Jaewon Kim wrote: Commit 6b03ae0d42bf (drivers:

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