[PATCH 00/10] Fix documentation warnings at linux-next

This series fixes the documentation warnings found at next-20210114. Most of the changes here are trivial. While those patches could be merged via the docs tree during the next merge window, It sounds better to have those patches merged directly via each maintainer's tree, where the new warning

[PATCH 06/10] drm: amd: amdgpu_dm.h: fix a wrong kernel-doc markup

There's a missing colon, causing the markup to be ignored, solving those warnings: ../drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:340: warning: Incorrect use of kernel-doc format: * @active_vblank_irq_count ../drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:379: w

Re: [PATCH 2/2] drm/amdgpu/display: buffer INTERRUPT_LOW_IRQ_CONTEXT interrupt work

On 1/14/21 12:11 AM, Chen, Xiaogang wrote: On 1/12/2021 10:54 PM, Grodzovsky, Andrey wrote: On 1/4/21 1:01 AM, Xiaogang.Chen wrote: From: Xiaogang Chen amdgpu DM handles INTERRUPT_LOW_IRQ_CONTEXT interrupt(hpd, hpd_rx) by using work queue and uses single work_struct. If previous interrupt h

Re: [PATCH v6 1/4] drm/i915: Keep track of pwm-related backlight hooks separately

On Wed, 13 Jan 2021, Lyude Paul wrote: > Currently, every different type of backlight hook that i915 supports is > pretty straight forward - you have a backlight, probably through PWM > (but maybe DPCD), with a single set of platform-specific hooks that are > used for controlling it. > > HDR backl

[PATCH v4 3/7] dt-bindings: display: bridge: renesas, dw-hdmi: Convert binding to YAML

Convert the Renesas R-Car DWC HDMI TX text binding to YAML. Signed-off-by: Laurent Pinchart Reviewed-by: Rob Herring --- Changes since v3: - Use port instead of port-base Changes since v2: - Update MAINTAINERS Changes since v1: - Drop the part numbers in comments, only keep the SoC names -

[PATCH v4 2/7] dt-bindings: display: bridge: Add YAML schema for Synopsys DW-HDMI

Add a .yaml schema containing the common properties for the Synopsys DesignWare HDMI TX controller. This isn't a full device tree binding specification, but is meant to be referenced by platform-specific bindings for the IP core. Signed-off-by: Laurent Pinchart Reviewed-by: Philipp Zabel Reviewe

[PATCH v4 7/7] dt-bindings: display: bridge: Remove deprecated dw_hdmi.txt

dw_hdmi.txt has been replaced with synopsys,dw-hdmi.yaml, and all references to the old file have been converted. Remove it. Signed-off-by: Laurent Pinchart Acked-by: Rob Herring --- .../bindings/display/bridge/dw_hdmi.txt | 33 --- 1 file changed, 33 deletions(-) delete

[PATCH v4 5/7] dt-bindings: display: rockchip: dw-hdmi: Convert binding to YAML

Convert the Rockchip HDMI TX text binding to YAML. Signed-off-by: Laurent Pinchart --- Changes since v3: - Replace endpoint-base with endpoint Changes since v2: - Use Mark's @gmail.com e-mail address as the @rock-chips.com address bounces Changes since v1: - Drop pinctrl-0 and pinctrl-1 -

[PATCH v4 6/7] dt-bindings: display: sun8i-a83t-dw-hdmi: Reference dw-hdmi YAML schema

Replace the reference to the DWC HDMI text DT binding with a reference to the YAML equivalent. Signed-off-by: Laurent Pinchart Acked-by: Rob Herring Acked-by: Chen-Yu Tsai --- .../bindings/display/allwinner,sun8i-a83t-dw-hdmi.yaml| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-

[PATCH v4 4/7] dt-bindings: display: imx: hdmi: Convert binding to YAML

Convert the i.MX6 HDMI TX text binding to YAML. Signed-off-by: Laurent Pinchart Reviewed-by: Rob Herring --- Changes since v3: - Use port instead of port-base Changes since v1: - Only specify maxItems for clocks - Drop reg and interrupts as they're checked in the base schema - Rebase on top o

[PATCH v4 1/7] ARM: dts: imx6q(dl): Move 'port' nodes under 'ports' for HDMI encoder

In preparation for the conversion of the DWC HDMI TX device tree bindings to YAML, move the HDMI encoder's 'port' nodes under a 'ports' node. The 'ports' node is optional in the OF graph implementation, but YAML bindings require it. Signed-off-by: Laurent Pinchart --- arch/arm/boot/dts/imx6q.dts

[PATCH v4 0/7] dt-bindings: display: Convert DWC HDMI TX bindings to YAML

Hello, This patch series attempts a conversion of the DWC HDMI TX DT bindings to YAML. The DWC HDMI TX is an HDMI transmitter IP core from Synopsys, integrated in various SoCs with different glue layers. As such, some properties are defined in a common document, but sometimes need to be overridde

Re: [PATCH RESEND v2] drm/bridge/tc358775: Fixes bus formats read

Hi Vinay, Thank you for the patch. I'm afraid I've had close to no time for DRM bridge maintenance over the past few months, and I don't expect the situation to improve soon. I know how painful it can be to keep pinging without receiving any reply. I'm sorry about that, we have a shortage of mai

Re: [PATCH 1/2] drm/bridge/lontium-lt9611uxc: fix waiting for EDID to become available

Hi Dmitry, On Tue, Jan 05, 2021 at 08:20:39PM +0300, Dmitry Baryshkov wrote: > Gracious ping for these two patches I'm afraid I have very little time for DRM bridge maintenance at the moment :-S Judging by the lack of replies, it seems the other maintainers are also AWOL. We seem to have a shorta

Re: [PATCH 00/35] Add HMM-based SVM memory manager to KFD

Am 2021-01-11 um 11:29 a.m. schrieb Daniel Vetter: > On Fri, Jan 08, 2021 at 12:56:24PM -0500, Felix Kuehling wrote: >> Am 2021-01-08 um 11:53 a.m. schrieb Daniel Vetter: >>> On Fri, Jan 8, 2021 at 5:36 PM Felix Kuehling >>> wrote: Am 2021-01-08 um 11:06 a.m. schrieb Daniel Vetter: > On

Re: [PATCH 2/2] drm/amdgpu/display: buffer INTERRUPT_LOW_IRQ_CONTEXT interrupt work

On 1/12/2021 10:54 PM, Grodzovsky, Andrey wrote: On 1/4/21 1:01 AM, Xiaogang.Chen wrote: From: Xiaogang Chen amdgpu DM handles INTERRUPT_LOW_IRQ_CONTEXT interrupt(hpd, hpd_rx) by using work queue and uses single work_struct. If previous interrupt has not been handle

Re: [PATCH 00/35] Add HMM-based SVM memory manager to KFD

On Wed, Jan 13, 2021 at 09:31:11PM +0100, Daniel Vetter wrote: > On Wed, Jan 13, 2021 at 5:56 PM Jerome Glisse wrote: > > On Fri, Jan 08, 2021 at 03:40:07PM +0100, Daniel Vetter wrote: > > > On Thu, Jan 07, 2021 at 11:25:41AM -0500, Felix Kuehling wrote: > > > > Am 2021-01-07 um 4:23 a.m. schrieb

Re: [PATCH v3 2/2] drm/drm_vblank: set the dma-fence timestamp during send_vblank_event

On Wed, Jan 13, 2021 at 11:52 AM Veera Sundaram Sankaran wrote: > > The explicit out-fences in crtc are signaled as part of vblank event, > indicating all framebuffers present on the Atomic Commit request are > scanned out on the screen. Though the fence signal and the vblank event > notification

Re: [PATCH v5] drm/sun4i: tcon: fix inverted DCLK polarity

Hi Giulio, Thank you for the patch! Yet something to improve: [auto build test ERROR on sunxi/sunxi/for-next] [also build test ERROR on drm-exynos/exynos-drm-next drm-intel/for-linux-next tegra-drm/drm/tegra/for-next drm-tip/drm-tip v5.11-rc3 next-20210113] [cannot apply to mripard/sunxi/for

Re: [PATCH v3 2/2] drm/drm_vblank: set the dma-fence timestamp during send_vblank_event

On Wed, Jan 13, 2021 at 11:52 AM Veera Sundaram Sankaran wrote: > > The explicit out-fences in crtc are signaled as part of vblank event, > indicating all framebuffers present on the Atomic Commit request are > scanned out on the screen. Though the fence signal and the vblank event > notification

Re: [PATCH v3 1/2] dma-fence: allow signaling drivers to set fence timestamp

On Wed, Jan 13, 2021 at 11:52 AM Veera Sundaram Sankaran wrote: > Some drivers have hardware capability to get the precise HW timestamp > of certain events based on which the fences are triggered. The delta > between the event HW timestamp & current HW reference timestamp can > be used to calculat

linux-next: build failure after merge of the drm-misc tree

Hi all, After merging the drm-misc tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/gpu/drm/drm_cache.c: In function 'drm_need_swiotlb': drivers/gpu/drm/drm_cache.c:202:6: error: implicit declaration of function 'mem_encrypt_active' [-Werror=implicit-function-dec

Re: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12

On Tue, 12 Jan 2021 at 01:45, Christian König wrote: > > But what you have in your logs so far are only unrelated symptoms, the > root of the problem is that somebody is leaking memory. > > What you could do as well is to try to enable kmemleak I captured some memleaks. Do they contain any useful

Re: [PATCH 00/35] Add HMM-based SVM memory manager to KFD

Am 2021-01-13 um 11:47 a.m. schrieb Jerome Glisse: > On Wed, Jan 06, 2021 at 10:00:52PM -0500, Felix Kuehling wrote: >> This is the first version of our HMM based shared virtual memory manager >> for KFD. There are still a number of known issues that we're working through >> (see below). This will

[PATCH v6 4/4] drm/dp: Revert "drm/dp: Introduce EDID-based quirks"

This reverts commit 0883ce8146ed6074c76399f4e70dbed788582e12. Originally these quirks were added because of the issues with using the eDP backlight interfaces on certain laptop panels, which made it impossible to properly probe for DPCD backlight support without having a whitelist for panels that w

[PATCH v6 2/4] drm/i915/dp: Enable Intel's HDR backlight interface (only SDR for now)

So-recently a bunch of laptops on the market have started using DPCD backlight controls instead of the traditional DDI backlight controls. Originally we thought we had this handled by adding VESA backlight control support to i915, but the story ended up being a lot more complicated then that. Simp

[PATCH v6 3/4] drm/i915/dp: Allow forcing specific interfaces through enable_dpcd_backlight

Since we now support controlling panel backlights through DPCD using both the standard VESA interface, and Intel's proprietary HDR backlight interface, we should allow the user to be able to explicitly choose between one or the other in the event that we're wrong about panels reliably reporting sup

[PATCH v6 1/4] drm/i915: Keep track of pwm-related backlight hooks separately

Currently, every different type of backlight hook that i915 supports is pretty straight forward - you have a backlight, probably through PWM (but maybe DPCD), with a single set of platform-specific hooks that are used for controlling it. HDR backlights, in particular VESA and Intel's HDR backlight

[PATCH v6 0/4] drm/i915: Add support for Intel's eDP backlight controls

A while ago we ran into issues while trying to enable the eDP backlight control interface as defined by VESA, in order to make the DPCD backlight controls on newer laptop panels work. The issue ended up being much more complicated however, as we also apparently needed to add support for an Intel-sp

Re: [PATCH] drm/mediatek: mtk_dpi: Create connector for bridges

Hi, Hsin-Yi: Chun-Kuang Hu 於 2020年12月11日 週五 下午10:04寫道： > > Hi, Hsin-Yi: > > Hsin-Yi Wang 於 2020年12月3日 週四 下午4:24寫道： > > > > Similar to a9d9fea74be2 ("drm/mediatek: mtk_dsi: Create connector for > > bridges"): > > > > Use the drm_bridge_connector helper to create a connector for pipelines > > tha

Re: [PATCH] drm: rcar-du: Use drmm_encoder_alloc() to manage encoder

Hi Kieran, Thank you for the patch. On Wed, Jan 13, 2021 at 05:02:53PM +, Kieran Bingham wrote: > The encoder allocation was converted to a DRM managed resource at the > same time as the addition of a new helper drmm_encoder_alloc() which > simplifies the same process. > > Convert the custom

Re: [Intel-gfx] [PATCH] drm-buf: Add debug option

Quoting Daniel Vetter (2021-01-13 20:50:11) > On Wed, Jan 13, 2021 at 4:43 PM Chris Wilson wrote: > > > > Quoting Daniel Vetter (2021-01-13 14:06:04) > > > We have too many people abusing the struct page they can get at but > > > really shouldn't in importers. Aside from that the backing page migh

Re: [Intel-gfx] [PATCH] drm-buf: Add debug option

On Wed, Jan 13, 2021 at 4:43 PM Chris Wilson wrote: > > Quoting Daniel Vetter (2021-01-13 14:06:04) > > We have too many people abusing the struct page they can get at but > > really shouldn't in importers. Aside from that the backing page might > > simply not exist (for dynamic p2p mappings) look

Re: [Intel-gfx] [PATCH] drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST

On Wed, Jan 13, 2021 at 7:34 PM Sean Paul wrote: > > On Wed, Jan 13, 2021 at 9:31 AM Daniel Vetter wrote: > > > > On Wed, Jan 13, 2021 at 2:39 PM Sean Paul wrote: > > > > > > On Wed, Jan 13, 2021 at 5:34 AM Anshuman Gupta > > > wrote: > > > > > > > > On 2021-01-07 at 04:08:58 +0530, Sean Paul

[Bug 209713] amdgpu drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_link_encoder.c:483 dcn10_get_dig_frontend+0x9e/0xc0 [amdgpu] when resuming from S3 state

https://bugzilla.kernel.org/show_bug.cgi?id=209713 --- Comment #7 from Klaus Mueller (kmuel...@justmail.de) --- Yeah, it came again yesterday evening - after it has been disappeared for about one week ... . -- You may reply to this email to add a comment. You are receiving this mail because: Yo

Re: [PATCH 00/35] Add HMM-based SVM memory manager to KFD

On Wed, Jan 13, 2021 at 5:56 PM Jerome Glisse wrote: > On Fri, Jan 08, 2021 at 03:40:07PM +0100, Daniel Vetter wrote: > > On Thu, Jan 07, 2021 at 11:25:41AM -0500, Felix Kuehling wrote: > > > Am 2021-01-07 um 4:23 a.m. schrieb Daniel Vetter: > > > > On Wed, Jan 06, 2021 at 10:00:52PM -0500, Felix

Re: [PATCH 00/31] Rid W=1 warnings from Video

On Wed, 13 Jan 2021, Sam Ravnborg wrote: > Hi Lee, > > On Wed, Jan 13, 2021 at 02:49:38PM +, Lee Jones wrote: > > This set is part of a larger effort attempting to clean-up W=1 > > kernel builds, which are currently overwhelmingly riddled with > > niggly little warnings. > > > > This patch-s

Re: [PATCH 30/31] video: fbdev: s3c-fb: Remove unused variable 'var' from 's3c_fb_probe_win()'

On 1/13/21, 9:50 AM, Lee Jones wrote: > > Fixes the following W=1 kernel build warning(s): > > drivers/video/fbdev/s3c-fb.c: In function ‘s3c_fb_probe_win’: > drivers/video/fbdev/s3c-fb.c:1176:28: warning: variable ‘var’ set but not > used [-Wunused-but-set-variable] > > Cc: Jingoo Han Acked-

Re: [PATCH 24/31] video: fbdev: s3c-fb: Fix some kernel-doc misdemeanours

On 1/13/21, 9:50 AM, Lee Jones wrote: > > Fixes the following W=1 kernel build warning(s): > > drivers/video/fbdev/s3c-fb.c:104: warning: Function parameter or member > 'osd_stride' not described in 's3c_fb_variant' > drivers/video/fbdev/s3c-fb.c:174: warning: Function parameter or member > 'v

[Bug 209713] amdgpu drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_link_encoder.c:483 dcn10_get_dig_frontend+0x9e/0xc0 [amdgpu] when resuming from S3 state

https://bugzilla.kernel.org/show_bug.cgi?id=209713 Oliver Reeh (oli...@diereehs.de) changed: What|Removed |Added CC||oli...@diereehs.de ---

[PATCH V4] dt-bindings: gpu: Convert v3d to json-schema

This converts the v3d bindings to yaml format. Signed-off-by: Stefan Wahren --- Changes in V4: - define order for required reg-names - adapt example Changes in V3: - drop redundant maxItems in case we already have items defined - fix order of reg-names enum - tag required items in description -

[PATCH v3 4/8] drm/vmwgfx: Cleanup fifo mmio handling

Going forward the svga device might reuse mmio for general register accesses, in order to prepare for that we need to cleanup our naming and handling of fifo specific mmio reads and writes. As part of this work lets switch to managed mapping of the fifo mmio to make the error handling cleaner. Sig

[PATCH v3 7/8] drm/vmwgfx: Cleanup the cmd/fifo split

Lets try to cleanup the usage of the term FIFO which we used for both our MMIO based cmd queue processing and for general command processing which could have been using command buffers interface. We're going to rename the functions which are processing commands (and work either via MMIO or command

[PATCH v3 1/8] drm/vmwgfx: add Zack Rusin as maintainer

From: Roland Scheidegger Reviewed-by: Zack Rusin Signed-off-by: Roland Scheidegger --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 389abcf847c8..d082757ca672 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -5784,6 +5784,7 @@ F:drivers/g

[PATCH v3 6/8] drm/vmwgfx: Remove the throttling code

Throttling was used before fencing to implement early vsync support in the xorg state tracker a long time ago. The xorg state tracker has been removed years ago and no one else has ever used throttling. It's time to remove this code, it hasn't been used or tested in years. Signed-off-by: Zack Rusi

[PATCH v3 8/8] drm/vmwgfx: Fix display register usage for some older configs

We can't be setting the display_id register to an invalid value because that makes our device reset the fb which causes nasty flicker (due to destruction and creation of a new fb). Also we can't be using the BITS_PER_PIXEL register if the 8BIT_EMULATION is not supported. Signed-off-by: Zack Rusin

[PATCH v3 5/8] drm/vmwgfx: Cleanup pci resource allocation

Instead of doing it in multiple spots lets centralize the code to handle pci resources. This also cleans up the error handling a bit and will make it a lot easier to add additional svga versions to the driver. Signed-off-by: Zack Rusin Reviewed-by: Martin Krastev Reviewed-by: Roland Scheidegger

[PATCH v3 0/8] Misc cleanups and fixes for vmwgfx

This is the same set I've sent earlier in the week. CI found a warning and I wanted to give the systems a chance to compile/run the fixed version before submitting it. Roland Scheidegger (1): drm/vmwgfx: add Zack Rusin as maintainer Zack Rusin (7): drm/vmwgfx: Remove stealth mode drm/vmwgfx

[PATCH v3 3/8] drm/vmwgfx: Switch to a managed drm device

To cleanup some of the error handling and prepare for some other work lets switch to a managed drm device. It will let us get a better handle on some of the error paths. Signed-off-by: Zack Rusin Reviewed-by: Martin Krastev Reviewed-by: Roland Scheidegger --- drivers/gpu/drm/vmwgfx/vmwgfx_cmdb

[PATCH v3 2/8] drm/vmwgfx: Remove stealth mode

Before drm got helpers for removing conflicting pci framebuffer devices we implemented something known as "stealth" mode which allowed vmwgfx to run even if it couldn't reserve pci resources. We can just switch to regular drm helpers instead of keeping the stealth mode alive as it makes our code a

Re: [PATCH 00/31] Rid W=1 warnings from Video

Hi Lee, On Wed, Jan 13, 2021 at 02:49:38PM +, Lee Jones wrote: > This set is part of a larger effort attempting to clean-up W=1 > kernel builds, which are currently overwhelmingly riddled with > niggly little warnings. > > This patch-set clears all of the W=1 warnings currently residing > in

Re: [PATCH v5 15/21] drm/tegra: Add new UAPI to header

On 1/13/21 8:14 PM, Dmitry Osipenko wrote: 11.01.2021 16:00, Mikko Perttunen пишет: +struct drm_tegra_submit_buf { + /** +* @mapping_id: [in] +* +* Identifier of the mapping to use in the submission. +*/ + __u32 mapping_id; I'm now in process of tryi

Re: [PATCH 28/30] drm/nouveau/dispnv50/headc57d: Make local function 'headc57d_olut' static

Reviewed-by: Lyude Paul On Wed, 2021-01-13 at 08:07 +, Lee Jones wrote: > Fixes the following W=1 kernel build warning(s): > >  drivers/gpu/drm/nouveau/dispnv50/headc57d.c:173:1: warning: no previous > prototype for ‘headc57d_olut’ [-Wmissing-prototypes] > > Cc: Ben Skeggs > Cc: David Airl

Re: [Intel-gfx] [PATCH] drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST

On Wed, Jan 13, 2021 at 9:31 AM Daniel Vetter wrote: > > On Wed, Jan 13, 2021 at 2:39 PM Sean Paul wrote: > > > > On Wed, Jan 13, 2021 at 5:34 AM Anshuman Gupta > > wrote: > > > > > > On 2021-01-07 at 04:08:58 +0530, Sean Paul wrote: > > > > From: Sean Paul > > > > > > > > The HDCP 1.4 spec do

Re: [PATCH v5 04/21] gpu: host1x: Remove cancelled waiters immediately

On 1/13/21 6:29 PM, Dmitry Osipenko wrote: 13.01.2021 01:20, Mikko Perttunen пишет: On 1/13/21 12:07 AM, Dmitry Osipenko wrote: 11.01.2021 16:00, Mikko Perttunen пишет: -void host1x_intr_put_ref(struct host1x *host, unsigned int id, void *ref) +void host1x_intr_put_ref(struct host1x *host, uns

[PATCH] drm: rcar-du: Use drmm_encoder_alloc() to manage encoder

The encoder allocation was converted to a DRM managed resource at the same time as the addition of a new helper drmm_encoder_alloc() which simplifies the same process. Convert the custom drm managed resource allocation of the encoder with the helper to simplify the implementation, and prevent hitt

Re: [PATCH 00/35] Add HMM-based SVM memory manager to KFD

On Fri, Jan 08, 2021 at 03:40:07PM +0100, Daniel Vetter wrote: > On Thu, Jan 07, 2021 at 11:25:41AM -0500, Felix Kuehling wrote: > > Am 2021-01-07 um 4:23 a.m. schrieb Daniel Vetter: > > > On Wed, Jan 06, 2021 at 10:00:52PM -0500, Felix Kuehling wrote: > > >> This is the first version of our HMM ba

Re: [PATCH 00/35] Add HMM-based SVM memory manager to KFD

On Wed, Jan 06, 2021 at 10:00:52PM -0500, Felix Kuehling wrote: > This is the first version of our HMM based shared virtual memory manager > for KFD. There are still a number of known issues that we're working through > (see below). This will likely lead to some pretty significant changes in > MMU

Re: [PATCH 14/31] video: fbdev: aty: mach64_ct: Remove some set but unused variables

On Wed, 13 Jan 2021, Daniël Mantione wrote: > Hi, > > If I remember well, the removed lines have to do with the VGA/accelerator > mode of the chip. The current driver always runs the chip in accelerator > mode. Suppose you would want to support high resolution hardware text modes > with the drive

Re: [Intel-gfx] [PATCH] drm-buf: Add debug option

Quoting Daniel Vetter (2021-01-13 14:06:04) > We have too many people abusing the struct page they can get at but > really shouldn't in importers. Aside from that the backing page might > simply not exist (for dynamic p2p mappings) looking at it and using it > e.g. for mmap can also wreak the page

Re: [PATCH] drm/panfrost: Use delayed timer as default in devfreq profile

On 05/01/2021 16:41, Lukasz Luba wrote: Devfreq framework supports 2 modes for monitoring devices. Use delayed timer as default instead of deferrable timer in order to monitor the GPU status regardless of CPU idle. Signed-off-by: Lukasz Luba Looks reasonable to me. Reviewed-by: Steven Price

Re: [PATCH V3] dt-bindings: gpu: Convert v3d to json-schema

On Sat, Jan 09, 2021 at 11:50:32AM +0100, Stefan Wahren wrote: > This converts the v3d bindings to yaml format. > > Signed-off-by: Stefan Wahren > --- > > Changes in V3: > - drop redundant maxItems in case we already have items defined > - fix order of reg-names enum > - tag required items in de

Re: [PATCH v9, 01/11] dt-bindings: mediatek: add rdma-fifo-size description for mt8183 display

Rob Herring 於 2021年1月12日 週二 下午10:49寫道： > > On Thu, 07 Jan 2021 11:11:11 +0800, Yongqiang Niu wrote: > > rdma fifo size may be different even in same SOC, add this > > property to the corresponding rdma Applied to mediatek-drm-next [1], thanks. [1] https://git.kernel.org/pub/scm/linux/kernel/git

Re: [PATCH] drm/ttm: stop using GFP_TRANSHUGE_LIGHT

On Wed, Jan 13, 2021 at 3:46 PM Christian König wrote: > > Am 13.01.21 um 14:27 schrieb Daniel Vetter: > > On Wed, Jan 13, 2021 at 02:13:25PM +0100, Christian König wrote: > >> The only flag we really need is __GFP_NOMEMALLOC, highmem depends on > >> dma32 and moveable/compound should never be set

[PATCH 30/31] video: fbdev: s3c-fb: Remove unused variable 'var' from 's3c_fb_probe_win()'

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/s3c-fb.c: In function ‘s3c_fb_probe_win’: drivers/video/fbdev/s3c-fb.c:1176:28: warning: variable ‘var’ set but not used [-Wunused-but-set-variable] Cc: Jingoo Han Cc: Ben Dooks Cc: linux-fb...@vger.kernel.org Cc: dri-devel

[PATCH 29/31] video: fbdev: s1d13xxxfb: Function name must be on the 2nd line in kernel-doc

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/s1d13xxxfb.c:515: warning: Cannot understand * Cc: Kristoffer Ericson Cc: Thibaut VARENE Cc: Ben Dooks Cc: dri-devel@lists.freedesktop.org Cc: linux-fb...@vger.kernel.org Signed-off-by: Lee Jones --- drivers/video/fbdev/s

[PATCH 31/31] video: fbdev: mx3fb: Fix some kernel-doc issues

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/mx3fb.c:738: warning: Function parameter or member 'fbi' not described in 'mx3fb_set_fix' drivers/video/fbdev/mx3fb.c:738: warning: Excess function parameter 'info' description in 'mx3fb_set_fix' drivers/video/fbdev/mx3fb.c:

[PATCH 23/31] video: fbdev: s1d13xxxfb: Mark debug variables as __maybe_unused

Can't declare these under the same clause as their use, since debugging is enabled manually with an '#if {0,1}', so mark them as __maybe_unused instead to notify the compiler that this behaviour is expected. Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/s1d13xxxfb.c: In fu

[PATCH 22/31] video: fbdev: cirrusfb: Remove unused variable 'dummy' from 'WHDR()'

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/cirrusfb.c: In function ‘WHDR’: drivers/video/fbdev/cirrusfb.c:2466:16: warning: variable ‘dummy’ set but not used [-Wunused-but-set-variable] Cc: Jeff Garzik Cc: dri-devel@lists.freedesktop.org Cc: linux-fb...@vger.kernel.o

[PATCH 25/31] video: fbdev: mx3fb: Remove unused variable 'enabled'

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/mx3fb.c: In function ‘sdc_disable_channel’: drivers/video/fbdev/mx3fb.c:448:11: warning: variable ‘enabled’ set but not used [-Wunused-but-set-variable] Cc: Sam Ravnborg Cc: Arnd Bergmann Cc: Software Engineering Cc: dri-d

[PATCH 24/31] video: fbdev: s3c-fb: Fix some kernel-doc misdemeanours

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/s3c-fb.c:104: warning: Function parameter or member 'osd_stride' not described in 's3c_fb_variant' drivers/video/fbdev/s3c-fb.c:174: warning: Function parameter or member 'variant' not described in 's3c_fb_win' drivers/video

[PATCH 27/31] video: fbdev: sis: init: Remove unused variables 'cr_data2', 'VT' and 'HT'

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/sis/init.c: In function ‘SiS_Generic_ConvertCRData’: drivers/video/fbdev/sis/init.c:3543:37: warning: variable ‘cr_data2’ set but not used [-Wunused-but-set-variable] drivers/video/fbdev/sis/init.c:3542:39: warning: variable

[PATCH 28/31] video: fbdev: cirrusfb: Add description for 'info' and correct spelling of 'regbase'

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/cirrusfb.c:2815: warning: Function parameter or member 'info' not described in 'cirrusfb_dbg_print_regs' drivers/video/fbdev/cirrusfb.c:2815: warning: Function parameter or member 'regbase' not described in 'cirrusfb_dbg_prin

[PATCH 20/31] video: fbdev: core: fbcon: Mark 'pending' as __maybe_unused

'pending' is only used if FBCONDEBUG is defined. Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/core/fbcon.c: In function ‘fbcon_exit’: drivers/video/fbdev/core/fbcon.c:3295:7: warning: variable ‘pending’ set but not used [-Wunused-but-set-variable] Cc: car...@compsci.br

[PATCH 26/31] video: fbdev: riva: riva_hw: Remove set but unused variables 'vus_p' and 'vus_n'

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/riva/riva_hw.c: In function ‘nv10CalcArbitration’: drivers/video/fbdev/riva/riva_hw.c:845:23: warning: variable ‘vus_p’ set but not used [-Wunused-but-set-variable] drivers/video/fbdev/riva/riva_hw.c:845:16: warning: variable

[PATCH 21/31] video: fbdev: sstfb: Mark 3 debug variables as __maybe_unused

These are only used if SST_DEBUG_FUNC is set. Declare them under the same clause as their use. Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/sstfb.c: In function ‘sst_detect_ics’: drivers/video/fbdev/sstfb.c:934:26: warning: variable ‘n_clk1_b’ set but not used [-Wunuse

[PATCH 18/31] video: fbdev: neofb: Remove unused variable 'CursorMem'

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/neofb.c: In function ‘neo_init_hw’: drivers/video/fbdev/neofb.c:1846:6: warning: variable ‘CursorMem’ set but not used [-Wunused-but-set-variable] Cc: Evgeny Novikov Cc: Mike Rapoport Cc: Oliver Kropp Cc: "Thomas J. Moore"

[PATCH 19/31] video: fbdev: tdfxfb: Remove unused variable 'tmp'

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/tdfxfb.c: In function ‘att_outb’: drivers/video/fbdev/tdfxfb.c:209:16: warning: variable ‘tmp’ set but not used [-Wunused-but-set-variable] Cc: "Gustavo A. R. Silva" Cc: Hannu Mallat Cc: Frodo Looijaard Cc: Philip Edelbroc

[PATCH 17/31] video: fbdev: aty: radeon_monitor: Remove unused variable 'mon_types'

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/aty/radeon_monitor.c: In function ‘radeon_probe_screens’: drivers/video/fbdev/aty/radeon_monitor.c:491:8: warning: variable ‘mon_types’ set but not used [-Wunused-but-set-variable] Cc: Benjamin Herrenschmidt Cc: linux-fb...@

[PATCH 16/31] video: fbdev: pm2fb: Fix some kernel-doc formatting issues

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/pm2fb.c:1515: warning: Function parameter or member 'pdev' not described in 'pm2fb_probe' drivers/video/fbdev/pm2fb.c:1515: warning: Function parameter or member 'id' not described in 'pm2fb_probe' drivers/video/fbdev/pm2fb.

[PATCH 15/31] video: fbdev: via: lcd: Remove unused variable 'mode_crt_table'

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/via/lcd.c: In function ‘viafb_lcd_set_mode’: drivers/video/fbdev/via/lcd.c:540:29: warning: variable ‘mode_crt_table’ set but not used [-Wunused-but-set-variable] Cc: Florian Tobias Schandinat Cc: linux-fb...@vger.kernel.org

[PATCH 14/31] video: fbdev: aty: mach64_ct: Remove some set but unused variables

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/aty/mach64_ct.c: In function ‘aty_init_pll_ct’: drivers/video/fbdev/aty/mach64_ct.c:405:46: warning: variable ‘vga_dsp_on_off’ set but not used [-Wunused-but-set-variable] drivers/video/fbdev/aty/mach64_ct.c:405:30: warning:

[PATCH 12/31] video: fbdev: sis: oem310: Remove some unused static const tables

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/sis/oem310.h:213:28: warning: ‘SiS_TVDelay661_301B’ defined but not used [-Wunused-const-variable=] drivers/video/fbdev/sis/oem310.h:203:28: warning: ‘SiS_TVDelay661_301’ defined but not used [-Wunused-const-variable=] Cc: T

[PATCH 13/31] video: fbdev: nvidia: nv_setup: Remove a couple of unused 'tmp' variables

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/nvidia/nv_setup.c: In function ‘NVWriteAttr’: drivers/video/fbdev/nvidia/nv_setup.c:92:14: warning: variable ‘tmp’ set but not used [-Wunused-but-set-variable] drivers/video/fbdev/nvidia/nv_setup.c: In function ‘NVReadAttr’:

[PATCH 11/31] video: fbdev: sis: init: Remove four unused variables

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/sis/init.c: In function ‘SiS_SetCRT1ModeRegs’: drivers/video/fbdev/sis/init.c:2651:49: warning: variable ‘resindex’ set but not used [-Wunused-but-set-variable] drivers/video/fbdev/sis/init.c: In function ‘SiS_Generic_Convert

[PATCH 10/31] video: fbdev: riva: riva_hw: Remove a bunch of unused variables

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/riva/riva_hw.c: In function ‘nv10CalcArbitration’: drivers/video/fbdev/riva/riva_hw.c:849:9: warning: variable ‘pclks_2_top_fifo’ set but not used [-Wunused-but-set-variable] drivers/video/fbdev/riva/riva_hw.c:848:43: warning

[PATCH 08/31] video: fbdev: sis: sis_main: Remove unused variable 'reg'

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/sis/sis_main.c: In function ‘sisfb_post_xgi_ddr2’: drivers/video/fbdev/sis/sis_main.c:5032:5: warning: variable ‘reg’ set but not used [-Wunused-but-set-variable] Cc: Thomas Winischhofer Cc: Gerd Knorr Cc: dri-devel@lists.f

[PATCH 09/31] video: fbdev: sis: Remove superfluous include of 'init.h'

Neither 'sis.h' nor any of its consumers uses these tables. Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/sis/init.h:144:28: warning: ‘SiS_VGA_DAC’ defined but not used [-Wunused-const-variable=] drivers/video/fbdev/sis/init.h:132:28: warning: ‘SiS_EGA_DAC’ defined but n

[PATCH 07/31] video: fbdev: riva: fbdev: Fix some kernel-doc misdemeanours

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/riva/fbdev.c:485: warning: Function parameter or member 'data8' not described in 'rivafb_load_cursor_image' drivers/video/fbdev/riva/fbdev.c:485: warning: Excess function parameter 'data' description in 'rivafb_load_cursor_im

[PATCH 05/31] video: of_videomode: Fix formatting in kernel-doc header

Fixes the following W=1 kernel build warning(s): drivers/video/of_videomode.c:32: warning: Function parameter or member 'np' not described in 'of_get_videomode' drivers/video/of_videomode.c:32: warning: Function parameter or member 'vm' not described in 'of_get_videomode' drivers/video/of_vid

[PATCH 03/31] video: fbdev: aty: atyfb_base: Remove superfluous code surrounding 'dac_type'

If used, 'dac_type' is overwritten in the '#ifdef CONFIG_ATARI' clause. It's also not used after the last assignment, so we'll rid that too. Cc: Bartlomiej Zolnierkiewicz Cc: Vaibhav Gupta Cc: Alex Kern Cc: "Eddie C. Dost" Cc: Anthony Tong Cc: dri-devel@lists.freedesktop.org Cc: linux-fb...@

[PATCH 06/31] video: fbdev: core: fb_notify: Demote non-conformant kernel-doc header

Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/core/fb_notify.c:44: warning: Function parameter or member 'val' not described in 'fb_notifier_call_chain' drivers/video/fbdev/core/fb_notify.c:44: warning: Function parameter or member 'v' not described in 'fb_notifier_call_

[PATCH 04/31] video: fbdev: aty: atyfb_base: Mark 'dac_type' as __maybe_unused

'dac_type' is only used in the '#ifdef CONFIG_ATARI' clause. Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/aty/atyfb_base.c: In function ‘aty_init’: drivers/video/fbdev/aty/atyfb_base.c:2363:6: warning: variable ‘dac_type’ set but not used [-Wunused-but-set-variable] Cc

[PATCH 01/31] video: fbdev: core: fbmon: Add missing description for 'specs'

Also fix a formatting issue Fixes the following W=1 kernel build warning(s): drivers/video/fbdev/core/fbmon.c:617: warning: Function parameter or member 'specs' not described in 'fb_create_modedb' drivers/video/fbdev/core/fbmon.c:1103: warning: bad line: Cc: James Simmons Cc: Egbert Eich Cc

[PATCH 02/31] video: of_display_timing: Provide missing description for 'dt'

Fixes the following W=1 kernel build warning(s): drivers/video/of_display_timing.c:58: warning: Function parameter or member 'dt' not described in 'of_parse_display_timing' Cc: Steffen Trumtrar Cc: Sascha Hauer Cc: dri-devel@lists.freedesktop.org Cc: linux-fb...@vger.kernel.org Signed-off-by:

[PATCH 00/31] Rid W=1 warnings from Video

This set is part of a larger effort attempting to clean-up W=1 kernel builds, which are currently overwhelmingly riddled with niggly little warnings. This patch-set clears all of the W=1 warnings currently residing in drivers/video. Lee Jones (31): video: fbdev: core: fbmon: Add missing descrip

Re: [PATCH] drm/ttm: stop using GFP_TRANSHUGE_LIGHT

Am 13.01.21 um 14:27 schrieb Daniel Vetter: On Wed, Jan 13, 2021 at 02:13:25PM +0100, Christian König wrote: The only flag we really need is __GFP_NOMEMALLOC, highmem depends on dma32 and moveable/compound should never be set in the first place. Signed-off-by: Christian König Needs Fixes: lin

Re: [PATCH v3 01/12] drm: Add dummy page per device or GEM object

On 1/13/21 4:14 AM, Christian König wrote: Am 12.01.21 um 16:59 schrieb Andrey Grodzovsky: On 1/12/21 7:32 AM, Christian König wrote: Am 12.01.21 um 10:10 schrieb Daniel Vetter: On Mon, Jan 11, 2021 at 03:45:10PM -0500, Andrey Grodzovsky wrote: On 1/11/21 11:15 AM, Daniel Vetter wrote: On

Re: [Intel-gfx] [PATCH] drm/i915/hdcp: Disable the QSES check for HDCP 1.4 over MST

On Wed, Jan 13, 2021 at 2:39 PM Sean Paul wrote: > > On Wed, Jan 13, 2021 at 5:34 AM Anshuman Gupta > wrote: > > > > On 2021-01-07 at 04:08:58 +0530, Sean Paul wrote: > > > From: Sean Paul > > > > > > The HDCP 1.4 spec does not require the QUERY_STREAM_ENCRYPTION_STATUS > > IMHO DP 1.4 vesa spe

Re: [PATCH -next] phy: mediatek: Mark mtk_mipi_tx_driver with static keyword

On 12-01-21, 09:38, Zou Wei wrote: > Fix the following sparse warning: > > drivers/phy/mediatek/phy-mtk-mipi-dsi.c:237:24: warning: symbol > 'mtk_mipi_tx_driver' was not declared. Should it be static? Applied, thanks -- ~Vinod ___ dri-devel mailing l

  1   2   >