Re: [RFC v2 01/11] OPP: Don't overwrite rounded clk rate

2019-06-13 Thread Rajendra Nayak
Now, the request to change the frequency starts from cpufreq governors, like schedutil when they calls: __cpufreq_driver_target(policy, 599 MHz, CPUFREQ_RELATION_L); CPUFREQ_RELATION_L means: lowest frequency at or above target. And so I would expect the frequency to get set to 600MHz (if we

[Bug 109955] amdgpu [RX Vega 64] system freeze while gaming

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=109955 Jiri Slaby changed: What|Removed |Added QA Contact|dri-devel@lists.freedesktop | |.org

Re: [PATCH v2 2/2] drm/komeda: Adds komeda_kms_drop_master

2019-06-13 Thread james qian wang (Arm Technology China)
On Thu, Jun 13, 2019 at 04:30:08PM +0200, Daniel Vetter wrote: > On Thu, Jun 13, 2019 at 02:24:37PM +0100, Liviu Dudau wrote: > > On Thu, Jun 13, 2019 at 11:08:14AM +0200, Daniel Vetter wrote: > > > On Thu, Jun 13, 2019 at 09:28:13AM +0100, Liviu Dudau wrote: > > > > On Thu, Jun 13, 2019 at

Re: [RFC v2 01/11] OPP: Don't overwrite rounded clk rate

2019-06-13 Thread Viresh Kumar
On 13-06-19, 15:24, Viresh Kumar wrote: > I am confused as hell on what we should be doing and what we are doing > right now. And if we should do better. > > Let me explain with an example. > > - The clock provider supports following frequencies: 500, 600, 700, > 800, 900, 1000 MHz. > > - The

Re: [PATCH v17 03/15] arm64: Introduce prctl() options to control the tagged user addresses ABI

2019-06-13 Thread Kees Cook
On Thu, Jun 13, 2019 at 04:26:32PM +0100, Catalin Marinas wrote: > On Thu, Jun 13, 2019 at 12:02:35PM +0100, Dave P Martin wrote: > > On Wed, Jun 12, 2019 at 01:43:20PM +0200, Andrey Konovalov wrote: > > > +static int zero; > > > +static int one = 1; > > > > !!! > > > > And these can't even be

Re: [PATCH v3, 20/27] drm/mediatek: add background color input select function for ovl/ovl_2l

2019-06-13 Thread CK Hu
Hi, Yongqiang: On Wed, 2019-06-05 at 19:42 +0800, yongqiang@mediatek.com wrote: > From: Yongqiang Niu > > This patch add background color input select function for ovl/ovl_2l > > ovl include 4 DRAM layer and 1 background color layer > ovl_2l include 4 DRAM layer and 1 background color

Re: [PATCH v3, 18/27] drm/medaitek: add layer_nr for ovl private data

2019-06-13 Thread CK Hu
Hi, Yongqiang: On Wed, 2019-06-05 at 19:42 +0800, yongqiang@mediatek.com wrote: > From: Yongqiang Niu > > This patch add layer_nr for ovl private data > ovl_2l almost same with with ovl hardware, except the > layer number for ovl_2l is 2 and ovl is 4. > this patch is a preparation for

Re: [PATCH v3, 17/27] drm/mediatek: add gmc_bits for ovl private data

2019-06-13 Thread CK Hu
Hi, Yongqiang: On Wed, 2019-06-05 at 19:42 +0800, yongqiang@mediatek.com wrote: > From: Yongqiang Niu > > This patch add gmc_bits for ovl private data > GMC register was set RDMA ultra and pre-ultra threshold. > 10bit GMC register define is different with other SOC, gmc_thrshd_l not > used.

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

2019-06-13 Thread Stephen Rothwell
Hi all, After merging the drm-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:4031:18: error: initialization of 'int (*)(struct drm_connector *, struct drm_atomic_state *)' from incompatible pointer type

Re: [PATCH v3, 16/27] drm/mediatek: add component DITHER

2019-06-13 Thread CK Hu
Hi, Yongqiang: On Wed, 2019-06-05 at 19:42 +0800, yongqiang@mediatek.com wrote: > From: Yongqiang Niu > > This patch add component DITHER Reviewed-by: CK Hu > > Signed-off-by: Yongqiang Niu > --- > drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 32 > + >

Re: [PATCH v3, 15/27] drm/mediatek: add component OVL_2L1

2019-06-13 Thread CK Hu
Hi, Yongqiang: On Wed, 2019-06-05 at 19:42 +0800, yongqiang@mediatek.com wrote: > From: Yongqiang Niu > > This patch add component OVL_2L1 Reviewed-by: CK Hu > > Signed-off-by: Yongqiang Niu > --- > drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 1 + >

Re: [PATCH v3, 14/27] drm/mediatek: add commponent OVL_2L0

2019-06-13 Thread CK Hu
Hi, Yongqiang: On Wed, 2019-06-05 at 19:42 +0800, yongqiang@mediatek.com wrote: > From: Yongqiang Niu > > This patch add commponent OVL_2L0 Reviewed-by: CK Hu > > Signed-off-by: Yongqiang Niu > --- > drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 2 ++ >

Re: [PATCH 5/9] ARM: dts: sun8i: r40: Add TCON TOP LCD clocking

2019-06-13 Thread Chen-Yu Tsai
On Fri, Jun 14, 2019 at 2:54 AM Jagan Teki wrote: > > According to Fig 7-2. TCON Top Block Diagram in User manual. > > TCON TOP can have an hierarchy for TCON_LCD0, LCD1 like > TCON_TV0, TV1 so, the tcon top would handle the clocks of > TCON_LCD0, LCD1 similar like TV0, TV1. That is not

Re: [PATCH v3, 13/27] drm/mediatek: add ddp component CCORR

2019-06-13 Thread CK Hu
Hi, Yongqiang: On Wed, 2019-06-05 at 19:42 +0800, yongqiang@mediatek.com wrote: > From: Yongqiang Niu > > This patch add ddp component CCORR This patch is identical to v2, and I've give a 'Reviewed-by' for v2 [1], so you should keep this 'Reviewed-by' tag in this patch, so I still give you

Re: [linux-sunxi] [PATCH 2/9] drm/sun4i: tcon: Add TCON LCD support for R40

2019-06-13 Thread Chen-Yu Tsai
On Fri, Jun 14, 2019 at 11:19 AM Chen-Yu Tsai wrote: > > On Fri, Jun 14, 2019 at 2:53 AM Jagan Teki wrote: > > > > TCON LCD0, LCD1 in allwinner R40, are used for managing > > LCD interfaces like RGB, LVDS and DSI. > > > > Like TCON TV0, TV1 these LCD0, LCD1 are also managed via > > tcon top. > >

Re: [PATCH v3, 11/27] drm/mediatek: add mmsys private data for ddp path config

2019-06-13 Thread CK Hu
Hi, Yongqiang: On Wed, 2019-06-05 at 19:42 +0800, yongqiang@mediatek.com wrote: > From: Yongqiang Niu > > This patch add mmsys private data for ddp path config > all these register offset and value will be different in future SOC > add these define into mmsys private data > u32

Re: [PATCH 4/9] drm/sun4i: tcon_top: Use clock name index macros

2019-06-13 Thread Chen-Yu Tsai
On Fri, Jun 14, 2019 at 2:54 AM Jagan Teki wrote: > > TCON TOP mux blocks in R40 are registering clock using > tcon top clock index numbers. > > Right now the code is using, real numbers start with 0, but > we have proper macros that defined these name index numbers. > > Use the existing macros,

Re: [PATCH 3/9] ARM: dts: sun8i: r40: Use tcon top clock index macros

2019-06-13 Thread Chen-Yu Tsai
On Fri, Jun 14, 2019 at 2:54 AM Jagan Teki wrote: > > tcon_tv0, tcon_tv1 nodes have a clock names of tcon-ch0, > tcon-ch1 which are referring tcon_top clocks via index > numbers like 0, 1 with CLK_TCON_TV0 and CLK_TCON_TV1 > respectively. > > Use the macro in place of index numbers, for more code

Re: [linux-sunxi] [PATCH 2/9] drm/sun4i: tcon: Add TCON LCD support for R40

2019-06-13 Thread Chen-Yu Tsai
On Fri, Jun 14, 2019 at 2:53 AM Jagan Teki wrote: > > TCON LCD0, LCD1 in allwinner R40, are used for managing > LCD interfaces like RGB, LVDS and DSI. > > Like TCON TV0, TV1 these LCD0, LCD1 are also managed via > tcon top. > > Add support for it, in tcon driver. > > Signed-off-by: Jagan Teki

Re: [linux-sunxi] [PATCH 1/9] dt-bindings: display: Add TCON LCD compatible for R40

2019-06-13 Thread Chen-Yu Tsai
On Fri, Jun 14, 2019 at 2:53 AM Jagan Teki wrote: > > Like TCON TV0, TV1 allwinner R40 has TCON LCD0, LCD1 which > are managed via TCON TOP. > > Add tcon lcd compatible R40, the same compatible can handle > TCON LCD0, LCD1. > > Cc: Rob Herring > Cc: Mark Rutland > Signed-off-by: Jagan Teki

Re: [PATCH v3, 10/27] drm/mediatek: split DISP_REG_CONFIG_DSI_SEL setting into another use case

2019-06-13 Thread CK Hu
+Bibby: Hi, Yongqiang: On Wed, 2019-06-05 at 19:42 +0800, yongqiang@mediatek.com wrote: > From: Yongqiang Niu > > Here is two modifition in this patch: > 1.bls->dpi0 and rdma1->dsi are differen usecase, > Split DISP_REG_CONFIG_DSI_SEL setting into anther usecase > 2.remove

Re: [GIT,PULL] mediatek drm fixes for 5.2

2019-06-13 Thread CK Hu
On Thu, 2019-06-13 at 10:27 +0200, Daniel Vetter wrote: > On Thu, Jun 13, 2019 at 02:31:18PM +0800, CK Hu wrote: > > Hi, Daniel: > > > > On Wed, 2019-06-12 at 18:25 +0200, Daniel Vetter wrote: > > > On Wed, Jun 12, 2019 at 03:51:08PM +0800, CK Hu wrote: > > > > Hi Dave, Daniel: > > > > > > > >

[PATCH] gpu: ipu-v3: image-convert: Enable double write reduction

2019-06-13 Thread Steve Longerbeam
For the write channels with 4:2:0 subsampled YUV formats, avoid chroma overdraw by only writing chroma for even lines (skip odd chroma rows). This reduces necessary write memory bandwidth by at least 25% (more with rotation enabled). Signed-off-by: Steve Longerbeam ---

Re: [PATCH 18/22] mm: mark DEVICE_PUBLIC as broken

2019-06-13 Thread Ira Weiny
On Thu, Jun 13, 2019 at 07:58:29PM +, Jason Gunthorpe wrote: > On Thu, Jun 13, 2019 at 12:53:02PM -0700, Ralph Campbell wrote: > > > > On 6/13/19 12:44 PM, Jason Gunthorpe wrote: > > > On Thu, Jun 13, 2019 at 11:43:21AM +0200, Christoph Hellwig wrote: > > > > The code hasn't been used since

Re: [PATCH 4/5] drm/connector: Split out orientation quirk detection

2019-06-13 Thread dbasehore .
On Wed, Jun 12, 2019 at 5:33 AM Hans de Goede wrote: > > Hi, > > On 12-06-19 02:16, dbasehore . wrote: > > On Tue, Jun 11, 2019 at 1:54 AM Hans de Goede wrote: > >> > >> Hi, > >> > >> On 11-06-19 10:08, Jani Nikula wrote: > >>> On Mon, 10 Jun 2019, Derek Basehore wrote: > This removes the

Re: [PATCH 1/5] drm/panel: Add helper for reading DT rotation

2019-06-13 Thread dbasehore .
On Wed, Jun 12, 2019 at 2:20 PM Sam Ravnborg wrote: > > Hi Derek. > > On Mon, Jun 10, 2019 at 09:03:46PM -0700, Derek Basehore wrote: > > This adds a helper function for reading the rotation (panel > > orientation) from the device tree. > > > > Signed-off-by: Derek Basehore > > --- > >

Re: dev_pagemap related cleanups

2019-06-13 Thread Ira Weiny
On Thu, Jun 13, 2019 at 08:40:46PM +, Jason Gunthorpe wrote: > On Thu, Jun 13, 2019 at 11:27:39AM -0700, Dan Williams wrote: > > On Thu, Jun 13, 2019 at 2:43 AM Christoph Hellwig wrote: > > > > > > Hi Dan, Jérôme and Jason, > > > > > > below is a series that cleans up the dev_pagemap

[Bug 110907] Xorg 1.19.6 segfaults at address 0x6d with mesa 19.1

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110907 hvba...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[PATCH] drm/amdgpu: Fix connector atomic_check compilation fail

2019-06-13 Thread Sean Paul
From: Sean Paul I missed amdgpu in my connnector_helper_funcs->atomic_check conversion, which is understandably causing compilation failures. Fixes: 6f3b62781bbd ("drm: Convert connector_helper_funcs->atomic_check to accept drm_atomic_state") Cc: Daniel Vetter Cc: Ville Syrjälä Cc: Jani

Re: [PATCH 13/22] device-dax: use the dev_pagemap internal refcount

2019-06-13 Thread Ira Weiny
On Thu, Jun 13, 2019 at 11:43:16AM +0200, Christoph Hellwig wrote: > The functionality is identical to the one currently open coded in > device-dax. > > Signed-off-by: Christoph Hellwig > --- > drivers/dax/dax-private.h | 4 --- > drivers/dax/device.c | 52

[Bug 110795] Unable to install on latest Ubuntu (19.04)

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110795 --- Comment #20 from Rolf --- @Andre, thank you for the clarification. My bug may have been correctly filed, but it seems I vented my frustration with AMD in the wrong direction. I did think, and I think most people following that link would as

[Bug 110897] HyperZ is broken for r300 (bad z for some micro and macrotiles?)

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110897 Richard Thier changed: What|Removed |Added Severity|minor |normal Priority|lowest

[Bug 102646] Screen flickering under amdgpu-experimental [buggy auto power profile]

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=102646 Seth Lorecanth changed: What|Removed |Added CC||issethloreca...@gmail.com --- Comment

[Bug 110897] HyperZ is broken for r300 (bad z for some micro and macrotiles?)

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110897 --- Comment #25 from Richard Thier --- Pfff it is bad once again now and I have no idea why... maybe a real heisenbug because of some state :-( Also turning off the machine or rebooting does not seem to help despite I went back to the "-O2"

[Bug 110856] Freesync causes in-game blackscreens when game has low fps.

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110856 --- Comment #10 from Ropid --- Those Xorg config options you tried to use do not exist on the xf86-video-amdgpu driver (I mean "CustomEDID" etc.). Those EDID options you used are unique Nvidia driver config options and do not exist in any other

[PATCH v5 1/3] dma-buf: give each buffer a full-fledged inode

2019-06-13 Thread Chenbo Feng
From: Greg Hackmann By traversing /proc/*/fd and /proc/*/map_files, processes with CAP_ADMIN can get a lot of fine-grained data about how shmem buffers are shared among processes. stat(2) on each entry gives the caller a unique ID (st_ino), the buffer's size (st_size), and even the number of

[PATCH v5 0/3] Improve the dma-buf tracking

2019-06-13 Thread Chenbo Feng
Currently, all dma-bufs share the same anonymous inode. While we can count how many dma-buf fds or mappings a process has, we can't get the size of the backing buffers or tell if two entries point to the same dma-buf. And in debugfs, we can get a per-buffer breakdown of size and reference count,

[PATCH v5 3/3] dma-buf: add show_fdinfo handler

2019-06-13 Thread Chenbo Feng
From: Greg Hackmann The show_fdinfo handler exports the same information available through debugfs on a per-buffer basis. Signed-off-by: Greg Hackmann Signed-off-by: Chenbo Feng --- drivers/dma-buf/dma-buf.c | 15 +++ 1 file changed, 15 insertions(+) diff --git

[PATCH v5 2/3] dma-buf: add DMA_BUF_SET_NAME ioctls

2019-06-13 Thread Chenbo Feng
From: Greg Hackmann This patch adds complimentary DMA_BUF_SET_NAME ioctls, which lets userspace processes attach a free-form name to each buffer. This information can be extremely helpful for tracking and accounting shared buffers. For example, on Android, we know what each buffer will be

Re: [PATCH 2/4] backlight: Expose brightness curve type through sysfs

2019-06-13 Thread Matthias Kaehlcke
I noticed a few minor things when glancing over the patch on patchwork On Thu, Jun 13, 2019 at 12:43:24PM -0700, Matthias Kaehlcke wrote: > Backlight brightness curves can have different shapes. The two main > types are linear and non-linear curves. The human eye doesn't > perceive linearly

Re: [PATCH v4 2/3] dma-buf: add DMA_BUF_SET_NAME ioctls

2019-06-13 Thread Chenbo Feng
On Thu, Jun 13, 2019 at 1:15 PM Suren Baghdasaryan wrote: > > On Wed, Jun 12, 2019 at 2:48 PM 'Chenbo Feng' via kernel-team > wrote: > > > > From: Greg Hackmann > > > > This patch adds complimentary DMA_BUF_SET_NAME ioctls, which lets > > userspace processes attach a free-form name to each

[Bug 109955] amdgpu [RX Vega 64] system freeze while gaming

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=109955 --- Comment #32 from Sam --- Created attachment 144535 --> https://bugs.freedesktop.org/attachment.cgi?id=144535=edit dmesg from the freeze which didn't completely bork everything. It starts on line 1181 -- You are receiving this mail

[Bug 109955] amdgpu [RX Vega 64] system freeze while gaming

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=109955 --- Comment #31 from Sam --- I have attached another trace I managed to get today at 22:24 while playing Pillars Of Eternity (OpenGL) It didn't freeze the whole as usual, just the whole Plasma and X sessions, so the other TTYs were

[Bug 110856] Freesync causes in-game blackscreens when game has low fps.

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110856 --- Comment #9 from Arek Tumas --- Created attachment 144534 --> https://bugs.freedesktop.org/attachment.cgi?id=144534=edit /etc/mkinitcpio.conf I also changed this file to point to my custom edid.bin file -- You are receiving this mail

Re: [PATCH 2/5] dt-bindings: display/panel: Expand rotation documentation

2019-06-13 Thread dbasehore .
On Thu, Jun 13, 2019 at 5:52 AM Rob Herring wrote: > > On Tue, Jun 11, 2019 at 4:02 PM dbasehore . wrote: > > > > On Tue, Jun 11, 2019 at 8:25 AM Rob Herring wrote: > > > > > > On Mon, Jun 10, 2019 at 10:03 PM Derek Basehore > > > wrote: > > > > > > > > This adds to the rotation documentation

Re: [PATCH v2 00/13] tda998x updates

2019-06-13 Thread Russell King - ARM Linux admin
On Thu, Jun 13, 2019 at 03:51:06PM -0400, Sven Van Asbroeck wrote: > On Thu, Jun 13, 2019 at 10:29 AM Russell King - ARM Linux admin > wrote: > > > > This series represents development work collected over the last six > > months to improve the TDA998x driver, particularly for the audio > > side.

Re: Cleanup of -Wunused-const-variable in drivers/gpu/drm/msm/disp/dpu1/dpu_formats.c

2019-06-13 Thread Rob Clark
so, for dpu_format_map_tile, I'd like to define a fourcc modifier for tiled formats (we currently have a workaround in userspace w/ a private modifier in the gallium driver).. I think the problem is defining the layout of the tiled format(s) (there are at least two per generation and I can't

[Bug 110856] Freesync causes in-game blackscreens when game has low fps.

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110856 --- Comment #8 from Arek Tumas --- I've tried it but it did not work. I made a custom edid.bin file through CRU on windows, but in rocket League when I click on menus the screen resets/flashes black (as in the monitors hardware does). Also

Re: Cleanup of -Wunused-const-variable in drivers/gpu/drm/msm/disp/dpu1/dpu_formats.c

2019-06-13 Thread Sean Paul
On Thu, Jun 13, 2019 at 4:13 PM Nathan Huckleberry wrote: > > Hey all, > > I'm looking into cleaning up ignored warnings in the kernel so we can > remove compiler flags to ignore warnings. > > There are several unused variables in dpu_formats.c > ('dpu_format_map_tile', 'dpu_format_map_p010', >

Re: dev_pagemap related cleanups

2019-06-13 Thread Andrew Morton
On Thu, 13 Jun 2019 14:24:20 -0600 Logan Gunthorpe wrote: > > > On 2019-06-13 2:21 p.m., Dan Williams wrote: > > On Thu, Jun 13, 2019 at 1:18 PM Logan Gunthorpe wrote: > >> > >> > >> > >> On 2019-06-13 12:27 p.m., Dan Williams wrote: > >>> On Thu, Jun 13, 2019 at 2:43 AM Christoph Hellwig

Re: [PULL] drm-misc-fixes

2019-06-13 Thread Daniel Vetter
On Thu, Jun 13, 2019 at 10:39:46AM -0400, Sean Paul wrote: > > Hi Da.*, > A bit more meat on this PR, which should probably be expected given how light > we > have been on the last 4. > > > drm-misc-fixes-2019-06-13: > meson: A few G12A fixes across the driver (Neil) > quirks: A couple quirks

Re: [RFC][PATCH 0/2] drm: PATH prop for all connectors?

2019-06-13 Thread Daniel Vetter
On Thu, Jun 13, 2019 at 09:43:33PM +0300, Ville Syrjala wrote: > From: Ville Syrjälä > > Here's a possible apporoach for providing userspace with > some stable connector identifiers. Combine with the bus > name of the GPU and you should have some kind of real > physical path description.

Re: [PATCH v2 01/13] drm/i2c: tda998x: introduce tda998x_audio_settings

2019-06-13 Thread Russell King - ARM Linux admin
On Thu, Jun 13, 2019 at 02:48:47PM -0400, Sven Van Asbroeck wrote: > Nit: checkpatch.pl appears unhappy with this patch: > > WARNING: line over 80 characters > #222: FILE: drivers/gpu/drm/i2c/tda998x_drv.c:1011: > + audio.params.config = priv->audio_port[i].config; > > WARNING: line over 80

Re: dev_pagemap related cleanups

2019-06-13 Thread Dan Williams
On Thu, Jun 13, 2019 at 1:18 PM Logan Gunthorpe wrote: > > > > On 2019-06-13 12:27 p.m., Dan Williams wrote: > > On Thu, Jun 13, 2019 at 2:43 AM Christoph Hellwig wrote: > >> > >> Hi Dan, Jérôme and Jason, > >> > >> below is a series that cleans up the dev_pagemap interface so that > >> it is

Re: [PATCH] drm/omap: Migrate minimum FCK/PCK ratio from Kconfig to dts

2019-06-13 Thread Rob Herring
On Fri, May 10, 2019 at 02:42:29PM -0500, Adam Ford wrote: > Currently the source code is compiled using hard-coded values > from CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK. This patch allows this > clock divider value to be moved to the device tree and be changed > without having to recompile the kernel.

Re: [RESEND PATCH v3 2/3] dma-buf: add DMA_BUF_{GET,SET}_NAME ioctls

2019-06-13 Thread Suren Baghdasaryan
On Wed, Jun 12, 2019 at 2:49 PM 'Chenbo Feng' via kernel-team wrote: > > On Wed, Jun 12, 2019 at 7:43 AM Sumit Semwal wrote: > > > > Hello Chenbo, > > > > Thanks very much for your patches. Other than a couple tiny nits > > below, I think these look good, and I will merge them before the end > >

Re: [PATCH v4 2/3] dma-buf: add DMA_BUF_SET_NAME ioctls

2019-06-13 Thread Suren Baghdasaryan
On Wed, Jun 12, 2019 at 2:48 PM 'Chenbo Feng' via kernel-team wrote: > > From: Greg Hackmann > > This patch adds complimentary DMA_BUF_SET_NAME ioctls, which lets > userspace processes attach a free-form name to each buffer. > > This information can be extremely helpful for tracking and

Re: [PATCH 08/22] memremap: pass a struct dev_pagemap to ->kill

2019-06-13 Thread Dan Williams
On Thu, Jun 13, 2019 at 1:12 PM Logan Gunthorpe wrote: > > > > On 2019-06-13 3:43 a.m., Christoph Hellwig wrote: > > Passing the actual typed structure leads to more understandable code > > vs the actual references. > > Ha, ok, I originally suggested this to Dan when he introduced the >

Re: [PATCH 09/22] memremap: lift the devmap_enable manipulation into devm_memremap_pages

2019-06-13 Thread Dan Williams
On Thu, Jun 13, 2019 at 12:35 PM Jason Gunthorpe wrote: > > On Thu, Jun 13, 2019 at 11:43:12AM +0200, Christoph Hellwig wrote: > > Just check if there is a ->page_free operation set and take care of the > > static key enable, as well as the put using device managed resources. > > diff --git

[Bug 110897] HyperZ is broken for r300 (bad z for some micro and macrotiles?)

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110897 --- Comment #24 from Richard Thier --- Hmmm... With -O3 I see the same kind of issue. It seems it is there when highest optimization is on maybe? I will build -O2 once again without a restart just to see. -- You are receiving this mail

Re: [PATCH 1/3] dt-bindings: Add binding for IT6505.

2019-06-13 Thread Rob Herring
On Wed, May 08, 2019 at 05:31:56PM +0800, allen wrote: > From: Allen Chen > > Add a DT binding documentation for IT6505. > > Signed-off-by: Allen Chen > > --- > .../bindings/display/bridge/ite,it6505.txt | 30 > ++ > .../devicetree/bindings/vendor-prefixes.txt

[PATCH 1/4] MAINTAINERS: Add entry for stable backlight sysfs ABI documentation

2019-06-13 Thread Matthias Kaehlcke
Add an entry for the stable backlight sysfs ABI to the MAINTAINERS file. Signed-off-by: Matthias Kaehlcke --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 57f496cff999..d51e74340870 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -2857,6 +2857,7

[PATCH 2/4] backlight: Expose brightness curve type through sysfs

2019-06-13 Thread Matthias Kaehlcke
Backlight brightness curves can have different shapes. The two main types are linear and non-linear curves. The human eye doesn't perceive linearly increasing/decreasing brightness as linear (see also 88ba95bedb79 "backlight: pwm_bl: Compute brightness of LED linearly to human eye"), hence many

[PATCH 3/4] backlight: pwm_bl: Set scale type for CIE 1931 curves

2019-06-13 Thread Matthias Kaehlcke
For backlight curves calculated with the CIE 1931 algorithm set the brightness scale type property accordingly. This makes the scale type available to userspace via the 'scale' sysfs attribute. Signed-off-by: Matthias Kaehlcke --- drivers/video/backlight/pwm_bl.c | 5 - 1 file changed, 4

[PATCH 0/4] backlight: Expose brightness curve type through sysfs

2019-06-13 Thread Matthias Kaehlcke
Backlight brightness curves can have different shapes. The two main types are linear and non-linear curves. The human eye doesn't perceive linearly increasing/decreasing brightness as linear (see also 88ba95bedb79 "backlight: pwm_bl: Compute brightness of LED linearly to human eye"), hence many

[PATCH 4/4] backlight: pwm_bl: Set scale type for brightness curves specified in the DT

2019-06-13 Thread Matthias Kaehlcke
Check if a brightness curve specified in the device tree is linear or not and set the corresponding property accordingly. This makes the scale type available to userspace via the 'scale' sysfs attribute. To determine if a curve is linear it is compared to a interpolated linear curve between min

Re: [RFC/WIP] drm/rockchip: Support CRTC gamma LUT

2019-06-13 Thread Ilia Mirkin
Note that userspace may provide any size of gamma lut. Have a look at i915/intel_color.c:intel_color_check which filters out only the allowed sizes. Consider having a special allowance for 256-sized LUTs since that's what most legacy userspace will set, and it seems like a waste to create a 10-bit

[RFC/WIP] drm/rockchip: Support CRTC gamma LUT

2019-06-13 Thread Ezequiel Garcia
Add CRTC gamma LUT configuration on RK3288 and RK3399. Signed-off-by: Ezequiel Garcia --- This patch seems to work well on RK3288, but produces a distorted output on RK3399. I was hoping someone could have any idea, so we can support both platforms. drivers/gpu/drm/rockchip/rockchip_drm_vop.c

Re: [PATCH] drm/connector: Fix kerneldoc warning in HDR_OUTPUT_METADATA description

2019-06-13 Thread Sean Paul
On Thu, Jun 13, 2019 at 12:57:29PM -0400, Alex Deucher wrote: > On Thu, Jun 13, 2019 at 11:17 AM Sean Paul wrote: > > > > From: Sean Paul > > > > Fixes the following warning: > > ../drivers/gpu/drm/drm_connector.c:981: WARNING: Definition list ends > > without a blank line; unexpected unindent.

Re: [PATCH v5 00/11] drm: Add self refresh helpers

2019-06-13 Thread Sean Paul
On Tue, Jun 11, 2019 at 12:08:14PM -0400, Sean Paul wrote: > From: Sean Paul I've pushed the first 6 (all reviewed) patches to drm-misc-next, I'll wait for a rockchip review on the last 5 and apply them when that comes through. Thanks all for the comments! Sean > > Back again with a new

Re: Drop use of DRM_WAIT_ON() [Was: drm/drm_vblank: Change EINVAL by the correct errno]

2019-06-13 Thread Rodrigo Siqueira
Hi Sam, I tested it by using VKMS and kms_flip, and tests related to “vblank” fails (e.g., basic-flip-vs-wf_vblank, blocking-absolute-wf_vblank, flip-vs-absolute-wf_vblank, etc). I tried to dig into this issue, and you can see my comments inline: On Thu, Jun 13, 2019 at 2:04 AM Sam Ravnborg

[PATCH 2/9] drm/sun4i: tcon: Add TCON LCD support for R40

2019-06-13 Thread Jagan Teki
TCON LCD0, LCD1 in allwinner R40, are used for managing LCD interfaces like RGB, LVDS and DSI. Like TCON TV0, TV1 these LCD0, LCD1 are also managed via tcon top. Add support for it, in tcon driver. Signed-off-by: Jagan Teki --- drivers/gpu/drm/sun4i/sun4i_tcon.c | 7 +++ 1 file changed, 7

[PATCH 1/9] dt-bindings: display: Add TCON LCD compatible for R40

2019-06-13 Thread Jagan Teki
Like TCON TV0, TV1 allwinner R40 has TCON LCD0, LCD1 which are managed via TCON TOP. Add tcon lcd compatible R40, the same compatible can handle TCON LCD0, LCD1. Cc: Rob Herring Cc: Mark Rutland Signed-off-by: Jagan Teki --- Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 1 +

[PATCH 8/9] ARM: dts: sun8i: r40: Add MIPI DSI pipeline

2019-06-13 Thread Jagan Teki
Add MIPI DSI pipeline for Allwinner R40. Unlike conventional Display pipeline in allwinner, R40 have TCON TCOP which would interact various block like muxes, tcon lcd, tcon_tv for better pipeline fitting. For MIPI DSI pipeline, we have to configure the tcon_lcd0 block which would interact with

[PATCH 6/9] dt-bindings: sun6i-dsi: Add R40 MIPI-DSI compatible (w/ A64 fallback)

2019-06-13 Thread Jagan Teki
The MIPI DSI controller on Allwinner R40 is similar on the one on A64 like doesn't associate any DSI_SCLK gating. So, add R40 compatible and append A64 compatible as fallback. Cc: Rob Herring Cc: Mark Rutland Signed-off-by: Jagan Teki ---

[DO NOT MERGE] [PATCH 9/9] ARM: dts: sun8i-r40: bananapi-m2-ultra: Enable Bananapi S070WV20-CT16 DSI panel

2019-06-13 Thread Jagan Teki
This patch add support for Bananapi S070WV20-CT16 DSI panel to BPI-M2U board. DSI panel connected via board DSI port with, - DCDC1 as VCC-DSI supply - PH18 gpio for lcd enable pin - PD17 gpio for lcd reset pin - PD16 gpio for backlight enable pin Signed-off-by: Jagan Teki ---

[PATCH 3/9] ARM: dts: sun8i: r40: Use tcon top clock index macros

2019-06-13 Thread Jagan Teki
tcon_tv0, tcon_tv1 nodes have a clock names of tcon-ch0, tcon-ch1 which are referring tcon_top clocks via index numbers like 0, 1 with CLK_TCON_TV0 and CLK_TCON_TV1 respectively. Use the macro in place of index numbers, for more code readability. Signed-off-by: Jagan Teki ---

[PATCH 0/9] drm/sun4i: Allwinner R40 MIPI-DSI support

2019-06-13 Thread Jagan Teki
This is initial version for supporting MIPI-DSI on Allwinner R40. The controller look similar like, Allwinnwe A64 so it has dependencies with A64 MIPI DSI changes, DSI fixes and R40 pwm driver [1] [2] [3] PLL-MIPI, dclk divders logic bpp/lanes are properly work for R40, like A31, A64. patch

[PATCH 4/9] drm/sun4i: tcon_top: Use clock name index macros

2019-06-13 Thread Jagan Teki
TCON TOP mux blocks in R40 are registering clock using tcon top clock index numbers. Right now the code is using, real numbers start with 0, but we have proper macros that defined these name index numbers. Use the existing macros, instead of real numbers for more code readability.

[PATCH 7/9] dt-bindings: sun6i-dsi: Add R40 DPHY compatible (w/ A31 fallback)

2019-06-13 Thread Jagan Teki
The MIPI DSI PHY controller on Allwinner R40 is similar on the one on A31. Add R40 compatible and append A31 compatible as fallback. Cc: Rob Herring Cc: Mark Rutland Signed-off-by: Jagan Teki --- Documentation/devicetree/bindings/display/sunxi/sun6i-dsi.txt | 1 + 1 file changed, 1

[PATCH 5/9] ARM: dts: sun8i: r40: Add TCON TOP LCD clocking

2019-06-13 Thread Jagan Teki
According to Fig 7-2. TCON Top Block Diagram in User manual. TCON TOP can have an hierarchy for TCON_LCD0, LCD1 like TCON_TV0, TV1 so, the tcon top would handle the clocks of TCON_LCD0, LCD1 similar like TV0, TV1. But, the current tcon_top node is using dsi clock name with CLK_DSI_DPHY which is

Re: [PATCH] drm/amd/display: fix compilation error

2019-06-13 Thread Alex Deucher
On Thu, Jun 13, 2019 at 2:42 PM Sam Ravnborg wrote: > > Hi Alex. > > On Wed, Jun 12, 2019 at 10:35:26PM -0400, Alex Deucher wrote: > > On Wed, Jun 12, 2019 at 10:34 PM Hariprasad Kelam > > wrote: > > > > > > this patch fixes below compilation error > > > > > >

[Bug 105113] [hawaii, radeonsi, clover] Running Piglit cl/program/execute/{, tail-}calls{, -struct, -workitem-id}.cl cause GPU VM error and ring stalled GPU lockup

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105113 Jan Vesely changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

Re: Drop use of DRM_WAIT_ON() [Was: drm/drm_vblank: Change EINVAL by the correct errno]

2019-06-13 Thread Sam Ravnborg
Hi Rodrigo et al. On Thu, Jun 13, 2019 at 07:04:03AM +0200, Sam Ravnborg wrote: > Hi Rodrigo. > > On Wed, Jun 12, 2019 at 11:10:54PM -0300, Rodrigo Siqueira wrote: > > For historical reason, the function drm_wait_vblank_ioctl always return > > -EINVAL if something gets wrong. This scenario

[RFC][PATCH 2/2] drm/i915: Populate PATH prop for every connector

2019-06-13 Thread Ville Syrjala
From: Ville Syrjälä Userspace may want stable identifiers for connectors. Let's try to provide that via the PATH prop. I tried to make these somewhat abstract by using just "port_type:index" type of approach, where we derive the index from the physical instance of that hw block, so it should

[RFC][PATCH 0/2] drm: PATH prop for all connectors?

2019-06-13 Thread Ville Syrjala
From: Ville Syrjälä Here's a possible apporoach for providing userspace with some stable connector identifiers. Combine with the bus name of the GPU and you should have some kind of real physical path description. Unfortunately the ship has sailed for MST connectors because userspace is already

[RFC][PATCH 1/2] drm: Improve PATH prop docs

2019-06-13 Thread Ville Syrjala
From: Ville Syrjälä The PATH blob is already being parsed by userspace for MST connectors so the layout of the blob is now uabi. Let's document what it should look like. Also add a clear note saying non-MST connectors can have a PATH prop too. Cc: Daniel Vetter Cc: Pekka Paalanen Cc: Ilia

Re: [PATCH] drm/amd/display: fix compilation error

2019-06-13 Thread Sam Ravnborg
Hi Alex. On Wed, Jun 12, 2019 at 10:35:26PM -0400, Alex Deucher wrote: > On Wed, Jun 12, 2019 at 10:34 PM Hariprasad Kelam > wrote: > > > > this patch fixes below compilation error > > > > drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c: In > > function

Re: dev_pagemap related cleanups

2019-06-13 Thread Dan Williams
On Thu, Jun 13, 2019 at 2:43 AM Christoph Hellwig wrote: > > Hi Dan, Jérôme and Jason, > > below is a series that cleans up the dev_pagemap interface so that > it is more easily usable, which removes the need to wrap it in hmm > and thus allowing to kill a lot of code > > Diffstat: > > 22 files

[Bug 110856] Freesync causes in-game blackscreens when game has low fps.

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110856 --- Comment #7 from Ropid --- I saw the same issue when I tried the BenQ EX3203R for a few days. I could work around the problem by extracting and saving the monitor's EDID in a file, and changing the VRR range in that file from the original

[Bug 110914] Heavy corruption on R300 with modesetting and GLAMOR

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110914 Bug ID: 110914 Summary: Heavy corruption on R300 with modesetting and GLAMOR Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity:

[PATCH v2] drm/edid: parse CEA blocks embedded in DisplayID

2019-06-13 Thread Andres Rodriguez
DisplayID blocks allow embedding of CEA blocks. The payloads are identical to traditional top level CEA extension blocks, but the header is slightly different. This change allows the CEA parser to find a CEA block inside a DisplayID block. Additionally, it adds support for parsing the embedded

Re: [PATCH] armada: no need to check return value of debugfs_create functions

2019-06-13 Thread Greg Kroah-Hartman
On Thu, Jun 13, 2019 at 05:15:59PM +0100, Russell King - ARM Linux admin wrote: > On Thu, Jun 13, 2019 at 06:01:14PM +0200, Greg Kroah-Hartman wrote: > > On Thu, Jun 13, 2019 at 03:36:00PM +0100, Russell King - ARM Linux admin > > wrote: > > > On Thu, Jun 13, 2019 at 03:28:50PM +0200, Greg

Re: [PATCH] malidp: no need to check return value of debugfs_create functions

2019-06-13 Thread Greg Kroah-Hartman
On Thu, Jun 13, 2019 at 05:27:55PM +0100, Liviu Dudau wrote: > On Thu, Jun 13, 2019 at 05:57:13PM +0200, Greg Kroah-Hartman wrote: > > On Thu, Jun 13, 2019 at 03:52:22PM +0100, Liviu Dudau wrote: > > > On Thu, Jun 13, 2019 at 03:28:29PM +0200, Greg Kroah-Hartman wrote: > > > > When calling debugfs

Re: [PATCH] drm/connector: Fix kerneldoc warning in HDR_OUTPUT_METADATA description

2019-06-13 Thread Alex Deucher
On Thu, Jun 13, 2019 at 11:17 AM Sean Paul wrote: > > From: Sean Paul > > Fixes the following warning: > ../drivers/gpu/drm/drm_connector.c:981: WARNING: Definition list ends without > a blank line; unexpected unindent. > > Fixes: a09db883e5d9 ("drm: Fix docbook warnings in hdr metadata helper

Re: [PATCH] host1x: debugfs_create_dir() can never return NULL

2019-06-13 Thread Thierry Reding
On Thu, Jun 13, 2019 at 01:45:22PM +0200, Greg Kroah-Hartman wrote: > So there is no need to check for a value that can never happen. No need > to check the return value all anyway, as any debugfs call can take the > result of this function as an option just fine. > > Cc: Thierry Reding > Cc:

Re: [PATCH v3 8/9] drm: Remove lock interfaces from GEM VRAM helpers

2019-06-13 Thread Daniel Vetter
On Thu, Jun 13, 2019 at 09:30:40AM +0200, Thomas Zimmermann wrote: > The lock functions and the locked-pin/unpin functions of GEM VRAM are not > requried any longer. Remove them. > > Signed-off-by: Thomas Zimmermann btw a neat thing we could do for these helpers would be to integrate them more

Re: [PATCH v2] drm/komeda: Make Komeda interrupts shareable

2019-06-13 Thread Liviu Dudau
On Thu, Jun 13, 2019 at 04:13:10PM +0100, Ayan Halder wrote: > Komeda interrupts may be shared with other hardware blocks. > One needs to use devm_request_irq() with IRQF_SHARED to create a shared > interrupt handler. > As a result of not using drm_irq_install() api, one needs to set > "(struct

Re: [PATCH] malidp: no need to check return value of debugfs_create functions

2019-06-13 Thread Liviu Dudau
On Thu, Jun 13, 2019 at 05:57:13PM +0200, Greg Kroah-Hartman wrote: > On Thu, Jun 13, 2019 at 03:52:22PM +0100, Liviu Dudau wrote: > > On Thu, Jun 13, 2019 at 03:28:29PM +0200, Greg Kroah-Hartman wrote: > > > When calling debugfs functions, there is no need to ever check the > > > return value.

[Bug 110783] Mesa 19.1 rc crashing MPV with VAAPI

2019-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=110783 --- Comment #14 from Gert Wollny --- Well, I already pointed out that the fix is by no means complete, because even if I provide a TGSI that doesn't use TEX_LZ, I still have to take care of the DIV, which is a bit more tedious and there is

  1   2   3   4   >