[PATCH v4 2/2] Input: add support for the STMicroelectronics FingerTip touchscreen

The stmfts (ST-Microelectronics FingerTip S) touchscreen device is a capacitive multi-touch controller mainly for mobile use. It's connected through i2c bus at the address 0x49 and it interfaces with userspace through input event interface. At the current state it provides a touchscreen multitouc

[PATCH v4 1/2] Input: add STMicroelectronics FingerTip touchscreen driver

Add binding for the STMicroelectronics FingerTip (stmfts) touchscreen driver. Signed-off-by: Andi Shyti Reviewed-by: Javier Martinez Canillas Acked-by: Rob Herring --- .../bindings/input/touchscreen/st,stmfts.txt | 43 ++ 1 file changed, 43 insertions(+) create mode

[PATCH v4 0/2] STM FingerTip S touchscreen support for TM2 board

Hi, this patchset provides support for the ST-Microelectronics FingerTip S touchscreen device. It's tested on top of mainline kernel on TM2 and TM2e boards. Thanks, Andi Changelog V3-V4 === V3: https://marc.info/?l=linux-kernel&m=149062016401170&w=2 After an offline discussion, I ap

[PATCH v9 2/4] arm64: dts: hisi: add kirin pcie node

Add PCIe node for hi3660, and add binding documentation. Cc: Guodong Xu Signed-off-by: Xiaowei Song --- arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 31 +++ 1 file changed, 31 insertions(+) diff --git a/arch/arm64/boot/dts/hisilicon/hi3660.dtsi b/arch/arm64/boot/dts

[PATCH v9 1/4] PCI: hisi: Add DT binding for PCIe of Kirin SoC series

Signed-off-by: Xiaowei Song --- .../devicetree/bindings/pci/kirin-pcie.txt | 50 ++ 1 file changed, 50 insertions(+) create mode 100644 Documentation/devicetree/bindings/pci/kirin-pcie.txt diff --git a/Documentation/devicetree/bindings/pci/kirin-pcie.txt b/Documenta

[PATCH v9 0/4] add PCIe driver for Kirin PCIe

Before Version Patches == patch V8 http://www.spinics.net/lists/linux-pci/msg61715.html patch V7 https://www.spinics.net/lists/linux-pci/msg61664.html patch V6 https://www.spinics.net/lists/linux-pci/msg61610.html patch V4 https://www.spinics.net/lists/linux-pci/msg61406.html

[PATCH v9 4/4] ARM64: defconfig: Enable Kirin PCIe

Cc: Guodong Xu Signed-off-by: Xiaowei Song --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index 7c48028ec64a..d56d8f1062ab 100644 --- a/arch/arm64/configs/defconfig +++ b/arch/arm64/configs/defconfi

[PATCH v9 3/4] PCI: dwc: kirin: add PCIe Driver for HiSilicon Kirin SoC

Hisilicon PCIe Driver shares the common functions for PCIe dw-host The poweron functions is developed on hi3660 SoC, while Others Functions are common for Kirin series SoCs. Low power mode (L1 sub-state and Suspend/Resume), hotplug and MSI feature are not supported currently. Cc: Guodong Xu Sig

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

> Dear fellow Maintainers, > > Enjoy! ... or not! Please remove these patches from your tree, since they cause build problems in the USB subsystem. I have asked Kuppuswamy to squash all un-bisectable patches and re-submit. Once in my possession, the plan is to push out another pull-request. >

Re: Q. drm/i915 shrinker, synchronize_rcu_expedited() from handlers

On Tue, 30 May 2017, Hugh Dickins wrote: > On Mon, 22 May 2017, Joonas Lahtinen wrote: >> On la, 2017-05-20 at 10:56 +0900, J. R. Okajima wrote: >> > "J. R. Okajima": >> > > >> > > I don't know whether the fix is good to me or not yet. I will test your >> > > fix, but I am busy now and my test wi

[PATCH] mISDN: Fix a sleep-in-atomic bug

The driver may sleep under a read spin lock, and the function call path is: send_socklist (acquire the lock by read_lock) skb_copy(GFP_KERNEL) --> may sleep To fix it, the "GFP_KERNEL" is replaced with "GFP_ATOMIC". Signed-off-by: Jia-Ju Bai --- drivers/isdn/mISDN/stack.c |2 +- 1 file ch

Re: [PATCH v2] perf: fix double free at function perf_hpp__reset_output_field

Hi jirka, Will you send a patch to fix this issue? If not I will send my solution in a new thread. I have given up to add 'dynamic sort' feature since my code is not working and I am engaged in other things. I still hope this fix can be picked up. Thanks! On Wed, Apr 12, 2017 at 09:48:08AM +0800

[PATCH] i2c: at91: Fix compilation warning.

Replace '%d' by '%zu' to fix the following compilation warning:- drivers/i2c/busses/i2c-at91.c:277:2: warning: format ‘%d’ expects argument of type ‘int’, but argument 5 has type ‘size_t’ [-Wformat=] dev_dbg(dev->dev, "wrote 0x%x, to go %d\n", *dev->buf, dev->buf_len); ^ drivers/i2c/busses/i2

Re: [PATCH] drm/pl111: select DRM_PANEL

On Tue, May 30, 2017 at 01:35:51PM +0200, Linus Walleij wrote: > On Tue, May 30, 2017 at 11:22 AM, Arnd Bergmann wrote: > > > When DRM_PANEL is disabled, we get a link error for pl111: > > > > drivers/gpu/built-in.o: In function `pl111_connector_destroy': > > pl111_connector.c:(.text+0x3487e6): u

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

Hi, On 31/05/2017 at 07:45:07 +0200, Heiner Kallweit wrote: > Am 31.05.2017 um 06:33 schrieb Stephen Rothwell: > > Hi Alexandre, > > > > After merging the rtc tree, today's linux-next build (arm > > multi_v7_defconfig) failed like this: > > > > drivers/rtc/rtc-ds1307.c: In function 'ds1307_probe

Re: [PATCH v2] perf: fix double free at function perf_hpp__reset_output_field

On Wed, May 31, 2017 at 03:05:51PM +0800, Du, Changbin wrote: > > Hi jirka, Will you send a patch to fix this issue? If not I will send my > solution in a new thread. oops, forgot about this one.. I'll pick it up thanks, jirka

Re: [PATCH 00/58] ARM: at91: rework Atmel TCB drivers

Hi, On 31/05/2017 at 08:34:00 +0200, Peter Rosin wrote: > On 2017-05-30 23:50, Alexandre Belloni wrote: > > Hi, > > > > This series reworks the Atmel Timer counter Block drivers. Those blocks > > each have 3 counters with 2 channels each and can be used for > > multiple functions: > > - timers >

[PATCH v6 20/21] arm: multi_v7: Enable dwmac-sun8i driver on multi_v7_defconfig

Enable the dwmac-sun8i driver in the multi_v7 default configuration Signed-off-by: Corentin Labbe --- arch/arm/configs/multi_v7_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig index 705d908e004a..60c0c01002c

[PATCH v6 01/21] net-next: stmmac: export stmmac_set_mac_addr/stmmac_get_mac_addr

Thoses symbol will be needed for the dwmac-sun8i ethernet driver. For letting it to be build as module, they need to be exported. Signed-off-by: Corentin Labbe --- drivers/net/ethernet/stmicro/stmmac/dwmac_lib.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/net/et

[PATCH v6 10/21] arm: sun8i: orangepi-one: Enable dwmac-sun8i

The dwmac-sun8i hardware is present on the Orange PI One. It uses the internal PHY. This patch create the needed emac node. Signed-off-by: Corentin Labbe --- arch/arm/boot/dts/sun8i-h3-orangepi-one.dts | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm/boot/dts/sun8i-h3-orange

[PATCH v6 12/21] arm: sun8i: orangepi-pc-plus: Set EMAC activity LEDs to active high

On the Orange Pi PC Plus, the polarity of the LEDs on the RJ45 Ethernet port were changed from active low to active high. Signed-off-by: Chen-Yu Tsai Signed-off-by: Corentin Labbe --- arch/arm/boot/dts/sun8i-h3-orangepi-pc-plus.dts | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/a

Re: [RFC][PATCHv3 2/5] printk: introduce printing kernel thread

Hello Petr, On (05/29/17 11:29), Petr Mladek wrote: [..] > > +static inline bool console_offload_printing(void) > > +{ > > + static struct task_struct *printing_task; > > + static unsigned long long lines_printed; > > + static unsigned long saved_csw; > > + > > + if (!printk_offloading_ena

[PATCH v6 21/21] arm64: defconfig: Enable dwmac-sun8i driver on defconfig

Enable the dwmac-sun8i ethernet driver as a module in the ARM64 defconfig. Signed-off-by: Corentin Labbe --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index 000de61802a1..fd7d22b8480c 100644 --- a/

[PATCH v6 17/21] arm64: allwinner: pine64-plus: Enable dwmac-sun8i

The dwmac-sun8i hardware is present on the pine64 plus. It uses an external PHY rtl8211e via RGMII. Signed-off-by: Corentin Labbe --- .../arm64/boot/dts/allwinner/sun50i-a64-pine64-plus.dts | 17 - 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/

[PATCH v6 19/21] arm: sunxi: Enable dwmac-sun8i driver on sunxi_defconfig

Enable the dwmac-sun8i driver in the sunxi default configuration Signed-off-by: Corentin Labbe --- arch/arm/configs/sunxi_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/configs/sunxi_defconfig b/arch/arm/configs/sunxi_defconfig index 5cd5dd70bc83..504e02238031 100644 ---

[PATCH v6 13/21] arm: sun8i: nanopi-neo: Enable dwmac-sun8i

The dwmac-sun8i hardware is present on the NanoPi Neo. It uses the internal PHY. This patch create the needed emac node. Signed-off-by: Corentin Labbe --- arch/arm/boot/dts/sun8i-h3-nanopi-neo.dts | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/boot/dts/sun8i-h3-nanopi-neo.dt

[PATCH v6 18/21] arm64: allwinner: bananapi-m64: Enable dwmac-sun8i

The dwmac-sun8i hardware is present on the BananaPi M64. It uses an external PHY rtl8211e via RGMII. Signed-off-by: Corentin Labbe --- arch/arm64/boot/dts/allwinner/sun50i-a64-bananapi-m64.dts | 15 +++ 1 file changed, 15 insertions(+) diff --git a/arch/arm64/boot/dts/allwinner/sun

[PATCH v6 15/21] arm64: allwinner: sun50i-a64: add dwmac-sun8i Ethernet driver

The dwmac-sun8i is an Ethernet MAC that supports 10/100/1000 Mbit connections. It is very similar to the device found in the Allwinner H3, but lacks the internal 100 Mbit PHY and its associated control bits. This adds the necessary bits to the Allwinner A64 SoC .dtsi, but keeps it disabled at this

[PATCH] bcache: Fix a sleep-in-atomic bug

The driver may sleep under a spin lock, and the function call path is: journal_wait_for_write (acquire the lock by spin_lock) closure_sync schedule --> may sleep To fix it, the lock is released before "closure_sync", and the lock is acquired again after this function. Signed-off-by: Jia-Ju

[PATCH v6 16/21] arm64: allwinner: pine64: Enable dwmac-sun8i

The dwmac-sun8i hardware is present on the pine64 It uses an external PHY via RMII. Signed-off-by: Corentin Labbe --- arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts | 16 1 file changed, 16 insertions(+) diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts b/a

[PATCH v6 14/21] arm64: allwinner: sun50i-a64: Add dt node for the syscon control module

This patch add the dt node for the syscon register present on the Allwinner A64. Only two register are present in this syscon and the only one useful is the one dedicated to EMAC clock. Signed-off-by: Corentin Labbe --- arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 6 ++ 1 file changed, 6

[PATCH v6 05/21] net-next: stmmac: Add dwmac-sun8i

The dwmac-sun8i is a heavy hacked version of stmmac hardware by allwinner. In fact the only common part is the descriptor management and the first register function. Signed-off-by: Corentin Labbe --- drivers/net/ethernet/stmicro/stmmac/Kconfig| 11 + drivers/net/ethernet/stmicro/stmmac/

[PATCH v6 11/21] arm: sun8i: orangepi-2: Enable dwmac-sun8i

The dwmac-sun8i hardware is present on the Orange PI 2. It uses the internal PHY. This patch create the needed emac node. Signed-off-by: Corentin Labbe --- arch/arm/boot/dts/sun8i-h3-orangepi-2.dts | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm/boot/dts/sun8i-h3-orangepi-2

[PATCH v6 06/21] arm: sun8i: sunxi-h3-h5: Add dt node for the syscon control module

This patch add the dt node for the syscon register present on the Allwinner H3/H5 Only two register are present in this syscon and the only one useful is the one dedicated to EMAC clock.. Signed-off-by: Corentin Labbe --- arch/arm/boot/dts/sunxi-h3-h5.dtsi | 6 ++ 1 file changed, 6 insertio

[PATCH v6 09/21] arm: sun8i: orangepi-zero: Enable dwmac-sun8i

The dwmac-sun8i hardware is present on the Orange PI Zero. It uses the internal PHY. This patch create the needed emac node. Signed-off-by: Corentin Labbe --- arch/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dts | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm/boot/dts/sun8i-h2

[PATCH v6 07/21] arm: sun8i: sunxi-h3-h5: add dwmac-sun8i ethernet driver

The dwmac-sun8i is an ethernet MAC hardware that support 10/100/1000 speed. This patch enable the dwmac-sun8i on Allwinner H3/H5 SoC Device-tree. SoC H3/H5 have an internal PHY, so optionals syscon and ephy are set. Signed-off-by: Corentin Labbe --- arch/arm/boot/dts/sunxi-h3-h5.dtsi | 34 +

Re: Q. drm/i915 shrinker, synchronize_rcu_expedited() from handlers

On ti, 2017-05-30 at 13:00 -0700, Hugh Dickins wrote: > On Mon, 22 May 2017, Joonas Lahtinen wrote: > > On la, 2017-05-20 at 10:56 +0900, J. R. Okajima wrote: > > > "J. R. Okajima": > > > >  > > > > I don't know whether the fix is good to me or not yet. I will test your > > > > fix, but I am busy n

[PATCH v6 08/21] arm: sun8i: orangepi-pc: Enable dwmac-sun8i

The dwmac-sun8i hardware is present on the Orange PI PC. It uses the internal PHY. This patch create the needed emac node. Signed-off-by: Corentin Labbe --- arch/arm/boot/dts/sun8i-h3-orangepi-pc.dts | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm/boot/dts/sun8i-h3-orangepi

[PATCH v6 03/21] dt-bindings: net-next: Add DT bindings documentation for Allwinner dwmac-sun8i

This patch adds documentation for Device-Tree bindings for the Allwinner dwmac-sun8i driver. Signed-off-by: Corentin Labbe Acked-by: Rob Herring --- .../devicetree/bindings/net/dwmac-sun8i.txt| 78 ++ 1 file changed, 78 insertions(+) create mode 100644 Documentation

Re: linux-next 20170519 and later - ^S/^Q borkage on ttys.

On 05/31/17 05:48, valdis.kletni...@vt.edu wrote: Pretty drastic. Hit ^S to pause scrolling, and instantly hung terminal. Seen on both urxvt and xterm under x11, and on virtual console screens. This appears in dmesg: [ 1844.182058] INFO: task kworker/u8:3:129 blocked for more than 120 second

[PATCH v6 04/21] dt-bindings: syscon: Add DT bindings documentation for Allwinner syscon

This patch adds documentation for Device-Tree bindings for the syscon present in allwinner devices. Signed-off-by: Corentin Labbe Acked-by: Rob Herring --- .../devicetree/bindings/misc/allwinner,syscon.txt | 19 +++ 1 file changed, 19 insertions(+) create mode 100644 Docume

[PATCH v6 00/21] net-next: stmmac: add dwmac-sun8i ethernet driver

Hello This patch series add the driver for dwmac-sun8i which handle the Ethernet MAC present on Allwinner H3/H5/A83T/A64 SoCs. This driver is the continuation of the sun8i-emac driver. During the development, it appeared that in fact the hardware was a modified version of some dwmac. So the drive

[PATCH v6 02/21] net-next: stmmac: add optional setup function

Instead of adding more ifthen logic for adding a new mac_device_info setup function, it is easier to add a function pointer to the function needed. Signed-off-by: Corentin Labbe --- drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 4 +++- include/linux/stmmac.h| 1

Re: [RFC][PATCHv3 2/5] printk: introduce printing kernel thread

Hello Jan, On (05/29/17 14:12), Jan Kara wrote: [..] > Actually I had something very similar in old versions of my patch set. And > it didn't work very well. The problem was that e.g. sometimes scheduler > decided that printk kthread should run on the same CPU as the process > currently doing prin

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

On 25/05/2017 10:37, Marc Zyngier wrote: > On 20/04/17 15:28, Marc Gonzalez wrote: > >> The MSI controller in Tango supports 256 message-signaled interrupts, >> and a single doorbell address. >> >> Signed-off-by: Marc Gonzalez >> --- >> drivers/pci/host/pcie-tango.c | 232 >> +++

Re: [PATCH v2 1/3] pwm: sun4i: improve hardware read out

On 31/05/2017 at 11:34:43 +0800, Chen-Yu Tsai wrote: > On Wed, May 31, 2017 at 3:32 AM, Alexandre Belloni > wrote: > > +static void sun4i_pwm_get_state(struct pwm_chip *chip, > > + struct pwm_device *pwm, > > + struct pwm_state *state) >

[PATCH] libcfs: Fix a sleep-in-atomic bug in cfs_wi_exit

The driver may sleep under a spin lock, and the function call path is: cfs_wi_exit (acquire the lock by spin_lock) LASSERT lbug_with_loc libcfs_debug_dumplog schedule and kthread_run --> may sleep To fix it, all "LASSERT" is placed out of the spin_lock and spin_unlock. Signed-

[PATCH] libcfs: Fix a sleep-in-atomic bug in cfs_wi_deschedule

The driver may sleep under a spin lock, and the function call path is: cfs_wi_deschedule (acquire the lock by spin_lock) LASSERT lbug_with_loc libcfs_debug_dumplog schedule and kthread_run --> may sleep To fix it, all "LASSERT" is placed out of the spin_lock and spin_unlock. S

Re: [V2, 2/6] tty: serial: lpuart: add little endian 32 bit register support

Hi Andy, On Wed, May 17, 2017 at 12:55:59PM +0300, Andy Shevchenko wrote: > On Wed, May 17, 2017 at 8:43 AM, Dong Aisheng wrote: > > On Wed, May 17, 2017 at 08:37:41AM +0300, Nikita Yushchenko wrote: > >> > >> > >> 17.05.2017 06:39, Dong Aisheng wrote: > >> > On Tue, May 16, 2017 at 02:15:08PM +0

[PATCH] libcfs: Fix a sleep-in-atomic bug in cfs_wi_schedule

The driver may sleep under a spin lock, and the function call path is: cfs_wi_schedule (acquire the lock by spin_lock) LASSERT lbug_with_loc libcfs_debug_dumplog schedule and kthread_run --> may sleep To fix it, all "LASSERT" is placed out of the spin_lock and spin_unlock. Sig

Re: [RFC][PATCH 00/23] VFS: Introduce superblock configuration context [ver #4]

On Tue, May 30, 2017 at 5:36 PM, David Howells wrote: > Al Viro wrote: > >> Random notes: >> * "sb_config" looks rather odd in the current variant; mount_context, >> perhaps? Or fs_context, for that matter... Anyway, that's trivial. > > You can argue that one with Miklós. He argued again

Re: [PATCH] bcache: Fix a sleep-in-atomic bug

On Wed, May 31, 2017 at 03:23:40PM +0800, Jia-Ju Bai wrote: > The driver may sleep under a spin lock, and the function call path is: > journal_wait_for_write (acquire the lock by spin_lock) > closure_sync > schedule --> may sleep This patch is incorrect, you've introduced a double unlock. D

[PATCH V2] libcfs: Fix a sleep-in-atomic bug in cfs_wi_deschedule

The driver may sleep under a spin lock, and the function call path is: cfs_wi_deschedule (acquire the lock by spin_lock) LASSERT lbug_with_loc libcfs_debug_dumplog schedule and kthread_run --> may sleep To fix it, all "LASSERT" is placed out of the spin_lock and spin_unlock. S

Re: [PATCH V1 1/2] leds: leds-qti-rgb: Add LED driver for QTI TRI_LED module

Hi! > +- qcom,support-blink: > + Usage: optional > + Value type: > + Definition: An array of integer values to indicate if "blue", "green", > "red" > + LEDs support blink control. The values are listed as the fixed > + order for "blue", "green", "red" LEDs. N

Re: [RFC PATCH 1/2] sched/rt: add utilization tracking

On Tue, May 30, 2017 at 06:24:27PM +0200, Vincent Guittot wrote: > On 30 May 2017 at 17:50, Morten Rasmussen wrote: > > On Wed, May 24, 2017 at 11:00:51AM +0200, Vincent Guittot wrote: > >> @@ -1534,6 +1534,8 @@ static struct task_struct *_pick_next_task_rt(struct > >> rq *rq) > >> return p

[PATCH V2] libcfs: Fix a sleep-in-atomic bug in cfs_wi_exit

The driver may sleep under a spin lock, and the function call path is: cfs_wi_exit (acquire the lock by spin_lock) LASSERT lbug_with_loc libcfs_debug_dumplog schedule and kthread_run --> may sleep To fix it, all "LASSERT" is placed out of the spin_lock and spin_unlock. Signed-

Re: [PATCH v2 5/7] drm/ltdc: Use the panel-bridge helper.

Hi Boris, On 05/31/2017 11:56 AM, Boris Brezillon wrote: Hi Philippe, Le Tue, 30 May 2017 16:55:42 +, Philippe CORNU a écrit : Hi Eric, I took your patch for the panel-bridge and it works perfectly in both DPI mode (panel RGB //) and DSI mode (bridge dw mipi dsi), bravo :-) I still do

Re: [PATCH 1/2] DT: pinctrl: Add binding documentation for Spreadtrum pin controller

Hi Linus, On 一, 5月 29, 2017 at 06:18:29下午 +0200, Linus Walleij wrote: > On Sat, May 27, 2017 at 7:56 AM, Baolin Wang > wrote: > > > This patch adds the binding documentation for Spreadtrum SC9860 pin > > controller device. > > > > Signed-off-by: Baolin Wang > (...) > > > +* Spreadtrum Pin Co

Re: [PATCH] mm: consider memblock reservations for deferred memory initialization sizing

On Wed, May 31, 2017 at 08:42:27AM +0200, Michal Hocko wrote: > From: Michal Hocko > > We have seen an early OOM killer invocation on ppc64 systems with > crashkernel=4096M > kthreadd invoked oom-killer: > gfp_mask=0x16040c0(GFP_KERNEL|__GFP_COMP|__GFP_NOTRACK), nodemask=7, order=0, > oom

Re: [PATCH 2/2] pinctrl: sprd: Add Spreadtrum pin control driver

Hi Linus, On 一, 5月 29, 2017 at 06:28:49下午 +0200, Linus Walleij wrote: > On Sat, May 27, 2017 at 7:56 AM, Baolin Wang > wrote: > > > This patch adds the pin control driver for Spreadtrum SC9860 platform. > > > > Signed-off-by: Baolin Wang > > Overall I see that you want to store functions and

[PATCH] libcfs: Fix a sleep-in-atomic bug in cfs_wi_sched_destroy

The driver may sleep under a spin lock, and the function call path is: cfs_wi_sched_destroy (acquire the lock by spin_lock) LASSERT lbug_with_loc libcfs_debug_dumplog schedule and kthread_run --> may sleep To fix it, all "LASSERT" is placed out of the spin_lock and spin_unlock.

Re: [PATCH] drm/i915/gvt: remove redundant -Wall

On 2017.05.21 00:15:27 -0700, Nick Desaulniers wrote: > This flag is already set in the top level Makefile of the kernel. > > Also, by having set CONFIG_DRM_I915_GVT, thereby appending -Wall to > ccflags, you undo all the -Wno-* cflags previously set in the Make > variable KBUILD_CFLAGS. > > For

Re: [V2, 2/6] tty: serial: lpuart: add little endian 32 bit register support

Hi Nikita, On Tue, May 23, 2017 at 08:24:18AM +0300, Nikita Yushchenko wrote: > Hi, > > Alternative solution could be - have separate write path for earlycon. > >>> > >>> It looks to me having the same issue with a separate write patch > >>> for earlycon as we still need distinguish Little o

Re: [PATCH v2 5/7] drm/ltdc: Use the panel-bridge helper.

Hi Archit, Le Wed, 31 May 2017 13:31:16 +0530, Archit Taneja a écrit : > Hi Boris, > > On 05/31/2017 11:56 AM, Boris Brezillon wrote: > > Hi Philippe, > > > > Le Tue, 30 May 2017 16:55:42 +, > > Philippe CORNU a écrit : > > > >> Hi Eric, > >> > >> I took your patch for the panel-bridge a

Re: [kbuild-all] [PATCH v4 3/9] arm: dts: mt7623: add mt7623-mt6323.dtsi file

Hi, Matthias On 05/29, Matthias Brugger wrote: > > >On 28/05/17 13:31, kbuild test robot wrote: >>Hi John, >> >>[auto build test ERROR on robh/for-next] >>[also build test ERROR on v4.12-rc2 next-20170526] >>[if your patch is applied to the wrong git tree, please drop us a note to >>help improve

[PATCH] libcfs: Fix a sleep-in-atomic bug in cfs_wi_scheduler

The driver may sleep under a spin lock, and the function call path is: cfs_wi_scheduler (acquire the lock by spin_lock) LASSERT lbug_with_loc libcfs_debug_dumplog schedule and kthread_run --> may sleep To fix it, all "LASSERT" is placed out of the spin_lock and spin_unlock. Si

[PATCH 1/5] x86: boot/copy, remove unused functions

copy_from_gs and copy_to_gs are unused in the boot code. They have actually never been used -- they were always commented out since their addition in 5be865661516 ("String-handling functions for the new x86 setup code.") in 2007. So remove them -- they can be restored from history if need be. Sign

[PATCH 3/5] x86_64: boot, extract efi_pe_entry from startup_64

efi_pe_entry body is somehow squashed into startup_64. In the old days, we forced startup_64 to start at offset 0x200 and efi_pe_entry to start at 0x210. But this requirement was removed in 99f857db8857 ("x86, build: Dynamically find entry points in compressed startup code") long time ago. The way

[PATCH 5/5] x86: entry, use ENTRY instead of ALIGN+GLOBAL for stub32_clone

ALIGN+GLOBAL is effectively what ENTRY does, so use ENTRY which is dedicated for global functions. Note that this is a C-like leaf function -- it has a correct stack frame, switches one argument and continues by jumping into C. And since each ENTRY should be balanced by some END*, we add a corresp

[PATCH 4/5] x86: math-emu, add ENDPROC to functions

Functions in math-emu are annotated as ENTRY, but their ends are not annotated at all. But these are standard functions called from C, with proper stack register update etc. Omitting the ends means: * the annotations are not paired and we cannot deal with such functions e.g. in objtool * the sym

[PATCH 2/5] x86_32: boot, extract efi_pe_entry from startup_32

efi_pe_entry body is somehow squashed into startup_32. In the old days, we forced startup_32 to start at offset 0x00 and efi_pe_entry to start at 0x10. But this requirement was removed in 99f857db8857 ("x86, build: Dynamically find entry points in compressed startup code") long time ago. The way i

[PATCH 02/28] ext4: fix lockdep warning about recursive inode locking

Setting a large xattr value may require writing the attribute contents to an external inode. In this case we may need to lock the xattr inode along with the parent inode. This doesn't pose a deadlock risk because xattr inodes are not directly visible to the user and their access is restricted. Ass

[PATCH 03/28] ext4: lock inode before calling ext4_orphan_add()

ext4_orphan_add() requires caller to be holding the inode lock. Add missing lock statements. WARNING: CPU: 3 PID: 1806 at fs/ext4/namei.c:2731 ext4_orphan_add+0x4e/0x240 CPU: 3 PID: 1806 Comm: python Not tainted 4.12.0-rc1+ #746 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs

[PATCH 27/28] ext4: xattr inode deduplication

Ext4 now supports xattr values that are up to 64k in size (vfs limit). Large xattr values are stored in external inodes each one holding a single value. Once written the data blocks of these inodes are immutable. The real world use cases are expected to have a lot of value duplication such as inhe

[PATCH 22/28] ext4: move struct ext4_xattr_inode_array to xattr.h

Since this is a xattr specific data structure it is cleaner to keep it in xattr header file. Signed-off-by: Tahsin Erdogan --- fs/ext4/ext4.h | 4 fs/ext4/xattr.h | 5 + 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h index 603edb5ff304..5

[PATCH 26/28] ext4: cleanup transaction restarts during inode deletion

During inode deletion, journal credits that will be needed are hard to determine, that is why we have journal extend/restart calls in several places. Whenever a transaction is restarted, filesystem must be in a consistent state because there is no atomicity guarantee beyond a restart call. Add ext

[PATCH] libcfs: Fix a sleep-in-atomic bug in cfs_percpt_lock and cfs_percpt_unlock

The driver may sleep under a spin lock, and the function call path is: cfs_percpt_lock/cfs_percpt_unlock (acquire the lock by spin_lock) LASSERT lbug_with_loc libcfs_debug_dumplog schedule and kthread_run --> may sleep To fix it, all "LASSERT" is placed out of the spin_lock and

[PATCH 28/28] quota: add extra inode count to dquot transfer functions

Ext4 ea_inode feature allows storing xattr values in external inodes to be able to store values that are bigger than a block in size. Ext4 also has deduplication support for these type of inodes. With deduplication, the actual storage waste is eliminated but the users of such inodes are still charg

Re: [PATCH v2 2/5] dt-bindings : Document the STM32F4 CRC32 binding

On Tue, May 30, 2017 at 05:50:24PM -0500, Rob Herring wrote: > On Sat, May 20, 2017 at 04:32:12PM +0300, Cosar Dindar wrote: > > Add device tree binding for STM32F4. > > > > Signed-off-by: Cosar Dindar > > --- > > Documentation/devicetree/bindings/crypto/st,stm32-crc.txt | 4 ++-- > > 1 file cha

Hello Beautiful

I hope you are doing well and this email meet you in good health condition. My name is Wesley.I`m from the US but currently in Syria for peace keeping mission. I want to get to know you better, if I may be so bold. I consider myself an easy-going man, and I am currently looking for a relationsh

Re: [PATCH v5 08/10] drm/arm: malidp: Use crtc->mode_valid() callback

On Tue, May 30, 2017 at 10:37:29AM +0100, Liviu Dudau wrote: > On Tue, May 30, 2017 at 09:29:44AM +0200, Neil Armstrong wrote: > > On 05/25/2017 04:19 PM, Jose Abreu wrote: > > > Now that we have a callback to check if crtc supports a given mode > > > we can use it in malidp so that we restrict the

[PATCH 25/28] ext4: add ext4_is_quota_file()

IS_NOQUOTA() indicates whether quota is disabled for an inode. Ext4 also uses it to check whether an inode is for a quota file. The distinction currently doesn't matter because quota is disabled only for the quota files. When we start disabling quota for other inodes in the future, we will want to

[PATCH] mtd: nand: atmel: mark resume function __maybe_unused

The newly added suspend/resume support causes a harmless warning: drivers/mtd/nand/atmel/nand-controller.c:2513:12: error: 'atmel_nand_controller_resume' defined but not used [-Werror=unused-function] This shuts up the warning with a __maybe_unused annotation. Fixes: b107007a7114 ("mtd: nand: a

[PATCH 23/28] mbcache: make mbcache more generic

Large xattr feature would like to use the mbcache for xattr value deduplication. Current implementation is geared towards xattr block deduplication. Make it more generic so that it can be used by both. Signed-off-by: Tahsin Erdogan --- fs/ext2/xattr.c | 18 +- fs/ext4/xat

[PATCH 14/28] ext4: fix ext4_xattr_make_inode_space() value size calculation

ext4_xattr_make_inode_space() is interested in calculating the inline space used in an inode. When a xattr entry refers to an external inode the value size indicates the external inode size, not the value size in the inline area. Change the function to take this into account. Signed-off-by: Tahsin

[PATCH 19/28] ext4: ext4_xattr_delete_inode() should return accurate errors

In a few places the function returns without trying to pass the actual error code to the caller. Fix those. Signed-off-by: Tahsin Erdogan --- fs/ext4/xattr.c | 16 ++-- 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/fs/ext4/xattr.c b/fs/ext4/xattr.c index 1d354e447842

[PATCH 21/28] ext4: modify ext4_xattr_ino_array to hold struct inode *

Tracking struct inode * rather than the inode number eliminates the repeated ext4_xattr_inode_iget() call later. The second call cannot fail in practice but still requires explanation when it wants to ignore the return value. Avoid the trouble and make things simple. Signed-off-by: Tahsin Erdogan

[PATCH 24/28] ext4: rename mb block cache functions

There will be a second cache instance that tracks ea_inodes. Make existing names more explicit so that it is clear that they refer to xattr block cache. Signed-off-by: Tahsin Erdogan --- fs/ext4/xattr.c | 36 1 file changed, 20 insertions(+), 16 deletions(-)

[PATCH 18/28] ext4: retry storing value in external inode with xattr block too

When value size is <= EXT4_XATTR_MIN_LARGE_EA_SIZE(), and it doesn't fit in either inline or xattr block, a second try is made to store it in an external inode while storing the entry itself in inline area. There should also be an attempt to store the entry in xattr block. This patch adds a retry

[PATCH net-next] nfp: add MAY_USE_DEVLINK dependency

When devlink is configured as a loadable module, a built-in nfp driver causes a link error: drivers/net/built-in.o: In function `nfp_devlink_port_register': (.text+0xb8b05): undefined reference to `devlink_port_type_eth_set' drivers/net/built-in.o: In function `nfp_devlink_port_register': (.text+0

RE: [PATCH V1 1/2] leds: leds-qti-rgb: Add LED driver for QTI TRI_LED module

Hi Pavel, Thanks for the reviewing. For the order, the hardware register mapping has this order (blue/green/red) from bit0/1/2, I can revert it to (red/green/blue) if there is a strong concern. For these two properties: qcom,off-ms/ qcom,on-ms, I am using them to assign the default blinking on/o

Re: [PATCH 7/7] thermal: max77620: fix pinmux conflict on reprobe

On Tue, May 30, 2017 at 11:57:07AM -0700, Eduardo Valentin wrote: > On Tue, May 30, 2017 at 06:25:54PM +0200, Johan Hovold wrote: > > Use the new helper for reusing a device-tree node of another device > > instead of managing the node references explicitly. > > > > This also makes sure that the ne

[PATCH 20/28] ext4: improve journal credit handling in set xattr paths

Both ext4_set_acl() and ext4_set_context() need to be made aware of ea_inode feature when it comes to credits calculation. Also add a sufficient credits check in ext4_xattr_set_handle() right after xattr write lock is grabbed. Original credits calculation is done outside the lock so there is a pos

[PATCH 17/28] ext4: fix credits calculation for xattr inode

When there is no space for a value in xattr block, it may be stored in an xattr inode even if the value length is less than EXT4_XATTR_MIN_LARGE_EA_SIZE(). So the current assumption in credits calculation is wrong. Signed-off-by: Tahsin Erdogan --- fs/ext4/xattr.c | 3 +-- 1 file changed, 1 inse

Re: [PATCH 6/7] clocksource: Rename CLKSRC_OF to TIMER_OF

On Sat, May 27, 2017 at 11:58 AM, Daniel Lezcano wrote: > The config option name is now renamed to 'TIMER_OF' for consistency with > the CLOCKSOURCE_OF_DECLARE => TIMER_OF_DECLARE change. > > Signed-off-by: Daniel Lezcano > --- > arch/arm/Kconfig| 10 +++--- > arch/arm/ma

Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE

On Wed 31-05-17 08:30:08, Vlastimil Babka wrote: > On 05/30/2017 06:06 PM, Andrea Arcangeli wrote: > > > > I'm not sure if it should be considered a bug, the prctl is intended > > to use normally by wrappers so it looks optimal as implemented this > > way: affecting future vmas only, which will al

Re: [PATCH 1/7] USB: core: fix device node leak

On Tue, May 30, 2017 at 03:55:56PM -0700, Tyrel Datwyler wrote: > On 05/30/2017 09:25 AM, Johan Hovold wrote: > > Make sure to release any OF device-node reference taken when creating > > the USB device. > > > > Note that we currently do not hold a reference to the root hub > > device-tree node (i

[PATCH 16/28] ext4: fix ext4_xattr_cmp()

When a xattr entry refers to an external inode, the value data is not available in the inline area so we should not attempt to read it using value offset. Signed-off-by: Tahsin Erdogan --- fs/ext4/xattr.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/ext4/xattr.c b/fs/

[PATCH 11/28] ext4: clean up ext4_xattr_inode_get()

The input and output values of *size parameter are equal on successful return from ext4_xattr_inode_get(). On error return, the callers ignore the output value so there is no need to update it. Also check for NULL return from ext4_bread(). If the actual xattr inode size happens to be smaller than

[PATCH 15/28] ext4: fix ext4_xattr_move_to_block()

When moving xattr entries from inline area to a xattr block, entries that refer to external xattr inodes need special handling because value data is not available in the inline area but rather should be read from its external inode. Signed-off-by: Tahsin Erdogan --- fs/ext4/xattr.c | 19

  1   2   3   4   5   6   7   8   9   10   >