Hi Andrzej,
2017년 06월 19일 20:03에 Andrzej Hajda 이(가) 쓴 글:
> Hi Inki,
>
> On 28.12.2016 15:32, Gabriel Krisman Bertazi wrote:
>> num_ioctls is already assigned when declaring the exynos_drm_driver
>> structure. No need to duplicate it here.
>>
>> Signed-off-by: Gabriel Krisman Bertazi
each SE take 16 bit in cu_ao_mask. For ASICs with 4 SE, cu_ao_mask
has invalid value. so I change cu_ao_mask to cu_ao_bitmap[4][4] and increase
kmd driver version.
On Tue, Jun 20, 2017 at 11:49:23AM +0200, Christian König wrote:
> I'm not 100% sure what this is all about, but it clearly won't
With instantaneous high precision vblank timestamping
that updates at leading edge of vblank, a cooked hw
vblank counter which increments at leading edge of
vblank, and reliable page flip execution and completion
at leading edge of vblank, we should meet the requirements
for fast/immediate vblank
With instantaneous high precision vblank timestamping
that updates at leading edge of vblank, the emulated
"hw vblank counter" from vblank timestamping which
increments at leading edge of vblank, and reliable
page flip execution and completion at leading edge
of vblank, we should meet the
With instantaneous high precision vblank timestamping
that updates at leading edge of vblank, the emulated
"hw vblank counter" from vblank timestamping, which
increments at leading edge of vblank, and reliable
page flip execution and completion at leading edge of
vblank, we should meet the
With instantaneous high precision vblank timestamping
that updates at leading edge of vblank, a cooked hw
vblank counter which increments at leading edge of
vblank, and reliable page flip execution and completion
at leading edge of vblank, we should meet the requirements
for fast/immediate vblank
This patch series sets dev->vblank_disable_immediate = true on
radeon/amdgpu-kms, nouveau-kms for nv50+, and vc4 for the real
kms driver (as opposed to dispmanx firmware backed kms).
All the drivers should be ready in theory, given their implementation,
for fast vblank disable/enable. In
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #21 from Michel Dänzer ---
Plymouth shouldn't get the values with drmModeCrtcGetGamma — there's no
guarantee that the CLUT contains suitable values at that point (e.g. the
hardware could currently be programmed
of_device_ids are not supposed to change at runtime. All functions
working with of_device_ids provided by work with const
of_device_ids. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
8836 744 09580256c
Add const to drm_encoder_helper_funcs structures.
Bhumika Goyal (2):
drm/rockchip: add const to drm_encoder_helper_funcs structures
drm/sun4i: add const to drm_encoder_helper_funcs structures
drivers/gpu/drm/rockchip/analogix_dp-rockchip.c | 3 ++-
drivers/gpu/drm/rockchip/inno_hdmi.c
From: Kuninori Morimoto
This driver's Copyright is under Renesas Solutions Corp
Signed-off-by: Kuninori Morimoto
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi-i2s-audio.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
From: Frank Rowand
Convert non-ascii up and down arrows to '^' and 'v'
Signed-off-by: Frank Rowand
---
.../devicetree/bindings/display/panel/display-timing.txt | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git
On 2017-06-20 11:40, Daniel Vetter wrote:
> On Sat, Jun 17, 2017 at 07:48:02PM +0200, Peter Rosin wrote:
>> All layers of all supported chips support this, the only variable is the
>> base address of the lookup table in the register map.
>>
>> Signed-off-by: Peter Rosin
>
> As
Hi,
On Tuesday 20 June 2017 04:59 PM, Benjamin Gaignard wrote:
2017-06-20 6:55 GMT+02:00 Arvind Yadav :
Replace '%d' by '%zu' and '%lu' to fix the following compilation warning:-
drivers/gpu/drm/sti/sti_hqvdp.c: In function ‘sti_hqvdp_start_xp70’:
of_device_ids are not supposed to change at runtime. All functions
working with of_device_ids provided by work with const
of_device_ids. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
4222 664 048861316
Although header is included only once but still having an include guard
is a good practice. To avoid confusion, add SoC prefix to existing
Exynos5433 header include guard.
Signed-off-by: Krzysztof Kozlowski
---
Changes since v1:
1. Just re-order patches in patchset and
The default implementation should be used.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c
b/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c
index
On Tue, Jun 20, 2017 at 2:32 AM, Jani Nikula
wrote:
> On Tue, 20 Jun 2017, Daniel Vetter wrote:
>> In
>>
>> commit 91eefc05f0ac71902906b2058360e61bd25137fe
>> Author: Daniel Vetter
>> Date: Wed Dec 14 00:08:10 2016
Drivers no longer have any need for these callbacks, and there are no
users. Zap. Zap-zap-zzzap-p-pp-p.
Signed-off-by: Peter Rosin
---
include/drm/drm_fb_helper.h | 32
include/drm/drm_modeset_helper_vtables.h | 16
Hi!
This series adds support for an 8-bit clut mode in the atmel-hlcdc
driver.
This is the same code as in patch 1/3 of v3. I will redo 2/3 and 3/3
of that series some other way and it feels orthogonal to this driver,
and that might take some time to get right, so I'm going to handle
that on its
The redundant fb helpers .load_lut, .gamma_set and .gamma_get are
no longer used. Remove the dead code and hook up the crtc .gamma_set
to use the crtc gamma_store directly instead of duplicating that
info locally.
Signed-off-by: Peter Rosin
---
The driver stores lut values from the fbdev interface, and is able
to give them back, but does not appear to do anything with these
lut values. The generic fb helpers have replaced this function,
and may even have made the driver work for the C8 mode from the
fbdev interface. But that is untested.
DRM drivers supporting clut may want a convenient way to only use
non-default .gamma_set and .gamma_get ops in the drm_fb_helper_funcs
in order to avoid the following
/*
* The driver really shouldn't advertise pseudo/directcolor
* visuals if it can't deal with the
The redundant fb helpers .load_lut, .gamma_set and .gamma_get are
no longer used. Remove the dead code and hook up the crtc .gamma_set
to use the crtc gamma_store directly instead of duplicating that
info locally.
Signed-off-by: Peter Rosin
---
Add const to drm_encoder_helper_funcs structures as they are only passed
as an argument to the function drm_encoder_helper_add and this argument
is of type const. So, add const to these structures. Also, fix line over
80 characters warning while adding const.
Signed-off-by: Bhumika Goyal
The redundant fb helpers .load_lut, .gamma_set and .gamma_get are
no longer used. Remove the dead code and hook up the crtc .gamma_set
to use the crtc gamma_store directly instead of duplicating that
info locally.
Signed-off-by: Peter Rosin
---
All layers of all supported chips support this, the only variable is the
base address of the lookup table in the register map.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 4
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c| 13
This makes the redundant fb helpers .load_lut, .gamma_set and .gamma_get
totally obsolete.
I think the gamma_store can end up invalid on error. But the way I read
it, that can happen in drm_mode_gamma_set_ioctl as well, so why should
this pesky legacy fbdev stuff be any better?
The redundant fb helper .load_lut is no longer used, and can not
work right without also providing the fb helpers .gamma_set and
.gamma_get thus rendering the code in this driver suspect.
Just remove the dead code.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/stm/ltdc.c | 12
The DECON headers contain only defines for registers. There are no
other drivers using them so this should be put locally to the Exynos DRM
driver. Keeping headers local helps managing the code.
Suggested-by: Marek Szyprowski
Signed-off-by: Krzysztof Kozlowski
On Tue, Jun 20, 2017 at 11:53 AM, Emil Velikov wrote:
> On 19 June 2017 at 17:31, Krzysztof Kozlowski wrote:
>> Although header is included only once but still having an include guard
>> is a good practice. To avoid confusion, add SoC prefix to
The redundant fb helpers .gamma_set and .gamma_get are no longer
used. Remove the dead code and hook up the crtc .gamma_set
to use the crtc gamma_store directly instead of duplicating that
info locally.
It is a bit strange that the fb helper .load_lut was not hooked
up, so this change may well
The redundant fb helpers .load_lut, .gamma_set and .gamma_get are
no longer used. Remove the dead code and hook up the crtc .gamma_set
to use the crtc gamma_store directly instead of duplicating that
info locally.
Signed-off-by: Peter Rosin
---
On Tue, Jun 20, 2017 at 12:57 PM, Emil Velikov wrote:
> On 20 June 2017 at 11:02, Krzysztof Kozlowski wrote:
>> On Tue, Jun 20, 2017 at 11:53 AM, Emil Velikov
>> wrote:
>>> On 19 June 2017 at 17:31, Krzysztof Kozlowski
Add const to drm_encoder_helper_funcs structures as they are only passed
as an argument to the function drm_encoder_helper_add and this argument
is of type const. So, add const to these structures.
Signed-off-by: Bhumika Goyal
---
drivers/gpu/drm/sun4i/sun4i_rgb.c | 2 +-
The redundant fb helpers .load_lut, .gamma_set and .gamma_get are
no longer used. Remove the dead code and hook up the crtc .gamma_set
to use the crtc gamma_store directly instead of duplicating that
info locally.
Signed-off-by: Peter Rosin
---
of_device_ids are not supposed to change at runtime. All functions
working with of_device_ids provided by work with const
of_device_ids. So mark the non-const structs as const.
File size before:
textdata bss dec hex filename
15845 640 0 164854065
The redundant fb helpers .load_lut, .gamma_set and .gamma_get are
no longer used. Remove the dead code and hook up the crtc .gamma_set
to use the crtc gamma_store directly instead of duplicating that
info locally.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/ast/ast_drv.h |
Hi!
While trying to get CLUT support for the atmel_hlcdc driver, and
specifically for the emulated fbdev interface, I received some
push-back that my feeble in-driver attempts should be solved
by the core. This is my attempt to do it right.
Boris and Daniel, was this approximately what you had
Replace '%d' by '%zu' and '%lu' to fix the following compilation warning:-
drivers/gpu/drm/sti/sti_hqvdp.c: In function ‘sti_hqvdp_start_xp70’:
drivers/gpu/drm/sti/sti_hqvdp.c:925:3: warning: format ‘%d’ expects argument of
type ‘int’, but argument 4 has type ‘size_t’ [-Wformat=]
On 2017年06月20日 21:07, Bhumika Goyal wrote:
Add const to drm_encoder_helper_funcs structures as they are only passed
as an argument to the function drm_encoder_helper_add and this argument
is of type const. So, add const to these structures. Also, fix line over
80 characters warning while adding
https://bugs.freedesktop.org/show_bug.cgi?id=98795
Samuel Pitoiset changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=93826
--- Comment #73 from Eike ---
(In reply to iuno from comment #72)
> Another, slightly off-topic, question: the VertRefresh value shows the
> FreeSync range for my display (35-90), your values are 50-144, does that
> mean you can
On Tue, 2017-06-20 at 22:28 +0200, Daniel Vetter wrote:
> In
>
> commit 91eefc05f0ac71902906b2058360e61bd25137fe
> Author: Daniel Vetter
> Date: Wed Dec 14 00:08:10 2016 +0100
>
> drm: Tighten locking in drm_mode_getconnector
>
> I reordered the logic a bit in
On Tue, Jun 20, 2017 at 10:28:37PM +0200, Daniel Vetter wrote:
> In
>
> commit 91eefc05f0ac71902906b2058360e61bd25137fe
> Author: Daniel Vetter
> Date: Wed Dec 14 00:08:10 2016 +0100
>
> drm: Tighten locking in drm_mode_getconnector
>
> I reordered the logic a bit
On 06/21/2017 02:54 AM, Olof Johansson wrote:
> Hey,
>
> This was reported back in February and it seems nobody's given a shit?
>
> I've got a machine here with a Quadro 4000 that the screen locks up on
> every single time the monitor goes to sleep. Userspace is Ubuntu 16.04,
> kernel is recent
The last rework left behind two unused variables:
drm/arm/hdlcd_crtc.c: In function 'hdlcd_plane_atomic_update':
drm/arm/hdlcd_crtc.c:264:13: warning: unused variable 'src_y'
[-Wunused-variable]
drm/arm/hdlcd_crtc.c:264:6: warning: unused variable 'src_x' [-Wunused-variable]
This removes them.
In
commit 91eefc05f0ac71902906b2058360e61bd25137fe
Author: Daniel Vetter
Date: Wed Dec 14 00:08:10 2016 +0100
drm: Tighten locking in drm_mode_getconnector
I reordered the logic a bit in that IOCTL, but that broke userspace
since it'll get the new mode list, but
On Tue, Jun 20, 2017 at 9:32 PM, Pandiyan, Dhinakaran
wrote:
> Isn't this overwriting the -EFAULT return in case copy_to_user() failed
> while copying the modes ?
Indeed, thanks for spotting this. New patch in-flight.
-Daniel
--
Daniel Vetter
Software Engineer,
When compile-testing for something other than ARCH_QCOM,
we run into a link error:
drivers/gpu/drm/msm/adreno/a5xx_gpu.o: In function `a5xx_hw_init':
a5xx_gpu.c:(.text.a5xx_hw_init+0x600): undefined reference to
`qcom_mdt_get_size'
a5xx_gpu.c:(.text.a5xx_hw_init+0x93c): undefined reference to
In zap_shader_load_mdt(), we pass a pointer to a phys_addr_t
into dmam_alloc_coherent, which the compiler warns about:
drivers/gpu/drm/msm/adreno/a5xx_gpu.c: In function 'zap_shader_load_mdt':
drivers/gpu/drm/msm/adreno/a5xx_gpu.c:54:50: error: passing argument 3 of
'dmam_alloc_coherent' from
On Tue, 2017-06-20 at 11:16 +0200, Daniel Vetter wrote:
> In
>
> commit 91eefc05f0ac71902906b2058360e61bd25137fe
> Author: Daniel Vetter
> Date: Wed Dec 14 00:08:10 2016 +0100
>
> drm: Tighten locking in drm_mode_getconnector
>
> I reordered the logic a bit in
https://bugs.freedesktop.org/show_bug.cgi?id=100070
--- Comment #10 from Marek Olšák ---
I have a basic initial fix for the grass issue. It works as follows.
The GLSL discard call site sets a flag that the pixel should be killed, but
doesn't kill the thread. The thread is
Hi Dave,
This time around, the biggest thing is a bunch of GEM rework for more
fine grained locking and prep work to handle multiple address spaces
(ie. per-process pagetables). Also some HDMI fixes for 8x96
(snapdragon 820).
One unrelated bus patch, for something that seems to get merged
https://bugs.freedesktop.org/show_bug.cgi?id=101528
Bug ID: 101528
Summary: RX460 Memory clock stays high until card is "used"
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
On Tue, Jun 20, 2017 at 11:16 AM, Daniel Vetter wrote:
> In
>
> commit 91eefc05f0ac71902906b2058360e61bd25137fe
> Author: Daniel Vetter
> Date: Wed Dec 14 00:08:10 2016 +0100
>
> drm: Tighten locking in drm_mode_getconnector
>
> I reordered
https://bugs.freedesktop.org/show_bug.cgi?id=100070
--- Comment #9 from Marek Olšák ---
It might be a WQM vs KILL issue.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
Problem : While running IGT kms_atomic_transition test suite i encountered
a hang in drmHandleEvent immediately following an atomic_commit.
After dumping the atomic state I relized that in this case there was
not even one CRTC attached to the state and only disabled
planes. This probably due to a
https://bugs.freedesktop.org/show_bug.cgi?id=101294
Marek Olšák changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freedesktop.org/show_bug.cgi?id=101387
--- Comment #20 from Carlo Caione ---
> That could be a plymouth bug. I've noticed that it doesn't seem to call
> drmModeCrtcSetGamma to make sure the display CLUTs are initialized to
> appropriate values.
Can you expand on
On Tue, 2017-06-20 at 11:03 +0200, Daniel Vetter wrote:
> On Mon, Jun 05, 2017 at 02:56:04PM -0700, Puthikorn Voravootivat wrote:
> > This patch set contain 3 patches which are already reviewed by DK.
> > Another 6 patches in previous version was already merged in v7 and v9.
> > - First patch
Archit Taneja writes:
> On 06/16/2017 08:13 PM, Eric Anholt wrote:
>> Archit Taneja writes:
>>
>>> On 06/16/2017 02:11 AM, Eric Anholt wrote:
If the panel-bridge is being set up after the drm_mode_config_reset(),
then the connector's
On Tue, Jun 20, 2017 at 12:54 PM, Olof Johansson wrote:
> Hey,
>
> This was reported back in February and it seems nobody's given a shit?
>
Apparently not -- including you. Someone who was interested in seeing this
issue fixed would certainly have provided a kernel bisection
Hi Dave,
A few fixes for 4.12:
- Add a new Polaris12 pci id
- A stack corruption fix
- Suspend/resume fix
- PX fix
- Display flickering fix
The following changes since commit 7119dbdf7c52042acb1b02f116fa3257e97659ea:
Merge tag 'drm-intel-fixes-2017-06-15' of
Hey,
This was reported back in February and it seems nobody's given a shit?
I've got a machine here with a Quadro 4000 that the screen locks up on
every single time the monitor goes to sleep. Userspace is Ubuntu 16.04,
kernel is recent mainline (4.12-rc4+). It's been happening since 4.10
though.
https://bugs.freedesktop.org/show_bug.cgi?id=101499
--- Comment #13 from Carlo Caione ---
> I just tried the HEAD of xf86-video-amdgpu and now instead of
> having a black screen I have the image corruption as shown
> in the picture.
Just FYI this is due to commit b09fde0d81
Hi Rob,
On Wed, Jun 14, 2017 at 2:49 PM, Thierry Reding
wrote:
> On Tue, Apr 25, 2017 at 01:18:35PM -0300, Marco Franchi wrote:
>> Add driver for Seiko Instruments Inc. 4.3" WVGA (800 x RGB x 480)
>> TFT with Touch-Panel.
>>
>> Datasheet available at:
>>
Hi Dave, a mixed bag of i915 fixes. The memory allocation changes from
Chris and deadlock fixes from Ville are the important ones.
BR,
Jani.
The following changes since commit c380f681245d7ae57f17d9ebbbe8f8f1557ee1fb:
drm/i915: Fix GVT-g PVINFO version compatibility check (2017-06-13
Hi Dave,
One more -misc-next pull for 4.13 from drm-misc-next. These 3 patches came less
than an hour after my last PR, so we'll sneak these in and cut over to
next-fixes after this.
All 3 are vc4. 2 add tiling support to vc4 and the other replaces hand-rolled
atomic commit code with the helpers.
On Tue, Jun 20, 2017 at 01:39:13PM +0200, Gerd Hoffmann wrote:
> Fix qxl __user annotations in uapi include.
> Also some more sparse easy warnings.
> Some iomem address space issues left for another day.
>
> Gerd Hoffmann (3):
> drm/qxl: fix __user annotations
> drm/qxl: declare a bunch of
Hi Jose,
Am Freitag, 9. Juni 2017, 13:53:12 CEST schrieb Jose Abreu:
> On 09-06-2017 12:04, Jose Abreu wrote:
> > Currently HDMI 2.0 PHYs do not have a default configuration function.
> >
> > As these PHYs have the same register layout as the 3D PHYs we can
> > safely use the default
On Tue, Jun 20, 2017 at 11:23:20AM +0100, Liviu Dudau wrote:
> drm_fbdev_cma_set_suspend{,_unlocked} use an integer parameter
> to describe whether the intended state is a suspend or a resume.
> It then passes the value to drm_fb_helper_set_suspend{,_unlocked}
> which uses a boolean. Switch to
On Mon, 2017-06-19 at 21:38 +0530, Shashank Sharma wrote:
> This patch checks encoder level support for HDMI YCBCR outputs.
> HDMI output mode is a connector property, this patch checks if
> source and sink can support the HDMI output type selected by user.
> And if they both can, it commits the
On Tue, Jun 20, 2017 at 06:38:00PM +0530, Bhumika Goyal wrote:
> Add const to drm_encoder_helper_funcs structures as they are only passed
> as an argument to the function drm_encoder_helper_add and this argument
> is of type const. So, add const to these structures.
>
> Signed-off-by: Bhumika
On Tue, Jun 20, 2017 at 11:19:02AM +0200, Daniel Vetter wrote:
> Ack for the 2 drm patches, but I can also pick them up through drm-misc if
> you prefer that (but then it'll be 4.14).
Nah, I'll plan to set up a dma-mapping tree so that we'll have common
place for dma-mapping work.
On Tue, Jun 20, 2017 at 11:04:00PM +1000, Stephen Rothwell wrote:
> git://git.linaro.org/people/mszyprowski/linux-dma-mapping.git#dma-mapping-next
>
> Contacts: Marek Szyprowski and Kyungmin Park (cc'd)
>
> I have called your tree dma-mapping-hch for now. The other tree has
> not been updated
On Tue, Jun 20, 2017 at 02:14:36PM +0100, Robin Murphy wrote:
> Hi Christoph,
>
> On 20/06/17 13:41, Christoph Hellwig wrote:
> > On Fri, Jun 16, 2017 at 08:10:15PM +0200, Christoph Hellwig wrote:
> >> I plan to create a new dma-mapping tree to collect all this work.
> >> Any volunteers for
Hi Christoph,
On 20/06/17 13:41, Christoph Hellwig wrote:
> On Fri, Jun 16, 2017 at 08:10:15PM +0200, Christoph Hellwig wrote:
>> I plan to create a new dma-mapping tree to collect all this work.
>> Any volunteers for co-maintainers, especially from the iommu gang?
>
> Ok, I've created the new
Hi Christoph,
On Tue, 20 Jun 2017 14:41:40 +0200 Christoph Hellwig wrote:
>
> On Fri, Jun 16, 2017 at 08:10:15PM +0200, Christoph Hellwig wrote:
> > I plan to create a new dma-mapping tree to collect all this work.
> > Any volunteers for co-maintainers, especially from the iommu
Hi Dave,
drm-intel-next-2017-06-19:
Final pile of features for 4.13
New uabi:
- batch bo in first slot, for faster execbuf assembly in userspace
(Chris Wilson)
- (sub)slice getparam, needed for mesa perf support (Robert Bragg)
First pile of patches for cnl/cfl support, maintained by Rodrigo
On Fri, Jun 16, 2017 at 08:10:15PM +0200, Christoph Hellwig wrote:
> I plan to create a new dma-mapping tree to collect all this work.
> Any volunteers for co-maintainers, especially from the iommu gang?
Ok, I've created the new tree:
git://git.infradead.org/users/hch/dma-mapping.git for-next
Change-Id: Ie2a812716a6802f7a5a0bc09b1a8db824c5bf2ed
Signed-off-by: Flora Cui
---
amdgpu/amdgpu.h | 2 +-
amdgpu/amdgpu_gpu_info.c | 2 +-
include/drm/amdgpu_drm.h | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/amdgpu/amdgpu.h b/amdgpu/amdgpu.h
Hi Arvind,
[auto build test WARNING on drm/drm-next]
[also build test WARNING on v4.12-rc6 next-20170620]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Arvind-Yadav/drm-sti-sti_hqvdp-Fix
Flagged by sparse.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_drv.h | 1 +
drivers/gpu/drm/qxl/qxl_drv.c | 1 -
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/qxl/qxl_drv.h b/drivers/gpu/drm/qxl/qxl_drv.h
index
Flagged by sparse.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_display.c | 18 +-
drivers/gpu/drm/qxl/qxl_object.c | 4 ++--
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/gpu/drm/qxl/qxl_display.c
Drop them from u64 fields, tag local variables correctly instead.
While being at it switch the code to use u64_to_user_ptr().
Signed-off-by: Gerd Hoffmann
Acked-by: Daniel Vetter
---
include/uapi/drm/qxl_drm.h | 6 +++---
Fix qxl __user annotations in uapi include.
Also some more sparse easy warnings.
Some iomem address space issues left for another day.
Gerd Hoffmann (3):
drm/qxl: fix __user annotations
drm/qxl: declare a bunch of functions as static
drm/qxl: move extern variable declaration header file
2017-06-20 6:55 GMT+02:00 Arvind Yadav :
> Replace '%d' by '%zu' and '%lu' to fix the following compilation warning:-
>
> drivers/gpu/drm/sti/sti_hqvdp.c: In function ‘sti_hqvdp_start_xp70’:
> drivers/gpu/drm/sti/sti_hqvdp.c:925:3: warning: format ‘%d’ expects argument
2017-06-20 7:05 GMT+02:00 Arvind Yadav :
> of_device_ids are not supposed to change at runtime. All functions
> working with of_device_ids provided by work with const
> of_device_ids. So mark the non-const structs as const.
>
> File size before:
>textdata
On 20 June 2017 at 11:02, Krzysztof Kozlowski wrote:
> On Tue, Jun 20, 2017 at 11:53 AM, Emil Velikov
> wrote:
>> On 19 June 2017 at 17:31, Krzysztof Kozlowski wrote:
>>> Although header is included only once but still having an
drm_fbdev_cma_set_suspend{,_unlocked} use an integer parameter
to describe whether the intended state is a suspend or a resume.
It then passes the value to drm_fb_helper_set_suspend{,_unlocked}
which uses a boolean. Switch to using bool everywhere.
Signed-off-by: Liviu Dudau
On Tue, Jun 20, 2017 at 11:49:23AM +0200, Christian König wrote:
> I'm not 100% sure what this is all about, but it clearly won't work like
> this.
>
> > diff --git a/include/drm/amdgpu_drm.h b/include/drm/amdgpu_drm.h
> > index df250de..dcbe22c 100644
> > --- a/include/drm/amdgpu_drm.h
> > +++
On Tue, Jun 20, 2017 at 11:48:05AM +0200, Boris Brezillon wrote:
> On Tue, 20 Jun 2017 11:42:28 +0200
> Daniel Vetter wrote:
>
> > It's not obvious that when using the new color manager stuff you still
> > need to wire up the legacy helper to get legacy LUT support.
https://bugs.freedesktop.org/show_bug.cgi?id=93826
--- Comment #72 from i...@posteo.net ---
Created attachment 132082
--> https://bugs.freedesktop.org/attachment.cgi?id=132082=edit
parsed EDID from different MG279q
Thanks for that. The new EDID shows in fact other modes and timings, attached
https://bugs.freedesktop.org/show_bug.cgi?id=101382
cosiek...@o2.pl changed:
What|Removed |Added
Summary|[r300] Electronic super joy |[r300] Electronic super joy
On 19 June 2017 at 17:31, Krzysztof Kozlowski wrote:
> Although header is included only once but still having an include guard
> is a good practice. To avoid confusion, add SoC prefix to existing
> Exynos5433 header include guard.
>
> Signed-off-by: Krzysztof Kozlowski
I'm not 100% sure what this is all about, but it clearly won't work like
this.
diff --git a/include/drm/amdgpu_drm.h b/include/drm/amdgpu_drm.h
index df250de..dcbe22c 100644
--- a/include/drm/amdgpu_drm.h
+++ b/include/drm/amdgpu_drm.h
@@ -832,7 +832,7 @@ struct drm_amdgpu_info_device {
On Tue, 20 Jun 2017 11:42:28 +0200
Daniel Vetter wrote:
> It's not obvious that when using the new color manager stuff you still
> need to wire up the legacy helper to get legacy LUT support. Improve
> this with more links. drm_crtc_funcs->gamma_set already explains this
https://bugs.freedesktop.org/show_bug.cgi?id=101499
--- Comment #12 from Carlo Caione ---
Created attachment 132081
--> https://bugs.freedesktop.org/attachment.cgi?id=132081=edit
Corruption using xf86-video-amdgpu HEAD
Interesting. Thank you for explaining this and your
It's not obvious that when using the new color manager stuff you still
need to wire up the legacy helper to get legacy LUT support. Improve
this with more links. drm_crtc_funcs->gamma_set already explains this
properly.
Cc: Peter Rosin
Cc: Boris Brezillon
1 - 100 of 147 matches
Mail list logo