[Patch V7 8/8] arm64: defconfig: Enable tegra XUDC driver

Enable support for Nvidia XUSB device mode controller driver. Signed-off-by: Nagarjuna Kristam --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index 358b163..e9233df 100644 --- a/arch/arm64/configs/d

[Patch V7 5/8] arm64: tegra: Add xudc node for Tegra210

Tegra210 has one XUSB device mode controller, which can be operated HS and SS modes. Add DT support for XUSB device mode controller. Signed-off-by: Nagarjuna Kristam Reviewed-by: JC Kuo --- arch/arm64/boot/dts/nvidia/tegra210.dtsi | 19 +++ 1 file changed, 19 insertions(+) diff

[Patch V7 6/8] arm64: tegra: Enable xudc on Jetson TX1

Enable XUSB device mode driver for USB0 slot on Jetson TX1. Signed-off-by: Nagarjuna Kristam Reviewed-by: JC Kuo --- arch/arm64/boot/dts/nvidia/tegra210-p2597.dtsi | 31 +- 1 file changed, 30 insertions(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/nvidia/tegra210-

[Patch V7 2/8] phy: tegra: xusb: Add usb3 port fake support on Tegra210

On Tegra210, usb2 only otg/peripheral ports dont work in device mode. They need an assosciated usb3 port to work in device mode. Identify an unused usb3 port and assign it as a fake USB3 port to USB2 only port whose mode is otg/peripheral. Based on work by BH Hsieh . Signed-off-by: Nagarjuna Kris

[Patch V7 7/8] usb: gadget: Add UDC driver for tegra XUSB device mode controller

This patch adds UDC driver for tegra XUSB 3.0 device mode controller. XUSB device mode controller supports SS, HS and FS modes Based on work by: Mark Kuo Hui Fu Andrew Bresticker Signed-off-by: Nagarjuna Kristam Acked-by: Thierry Reding --- drivers/usb/gadget/udc/Kconfig | 12 +

Re: comments style: Re: [RFC PATCH v4 1/9] printk-rb: add a new printk ringbuffer implementation

On (08/22/19 15:50), Petr Mladek wrote: [..] > I could understand that you spend a lot of time on creating the > labels and that they are somehow useful for you. > > But I am not using them and I hope that I will not have to: > > + Grepping takes a lot of time, especially over several files. But

linux-next: Signed-off-by missing for commit in the drm tree

Hi all, Commit 88b703527ba7 ("drm/nouveau/kms/gf119-: add ctm property support") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell pgpDQVDZcqJpf.pgp Description: OpenPGP digital signature

Re: [PATCH v6 5/7] nfc: pn533: add UART phy driver

On Thu, Aug 22, 2019 at 10:09:09AM +, claudiu.bez...@microchip.com wrote: > Hi Lars, > > On 20.08.2019 15:03, Lars Poeschel wrote: > > This adds the UART phy interface for the pn533 driver. > > The pn533 driver can be used through UART interface this way. > > It is implemented as a serdev devi

linux-next: Signed-off-by missing for commit in the kvm-ppc tree

Hi all, Commit ff7240ccf0cd ("KVM: PPC: Book3S: Mark expected switch fall-through") is missing a Signed-off-by from its author. -- Cheers, Stephen Rothwell pgpnsvuxd3Z4H.pgp Description: OpenPGP digital signature

Re: [LKP] [drm/mgag200] 90f479ae51: vm-scalability.median -18.8% regression

Hi Am 22.08.19 um 22:02 schrieb Dave Airlie: > On Fri, 23 Aug 2019 at 03:25, Thomas Zimmermann wrote: >> >> Hi >> >> I was traveling and could reply earlier. Sorry for taking so long. >> >> Am 13.08.19 um 11:36 schrieb Feng Tang: >>> Hi Thomas, >>> >>> On Mon, Aug 12, 2019 at 03:25:45PM +0800, Fe

[PATCH v8 14/18] drm/virtio: switch from ttm to gem shmem helpers

virtio-gpu basically needs a sg_table for the bo, to tell the host where the backing pages for the object are. So the gem shmem helpers are a perfect fit. Some drm_gem_object_funcs need thin wrappers to update the host state, but otherwise the helpers handle everything just fine. Once the fencin

[PATCH v8 09/18] drm/virtio: rework virtio_gpu_object_create fencing

Rework fencing workflow. Stop using ttm helpers, use the virtio_gpu_array_* helpers instead. Due to using the gem reservation object it is initialized and ready for use before calling ttm_bo_init. So we can simply use the standard fencing workflow and drop the tricky logic which checks whenever

[PATCH v8 16/18] drm/virtio: drop virtio_gpu_object_{ref,unref}

No users left. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_drv.h | 15 --- 1 file changed, 15 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_drv.h b/drivers/gpu/drm/virtio/virtgpu_drv.h index 3e5b2d1db42d..85f974a9837b 100644 --- a/drivers/gpu/drm/virt

[PATCH v8 07/18] drm/virtio: add virtio_gpu_object_array & helpers

Some helper functions to manage an array of gem objects. v6: - add ticket to struct virtio_gpu_object_array. - add virtio_gpu_array_{lock,unlock}_resv helpers. - add virtio_gpu_array_add_fence helper. v5: some small optimizations (Chia-I Wu). v4: make them virtio-private instead of generic help

[PATCH v8 11/18] drm/virtio: rework virtio_gpu_transfer_to_host_ioctl fencing

Switch to the virtio_gpu_array_* helper workflow. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_drv.h | 4 +-- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 50 +++--- drivers/gpu/drm/virtio/virtgpu_plane.c | 21 --- drivers/gpu/drm/virtio/virtgpu_vq.c

[PATCH v8 17/18] drm/virtio: drop virtio_gpu_object_{reserve,unreserve}

No users left. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_drv.h | 21 - 1 file changed, 21 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_drv.h b/drivers/gpu/drm/virtio/virtgpu_drv.h index 85f974a9837b..fb35831ed351 100644 --- a/drivers/gpu/dr

[PATCH v8 18/18] drm/virtio: add fence sanity check

Make sure we don't leak half-initialized fences outside the driver. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_fence.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/gpu/drm/virtio/virtgpu_fence.c b/drivers/gpu/drm/virtio/virtgpu_fence.c index a0514f5bd006.

[PATCH v8 03/18] drm/virtio: simplify cursor updates

No need to do the reservation dance, we can just wait on the fence directly. Signed-off-by: Gerd Hoffmann Reviewed-by: Daniel Vetter --- drivers/gpu/drm/virtio/virtgpu_plane.c | 13 +++-- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_plane

[PATCH v8 04/18] drm/virtio: remove virtio_gpu_object_wait

No users left. Signed-off-by: Gerd Hoffmann Reviewed-by: Daniel Vetter --- drivers/gpu/drm/virtio/virtgpu_drv.h| 1 - drivers/gpu/drm/virtio/virtgpu_object.c | 13 - 2 files changed, 14 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_drv.h b/drivers/gpu/drm/virtio/vi

[PATCH v8 01/18] drm/virtio: pass gem reservation object to ttm init

With this gem and ttm will use the same reservation object, so mixing and matching ttm / gem reservation helpers should work fine. Signed-off-by: Gerd Hoffmann Reviewed-by: Daniel Vetter --- drivers/gpu/drm/virtio/virtgpu_object.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --

[PATCH v8 02/18] drm/virtio: switch virtio_gpu_wait_ioctl() to gem helper.

Use drm_gem_reservation_object_wait() in virtio_gpu_wait_ioctl(). This also makes the ioctl run lockless. v5: handle lookup failure. v2: use reservation_object_test_signaled_rcu for VIRTGPU_WAIT_NOWAIT. Signed-off-by: Gerd Hoffmann Reviewed-by: Daniel Vetter --- drivers/gpu/drm/virtio/virtgpu_

[PATCH v8 06/18] drm/virtio: remove ttm calls from in virtio_gpu_object_{reserve,unreserve}

Call reservation_object_* directly instead of using ttm_bo_{reserve,unreserve}. v4: check for EINTR only. v3: check for EINTR too. Signed-off-by: Gerd Hoffmann Reviewed-by: Daniel Vetter --- drivers/gpu/drm/virtio/virtgpu_drv.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff

[PATCH v8 15/18] drm/virtio: remove virtio_gpu_alloc_object

Thin wrapper around virtio_gpu_object_create(), but calling that directly works equally well. Signed-off-by: Gerd Hoffmann Acked-by: Daniel Vetter --- drivers/gpu/drm/virtio/virtgpu_drv.h | 4 drivers/gpu/drm/virtio/virtgpu_gem.c | 23 --- drivers/gpu/drm/virtio/vi

[PATCH v8 08/18] drm/virtio: rework virtio_gpu_execbuffer_ioctl fencing

Rework fencing workflow, starting with virtio_gpu_execbuffer_ioctl. Stop using ttm helpers, use the virtio_gpu_array_* helpers (which work on the reservation objects directly) instead. Also store the object array in struct virtio_gpu_vbuffer, so we explicitly keep a reference of all buffers used i

[PATCH v8 10/18] drm/virtio: rework virtio_gpu_transfer_from_host_ioctl fencing

Switch to the virtio_gpu_array_* helper workflow. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_drv.h | 3 +- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 40 ++ drivers/gpu/drm/virtio/virtgpu_vq.c| 8 -- 3 files changed, 23 insertions(+), 28 del

[PATCH v8 12/18] drm/virtio: rework virtio_gpu_cmd_context_{attach,detach}_resource

Switch to the virtio_gpu_array_* helper workflow. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_drv.h | 4 ++-- drivers/gpu/drm/virtio/virtgpu_gem.c | 24 +++- drivers/gpu/drm/virtio/virtgpu_vq.c | 12 3 files changed, 21 insertions(+), 19 del

[PATCH v8 13/18] drm/virtio: drop virtio_gpu_object_list_validate/virtio_gpu_unref_list

No users left. Signed-off-by: Gerd Hoffmann Acked-by: Daniel Vetter --- drivers/gpu/drm/virtio/virtgpu_drv.h | 3 -- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 39 -- 2 files changed, 42 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_drv.h b/drivers/gpu/drm/

[PATCH v8 05/18] drm/virtio: drop no_wait argument from virtio_gpu_object_reserve

All callers pass no_wait = false. Signed-off-by: Gerd Hoffmann Reviewed-by: Daniel Vetter --- drivers/gpu/drm/virtio/virtgpu_drv.h | 5 ++--- drivers/gpu/drm/virtio/virtgpu_gem.c | 4 ++-- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 4 ++-- 3 files changed, 6 insertions(+), 7 deletions(-) dif

[PATCH] powerpc/8xx: Fix permanently mapped IMMR region.

When not using large TLBs, the IMMR region is still mapped as a whole block in the FIXMAP area. Do not remove pages mapped in the FIXMAP region when initialising paging. Properly report that the IMMR region is block-mapped even when not using large TLBs. Signed-off-by: Christophe Leroy --- arc

[PATCH] powerpc/32: Don't populate page tables for block mapped pages except on the 8xx.

Commit d2f15e0979ee ("powerpc/32: always populate page tables for Abatron BDI.") wrongly sets page tables for any PPC32 for using BDI, and does't update them after init (remove RX on init section, set text and rodata read-only) Only the 8xx requires page tables to be populated for using the BDI. T

[PATCH 2/3] f2fs: clean up __bio_alloc()'s parameter

Just cleanup, no logic change. Signed-off-by: Chao Yu --- fs/f2fs/data.c | 27 +++ 1 file changed, 11 insertions(+), 16 deletions(-) diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c index 9fcfbd4f0b8c..769c548e955a 100644 --- a/fs/f2fs/data.c +++ b/fs/f2fs/data.c @@ -259,26

[PATCH 3/3] f2fs: enhance f2fs_is_checkpoint_ready()'s readability

This patch changes sematics of f2fs_is_checkpoint_ready()'s return value as: return true when checkpoint is ready, other return false, it can improve readability of below conditions. f2fs_submit_page_write() ... if (is_sbi_flag_set(sbi, SBI_IS_SHUTDOWN) || !

[PATCH 1/3] f2fs: fix wrong error injection path in inc_valid_block_count()

If FAULT_BLOCK type error injection is on, in inc_valid_block_count() we may decrease sbi->alloc_valid_block_count percpu stat count incorrectly, fix it. Fixes: 36b877af7992 ("f2fs: Keep alloc_valid_block_count in sync") Signed-off-by: Chao Yu --- fs/f2fs/f2fs.h | 3 ++- 1 file changed, 2 insert

Re: [PATCH] gpio: Move gpiochip_lock/unlock_as_irq to gpio/driver.h

On Thu, Aug 22, 2019 at 5:19 AM YueHaibing wrote: > If CONFIG_GPIOLIB is not, gpiochip_lock/unlock_as_irq will > conflict as this: > > In file included from sound/soc/codecs/wm5100.c:18:0: > ./include/linux/gpio.h:224:19: error: static declaration of > gpiochip_lock_as_irq follows non-static dec

RE: [PATCH v2 01/11] dt-bindings: mmc: arasan: Update documentation for SD Card Clock

Hi Heiko/Uffe, > -Original Message- > From: Heiko Stuebner > Sent: Thursday, August 22, 2019 11:53 PM > To: Ulf Hansson ; linux-...@vger.kernel.org > Cc: Manish Narani ; Rob Herring ; > mark.rutl...@arm.com; Michal Simek ; > adrian.hun...@intel.com; christoph.muell...@theobroma-systems.

Re: [PATCH] gpio: ftgpio: Fix an error handling path in 'ftgpio_gpio_probe()'

On Thu, Aug 22, 2019 at 10:45 PM Christophe JAILLET wrote: > If 'devm_kcalloc()' fails, we should go through the error handling path, > should some clean-up be needed. > > Fixes: 42d9fc7176eb ("gpio: ftgpio: Pass irqchip when adding gpiochip") > Signed-off-by: Christophe JAILLET Patch applied,

Re: Aw: Re: BUG: devm_regulator_get returns EPROBE_DEFER (5.3-rc5..next-20190822) for bpi-r2/mt7623/mt7530

On Thu, Aug 22, 2019 at 10:28:44PM +0200, Frank Wunderlich wrote: Please don't top post, reply in line with needed context. This allows readers to readily follow the flow of conversation and understand what you are talking about and also helps ensure that everything in the discussion is being add

Re: [PATCH 2/7] firmware: add offset to request_firmware_into_buf

On Thu, 22 Aug 2019 21:24:46 +0200, Scott Branden wrote: > > Add offset to request_firmware_into_buf to allow for portions > of firmware file to be read into a buffer. Necessary where firmware > needs to be loaded in portions from file in memory constrained systems. AFAIU, this won't work with t

Re: [PATCH] HID: logitech-dj: add support of the G700(s) receiver

On Mon, Aug 12, 2019 at 6:26 PM Hans de Goede wrote: > > Hi, > > On 12-08-19 18:08, Benjamin Tissoires wrote: > > Both the G700 and the G700s are sharing the same receiver. > > Include support for this receiver in hid-logitech-dj so that userspace > > can differentiate both. > > > > Signed-off-by:

Re: [PATCH] powerpc/kvm: Mark expected switch fall-through

On Tue, Jul 30, 2019 at 04:46:37PM +0200, Paul Menzel wrote: > Date: Tue, 30 Jul 2019 10:53:10 +0200 > > Fix the error below triggered by `-Wimplicit-fallthrough`, by tagging > it as an expected fall-through. > > arch/powerpc/kvm/book3s_32_mmu.c: In function > ‘kvmppc_mmu_book3s_32_xlate_pte

[PATCH 0/5] misc: fastrpc: few fixes

Hi Greg, More testing on fastprc revealed few memory leaks in driver and few corner cases. These patches are the fixes for those cases. One patch from Jorge is to remove unsed definition. Thanks, srini Bjorn Andersson (2): misc: fastrpc: Reference count channel context misc: fastrpc: Don't

[PATCH 1/5] misc: fastrpc: Reference count channel context

From: Bjorn Andersson The channel context is referenced from the fastrpc user and might as user space holds the file descriptor open outlive the fastrpc device, which is removed when the remote processor is shutting down. Reference count the channel context in order to retain this object until a

[PATCH 4/5] misc: fastrpc: fix double refcounting on dmabuf

dma buf refcount has to be done by the driver which is going to use the fd. This driver already does refcount on the dmabuf fd if its actively using it but also does an additional refcounting via extra ioctl. This additional refcount can lead to memory leak in cases where the applications fail to c

[PATCH 3/5] misc: fastrpc: remove unused definition

From: Jorge Ramirez-Ortiz Remove unused INIT_MEMLEN_MAX define. Signed-off-by: Jorge Ramirez-Ortiz Signed-off-by: Abhinav Asati Signed-off-by: Vamsi Singamsetty Signed-off-by: Srinivas Kandagatla --- drivers/misc/fastrpc.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/misc/fast

Re: [PATCH v2] hid-logitech-dj: add the new Lightspeed receiver

On Tue, Jul 30, 2019 at 2:26 PM Filipe Laíns wrote: > > This patchs adds the new Lightspeed receiver. Currently it seems to only > be used in the G305. > > Signed-off-by: Filipe Laíns Applied to for-5.4/logitech Cheers, Benjamin > --- > drivers/hid/hid-ids.h | 3 ++- > drivers/hid/hi

[PATCH 5/5] misc: fastrpc: free dma buf scatter list

dma buf scatter list is never freed, free it! Orignally detected by kmemleak: backtrace: [] kmemleak_alloc+0x50/0x84 [] sg_kmalloc+0x38/0x60 [] __sg_alloc_table+0x60/0x110 [] sg_alloc_table+0x28/0x58 [] __sg_alloc_table_from_pages+0xc0/0x1ac [] sg_alloc_table_from_pages+0

[PATCH 2/5] misc: fastrpc: Don't reference rpmsg_device after remove

From: Bjorn Andersson As fastrpc_rpmsg_remove() returns the rpdev of the channel context is no longer a valid object, so ensure to update the channel context to no longer reference the old object and guard in the invoke code path against dereferencing it. TEST=stop and start remote proc1 using s

Re: [PATCH next v10 03/11] dt-bindings: usb: add binding for USB GPIO based connection detection driver

On Fri, Aug 23, 2019 at 9:58 AM Chunfeng Yun wrote: > It's used to support dual role switch via GPIO when use Type-B > receptacle, typically the USB ID pin is connected to an input > GPIO, and also used to enable/disable device when the USB Vbus > pin is connected to an input GPIO. > > Signed-off

[1/3] rtc/fsl: support flextimer for lx2160a

The patch supports flextimer for lx2160a Signed-off-by: Biwen Li --- drivers/rtc/rtc-fsl-ftm-alarm.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/rtc/rtc-fsl-ftm-alarm.c b/drivers/rtc/rtc-fsl-ftm-alarm.c index 4f7259c2d6a3..2b81525f6db8 100644 --- a/drivers/rtc/rtc-fsl-ftm-alarm.c

Re: [PATCH] arm64: dts: allwinner: orange-pi-3: Enable WiFi

Hi, On Fri, Aug 23, 2019 at 11:42:28AM +0200, meg...@megous.com wrote: > From: Ondrej Jirman > > Orange Pi 3 has AP6256 WiFi/BT module. WiFi part of the module is called > bcm43356 and can be used with the brcmfmac driver. The module is powered by > the two always on regulators (not AXP805). > >

[3/3] rtc/fsl: support flextimer for SoC LS1021A (ARM32)

Support flextimer for SoC LS1021A (ARM32) Signed-off-by: Biwen Li --- drivers/rtc/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig index 319bec4bef05..58d8b5f7cfc5 100644 --- a/drivers/rtc/Kconfig +++ b/drivers/rtc/Kconfig @@ -

[2/3] arm64: dts: lx2160a: add ftm_alarm0 DT node

The patch adds ftm_alarm0 DT node for Soc LX2160A FlexTimer1 module is used to wakeup the system in deep sleep Signed-off-by: Biwen Li --- arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi | 18 ++ 1 file changed, 18 insertions(+) diff --git a/arch/arm64/boot/dts/freescale/fsl-lx21

Re: [PATCH v2 11/11] vsock_test: wait for the remote to close the connection

On Thu, Aug 22, 2019 at 11:15:46AM +0200, Stefano Garzarella wrote: > On Tue, Aug 20, 2019 at 09:28:28AM +0100, Stefan Hajnoczi wrote: > > On Thu, Aug 01, 2019 at 05:25:41PM +0200, Stefano Garzarella wrote: > > > +/* Wait for the remote to close the connection */ > > > +void vsock_wait_remote_close

Re: [PATCH v2 2/2] reset: Reset controller driver for Intel LGM SoC

On Fri, 2019-08-23 at 17:47 +0800, Dilip Kota wrote: [...] > Thanks for pointing it out. > Reset is not supported on LGM platform. > I will update the reset_device() definition to "return -EOPNOTSUPP" In that case you can just drop intel_reset_device() completely, the core checks whether ops->rese

Re: [PATCH] arm64: dts: allwinner: orange-pi-3: Enable WiFi

On Fri, Aug 23, 2019 at 6:08 PM Maxime Ripard wrote: > > Hi, > > On Fri, Aug 23, 2019 at 11:42:28AM +0200, meg...@megous.com wrote: > > From: Ondrej Jirman > > > > Orange Pi 3 has AP6256 WiFi/BT module. WiFi part of the module is called > > bcm43356 and can be used with the brcmfmac driver. The m

Re: [EXT] [PATCH v3 2/2] drm/bridge: Add NWL MIPI DSI host controller support

Hi Guido, On Jo, 2019-08-22 at 19:03 +0200, Guido Günther wrote: > Hi Robert, > thanks for your comments! Most of this make sense, i have some > comments > inline below (mostly since I only have access to the imx8mq reference > manual but not to the any NWL IP docs): > > On Thu, Aug 22, 2019 at 0

[PATCH][rtc-next] rtc: fsl: fix spelling mistake: "memery" -> "memory"

From: Colin Ian King There is a spelling mistake in a dev_err error message. Fix it. Signed-off-by: Colin Ian King --- drivers/rtc/rtc-fsl-ftm-alarm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/rtc/rtc-fsl-ftm-alarm.c b/drivers/rtc/rtc-fsl-ftm-alarm.c index 4f7

Re: [PATCH] arm64: dts: allwinner: orange-pi-3: Enable WiFi

Hello Maxime, On Fri, Aug 23, 2019 at 12:08:07PM +0200, Maxime Ripard wrote: > Hi, > > On Fri, Aug 23, 2019 at 11:42:28AM +0200, meg...@megous.com wrote: > > From: Ondrej Jirman > > > > Orange Pi 3 has AP6256 WiFi/BT module. WiFi part of the module is called > > bcm43356 and can be used with the

Re: kernel BUG at include/linux/skbuff.h:LINE! (2)

On Mon, Aug 19, 2019 at 10:44 PM Xin Long wrote: > > On Sun, Aug 18, 2019 at 10:13 PM Dmitry Vyukov wrote: > > > > On Sun, Aug 18, 2019 at 7:07 AM Xin Long wrote: > > > > > > On Sat, Aug 17, 2019 at 2:38 AM syzbot > > > wrote: > > > > > > > > Hello, > > > > > > > > syzbot found the following cr

[v1] arm64: dts: ls1028a: Remove some fixed-clock definiation

Replace pclk/aclk/mclk fixed-clock clock provider with platform clockgen pre-divider provider, those clocks should be driven by the CGA_PLL2/2. More details please refer Reference Manual. Signed-off-by: Wen He --- arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi | 17 ++--- 1 file cha

Re: [PATCH v2 2/5] spi: spi-fsl-dspi: Exit the ISR with IRQ_NONE when it's not ours

On Fri, Aug 23, 2019 at 12:15:11AM +0300, Vladimir Oltean wrote: > The DSPI interrupt can be shared between two controllers at least on the > LX2160A. In that case, the driver for one controller might misbehave and > consume the other's interrupt. Fix this by actually checking if any of > the bits

Re: comments style: Re: [RFC PATCH v4 1/9] printk-rb: add a new printk ringbuffer implementation

On Fri 2019-08-23 14:54:45, Sergey Senozhatsky wrote: > On (08/21/19 07:46), John Ogness wrote: > [..] > > The labels are necessary for the technical documentation of the > > barriers. And, after spending much time in this, I find them very > > useful. But I agree that there needs to be a better wa

Re: [GIT PULL] perf/core improvements and fixes

* Arnaldo Carvalho de Melo wrote: > Hi Ingo/Thomas, > > Please consider pulling, > > Best regards, > > - Arnaldo > > Test results at the end of this message, as usual. > > The following changes since commit 4e92b18e5b0b61211f4511cdbc5803300eeead40: > > Merge tag 'perf-core-for-min

Re: [PATCH v2 2/5] spi: spi-fsl-dspi: Exit the ISR with IRQ_NONE when it's not ours

Hi Mark, On Fri, 23 Aug 2019 at 13:28, Mark Brown wrote: > > On Fri, Aug 23, 2019 at 12:15:11AM +0300, Vladimir Oltean wrote: > > The DSPI interrupt can be shared between two controllers at least on the > > LX2160A. In that case, the driver for one controller might misbehave and > > consume the o

[RESEND PATCH 3/5] bluetooth: hci_bcm: Give more time to come out of reset

From: Ondrej Jirman Some supported devices need more time to come out of reset (eg. BCM4345C5 in AP6256). I don't have/found a datasheet, so the value was arrive at experimentally with the Oprange Pi 3 board. Without increased delay, I got intermittent failures during probe. This is a Bluetooth

[RESEND PATCH 0/5] Add bluetooth support for Orange Pi 3

From: Ondrej Jirman (Resend to add missing lists, sorry for the noise.) This series implements bluetooth support for Xunlong Orange Pi 3 board. The board uses AP6256 WiFi/BT 5.0 chip. Summary of changes: - add more delay to let initialize the chip - let the kernel detect firmware file path -

Re: [PATCH 3/3] firmware: add mutex fw_lock_fallback for race condition

On Tue, 20 Aug 2019 03:26:55 +0200, Luis Chamberlain wrote: > > On Mon, Aug 19, 2019 at 09:19:51AM -0700, Scott Branden wrote: > > To be honest, I find the entire firmware code sloppy. > > And that is after years of cleanup on my part. Try going back to v4.1 > for instance, check the code out the

[RESEND PATCH 5/5] arm64: dts: allwinner: orange-pi-3: Enable UART1 / Bluetooth

From: Ondrej Jirman The board contains AP6256 WiFi/BT module that has its bluetooth part connected to SoC's UART1 port. Enable this port, and add node for the bluetooth device. Bluetooth part is named bcm4345c5. You'll need a BCM4345C5.hcd firmware file that can be found in the Xulongs's reposi

[RESEND PATCH 2/5] bluetooth: bcm: Add support for loading firmware for BCM4345C5

From: Ondrej Jirman Detect BCM4345C5 and load a corresponding firmware file. Signed-off-by: Ondrej Jirman --- Checkpatch reports a spurious error. drivers/bluetooth/btbcm.c | 3 +++ drivers/bluetooth/hci_bcm.c | 1 + 2 files changed, 4 insertions(+) diff --git a/drivers/bluetooth/btbcm.c b

[RESEND PATCH 1/5] dt-bindings: net: Add compatible for BCM4345C5 bluetooth device

From: Ondrej Jirman This is present in the AP6526 WiFi/Bluetooth 5.0 module. Signed-off-by: Ondrej Jirman --- Documentation/devicetree/bindings/net/broadcom-bluetooth.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/net/broadcom-bluetooth.txt b/Documen

[RESEND PATCH 4/5] arm64: dts: allwinner: h6: Add pin configs for uart1

From: Ondrej Jirman Orange Pi 3 uses UART1 for bluetooth. Add pinconfigs so that we can use them. Signed-off-by: Ondrej Jirman --- arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi b/arch/a

[PATCH v2] ARM: ftrace: remove mcount(),ftrace_caller_old() and ftrace_call_old()

Commit d3c61619568c ("ARM: 8788/1: ftrace: remove old mcount support") removed the old mcount support, but forget to remove these three declarations. This patch removes them. Signed-off-by: Jisheng Zhang --- Changes since v1: - remove mcount() declaration too arch/arm/include/asm/ftrace.h |

[PATCH v3] ARM: ftrace: remove mcount(),ftrace_caller_old() and ftrace_call_old()

Commit d3c61619568c ("ARM: 8788/1: ftrace: remove old mcount support") removed the old mcount support, but forget to remove these three declarations. This patch removes them. Signed-off-by: Jisheng Zhang --- Changes since v2: - really remove mcount() declaration too. I made a mistake when send

Re: [PATCH v3 04/10] KVM: Implement kvm_put_guest()

On 22/08/2019 17:24, Sean Christopherson wrote: > On Thu, Aug 22, 2019 at 04:46:10PM +0100, Steven Price wrote: >> On 22/08/2019 16:28, Sean Christopherson wrote: >>> On Wed, Aug 21, 2019 at 04:36:50PM +0100, Steven Price wrote: kvm_put_guest() is analogous to put_user() - it writes a single v

Re: [PATCHv2 0/4] Layerscape: Remove num-lanes property from PCIe nodes

On Fri, Aug 23, 2019 at 10:44:25AM +0100, Andrew Murray wrote: > On Thu, Aug 22, 2019 at 05:48:15PM +0100, Lorenzo Pieralisi wrote: > > On Tue, Aug 20, 2019 at 07:28:37AM +, Z.q. Hou wrote: > > > From: Hou Zhiqiang > > > > > > On FSL Layerscape SoCs, the number of lanes assigned to PCIe > > >

Re: Regression in 5.3-rc1 and later

Hi, To everyone on the long Cc list... What's happening with this? I was about to merge the patches for 32-bit ARM, which I don't want to do if doing so will cause this regression on 32-bit ARM as well. Thanks. On Thu, Aug 22, 2019 at 07:57:59AM +0100, Chris Clayton wrote: > Hi everyone, > >

Re: Regression in 5.3-rc1 and later

On Fri, Aug 23, 2019 at 11:36:54AM +0100, Russell King - ARM Linux admin wrote: > To everyone on the long Cc list... > > What's happening with this? I was about to merge the patches for 32-bit > ARM, which I don't want to do if doing so will cause this regression on > 32-bit ARM as well. tglx fi

Re: [PATCHv2] lib/test_kasan: add roundtrip tests

Hi Andrew, On Thu, Aug 22, 2019 at 04:48:57PM -0700, Andrew Morton wrote: > On Mon, 19 Aug 2019 17:14:49 +0100 Mark Rutland wrote: > > > In several places we need to be able to operate on pointers which have > > gone via a roundtrip: > > > > virt -> {phys,page} -> virt > > > > With KASAN_S

Re: Regression in 5.3-rc1 and later

Hi Russell, On 8/23/19 11:36 AM, Russell King - ARM Linux admin wrote: > Hi, > > To everyone on the long Cc list... > > What's happening with this? I was about to merge the patches for 32-bit > ARM, which I don't want to do if doing so will cause this regression on > 32-bit ARM as well. > The

Re: [PATCH] drm/komeda: Reordered the komeda's de-init functions

On Tuesday, 20 August 2019 18:46:19 BST Ayan Halder wrote: > The de-init routine should be doing the following in order:- > 1. Unregister the drm device > 2. Shut down the crtcs - failing to do this might cause a connector leakage > See the 'commit 109c4d18e574 ("drm/arm/malidp: Ensure that the crt

Re: [PATCH v6] ata/pata_buddha: Probe via modalias instead of initcall

Hi, On 8/20/19 6:57 PM, Max Staudt wrote: > Up until now, the pata_buddha driver would only check for cards on > initcall time. Now, the kernel will call its probe function as soon > as a compatible card is detected. > > v6: Only do the drvdata workaround for X-Surf (remove breaks otherwise) >

Re: [PATCH 1/3] PCI: Add PCI_ERROR_RESPONSE definition

On Thu, Aug 22, 2019 at 03:05:49PM -0500, Bjorn Helgaas wrote: > From: Bjorn Helgaas > > An MMIO read from a PCI device that doesn't exist or doesn't respond causes > a PCI error. There's no real data to return to satisfy the CPU read, so > most hardware fabricates ~0 data. > > Add a PCI_ERROR_

Re: [PATCH] perf cgroups: Don't rotate events for cgroups unnecessarily

Hi, We are seeing regression with our uncore perf driver(Marvell's ThunderX2, ARM64 server platform) on 5.3-Rc1. After bisecting, it turned out to be this patch causing the issue. Test case: Load module and run perf for more than 4 events( we have 4 counters, event multiplexing takes place for mo

Applied "spi: spi-fsl-dspi: Exit the ISR with IRQ_NONE when it's not ours" to the spi tree

The patch spi: spi-fsl-dspi: Exit the ISR with IRQ_NONE when it's not ours has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.3 All being well this means that it will be integrated into the linux-next tree (usually sometime in the nex

Re: [PATCH v9 1/8] ARM: aurora-l2: add prefix to MAX_RANGE_SIZE

On Fri, Jul 12, 2019 at 03:48:57PM +1200, Chris Packham wrote: > From: Jan Luebbe > > The macro name is too generic, so add a AURORA_ prefix. > > Signed-off-by: Jan Luebbe > Reviewed-by: Gregory CLEMENT > Signed-off-by: Chris Packham > --- > arch/arm/include/asm/hardware/cache-aurora-l2.h |

Re: comments style: Re: [RFC PATCH v4 1/9] printk-rb: add a new printk ringbuffer implementation

On Thu 2019-08-22 19:38:01, Andrea Parri wrote: > On Thu, Aug 22, 2019 at 03:50:52PM +0200, Petr Mladek wrote: > > On Wed 2019-08-21 07:46:28, John Ogness wrote: > > > On 2019-08-20, Sergey Senozhatsky > > > wrote: > > > > [..] > > > >> > + * > > > >> > + * Memory barrier involvement: > >

Re: [PATCH v6] ata/pata_buddha: Probe via modalias instead of initcall

On 08/23/2019 12:42 PM, Bartlomiej Zolnierkiewicz wrote: >> +static struct zorro_driver pata_buddha_driver = { >> +.name = "pata_buddha", >> +.id_table = pata_buddha_zorro_tbl, >> +.probe = pata_buddha_probe, >> +.remove = pata_buddha_remove, >> +

[PATCH v7] ata/pata_buddha: Probe via modalias instead of initcall

Up until now, the pata_buddha driver would only check for cards on initcall time. Now, the kernel will call its probe function as soon as a compatible card is detected. v7: Removed suppress_bind_attrs that slipped in v6: Only do the drvdata workaround for X-Surf (remove breaks otherwise) Styl

Re: [PATCH v9 1/8] ARM: aurora-l2: add prefix to MAX_RANGE_SIZE

On Fri, Aug 23, 2019 at 11:46:21AM +0100, Russell King - ARM Linux admin wrote: > On Fri, Jul 12, 2019 at 03:48:57PM +1200, Chris Packham wrote: > > From: Jan Luebbe > > > > The macro name is too generic, so add a AURORA_ prefix. > > > > Signed-off-by: Jan Luebbe > > Reviewed-by: Gregory CLEMEN

Re: [PATCH v2 2/5] spi: spi-fsl-dspi: Exit the ISR with IRQ_NONE when it's not ours

On Fri, Aug 23, 2019 at 01:30:27PM +0300, Vladimir Oltean wrote: > On Fri, 23 Aug 2019 at 13:28, Mark Brown wrote: > > It would be better to have done this as the first patch before > > the restructuring, that way we could send this as a fix - the > > refactoring while good doesn't really fit wit

Re: Regression in 5.3-rc1 and later

On Fri, Aug 23, 2019 at 11:43:32AM +0100, Vincenzo Frascino wrote: > Hi Russell, > > On 8/23/19 11:36 AM, Russell King - ARM Linux admin wrote: > > Hi, > > > > To everyone on the long Cc list... > > > > What's happening with this? I was about to merge the patches for 32-bit > > ARM, which I don

Re: [PATCH] Input: ili210x - switch to using threaded IRQ

On 8/11/19 6:11 PM, Dmitry Torokhov wrote: > Let's switch the driver to using threaded IRQ so that we do not need to > manage the interrupt and work separately, and we do not acknowledge > interrupt until we finished handling it completely. > > Signed-off-by: Dmitry Torokhov On ILI2117 Tested-by

Re: [PATCH 0/1] Fix shared IRQ behavior in spi-fsl-dspi

On Fri, Aug 23, 2019 at 12:24:49AM +0300, Vladimir Oltean wrote: > This patch is taken out of the "Poll mode for NXP DSPI driver" series > and respun against the "for-4.20" branch. > $(git describe --tags 13aed2392741) shows: > v4.20-rc1-18-g13aed2392741 Please don't send cover letters for single

Re: [PATCH v2 2/5] spi: spi-fsl-dspi: Exit the ISR with IRQ_NONE when it's not ours

On Fri, Aug 23, 2019 at 11:50:44AM +0100, Mark Brown wrote: > On Fri, Aug 23, 2019 at 01:30:27PM +0300, Vladimir Oltean wrote: > > Did you see this? > > https://lkml.org/lkml/2019/8/22/1542 > I'm not online enough to readily follow that link right now, I > did apply another patch for a similar is

Applied "spi: spi-fsl-dspi: Exit the ISR with IRQ_NONE when it's not ours" to the spi tree

The patch spi: spi-fsl-dspi: Exit the ISR with IRQ_NONE when it's not ours has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.4 All being well this means that it will be integrated into the linux-next tree (usually sometime in the nex

Applied "spi: spi-fsl-dspi: Remove impossible to reach error check" to the spi tree

The patch spi: spi-fsl-dspi: Remove impossible to reach error check has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.4 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 ho

Applied "spi: spi-fsl-dspi: Use poll mode in case the platform IRQ is missing" to the spi tree

The patch spi: spi-fsl-dspi: Use poll mode in case the platform IRQ is missing has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.4 All being well this means that it will be integrated into the linux-next tree (usually sometime in the

Applied "spi: spi-fsl-dspi: Reduce indentation level in dspi_interrupt" to the spi tree

The patch spi: spi-fsl-dspi: Reduce indentation level in dspi_interrupt has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.4 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 2

Re: [PATCH v5 15/20] RISC-V: KVM: Add timer functionality

On Fri, Aug 23, 2019 at 1:23 PM Alexander Graf wrote: > > On 22.08.19 10:46, Anup Patel wrote: > > From: Atish Patra > > > > The RISC-V hypervisor specification doesn't have any virtual timer > > feature. > > > > Due to this, the guest VCPU timer will be programmed via SBI calls. > > The host wil

Re: [PATCHv2 0/4] Layerscape: Remove num-lanes property from PCIe nodes

On Tue, Aug 20, 2019 at 07:28:37AM +, Z.q. Hou wrote: > From: Hou Zhiqiang > > On FSL Layerscape SoCs, the number of lanes assigned to PCIe > controller is not fixed, it is determined by the selected > SerDes protocol. The current num-lanes indicates the max lanes > PCIe controller can suppor

<    1   2   3   4   5   6   7   8   9   >