Re: [Intel-gfx] [PATCH v2 02/21] drm: Evaluate struct drm_device.vblank_disable_immediate on each use

Hi Am 15.01.20 um 15:37 schrieb Ville Syrjälä: > On Wed, Jan 15, 2020 at 01:16:33PM +0100, Thomas Zimmermann wrote: >> VBLANK interrupts can be disabled immediately or with a delay, where the >> latter is the default. The former option can be selected by setting >> get_vblank_timestamp, and enabli

[PATCH v2 3/5] drm/panel: Add Feixin K101 IM2BA02 panel

Feixin K101 IM2BA02 is a 800x1280 4-lane MIPI-DSI LCD panel. Add a panel driver for it. Signed-off-by: Icenowy Zheng --- Changes in v2: - Use regulator_bulk. - Small code fixes. MAINTAINERS | 6 + drivers/gpu/drm/panel/Kconfig | 9 + driver

[PATCH 1/3] drm/panel: make LVDS panel driver DPI capable

From: Stefan Agner The LVDS panel driver has almost everything which is required to describe a simple parallel RGB panel (also known as DPI, Display Pixel Interface). Signed-off-by: Stefan Agner Signed-off-by: Oleksandr Suvorov --- drivers/gpu/drm/panel/panel-lvds.c | 40

[PATCH v2 1/2] drm/msm: Add a GPU-wide wait queue

This wait queue is signaled on all IRQs for a given GPU and will be used as part of the new MSM_WAIT_IOVA ioctl so userspace can sleep until the value at a given iova reaches a certain condition. Signed-off-by: Brian Ho --- drivers/gpu/drm/msm/msm_gpu.c | 4 drivers/gpu/drm/msm/msm_gpu.h |

[PATCH] drm/scheduler: improve job distribution with multiple queues

This patch uses score based logic to select a new rq for better loadbalance between multiple rq/scheds instead of num_jobs. Below are test results after running amdgpu_test from mesa drm Before this patch: sched_name num of many times it got scheduled = =

WARNING in schedule_bh

Hello, syzbot found the following crash on: HEAD commit:95e20af9 Merge tag 'nfs-for-5.5-2' of git://git.linux-nfs... git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=17648c21e0 kernel config: https://syzkaller.appspot.com/x/.config?x=d9290aeb7e6cf1c4 da

Re: [PATCH 2/2] drm: sun4i: hdmi: Add support for sun4i HDMI encoder audio

Hi, On 1/15/20 10:32 AM, Maxime Ripard wrote: Hi Stefan, On Tue, Jan 14, 2020 at 11:04:55AM +0200, Stefan Mavrodiev wrote: On 1/10/20 6:26 PM, Maxime Ripard wrote: Hi, On Fri, Jan 10, 2020 at 04:11:40PM +0200, Stefan Mavrodiev wrote: Add HDMI audio support for the sun4i-hdmi encoder, used o

[PATCH 2/3] drm/panel: pass video modes bus_flags

From: Stefan Agner Make sure that the bus_flags parsed from the display timings are passed to the connector display info. Signed-off-by: Stefan Agner Signed-off-by: Oleksandr Suvorov --- drivers/gpu/drm/panel/panel-lvds.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a

Re: [PATCH] drm/amdgpu/display: Use u64 divide macro for round up division

On 1/13/20 9:07 AM, Ville Syrjälä wrote: > On Mon, Jan 13, 2020 at 08:20:42AM -0500, mikita.lip...@amd.com wrote: >> From: Mikita Lipski >> >> [why] >> Fix compilation warnings on i386 architecture: >> undefined reference to `__udivdi3' >> [how] >> Switch DIV_ROUND_UP to DIV64_U64_ROUND_UP >> >> R

[PATCH v2 1/5] dt-bindings: vendor-prefix: add Shenzhen Feixin Photoelectics Co., Ltd

Shenzhen Feixin Photoelectics Co., Ltd is a company to provide LCD modules. Add its vendor prefix. Signed-off-by: Icenowy Zheng Acked-by: Sam Ravnborg Acked-by: Rob Herring --- Changes in v2: - Added ACKs from Sam and Rob. Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++ 1 file

[PATCH v2 5/5] arm64: dts: allwinner: a64: add support for PineTab

PineTab is a 10.1" tablet by Pine64 with Allwinner A64 inside. It includes the following peripherals: USB: - A microUSB Type-B port connected to the OTG-capable USB PHY of Allwinner A64. The ID pin is connected to a GPIO of the A64 SoC, and the Vbus is connected to the Vbus of AXP803 PMIC. These

[PATCH v2 0/2] drm/msm: Add the MSM_WAIT_IOVA ioctl

This patch set implements the MSM_WAIT_IOVA ioctl which lets userspace sleep until the value at a given iova reaches a certain condition. This is needed in turnip to implement the VK_QUERY_RESULT_WAIT_BIT flag for vkGetQueryPoolResults. First, we add a GPU-wide wait queue that is signaled on all I

[PATCH v2 0/5] Add support for Pine64 PineTab

This patchset tries to add support for the PineTab tablet from Pine64. As it uses a specific MIPI-DSI panel, the support of the panel should be introduced first, with its DT binding. Then a device tree is added. Compared to v1 of the patchset, the accelerometer support is temporarily removed beca

[PATCH v2 2/5] dt-bindings: panel: add Feixin K101 IM2BA02 MIPI-DSI panel

Feixin K101 IM2BA02 is a 10.1" 800x1280 4-lane MIPI-DSI panel. Add device tree binding for it. Signed-off-by: Icenowy Zheng --- Changes in v2: - Set backlight property to optional. (Technically this panel requires backlight, but theortically it can be not adjustable.) - Tweaked the example to

[PATCH 0/3] Generic DPI panel on Colibri iMX7 / Col.Eval.board

Make LVDS panel driver DPI capable and use it to add generic RGB (DPI) panel support for Colibri iMX7 SoM on Colibri Evaluation Board. Oleksandr Suvorov (1): ARM: dts: imx7-colibri: add generic RGB (DPI) panel Stefan Agner (2): drm/panel: make LVDS panel driver DPI capable drm/panel: pas

[PATCH v2 4/5] dt-bindings: arm: sunxi: add binding for PineTab tablet

Add the device tree binding for Pine64's PineTab tablet, which uses Allwinner A64 SoC. Signed-off-by: Icenowy Zheng Reviewed-by: Rob Herring --- Changes in v2: - Added Review tag by Rob. Documentation/devicetree/bindings/arm/sunxi.yaml | 5 + 1 file changed, 5 insertions(+) diff --git a/D

[PATCH v2 2/2] drm/msm: Add MSM_WAIT_IOVA ioctl

Implements an ioctl to wait until a value at a given iova is greater than or equal to a supplied value. This will initially be used by turnip (open-source Vulkan driver for QC in mesa) for occlusion queries where the userspace driver can block on a query becoming available before continuing via vk

Re: [PATCH v3] drm/panfrost: Add the panfrost_gem_mapping concept

On Wed, 15 Jan 2020 20:15:54 -0600 Rob Herring wrote: > From: Boris Brezillon > > With the introduction of per-FD address space, the same BO can be mapped > in different address space if the BO is globally visible (GEM_FLINK) > and opened in different context or if the dmabuf is self-imported.

Re: [Intel-gfx] [PATCH v2 03/21] drm: Add get_vblank_timestamp() to struct drm_crtc_funcs

Hi Am 15.01.20 um 15:49 schrieb Ville Syrjälä: > On Wed, Jan 15, 2020 at 01:16:34PM +0100, Thomas Zimmermann wrote: >> The callback get_vblank_timestamp() is currently located in struct >> drm_driver, but really belongs into struct drm_crtc_funcs. Add an >> equivalent there. Driver will be convert

[git pull] vmwgfx-next

Dave, Daniel The main 5.6 -next pull from vmwgfx. Minor things here and there, as well as an added ioctl for host messaging and a corresponding api version bump. Thanks, Thomas The following changes since commit 71e7274066c646bb3d9da39d2f4db0a6404c0a2d: Merge tag 'drm-intel-next-2020-01-14' o

[git pull] ttm-prot-fix

From: Thomas Hellström (VMware) Dave, Daniel, A small fix for the long-standing ttm vm page protection hack. I'm sending this a separate pull request since it is touching mm code and similar to the vmwgfx coherent stuff, Linus might want this as a separate pull request. If sent separate it'd b

Re: [Intel-gfx] [PATCH v2 03/21] drm: Add get_vblank_timestamp() to struct drm_crtc_funcs

On Thu, Jan 16, 2020 at 09:44:55AM +0100, Thomas Zimmermann wrote: > Hi > > Am 15.01.20 um 15:49 schrieb Ville Syrjälä: > > On Wed, Jan 15, 2020 at 01:16:34PM +0100, Thomas Zimmermann wrote: > >> @@ -2020,3 +2042,193 @@ int drm_crtc_queue_sequence_ioctl(struct > >> drm_device *dev, void *data, >

RE: [PATCH] drm: Inject a cond_resched() into long drm_clflush_sg()

Quoting David Laight (2020-01-16 12:26:45) > However there is a call from __i915_gem_objet_set_pages() that > is preceded by a lockdep_assert_held() check - so mustn't sleep. That is a mutex; it's allowed to sleep. The might_sleep() here should help assuage your fears. -Chris _

[PATCH 3/5] drm/lima: support heap buffer creation

heap buffer is used as output of GP and input of PP for Mali Utgard GPU. Size of heap buffer depends on the task so is a runtime variable. Previously we just create a large enough buffer as heap buffer. Now we add a heap buffer type to be able to increase the backup memory dynamically when GP fail

[PATCH 4/5] drm/lima: recover task by enlarging heap buffer

Increase heap buffer backup memory when GP receive PLBU out of memory interrupt, then resume the task. Signed-off-by: Qiang Yu --- drivers/gpu/drm/lima/lima_gp.c| 51 +-- drivers/gpu/drm/lima/lima_mmu.c | 5 +++ drivers/gpu/drm/lima/lima_mmu.h | 1 + drivers

[PATCH 0/5] drm/lima: add heap buffer support

Support heap buffer allocation which can grow the back memory size when GP has an out of memory interrupt so that user don't need to allocate a very large buffer at the beginning. Qiang Yu (5): drm/lima: update register info drm/lima: add lima_vm_map_bo drm/lima: support heap buffer creation

[PATCH 1/5] drm/lima: update register info

>From Mali r10p0 kernel driver source code. Signed-off-by: Qiang Yu --- drivers/gpu/drm/lima/lima_regs.h | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/lima/lima_regs.h b/drivers/gpu/drm/lima/lima_regs.h index ace8ecefbe90..0124c90e0153 100644 --- a/drivers/gpu/drm/lima/lima

[PATCH 2/5] drm/lima: add lima_vm_map_bo

For dynamically mapping added backup memory of lima_bo to vm. This is a preparation for adding heap buffer support. Signed-off-by: Qiang Yu --- drivers/gpu/drm/lima/lima_vm.c | 40 ++ drivers/gpu/drm/lima/lima_vm.h | 1 + 2 files changed, 41 insertions(+) diff -

[PATCH 5/5] drm/lima: increase driver version to 1.1

Signed-off-by: Qiang Yu --- drivers/gpu/drm/lima/lima_drv.c | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/lima/lima_drv.c b/drivers/gpu/drm/lima/lima_drv.c index 18f88aaef1a2..2daac64d8955 100644 --- a/drivers/gpu/drm/lima/lima_drv.c +++ b/drivers/

Re: [PATCH v6 4/5] drm/tidss: New driver for TI Keystone platform Display SubSystem

On 15/01/2020 19:13, Sam Ravnborg wrote: > Hi Jyri. > >> Well, I'll bite the bullet then, and start mangling the code to the >> "strict" format. > > While touching the code please consider moving all logging > over to the new drm_{err,warn,info,dbg} functions. > They give the nice "[drm]" marker.

RE: [PATCH] drm: Inject a cond_resched() into long drm_clflush_sg()

Quoting David Laight (2020-01-16 13:58:44) > From: Chris Wilson > > Sent: 16 January 2020 12:29 > > > > Quoting David Laight (2020-01-16 12:26:45) > > > However there is a call from __i915_gem_objet_set_pages() that > > > is preceded by a lockdep_assert_held() check - so mustn't sleep. > > > > T

[PATCH 1/6] video: fbdev: controlfb: fix sparse warning about using incorrect type

Force le32_to_cpup() argument to be of proper type (const __le32 *). Also add missing inline keyword to control_par_to_var() definition (to match function prototype). Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/video/fbdev/controlfb.c | 5 +++-- 1 file changed, 3 insertions(+), 2 delet

[PATCH 2/6] video: fbdev: controlfb: remove obsolete module support

CONFIG_FB_CONTROL is bool, hence the Apple "control" frame buffer driver cannot be built as a module. Replace module_init() by device_initcall(). Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/video/fbdev/controlfb.c | 25 + 1 file changed, 1 insertion(+), 24 delet

[PATCH 4/6] video: fbdev: controlfb: remove function prototypes part #1

Reorder code a bit and then remove no longer needed function prototypes. Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/video/fbdev/controlfb.c | 41 +++-- 1 file changed, 13 insertions(+), 28 deletions(-) diff --git a/drivers/video/fbdev/controlfb.c b/drivers/

[PATCH 6/6] video: fbdev: controlfb: remove function prototypes part #3

Reorder code a bit and then remove no longer needed function prototypes. Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/video/fbdev/controlfb.c | 306 +++- 1 file changed, 147 insertions(+), 159 deletions(-) diff --git a/drivers/video/fbdev/controlfb.c b/driver

[PATCH 0/6] video: fbdev: controlfb: small cleanup

Hi, Small cleanup for controlfb driver: - fix sparse warnings - remove not working module support - add COMPILE_TEST support - remove redundant function prototypes Best regards, -- Bartlomiej Zolnierkiewicz Samsung R&D Institute Poland Samsung Electronics Bartlomiej Zolnierkiewicz (6): video

[PATCH 5/6] video: fbdev: controlfb: remove function prototypes part #2

Reorder code a bit and then remove no longer needed function prototypes. Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/video/fbdev/controlfb.c | 410 +++- 1 file changed, 198 insertions(+), 212 deletions(-) diff --git a/drivers/video/fbdev/controlfb.c b/driver

[PATCH 3/6] video: fbdev: controlfb: add COMPILE_TEST support

Add COMPILE_TEST support to controlfb driver for better compile testing coverage. Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/video/fbdev/Kconfig | 2 +- drivers/video/fbdev/controlfb.c | 21 +++-- 2 files changed, 20 insertions(+), 3 deletions(-) diff --git a/driv

Re: [RFC PATCH 4/4] drm/i915/gvt: move public gvt headers out into global include

On Thu, Jan 16, 2020 at 03:13:01PM +0100, Julian Stecklina wrote: > Hi Greg, Christoph, > > On Wed, 2020-01-15 at 16:22 +0100, Greg KH wrote: > > On Thu, Jan 09, 2020 at 07:13:57PM +0200, Julian Stecklina wrote: > > > Now that the GVT interface to hypervisors does not depend on i915/GVT > > > inte

Re: [PATCH 2/2] drm/bridge: Add tc358768 driver

On 17.12.2019 11:15, Peter Ujfalusi wrote: > Add basic support for the Toshiba TC358768 RGB to DSI bridge. > Not all the features of the TC358768 is implemented by the initial driver: > MIPI_DSI_MODE_VIDEO and MIPI_DSI_FMT_RGB888 is only supported and tested. > > Only write is implemented for mipi_

[PATCH] video: fbdev: arcfb: add COMPILE_TEST support

Add COMPILE_TEST support to arcfb driver for better compile testing coverage. Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/video/fbdev/Kconfig |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: b/drivers/video/fbdev/Kconfig ==

[PATCH 1/2] video: fbdev: sh_mobile_lcdcfb: fix sparse warnings about using incorrect types

Use ->screen_buffer instead of ->screen_base to fix sparse warnings. [ Please see commit 17a7b0b4d974 ("fb.h: Provide alternate screen_base pointer") for details. ] Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/video/fbdev/sh_mobile_lcdcfb.c |4 ++-- 1 file changed, 2 insertions(+)

[PATCH 2/2] video: fbdev: sh_mobile_lcdcfb: add COMPILE_TEST support

Add COMPILE_TEST support to sh_mobile_lcdcfb driver for better compile testing coverage. Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/video/fbdev/Kconfig |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) Index: b/drivers/video/fbdev/Kconfig =

[PATCH 1/2] video: fbdev: w100fb: fix sparse warnings

* Add missing __iomem annotations where needed. * Make w100fb_probe() static. * Return NULL pointer (instead of using plain integer) in w100_get_xtal_tabl(). Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/video/fbdev/w100fb.c | 18 ++ 1 file changed, 10 insertions(+), 8

[PATCH 2/2] video: fbdev: w100fb: add COMPILE_TEST support

Add COMPILE_TEST support to w100fb driver for better compile testing coverage. Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/video/fbdev/Kconfig |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: b/drivers/video/fbdev/Kconfig =

[PATCH 1/2] video: fbdev: wm8505fb: fix sparse warnings about using incorrect types

Use ->screen_buffer instead of ->screen_base to fix sparse warnings. [ Please see commit 17a7b0b4d974 ("fb.h: Provide alternate screen_base pointer") for details. ] Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/video/fbdev/wm8505fb.c |2 +- 1 file changed, 1 insertion(+), 1 deletio

[PATCH 1/2] video: fbdev: wm8505fb: fix sparse warnings about using incorrect types

Use ->screen_buffer instead of ->screen_base to fix sparse warnings. [ Please see commit 17a7b0b4d974 ("fb.h: Provide alternate screen_base pointer") for details. ] Signed-off-by: Bartlomiej Zolnierkiewicz --- Resend with Tony & linux-arm ML added to Cc:. drivers/video/fbdev/wm8505fb.c |

[PATCH 2/2] video: fbdev: wm8505fb: add COMPILE_TEST support

Add COMPILE_TEST support to wm8505fb driver for better compile testing coverage. Signed-off-by: Bartlomiej Zolnierkiewicz --- drivers/video/fbdev/Kconfig |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: b/drivers/video/fbdev/Kconfig ===

[Bug 206225] New: nouveau: Screen distortion and lockup on resume

https://bugzilla.kernel.org/show_bug.cgi?id=206225 Bug ID: 206225 Summary: nouveau: Screen distortion and lockup on resume Product: Drivers Version: 2.5 Kernel Version: 5.4.12 Hardware: Intel OS: Linux Tree: M

[Bug 206225] nouveau: Screen distortion and lockup on resume

https://bugzilla.kernel.org/show_bug.cgi?id=206225 --- Comment #1 from Christoph Marz (derchiller-fo...@online.de) --- Created attachment 286845 --> https://bugzilla.kernel.org/attachment.cgi?id=286845&action=edit 5.3.9 nouveau resume bug dmesg output after resume from hibernation before instal

[PULL] drm-intel-fixes

Hi Dave & Daniel, Two new fixes still, the VMA activity fixes are overflow from last week as I couldn't get CI results then. One important uAPI fix for PMU names to comply with tools/perf, thanks for our media team for noticing. A compile fix and two VMA activity tracking fixes for error capture

[Bug 206225] nouveau: Screen distortion and lockup on resume

https://bugzilla.kernel.org/show_bug.cgi?id=206225 --- Comment #2 from Christoph Marz (derchiller-fo...@online.de) --- Created attachment 286847 --> https://bugzilla.kernel.org/attachment.cgi?id=286847&action=edit 5.3.9 nouveau resume ok dmesg output after resume from hibernation right after in

[Bug 206225] nouveau: Screen distortion and lockup on resume

https://bugzilla.kernel.org/show_bug.cgi?id=206225 --- Comment #3 from Christoph Marz (derchiller-fo...@online.de) --- Created attachment 286849 --> https://bugzilla.kernel.org/attachment.cgi?id=286849&action=edit 5.4.12: Syslog excerpt: Resume after hibernation nouveau error messages and call

[Bug 206225] nouveau: Screen distortion and lockup on resume

https://bugzilla.kernel.org/show_bug.cgi?id=206225 --- Comment #4 from Christoph Marz (derchiller-fo...@online.de) --- Created attachment 286851 --> https://bugzilla.kernel.org/attachment.cgi?id=286851&action=edit 5.4.12: Syslog excerpt: Resume after suspend nouveau error messages, no call trac

[PULL] drm-misc-fixes

Hi Dave and Daniel, I'm delighted to present another -misc-fixes pull. Dock users rejoice, MST keeps getting better! Please pull! drm-misc-fixes-2020-01-16: virtio: maintain obj reservation lock when submitting cmds (Gerd) rockchip: increase link rate var size to accommodate rates (Tobias) mst:

[PATCH AUTOSEL 5.4 002/205] drm/panfrost: Add missing check for pfdev->regulator

From: Steven Price [ Upstream commit 52282163dfa651849e905886845bcf6850dd83c2 ] When modifying panfrost_devfreq_target() to support a device without a regulator defined I missed the check on the error path. Let's add it. Reported-by: Dan Carpenter Fixes: e21dd290881b ("drm/panfrost: Enable dev

[PATCH AUTOSEL 5.4 004/205] drm: panel-lvds: Potential Oops in probe error handling

From: Dan Carpenter [ Upstream commit fb2ee9bf084bcaeff1e5be100decc0eacb4af2d5 ] The "lvds->backlight" pointer could be NULL in situations where of_parse_phandle() returns NULL. This code is cleaner if we use the managed devm_of_find_backlight() so the clean up is automatic. Fixes: 7c9dff5bd64

[PATCH AUTOSEL 5.4 003/205] drm/v3d: don't leak bin job if v3d_job_init fails.

From: Iago Toral Quiroga [ Upstream commit 0d352a3a8a1f26168d09f7073e61bb4b328e3bb9 ] If the initialization of the job fails we need to kfree() it before returning. Signed-off-by: Iago Toral Quiroga Signed-off-by: Eric Anholt Link: https://patchwork.freedesktop.org/patch/msgid/20190916071125

[PATCH AUTOSEL 5.4 019/205] drm/amdgpu: remove excess function parameter description

From: yu kuai [ Upstream commit d0580c09c65cff211f589a40e08eabc62da463fb ] Fixes gcc warning: drivers/gpu/drm/amd/amdgpu/vcn_v2_5.c:431: warning: Excess function parameter 'sw' description in 'vcn_v2_5_disable_clock_gating' drivers/gpu/drm/amd/amdgpu/vcn_v2_5.c:550: warning: Excess function par

[PATCH AUTOSEL 5.4 035/205] drm/rockchip: Round up _before_ giving to the clock framework

From: Douglas Anderson [ Upstream commit 287422a95fe28e05c1952de0472e0dfdffa6caae ] I'm embarassed to say that even though I've touched vop_crtc_mode_fixup() twice and I swear I tested it, there's still a stupid glaring bug in it. Specifically, on veyron_minnie (with all the latest display timi

[PATCH AUTOSEL 5.4 048/205] drm: rcar_lvds: Fix color mismatches on R-Car H2 ES2.0 and later

From: Geert Uytterhoeven [ Upstream commit 3986457110a054466bf02f9c4a85aa2bba96177b ] Commit 5cca30ebe089be23 ("drm/rcar-du: Add LVDS_LANES quirk") states that LVDS lanes 1 and 3 are inverted on R-Car H2 ES1 only, and that the problem has been fixed in newer revisions. However, the code didn't

[PATCH AUTOSEL 5.4 058/205] xprtrdma: Connection becomes unstable after a reconnect

From: Chuck Lever [ Upstream commit a31b2f939219dd9bffdf01a45bd91f209f8cc369 ] This is because xprt_request_get_cong() is allowing more than one RPC Call to be transmitted before the first Receive on the new connection. The first Receive fills the Receive Queue based on the server's credit grant

[PATCH AUTOSEL 5.4 060/205] drm/tegra: Fix ordering of cleanup code

From: Thierry Reding [ Upstream commit 051172e8c1ceef8749f19faacc1d3bef65d20d8d ] Commit Fixes: b9f8b09ce256 ("drm/tegra: Setup shared IOMMU domain after initialization") changed the initialization order of the IOMMU related bits but didn't update the cleanup path accordingly. This asymmetry can

[PATCH AUTOSEL 5.4 059/205] xprtrdma: Fix MR list handling

From: Chuck Lever [ Upstream commit c3700780a096fc66467c81076ddf7f3f11d639b5 ] Close some holes introduced by commit 6dc6ec9e04c4 ("xprtrdma: Cache free MRs in each rpcrdma_req") that could result in list corruption. In addition, the result that is tabulated in @count is no longer used, so @cou

[PATCH AUTOSEL 5.4 066/205] drm/amdgpu/vi: silence an uninitialized variable warning

From: Dan Carpenter [ Upstream commit 4ff17a1df7d550257972a838220a8af4611c8f2c ] Smatch complains that we need to initialized "*cap" otherwise it can lead to an uninitialized variable bug in the caller. This seems like a reasonable warning and it doesn't hurt to silence it at least. drivers/gp

[PATCH AUTOSEL 5.4 169/205] drm/radeon: fix bad DMA from INTERRUPT_CNTL2

From: Sam Bobroff [ Upstream commit 62d91dd2851e8ae2ca552f1b090a3575a4edf759 ] The INTERRUPT_CNTL2 register expects a valid DMA address, but is currently set with a GPU MC address. This can cause problems on systems that detect the resulting DMA read from an invalid address (found on a Power8 g

[PATCH AUTOSEL 4.19 005/671] drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()

From: Dan Carpenter [ Upstream commit 09c4b49457434fa74749ad6194ef28464d9f5df9 ] This doesn't affect runtime because in the current code "idx" is always valid. First, we read from "vgdev->capsets[idx].max_size" before checking whether "idx" is within bounds. And secondly the bounds check is of

[PATCH AUTOSEL 4.19 001/671] drm/sti: do not remove the drm_bridge that was never added

From: Peter Rosin [ Upstream commit 66e31a72dc38543b2d9d1ce267dc78ba9beebcfd ] Removing the drm_bridge_remove call should avoid a NULL dereference during list processing in drm_bridge_remove if the error path is ever taken. The more natural approach would perhaps be to add a drm_bridge_add, but

[PATCH AUTOSEL 4.19 014/671] drm/hisilicon: hibmc: Don't overwrite fb helper surface depth

From: John Garry [ Upstream commit 0ff9f49646353ce31312411e7e7bd2281492a40e ] Currently the driver overwrites the surface depth provided by the fb helper to give an invalid bpp/surface depth combination. This has been exposed by commit 70109354fed2 ("drm: Reject unknown legacy bpp and depth for

[PATCH AUTOSEL 4.19 027/671] drm/msm: fix unsigned comparison with less than zero

From: Colin Ian King [ Upstream commit dfdb3be43ef1195c491e6c3760b922acb52e3575 ] The return from the call to _mixer_stages can be a negative error code however this is being assigned to an unsigned variable 'stages' hence the check is always false. Fix this by making 'stages' an int. Detected

Re: [Intel-gfx] [RFC PATCH v2 2/2] drm/i915/gen7: Clear all EU/L3 residual contexts

On Tue, Jan 14, 2020 at 09:45:48AM -0800, Akeem G Abodunrin wrote: > From: Prathap Kumar Valsan > > On gen7 and gen7.5 devices, there could be leftover data residuals in > EU/L3 from the retiring context. This patch introduces workaround to clear > that residual contexts, by submitting a batch bu

[PATCH AUTOSEL 4.19 053/671] drm: rcar-du: Fix the return value in case of error in 'rcar_du_crtc_set_crc_source()'

From: Christophe JAILLET [ Upstream commit 4d486f18d91b1876040bf87e9ad78981a08b15a6 ] We return 0 unconditionally in 'rcar_du_crtc_set_crc_source()'. However, 'ret' is set to some error codes if some function calls fail. Return 'ret' instead to propagate the error code. Fixes: 47a52d024e89 ("m

[PATCH AUTOSEL 4.19 054/671] drm: rcar-du: Fix vblank initialization

From: Laurent Pinchart [ Upstream commit 3d61fe5f59dd3e6f96fc0772156d257cb04dc656 ] The drm_vblank_init() takes the total number of CRTCs as an argument, but the rcar-du driver passes a bitmask of the CRTC indices. Fix it. Fixes: 4bf8e1962f91 ("drm: Renesas R-Car Display Unit DRM driver") Repor

[PATCH AUTOSEL 4.19 056/671] drm/dp_mst: Skip validating ports during destruction, just ref

From: Lyude Paul [ Upstream commit c54c7374ff44de5e609506aca7c0deae4703b6d1 ] Jerry Zuo pointed out a rather obscure hotplugging issue that it seems I accidentally introduced into DRM two years ago. Pretend we have a topology like this: |- DP-1: mst_primary |- DP-4: active display |- DP-

[PATCH AUTOSEL 4.19 041/671] drm/sun4i: hdmi: Fix double flag assignation

From: Maxime Ripard [ Upstream commit 1e0ff648940e603cab6c52cf3723017d30d78f30 ] The is_double flag is a boolean currently assigned to the value of the d variable, that is either 1 or 2. It means that this is_double variable is always set to true, even though the initial intent was to have it se

[PATCH AUTOSEL 4.19 111/671] drm/shmob: Fix return value check in shmob_drm_probe

From: YueHaibing [ Upstream commit 06c3bbd3c12737a50c2e981821b5585e1786e73d ] In case of error, the function devm_ioremap_resource() returns ERR_PTR() and never returns NULL. The NULL test in the return value check should be replaced with IS_ERR(). Fixes: 8f1597c8f1a5 ("drm: shmobile: Perform i

[PATCH AUTOSEL 4.19 105/671] drm/etnaviv: fix some off by one bugs

From: Dan Carpenter [ Upstream commit f5fd9fd4000984f19db689282054953981a50534 ] The ->nr_signal is the supposed to be the number of elements in the ->signal array. There was one place where it was 5 but it was supposed to be 4. That looks like a copy and paste bug. There were also two checks

[PATCH AUTOSEL 4.19 102/671] drm: Fix error handling in drm_legacy_addctx

From: YueHaibing [ Upstream commit c39191feed4540fed98badeb484833dcf659bb96 ] 'ctx->handle' is unsigned, it never less than zero. This patch use int 'tmp_handle' to handle the err condition. Fixes: 62968144e673 ("drm: convert drm context code to use Linux idr") Signed-off-by: YueHaibing Signed

[PATCH AUTOSEL 4.19 106/671] drm/fb-helper: generic: Fix setup error path

From: Noralf Trønnes [ Upstream commit 6e1490cf439aa86b104e5124c36275b964238e1f ] If register_framebuffer() fails during fbdev setup we will leak the framebuffer, the GEM buffer and the shadow buffer for defio. This is because drm_fb_helper_fbdev_setup() just calls drm_fb_helper_fini() on error

[PATCH AUTOSEL 4.19 166/671] fbdev: chipsfb: remove set but not used variable 'size'

From: YueHaibing [ Upstream commit 8e71fa5e4d86bedfd26df85381d65d6b4c860020 ] Fixes gcc '-Wunused-but-set-variable' warning: drivers/video/fbdev/chipsfb.c: In function 'chipsfb_pci_init': drivers/video/fbdev/chipsfb.c:352:22: warning: variable 'size' set but not used [-Wunused-but-set-variable

[PATCH AUTOSEL 4.19 152/671] drm/xen-front: Fix mmap attributes for display buffers

From: Oleksandr Andrushchenko [ Upstream commit 24ded292a5c2ed476f01c77fee65f8320552cd27 ] When GEM backing storage is allocated those are normal pages, so there is no point using pgprot_writecombine while mmaping. This fixes mismatch of buffer pages' memory attributes between the frontend and b

[PATCH AUTOSEL 4.19 171/671] drm/etnaviv: potential NULL dereference

From: Dan Carpenter [ Upstream commit 9e05352340d3a3e68c144136db9810b26ebb88c3 ] The etnaviv_gem_prime_get_sg_table() is supposed to return error pointers. Otherwise it can lead to a NULL dereference when it's called from drm_gem_map_dma_buf(). Fixes: 5f4a4a73f437 ("drm/etnaviv: fix gem_prime_

[PATCH AUTOSEL 4.19 204/671] drm/nouveau: fix missing break in switch statement

From: Colin Ian King [ Upstream commit 785cf1eeafa23ec63f426d322401054d13abe2a3 ] The NOUVEAU_GETPARAM_PCI_DEVICE case is missing a break statement and falls through to the following NOUVEAU_GETPARAM_BUS_TYPE case and may end up re-assigning the getparam->value to an undesired value. Fix this by

[PATCH AUTOSEL 4.19 203/671] drm/nouveau/pmu: don't print reply values if exec is false

From: Colin Ian King [ Upstream commit b1d03fc36ec9834465a08c275c8d563e07f6f6bf ] Currently the uninitialized values in the array reply are printed out when exec is false and nvkm_pmu_send has not updated the array. Avoid confusion by only dumping out these values if they have been actually upda

[PATCH AUTOSEL 4.19 202/671] drm/nouveau/bios/ramcfg: fix missing parentheses when calculating RON

From: Colin Ian King [ Upstream commit 13649101a25c53c87f4ab98a076dfe61f3636ab1 ] Currently, the expression for calculating RON is always going to result in zero no matter the value of ram->mr[1] because the ! operator has higher precedence than the shift >> operator. I believe the missing pare

[PATCH AUTOSEL 4.19 275/671] drm/fb-helper: generic: Call drm_client_add() after setup is done

From: Noralf Trønnes [ Upstream commit 6e3f17ee73f7e3c2ef0e2c8fd8624b2ece8ef2c9 ] Hotplug can happen while drm_fbdev_generic_setup() is running so move drm_client_add() call after setup is done to avoid drm_fbdev_client_hotplug() running in two threads at the same time. Fixes: 9060d7f49376 ("dr

[PATCH AUTOSEL 4.19 270/671] spi: tegra114: configure dma burst size to fifo trig level

From: Sowjanya Komatineni [ Upstream commit f4ce428c41fb22e3ed55496dded94df44cb920fa ] Fixes: Configure DMA burst size to be same as SPI TX/RX trigger levels to avoid mismatch. SPI FIFO trigger levels are calculated based on the transfer length. So this patch moves DMA slave configuration to ha

[PATCH AUTOSEL 4.19 281/671] drm/vmwgfx: Remove set but not used variable 'restart'

From: YueHaibing [ Upstream commit b2130cca9c8db5073b71d832da2a6c8311a8f3bb ] Fixes gcc '-Wunused-but-set-variable' warning: drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c: In function 'vmw_cmdbuf_work_func': drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c:514:7: warning: variable 'restart' set but not used [-

[PATCH AUTOSEL 4.19 356/671] backlight: lm3630a: Return 0 on success in update_status functions

From: Brian Masney [ Upstream commit d3f48ec0954c6aac736ab21c34a35d7554409112 ] lm3630a_bank_a_update_status() and lm3630a_bank_b_update_status() both return the brightness value if the brightness was successfully updated. Writing to these attributes via sysfs would cause a 'Bad address' error t

[PATCH AUTOSEL 4.19 438/671] backlight: pwm_bl: Fix heuristic to determine number of brightness levels

From: Matthias Kaehlcke [ Upstream commit 73fbfc499448455f1e1c77717040e09e25f1d976 ] With commit 88ba95bedb79 ("backlight: pwm_bl: Compute brightness of LED linearly to human eye") the number of set bits (aka hweight()) in the PWM period is used in the heuristic to determine the number of bright

[PATCH AUTOSEL 4.19 419/671] drm/msm/mdp5: Fix mdp5_cfg_init error return

From: Jeffrey Hugo [ Upstream commit fc19cbb785d7bbd1a1af26229b5240a3ab332744 ] If mdp5_cfg_init fails because of an unknown major version, a null pointer dereference occurs. This is because the caller of init expects error pointers, but init returns NULL on error. Fix this by returning the ex

[PATCH AUTOSEL 4.19 430/671] drm/msm/a3xx: remove TPL1 regs from snapshot

From: Rob Clark [ Upstream commit f47bee2ba447bebc304111c16ef1e1a73a9744dd ] These regs are write-only, and the hw throws a hissy-fit (ie. reboots) when we try to read them for GPU state snapshot, in response to a GPU hang. It is rather impolite when GPU recovery triggers an insta- reboot, so l

[PATCH AUTOSEL 4.19 465/671] drm/panel: make drm_panel.h self-contained

From: Jani Nikula [ Upstream commit bf3f5e98559360661a3d2af340d46522512c0b00 ] Fix build warning if drm_panel.h is built with CONFIG_OF=n or CONFIG_DRM_PANEL=n and included without the prerequisite err.h: ./include/drm/drm_panel.h: In function ‘of_drm_find_panel’: ./include/drm/drm_panel.h:203:

[PATCH AUTOSEL 4.19 496/671] drm: rcar-du: lvds: Fix bridge_to_rcar_lvds

From: Fabrizio Castro [ Upstream commit 0b936e6122738f4cf474d1f3ff636cba0edc8b94 ] Using name "bridge" for macro bridge_to_rcar_lvds argument doesn't work when the pointer name used by the caller is not "bridge". Rename the argument to "b" to allow for any pointer name. While at it, fix the con

[PATCH AUTOSEL 4.19 595/671] drm/msm/dsi: Implement reset correctly

From: Jeffrey Hugo [ Upstream commit 78e31c42261779a01bc73472d0f65f15378e9de3 ] On msm8998, vblank timeouts are observed because the DSI controller is not reset properly, which ends up stalling the MDP. This is because the reset logic is not correct per the hardware documentation. The document

[PATCH AUTOSEL 4.19 610/671] drm: panel-lvds: Potential Oops in probe error handling

From: Dan Carpenter [ Upstream commit fb2ee9bf084bcaeff1e5be100decc0eacb4af2d5 ] The "lvds->backlight" pointer could be NULL in situations where of_parse_phandle() returns NULL. This code is cleaner if we use the managed devm_of_find_backlight() so the clean up is automatic. Fixes: 7c9dff5bd64

[PATCH AUTOSEL 4.19 659/671] drm/radeon: fix bad DMA from INTERRUPT_CNTL2

From: Sam Bobroff [ Upstream commit 62d91dd2851e8ae2ca552f1b090a3575a4edf759 ] The INTERRUPT_CNTL2 register expects a valid DMA address, but is currently set with a GPU MC address. This can cause problems on systems that detect the resulting DMA read from an invalid address (found on a Power8 g

[PATCH AUTOSEL 4.14 002/371] drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()

From: Dan Carpenter [ Upstream commit 09c4b49457434fa74749ad6194ef28464d9f5df9 ] This doesn't affect runtime because in the current code "idx" is always valid. First, we read from "vgdev->capsets[idx].max_size" before checking whether "idx" is within bounds. And secondly the bounds check is of

[PATCH AUTOSEL 4.14 019/371] drm/dp_mst: Skip validating ports during destruction, just ref

From: Lyude Paul [ Upstream commit c54c7374ff44de5e609506aca7c0deae4703b6d1 ] Jerry Zuo pointed out a rather obscure hotplugging issue that it seems I accidentally introduced into DRM two years ago. Pretend we have a topology like this: |- DP-1: mst_primary |- DP-4: active display |- DP-

[PATCH AUTOSEL 4.14 001/371] drm/sti: do not remove the drm_bridge that was never added

From: Peter Rosin [ Upstream commit 66e31a72dc38543b2d9d1ce267dc78ba9beebcfd ] Removing the drm_bridge_remove call should avoid a NULL dereference during list processing in drm_bridge_remove if the error path is ever taken. The more natural approach would perhaps be to add a drm_bridge_add, but

  1   2   >