Re: Oops caused by race between livepatch and ftrace

On Tue, 21 May 2019 09:16:29 -0500 Josh Poimboeuf wrote: > > Hmm, this may blow up with lockdep, as I believe we already have a > > locking dependency of: > > > > text_mutex -> ftrace_lock > > > > And this will reverses it. (kprobes appears to take the locks in this > > order). > > > >

Re: [PATCH v3] staging: fieldbus: core: fix ->poll() annotation

On Tue, May 21, 2019 at 10:20:09AM -0400, Sven Van Asbroeck wrote: > From: Oscar Gomez Fuente > > ->poll() functions should return __poll_t, but the fieldbus > core's poll() does not. This generates a sparse warning. > > Fix the ->poll() return value, and use recommended __poll_t > constants

Re: [PATCH] perf arm64: Fix mksyscalltbl when system kernel headers are ahead of the kernel

On Tue, 21 May 2019, Arnaldo Carvalho de Melo wrote: > Em Tue, May 21, 2019 at 06:02:03AM +0300, Vitaly Chikunov escreveu: > > When a host system has kernel headers that are newer than a compiling > > kernel, mksyscalltbl fails with errors such as: > > > > : In function 'main': > > :271:44:

Re: [PATCH v2] cpuset: restore sanity to cpuset_cpus_allowed_fallback()

On Tue, Apr 09, 2019 at 04:40:03PM -0400, Joel Savitz wrote: > $ grep Cpus /proc/$$/status > Cpus_allowed: ff > Cpus_allowed_list: 0-7 (a) > $ taskset -p 4 $$ > pid 19202's current affinity mask: f > pid 19202's new affinity mask: 4 > > $ grep

Re: [PATCH 2/2] serial: 8250: Add support for 8250/16550 as MFD function

Greg Kroah-Hartman writes: > On Tue, May 21, 2019 at 01:50:25PM +0200, Esben Haabendal wrote: >> Greg Kroah-Hartman writes: >> >> > On Tue, May 21, 2019 at 01:11:08PM +0200, Esben Haabendal wrote: >> >> Greg Kroah-Hartman writes: >> >> >> >> >> I will try ad hold back with this thread until

[PATCH 2/3] rtc: s35390a: set uie_unsupported

Alarms are only supported on a per minute basis. This is why uie_unsupported is set. Furthermore issue a warning when a second based alarm is requested. Signed-off-by: Richard Leitner --- drivers/rtc/rtc-s35390a.c | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH 3/3] rtc: s35390a: introduce struct device in probe

To simplify access and shorten code introduce a struct device pointer in the s35390a probe function. Signed-off-by: Richard Leitner --- drivers/rtc/rtc-s35390a.c | 21 ++--- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/drivers/rtc/rtc-s35390a.c

[PATCH] arm: add missing include

Include corresponding header file for function soft_restart(). ../arch/arm/kernel/reboot.c:82:6: warning: no previous prototype for ‘soft_restart’ [-Wmissing-prototypes] void soft_restart(unsigned long addr) ^~~~ Signed-off-by: Philippe Mazenauer --- arch/arm/kernel/reboot.c |

Re: [PATCH 2/3] thermal: sun50i: add thermal driver for h6

On Tue, May 21, 2019 at 12:27:21PM +0200, Ondřej Jirman wrote: > On Tue, May 21, 2019 at 10:05:15AM +0200, Maxime Ripard wrote: > > On Sat, May 18, 2019 at 01:27:39AM +0800, Frank Lee wrote: > > > On Fri, May 17, 2019 at 3:36 PM Maxime Ripard > > > wrote: > > > > > > > > On Fri, May 17, 2019 at

Re: [PATCH] arm64: dts: allwinner: a64: Add lradc node

On Tue, May 21, 2019 at 03:52:47PM +0200, l...@z3ntu.xyz wrote: > On May 21, 2019 3:09:55 PM GMT+02:00, Maxime Ripard > wrote: > >On Tue, May 21, 2019 at 08:43:45AM +0200, l...@z3ntu.xyz wrote: > >> On May 20, 2019 1:07:42 PM GMT+02:00, Maxime Ripard > > wrote: > >> >On Sat, May 18, 2019 at

[PATCH 0/3] rtc: s35390a: uie_unsupported and minor fixes

As the s35390a does only support per-minute based alarms we have to set the uie_unsupported flag. Otherwise it delays for 10sec and fails afterwards with modern hwclock versions. Furthermore some other minor changes are made. All patches were tested on an i.MX6 platform. Richard Leitner (3):

[PATCH 1/3] rtc: s35390a: clarify INT2 pin output modes

Fix the INT2 mode mask to not include the "TEST" flag. Furthermore remove the not needed reversion of bits when parsing the INT2 modes. Instead reverse the INT2_MODE defines. Additionally mention the flag names from the datasheet for the different modes in the comments. Signed-off-by: Richard

Re: [PATCH v3] staging: fieldbus: core: fix ->poll() annotation

On Tue, May 21, 2019 at 10:20 AM Sven Van Asbroeck wrote: > > From: Oscar Gomez Fuente > > ->poll() functions should return __poll_t, but the fieldbus > core's poll() does not. This generates a sparse warning. > > Fix the ->poll() return value, and use recommended __poll_t > constants

Re: [PATCH] staging: fieldbus: solve warning incorrect type dev_core.c

On Tue, May 21, 2019 at 10:17 AM Greg KH wrote: > > > Greg already took this patch a while ago :) > Thanks for bringing that up Greg, I'll double-check your tree next time. Oscar, please ignore the v3 patch I posted. Sven

[PATCH v3] staging: fieldbus: core: fix ->poll() annotation

From: Oscar Gomez Fuente ->poll() functions should return __poll_t, but the fieldbus core's poll() does not. This generates a sparse warning. Fix the ->poll() return value, and use recommended __poll_t constants (EPOLLxxx). Signed-off-by: Oscar Gomez Fuente ---

Grüße mein Freund

Ich beabsichtige, Ihnen einen Teil meines Vermögens als freiwillige finanzielle Spende zukommen zu lassen. Wang Jianlin Wanda Group

Re: [PATCH] staging: fieldbus: solve warning incorrect type dev_core.c

On Tue, May 21, 2019 at 10:13:58AM -0400, Sven Van Asbroeck wrote: > On Fri, May 17, 2019 at 1:50 PM Oscar Gomez Fuente > wrote: > > > > These changes solve a warning realated to an incorrect type inilizer in the > > function > > fieldbus_poll. > > > > Signed-off-by: Oscar Gomez Fuente > > ---

Re: Oops caused by race between livepatch and ftrace

On Mon, May 20, 2019 at 05:39:10PM -0400, Steven Rostedt wrote: > On Mon, 20 May 2019 16:19:31 -0500 > Josh Poimboeuf wrote: > > > diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c > > index a12aff849c04..8259d4ba8b00 100644 > > --- a/kernel/trace/ftrace.c > > +++

Re: [PATCH] staging: fieldbus: solve warning incorrect type dev_core.c

On Fri, May 17, 2019 at 1:50 PM Oscar Gomez Fuente wrote: > > These changes solve a warning realated to an incorrect type inilizer in the > function > fieldbus_poll. > > Signed-off-by: Oscar Gomez Fuente > --- I've reviewed your patch and tested it on a live system. Everything looks good.

Re: [PATCH 1/2] selftests: Remove forced unbuffering for test running

On 5/20/19 11:21 PM, Takashi Iwai wrote: On Tue, 21 May 2019 00:37:48 +0200, Kees Cook wrote: As it turns out, the "stdbuf" command will actually force all subprocesses into unbuffered output, and some implementations of "echo" turn into single-character writes, which utterly wrecks writes to

Re: [PATCH] staging/gasket: Fix string split

On Tue, May 21, 2019 at 03:50:12PM +0200, Tianzheng Li wrote: > This patch removes unnecessary quoted string splits. > Signed-off-by: Tianzheng Li > Signed-off-by: Jie Zhang We need a blank line before the signed-off-by line. Care to fix this up and resend? thanks, greg k-h

[PATCH v5 0/5] prerequisites for device reserved local mem rework

From: Laurentiu Tudor For HCs that have local memory, replace the current DMA API usage with a genalloc generic allocator to manage the mappings for these devices. This is in preparation for dropping the existing "coherent" dma mem declaration APIs. Current implementation was relying on a short

[PATCH v5 5/5] USB: drop HCD_LOCAL_MEM flag

From: Laurentiu Tudor With the addition of the local memory allocator, the HCD_LOCAL_MEM flag can be dropped and the checks against it replaced with a check for the localmem_pool ptr being initialized. Signed-off-by: Laurentiu Tudor --- drivers/usb/core/buffer.c | 8 +++-

[PATCH v5 3/5] usb: host: ohci-sm501: init genalloc for local memory

From: Laurentiu Tudor In preparation for dropping the existing "coherent" dma mem declaration APIs, replace the current dma_declare_coherent_memory() based mechanism with the creation of a genalloc pool that will be used in the OHCI subsystem as replacement for the DMA APIs. For context, see

[PATCH v5 2/5] USB: use genalloc for USB HCs with local memory

From: Laurentiu Tudor For HCs that have local memory, replace the current DMA API usage with a genalloc generic allocator to manage the mappings for these devices. To help users, introduce a new HCD API, usb_hcd_setup_local_mem() that will setup up the genalloc backing up the device local

[PATCH v5 4/5] usb: host: ohci-tmio: init genalloc for local memory

From: Laurentiu Tudor In preparation for dropping the existing "coherent" dma mem declaration APIs, replace the current dma_declare_coherent_memory() based mechanism with the creation of a genalloc pool that will be used in the OHCI subsystem as replacement for the DMA APIs. For context, see

[PATCH v5 1/5] lib/genalloc.c: Add gen_pool_dma_zalloc() for zeroed DMA allocations

From: Fredrik Noring gen_pool_dma_zalloc() is a zeroed memory variant of gen_pool_dma_alloc(). Document return values of both, and indicate NULL as a "%NULL" constant. Signed-off-by: Fredrik Noring --- include/linux/genalloc.h | 1 + lib/genalloc.c | 29

[PATCH] arm: mm: make functions static

Make functions __arm_iommu_free_attrs(), arm_iommu_free_attrs(), arm_coherent_iommu_free_attrs(), arm_coherent_iommu_map_sg(), arm_iommu_map_sg(), arm_coherent_iommu_unmap_sg(), arm_iommu_unmap_sg(), arm_iommu_sync_sg_for_cpu() and arm_iommu_sync_sg_for_device() static, as they are only referenced

Re: [PATCH] signal/usb: Replace kill_pid_info_as_cred with kill_pid_usb_asyncio

On Tue, 21 May 2019, Eric W. Biederman wrote: > The usb support for asyncio encoded one of it's values in the wrong > field. It should have used si_value but instead used si_addr which is > not present in the _rt union member of struct siginfo. > > The practical result of this is that on a

[PATCH] video: fbdev: atafb: remove superfluous function prototypes

No need for them. Cc: Geert Uytterhoeven Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/video/fbdev/atafb.c | 21 - 1 file changed, 21 deletions(-) Index: b/drivers/video/fbdev/atafb.c === ---

Re: [PATCH net v3] netfilter: nf_queue:fix reinject verdict handling

On Mon, May 13, 2019 at 11:47:40PM +0530, Jagdish Motwani wrote: > From: Jagdish Motwani > > This patch fixes netfilter hook traversal when there are more than 1 hooks > returning NF_QUEUE verdict. When the first queue reinjects the packet, > 'nf_reinject' starts traversing hooks with a proper

Re: [PATCH 3/4] dt-bindings: dma: uart: rename binding

On 27-04-19, 11:36, Long Cheng wrote: > The filename matches mtk-uart-apdma.c. > So using "mtk-uart-apdma.txt" should be better. > And add some property. Applied with Robs r-b tag in last version, thanks Also fixed a trailing line in patch :( -- ~Vinod

Re: [PATCH 1/4] dmaengine: mediatek: Add MediaTek UART APDMA support

On 27-04-19, 11:36, Long Cheng wrote: > Add 8250 UART APDMA to support MediaTek UART. If MediaTek UART is > enabled by SERIAL_8250_MT6577, and we can enable this driver to offload > the UART device moving bytes. Applied, thanks -- ~Vinod

Re: [RFC PATCH] usb: host: xhci: allow __GFP_FS in dma allocation

On Tue, 21 May 2019, Oliver Neukum wrote: > On Mo, 2019-05-20 at 10:16 -0400, Alan Stern wrote: > > On Mon, 20 May 2019, Christoph Hellwig wrote: > > > > > GFP_KERNEL if you can block, GFP_ATOMIC if you can't for a good reason, > > > that is the allocation is from irq context or under a

Re: [PATCH] HID: Increase maximum report size allowed by hid_field_extract()

On Thu, May 9, 2019 at 9:30 PM Jiri Kosina wrote: > > On Fri, 26 Apr 2019, Kai-Heng Feng wrote: > > > >Ronald (Cc-ed) raised quite a good point: > > >what's the benefit of removing the error message if this function (and > > >__extract) can only report an unsigned 32 bits value? > > > > I didn’t

Re: [PATCH v6 1/3] dt-bindings: i2c: extend existing opencore bindings.

> Required properties: > -- compatible : "opencores,i2c-ocores" or "aeroflexgaisler,i2cmst" > +- compatible : "opencores,i2c-ocores", > + "aeroflexgaisler,i2cmst", > +"sifive,fu540-c000-i2c","sifive,i2c0". > + For Opencore based I2C IP

Re: [PATCH 4/4] serial: 8250-mtk: modify uart DMA rx

On 27-04-19, 11:36, Long Cheng wrote: > Modify uart rx and complete for DMA. > > Signed-off-by: Long Cheng > --- > drivers/tty/serial/8250/8250_mtk.c | 53 > > 1 file changed, 23 insertions(+), 30 deletions(-) > > diff --git

Re: [PATCH v2 0/6] Fix some bugs and add new feature for Spreadtrum DMA engine

On 06-05-19, 15:28, Baolin Wang wrote: > Hi, > > This patch set fixes some DMA engine bugs and adds interrupt support > for 2-stage transfer. Applied all, thanks -- ~Vinod

Re: [PATCH v6 3/3] i2c-ocores: sifive: add polling mode workaround for FU540-C000 SoC.

> static void ocores_process_polling(struct ocores_i2c *i2c) > { > + const struct of_device_id *match; > + > + match = of_match_node(ocores_i2c_match, i2c->adap.dev.of_node); > + > while (1) { > irqreturn_t ret; > int err; Please keep with the idea of

Re: [PATCH] arm64: dts: allwinner: a64: Add lradc node

On May 21, 2019 3:09:55 PM GMT+02:00, Maxime Ripard wrote: >On Tue, May 21, 2019 at 08:43:45AM +0200, l...@z3ntu.xyz wrote: >> On May 20, 2019 1:07:42 PM GMT+02:00, Maxime Ripard > wrote: >> >On Sat, May 18, 2019 at 07:09:30PM +0200, Luca Weiss wrote: >> >> Add a node describing the KEYADC on

[PATCH] staging/gasket: Fix string split

This patch removes unnecessary quoted string splits. Signed-off-by: Tianzheng Li Signed-off-by: Jie Zhang --- drivers/staging/gasket/gasket_core.c | 6 ++ drivers/staging/gasket/gasket_ioctl.c | 3 +-- drivers/staging/gasket/gasket_page_table.c | 14 ++ 3 files

Re: [PATCH] HID: multitouch: handle faulty Elo touch device

On Tue, May 21, 2019 at 3:38 PM Benjamin Tissoires wrote: > > Since kernel v5.0, one single win8 touchscreen device failed. > And it turns out this is because it reports 2 InRange usage per touch. > > It's a first, and I *really* wonder how this was allowed by Microsoft in > the first place. But

Re: [PATCH v4 02/10] kbuild: Support for Symbols.list creation

On Thu, May 9, 2019 at 11:40 PM Joe Lawrence wrote: > > From: Joao Moreira > > For automatic resolution of livepatch relocations, a file called > Symbols.list is used. This file maps symbols within every compiled > kernel object allowing the identification of symbols whose name is > unique, thus

staging: Add rtl8723bs sdio wifi driver

Hi, static analysis with Coverity has detected an issues in the rtl8723bs wifi driver: File: drivers/staging/rtl8723bs/os_dep/ioctl_linux.c in function rtw_dbg_port(): CID 18480: Operands don't affect result (CONSTANT_EXPRESSION_RESULT) dead_error_condition: The condition (extra_arg & 7U) > 7U

Re: [PATCH 0/7] introduce cpu.headroom knob to cpu controller

Hello Song. On Wed, Apr 10, 2019 at 07:43:35PM +, Song Liu wrote: > The load level above is measured as requests-per-second. > > When there is no side workload, the system has about 45% busy CPU with > load level of 1.0; and about 75% busy CPU at load level of 1.5. > > The saturation

Re: [PATCH v1] dmaengine: tegra-apb: Handle DMA_PREP_INTERRUPT flag properly

21.05.2019 7:55, Vinod Koul пишет: > On 08-05-19, 10:24, Jon Hunter wrote: >> >> On 05/05/2019 19:12, Dmitry Osipenko wrote: >>> The DMA_PREP_INTERRUPT flag means that descriptor's callback should be >>> invoked upon transfer completion and that's it. For some reason driver >>> completely disables

Re: [LKP] [mm] 42a3003535: will-it-scale.per_process_ops -25.9% regression

On Mon, May 20, 2019 at 05:53:28PM -0400, Johannes Weiner wrote: > Hello, > > On Mon, May 20, 2019 at 02:35:34PM +0800, kernel test robot wrote: > > Greeting, > > > > FYI, we noticed a -25.9% regression of will-it-scale.per_process_ops due to > > commit: > > > > > > commit:

Re: [alsa-devel] [PATCH v3 00/30] Update cros_ec_commands.h

Le jeudi 09 mai 2019 à 14:13 -0700, Gwendal Grignou a écrit : > The interface between CrosEC embedded controller and the host, > described by cros_ec_commands.h, as diverged from what the embedded > controller really support. > > The source of thruth is at >

RE: [PATCH v2] platform/x86: intel-vbtn: Report switch events when event wakes device

> -Original Message- > From: Jett Rink > Sent: Tuesday, May 21, 2019 8:37 AM > To: Mathew King > Cc: linux-kernel; AceLan Kao; Andy Shevchenko; Darren Hart; platform-driver- > x...@vger.kernel.org; Limonciello, Mario > Subject: Re: [PATCH v2] platform/x86: intel-vbtn: Report switch events

memory leak in lapb_register

Hello, syzbot found the following crash on: HEAD commit:f49aa1de Merge tag 'for-5.2-rc1-tag' of git://git.kernel.o.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1042cd9ca0 kernel config: https://syzkaller.appspot.com/x/.config?x=61dd9e15a761691d

[PATCH v10 6/7] ext4: disable map_sync for async flush

Dont support 'MAP_SYNC' with non-DAX files and DAX files with asynchronous dax_device. Virtio pmem provides asynchronous host page cache flush mechanism. We don't support 'MAP_SYNC' with virtio pmem and ext4. Signed-off-by: Pankaj Gupta Reviewed-by: Jan Kara --- fs/ext4/file.c | 10 ++

[PATCH v10 7/7] xfs: disable map_sync for async flush

Dont support 'MAP_SYNC' with non-DAX files and DAX files with asynchronous dax_device. Virtio pmem provides asynchronous host page cache flush mechanism. We don't support 'MAP_SYNC' with virtio pmem and xfs. Signed-off-by: Pankaj Gupta Reviewed-by: Darrick J. Wong --- fs/xfs/xfs_file.c | 9

memory leak in llc_conn_ac_send_sabme_cmd_p_set_x

Hello, syzbot found the following crash on: HEAD commit:f49aa1de Merge tag 'for-5.2-rc1-tag' of git://git.kernel.o.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10e4e228a0 kernel config: https://syzkaller.appspot.com/x/.config?x=61dd9e15a761691d

[PATCH v10 4/7] dm: enable synchronous dax

This patch sets dax device 'DAXDEV_SYNC' flag if all the target devices of device mapper support synchrononous DAX. If device mapper consists of both synchronous and asynchronous dax devices, we don't set 'DAXDEV_SYNC' flag. Signed-off-by: Pankaj Gupta --- drivers/md/dm-table.c | 14

Re: [PATCH 1/2] open: add close_range()

On 21/05/2019 13.34, Christian Brauner wrote: > The performance is striking. For good measure, comparing the following > simple close_all_fds() userspace implementation that is essentially just > glibc's version in [6]: > > static int close_all_fds(void) > { > DIR *dir; > struct

[PATCH v10 3/7] libnvdimm: add dax_dev sync flag

This patch adds 'DAXDEV_SYNC' flag which is set for nd_region doing synchronous flush. This later is used to disable MAP_SYNC functionality for ext4 & xfs filesystem for devices don't support synchronous flush. Signed-off-by: Pankaj Gupta --- drivers/dax/bus.c| 2 +-

[PATCH v10 2/7] virtio-pmem: Add virtio pmem driver

This patch adds virtio-pmem driver for KVM guest. Guest reads the persistent memory range information from Qemu over VIRTIO and registers it on nvdimm_bus. It also creates a nd_region object with the persistent memory range information so that existing 'nvdimm/pmem' driver can reserve this into

memory leak in llc_ui_sendmsg

Hello, syzbot found the following crash on: HEAD commit:f49aa1de Merge tag 'for-5.2-rc1-tag' of git://git.kernel.o.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=117ba18aa0 kernel config: https://syzkaller.appspot.com/x/.config?x=61dd9e15a761691d

memory leak in v9fs_cache_session_get_cookie

Hello, syzbot found the following crash on: HEAD commit:f49aa1de Merge tag 'for-5.2-rc1-tag' of git://git.kernel.o.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1224e228a0 kernel config: https://syzkaller.appspot.com/x/.config?x=61dd9e15a761691d

[PATCH v10 1/7] libnvdimm: nd_region flush callback support

This patch adds functionality to perform flush from guest to host over VIRTIO. We are registering a callback based on 'nd_region' type. virtio_pmem driver requires this special flush function. For rest of the region types we are registering existing flush function. Report error returned by host

[PATCH] HID: multitouch: handle faulty Elo touch device

Since kernel v5.0, one single win8 touchscreen device failed. And it turns out this is because it reports 2 InRange usage per touch. It's a first, and I *really* wonder how this was allowed by Microsoft in the first place. But IIRC, Breno told me this happened *after* a firmware upgrade...

Re: [PATCH] pert/report: Support s390 diag event display on x86

On Mon, May 20, 2019 at 04:42:42PM +0200, Thomas Richter wrote: > Perf report fails to display s390 specific event numbered bd000 > on an x86 platform. For example on s390 this works without error: > > [root@m35lp76 perf]# uname -m > s390x > [root@m35lp76 perf]# ./perf record -e rbd000 -- find /

Re: [PATCH] pert/report: Support s390 diag event display on x86

On Mon, May 20, 2019 at 02:03:22PM -0300, Arnaldo Carvalho de Melo wrote: > Em Mon, May 20, 2019 at 04:42:42PM +0200, Thomas Richter escreveu: > > Perf report fails to display s390 specific event numbered bd000 > > on an x86 platform. For example on s390 this works without error: > > > >

Re: [PATCH v2] platform/x86: intel-vbtn: Report switch events when event wakes device

On Mon, May 20, 2019 at 4:41 PM Mathew King wrote: > > When a switch event, such as tablet mode/laptop mode or docked/undocked, > wakes a device make sure that the value of the swich is reported. > Without when a device is put in tablet mode from laptop mode when it is > suspended or vice versa

[PATCH v10 0/7] virtio pmem driver

This patch series is ready to be merged via nvdimm tree as discussed with Dan. We have ack/review on XFS, EXT4 & VIRTIO patches. Need an ack on device mapper change in patch 4. Mike, Can you please review patch 4 which has change for dax with device mapper. Incorporated all the changes

Re: [PATCH v2] powerpc/mm: mark more tlb functions as __always_inline

Le 21/05/2019 à 15:13, Masahiro Yamada a écrit : With CONFIG_OPTIMIZE_INLINING enabled, Laura Abbott reported error with gcc 9.1.1: arch/powerpc/mm/book3s64/radix_tlb.c: In function '_tlbiel_pid': arch/powerpc/mm/book3s64/radix_tlb.c:104:2: warning: asm operand 3 probably doesn't

[PATCH v6 3/3] i2c-ocores: sifive: add polling mode workaround for FU540-C000 SoC.

The i2c-ocore driver already has a polling mode interface.But it needs a workaround for FU540 Chipset on HiFive unleashed board (RevA00). There is an erratum in FU540 chip that prevents interrupt driven i2c transfers from working, and also the I2C controller's interrupt bit cannot be cleared if

[PATCH v6 2/3] i2c-ocores: sifive: add support for i2c device on FU540-c000 SoC.

Update device id table for Opencore's I2C master based re-implementation used in FU540-c000 chipset on HiFive Unleashed platform. Device ID's include Sifive, soc-specific device for chip specific tweaks and sifive IP block specific device for generic programming model. Signed-off-by: Sagar

[PATCH v6 0/3] Extend dt bindings to support I2C on sifive devices and a fix broken IRQ in polling mode.

The patch is based on mainline v5.2-rc1 and extends DT-bindings for Opencore based I2C IP block reimplemented in FU540 SoC, available on HiFive unleashed board (Rev A00), and also provides a workaround for broken IRQ which affects the already available I2C polling mode interface in mainline,

Re: [PATCH 0/2] Enable new kprobe event at boot

On Tue, 21 May 2019 16:56:16 +0900 Masami Hiramatsu wrote: > Note that 'trace_event=' option enables trace event at very early > timing, but the events added by 'kprobe_event=' are enabled right > before enabling device drivers at this point. It is enough for > tracing device driver

[PATCH v6 1/3] dt-bindings: i2c: extend existing opencore bindings.

Reformatted compatibility strings to one valid combination on each line. Add FU540-C000 specific device tree bindings to already available i2-ocores file. This device is available on HiFive Unleashed Rev A00 board. Move interrupt under optional property list as this can be optional. The

Re: [PATCH 0/5] Exynos EHCI/OHCI: resolve conflict with the generic USB device bindings

Marek Szyprowski writes: > Dear All, > > Commit 69bec7259853 ("USB: core: let USB device know device node") added > support for attaching devicetree node for USB devices. Those nodes are > children of their USB host controller. However Exynos EHCI and OHCI > driver bindings already define

Re: [PATCH] perf arm64: Fix mksyscalltbl when system kernel headers are ahead of the kernel

Em Tue, May 21, 2019 at 06:02:03AM +0300, Vitaly Chikunov escreveu: > When a host system has kernel headers that are newer than a compiling > kernel, mksyscalltbl fails with errors such as: > > : In function 'main': > :271:44: error: '__NR_kexec_file_load' undeclared (first use in this >

[PATCH v2 05/10] Input: elan_i2c - do not query the info if they are provided

See the previous patch for a long explanation. TL;DR: the P52 and the t480s from Lenovo can't rely on I2C to fetch the information, so we need it from PS/2. Signed-off-by: Benjamin Tissoires -- changes in v2: - updated accroding to previous patch --- drivers/input/mouse/elan_i2c_core.c | 56

[PATCH v2 10/10] Input: elantech: remove P52 from SMBus blacklist

The P52 now works correctly over SMBus. Let's use this driver so we can update all five fingers every 8ms. Signed-off-by: Benjamin Tissoires -- new in v2 --- drivers/input/mouse/elantech.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/input/mouse/elantech.c

[PATCH v2 04/10] dt-bindings: add more optional properties for elan_i2c touchpads

Some new touchpads IC are connected through PS/2 and I2C. On some of these new IC, the I2C part doesn't have all of the information available. We need to be able to forward the touchpad parameters from PS/2 and thus, we need those new optional properties. Signed-off-by: Benjamin Tissoires --

[PATCH v2 09/10] Input: elan_i2c - correct the width/size base value

*_traces are the number of antennas. width_* is thus the space between 2 antennas. Which means, we should subtract 1 to the number of antennas to divide the touchpad by the number of holes between each antenna. Signed-off-by: Benjamin Tissoires -- new in v2 ---

[PATCH v2 07/10] Input: elan_i2c - handle physical middle button

Some models have a middle button, we should export it as well. Signed-off-by: Benjamin Tissoires -- new in v2 Is it really worth having a separate property, or should we just expose a middle button whatsoever? --- drivers/input/mouse/elan_i2c_core.c | 16 1 file changed, 12

[PATCH v2 06/10] Input: elantech/SMBus - export all capabilities from the PS/2 node

The recent touchpads might not have all the information regarding the characteristics through the I2C port. On some Lenovo t480s, this results in the touchpad not being detected as a clickpad, and on the Lenovo P52, this results in a failure while fetching the resolution through I2C. We need to

[PATCH v2 08/10] Input: elan_i2c - export true width/height

The width/height is actually in the same unit than X and Y. So we should not tamper the data, but just set the proper resolution, so that userspace can correctly detect which touch is a palm or a finger. Signed-off-by: Benjamin Tissoires -- new in v2 --- drivers/input/mouse/elan_i2c_core.c |

[PATCH v2 03/10] Input: elantech - detect middle button based on firmware version

Looks like the new generation of Lenovo machine also need to be added to the PnPID whitelist. This is definitively not going to scale, as there is nothing that tells us currently if a touchpad supports a true physical middle button. Consider that all new touchpads that are not clickpads (so

[PATCH v2 02/10] Input: elantech - add helper function elantech_is_buttonpad()

We check for this bit all over the code, better have it defined once for all. Signed-off-by: Benjamin Tissoires -- changes in v2: - updated with latest upstream --- drivers/input/mouse/elantech.c | 93 ++ 1 file changed, 49 insertions(+), 44 deletions(-) diff

[PATCH v2 01/10] Input: elantech - query the min/max information beforehand too

For the latest generation of Elantech touchpads, we need to forward the min/max information from PS/2 to SMBus. Prepare this work by fetching the information before creating the SMBus companion device. Signed-off-by: Benjamin Tissoires -- no changes in v2 --- drivers/input/mouse/elantech.c |

[PATCH v2 00/10] Fix Elan I2C touchpads in latest generation from Lenovo

Hi, This is the v2 from https://lkml.org/lkml/2018/10/12/633 So I initially thought it would be easy to integrate the suggested changes in the v1, but it turns our that the changes to have the touchscreen-width and height parameters were quite hard to do. I finally postponed the issue by

Re: [RFC PATCH] usb: host: xhci: allow __GFP_FS in dma allocation

On Tue, May 21, 2019 at 10:54:37AM +0200, Oliver Neukum wrote: > OK, but this leaves a question open. Will the GFP_NOIO actually > hurt, if it is used after memalloc_noio_save()? Unless we have a bug somewhere it should not make any difference, neither positively nor negatively.

Re: [PATCH v4 3/3] arm64: zynqmp: DT: Add Xilinx AMS node

Hi Manish, Thank you for posting this! It is very much needed in the mainline kernel, nice work. On Mon, Apr 22, 2019 at 10:54 AM Manish Narani wrote: > > The Xilinx AMS includes an ADC as well as on-chip sensors that can be > used to sample external and monitor on-die operating conditions,

Re: [RFC PATCH v2 13/17] sched: Add core wide task selection and scheduling.

> > Please try this and see how it compares with the vanilla v2. I think its > > time for a v3 now and we shall be posting it soon after some more > > testing and benchmarking. > > Is there any potential change between pre v3 and v3? I prefer working > based on v3 so that everyone are on the same

Re: [RFC PATCH] usb: host: xhci: allow __GFP_FS in dma allocation

On Mo, 2019-05-20 at 10:16 -0400, Alan Stern wrote: > On Mon, 20 May 2019, Christoph Hellwig wrote: > > > GFP_KERNEL if you can block, GFP_ATOMIC if you can't for a good reason, > > that is the allocation is from irq context or under a spinlock. If you > > think you have a case where you think

Re: [PATCH 3/5] i2c: core: Move ACPI IRQ handling to probe time

On Tue, May 21, 2019 at 02:11:04PM +0100, Charles Keepax wrote: > On Tue, May 21, 2019 at 03:57:04PM +0300, Andy Shevchenko wrote: > > On Tue, May 21, 2019 at 02:27:28PM +0300, Mika Westerberg wrote: > > > On Mon, May 20, 2019 at 09:49:34AM +0100, Charles Keepax wrote: > > > > Bring the ACPI path

[PATCH] staging: wilc1000: remove redundant masking of pkt_offset

From: Colin Ian King The masking update of pkg_offset is redundant as the updated value is never read and pkg_offset is re-assigned on the next iteration of the loop. Clean this up by removing the redundant assignment. Addresses-Coverity: ("Unused value") Signed-off-by: Colin Ian King ---

[PATCH v2] powerpc/mm: mark more tlb functions as __always_inline

With CONFIG_OPTIMIZE_INLINING enabled, Laura Abbott reported error with gcc 9.1.1: arch/powerpc/mm/book3s64/radix_tlb.c: In function '_tlbiel_pid': arch/powerpc/mm/book3s64/radix_tlb.c:104:2: warning: asm operand 3 probably doesn't match constraints 104 | asm volatile(PPC_TLBIEL(%0, %4,

Re: [PATCH 3/5] i2c: core: Move ACPI IRQ handling to probe time

On Tue, May 21, 2019 at 03:57:04PM +0300, Andy Shevchenko wrote: > On Tue, May 21, 2019 at 02:27:28PM +0300, Mika Westerberg wrote: > > On Mon, May 20, 2019 at 09:49:34AM +0100, Charles Keepax wrote: > > > Bring the ACPI path in sync with the device tree path and handle all the > > > IRQ fetching

Re: [PATCH resend] serial: 8250: Add support for using platform_device resources

On Tue, May 21, 2019 at 01:34:26PM +0200, Esben Haabendal wrote: > Allow getting memory resource (mapbase or iobase) as well as irq from > platform_device resources. > > The UPF_DEV_RESOURCES flag must be set for devices where platform_device > resources are to be used. When not set, driver

Re: [PATCH 1/2] open: add close_range()

* Christian Brauner: >> Solaris has an fdwalk function: >> >> >> >> So a different way to implement this would expose a nextfd system call > > Meh. If nextfd() then I would like it to be able to: > - get the nextfd(fd) >= fd

Re: [PATCH] arm64: dts: allwinner: a64: Add lradc node

On Tue, May 21, 2019 at 08:43:45AM +0200, l...@z3ntu.xyz wrote: > On May 20, 2019 1:07:42 PM GMT+02:00, Maxime Ripard > wrote: > >On Sat, May 18, 2019 at 07:09:30PM +0200, Luca Weiss wrote: > >> Add a node describing the KEYADC on the A64. > >> > >> Signed-off-by: Luca Weiss > >> --- > >>

Re: [PATCH 3/5] i2c: core: Move ACPI IRQ handling to probe time

On Tue, May 21, 2019 at 02:27:28PM +0300, Mika Westerberg wrote: > On Mon, May 20, 2019 at 09:49:34AM +0100, Charles Keepax wrote: > > Bring the ACPI path in sync with the device tree path and handle all the > > IRQ fetching at probe time. This leaves the only IRQ handling at device > >

Re: [RFC 0/7] introduce memory hinting API for external process

On Mon, May 20, 2019 at 7:55 PM Anshuman Khandual wrote: > > > > On 05/20/2019 10:29 PM, Tim Murray wrote: > > On Sun, May 19, 2019 at 11:37 PM Anshuman Khandual > > wrote: > >> > >> Or Is the objective here is reduce the number of processes which get > >> killed by > >> lmkd by triggering

Re: [PATCH] clocksource/drivers/timer-ti-dm: Change to new style declaration

On 21/05/2019 14:26, Philippe Mazenauer wrote: > Variable 'dmtimer_ops' was declared const static instead of static const. > > ../drivers/clocksource/timer-ti-dm.c:899:1: warning: ‘static’ is not at > beginning of declaration [-Wold-style-declaration] > const static struct omap_dm_timer_ops

Re: linux-next: Fixes tag needs some work in the drm-intel tree

Quoting Stephen Rothwell (2019-05-20 15:15:38) > Hi all, > > In commit > > 0d90ccb70211 ("drm/i915: Delay semaphore submission until the start of the > signaler") > > Fixes tag > > Fixes: e88619646971 ("drm/i915: Use HW semaphores for inter-engine synchroni > > has these problem(s): > >

[GIT] Crypto Fixes for 5.2

Hi Linus: This push fixes the following issues: - Two long-standing bugs in the powerpc assembly of vmx. - Stack overrun caused by HASH_MAX_DESCSIZE being too small. - Regression in caam. Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus Daniel

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