https://bugs.freedesktop.org/show_bug.cgi?id=99353
Bong Cosca changed:
What|Removed |Added
QA Contact|dri-devel@lists.freedesktop |
|.org
https://bugs.freedesktop.org/show_bug.cgi?id=102389
--- Comment #9 from jeremi.jasin...@gmail.com ---
I still have this problem, on linux 4.15 on KDE Neon with dc enabled.
So I bought DP to HDMI active converter, which supports 4k 60hz. While using
this converter and the same HDMI cable, blackscr
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #23 from Bong Cosca ---
Created attachment 137183
--> https://bugs.freedesktop.org/attachment.cgi?id=137183&action=edit
Video BIOS
Attached video BIOS may also prove useful in isolating this bug in the graphics
stack.
--
You are
Hi Wolfram,
On Mon, Feb 5, 2018 at 9:09 PM, Wolfram Sang
wrote:
> In one Renesas driver, I found a typo which turned an intended bit shift
> ('<<')
> into a comparison ('<'). Because this is a subtle issue, I looked tree wide
> for
> similar patterns. This small patch series is the outcome.
>
>
Add support for the Synopsys DesignWare MIPI DSI version 1.31
Two registers need to be updated/added for supporting 1.31:
* PHY_TMR_CFG 0x9c (updated)
1.30 [31:24] phy_hs2lp_time
[23:16] phy_lp2hs_time
[14: 0] max_rd_time
1.31 [25:16] phy_hs2lp_time
[ 9: 0] phy_lp2hs_time
On Mon, Feb 5, 2018 at 4:28 PM, Shawn Guo wrote:
> On Sun, Feb 04, 2018 at 11:19:24PM +0530, Jagan Teki wrote:
>> Series adda LVDS panel attributes on panel drivers instead of defining
>> them in dts nodes, and also added new icorem6 engicam boards.
>>
>> Jagan Teki (7):
>> drm/panel: simple: ad
>
> We are interested
who is we?
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Add documentation for sysfs interface of adp5520/adp5501 analog devices
backlight driver by reading code and looking through git commit logs.
Signed-off-by: Aishwarya Pant
Acked-by: Michael Hennerich
---
.../ABI/testing/sysfs-class-backlight-adp5520 | 31 ++
1 file chan
Hello.
On Mon, 5 Feb 2018, Heiko Stuebner wrote:
From: Zheng Yang
Add a driver for the Innosilicon hdmi phy used on rk3228/rk3229
and rk3328 socs from Rockchip.
Signed-off-by: Zheng Yang
Signed-off-by: Heiko Stuebner
---
+++ b/drivers/phy/rockchip/phy-rockchip-inno-hdmi.c
+static u32 inno_h
Add documentation for sysfs interface of adp8860 series backlight
devices by reading through code and git commits.
Signed-off-by: Aishwarya Pant
Acked-by: Michael Hennerich
---
.../ABI/testing/sysfs-class-backlight-adp8860 | 54 ++
1 file changed, 54 insertions(+)
crea
On 05/02/2018 at 09:47, Ludovic Desroches wrote:
> Use GPIO descriptors instead of relying on the old method.
>
> Signed-off-by: Ludovic Desroches
Acked-by: Nicolas Ferre
On this resent patch as well ;-)
> ---
> drivers/video/fbdev/atmel_lcdfb.c | 30 --
> 1 file
The AVR32 symbol was removed in commit 26202873bb51 ("avr32: remove
support for AVR32 architecture"). Remove the remaining references to it
from the Kconfig files.
Signed-off-by: Ulf Magnusson
---
Changes in v3:
Removal of the AVR32 dependency in PWM_ATMEL is already pending:
https://lkml.org/lkm
Add documentation for sysfs interfaces of Texas Instruments lm3639
backlight + flash led driver chip by looking through git commits and
reading code.
Signed-off-by: Aishwarya Pant
Acked-by: Daniel Thompson
---
Changes in v2:
- Update contact information
Documentation/ABI/testing/sysfs-class-ba
Due to a typo, the mask was destroyed by a comparison instead of a bit
shift.
Signed-off-by: Wolfram Sang
---
Only build tested. To be applied individually per subsystem.
drivers/gpu/drm/exynos/regs-fimc.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/exyno
In one Renesas driver, I found a typo which turned an intended bit shift ('<<')
into a comparison ('<'). Because this is a subtle issue, I looked tree wide for
similar patterns. This small patch series is the outcome.
Buildbot and checkpatch are happy. Only compile-tested. To be applied
individual
On 05/02/2018 at 09:23, Ludovic Desroches wrote:
> Use GPIO descriptors instead of relying on the old method.
>
> Signed-off-by: Ludovic Desroches
Acked-by: Nicolas Ferre
Thanks!
> ---
> drivers/video/fbdev/atmel_lcdfb.c | 30 --
> 1 file changed, 12 insertions(+)
Patchset contains documentation of the sysfs interfaces for the
following five backlight drivers-
1) lm3639
2) adp5520
3) adp8860
It was compiled from data sheets, reading code and git history logs. In v2 of
the patches, documentation for lp8788 and lp855x devices was dropped as the
attributes con
currently ttm code has no any allocation limit. So it allows pages
allocatation unlimited until OOM. Because if swap space is full
of swapped pages and then system memory will be filled up with ttm
pages. and then any memory allocation request will trigger OOM.
the following patches is for preve
for avoid OOM. if free swap space is less than 256MB, reject
the TTM page allocation. Otherwise, swap space will be full
of swapped pages and then system memory will be filled up
with ttm pages. and then any memory allocation request will
trigger OOM.
to cover two cases:
a. If total swap space > 2
set the no_retry flag in struct ttm_mem_global and init it
after ttm_mem_global_init
Signed-off-by: Roger He
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 8 +---
drivers/gpu/drm/ttm/ttm_memory.c| 3 +++
include/drm/ttm/ttm_memory.h| 3 +++
3 files changed, 11 insertions(
Reviewed-by: Yannick Fertré
On 02/05/2018 10:45 AM, Philippe Cornu wrote:
> Some boards use a dedicated voltage regulator for this panel.
> Add & document this related optional power-supply property.
>
> Signed-off-by: Philippe Cornu
> ---
> Documentation/devicetree/bindings/display/panel/ori
for saving memory and more bit flag can be used in future
Signed-off-by: Roger He
---
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 4 ++--
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 4 ++--
drivers/gpu/drm/ttm/ttm_bo.c | 3 ++-
include/drm/ttm/ttm_bo_api.h | 7 +
set TTM_OPT_FLAG_ALLOW_ALLOC_ANYWAY when we are servicing for page
fault routine.
for ttm_mem_global_reserve if in page fault routine, allow the gtt
pages reservation always. because page fault routing already grabbed
system memory and the allowance of this exception is harmless.
Otherwise, it wil
if true for it, allocate TTM pages regardless of zone global memory
account limit.
that is for another special case: suspend.
doesn't care the zone global memory account limit for this case.
Signed-off-by: Roger He
---
drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c | 2 +-
drivers/gpu/drm/amd/amd
Reviewed-by: Yannick Fertré
On 02/05/2018 10:45 AM, Philippe Cornu wrote:
> Add support for the optional power-supply.
>
> Note: A "dummy regulator" is returned by devm_regulator_get()
> if the optional regulator is not present in the device tree,
> simplifying the source code when enabling/disa
Reviewed-by: Yannick Fertré
On 02/01/2018 11:42 AM, Philippe Cornu wrote:
> ltdc supports natively some color formats with alpha (like
> ARGB, ARGB1555, ARGB...). Related non-alpha formats are
> supported too (ARGB->XRGB, ARGB->XRGB...) by
> adjusting ltdc blending factor
Reviewed-by: Yannick Fertré
On 02/01/2018 11:42 AM, Philippe Cornu wrote:
> Hw older versions support non-alpha color formats derived
> from native alpha color formats only on the primary layer.
> For instance, RG16 native format without alpha works fine
> on 2nd layer but XR24 (derived color fo
Hi Jagan,
On Sun, 2018-02-04 at 23:19 +0530, Jagan Teki wrote:
> This adds support for the Ampire AM-800480AYTZQW-00H 7.0" WGA LCD,
> which can be supported by the simple panel driver.
>
> Signed-off-by: Jagan Teki
> Reviewed-by: Rob Herring
> ---
> Changes for v3:
> - collect Rob reiew tag
>
With a bit of refactoring we can contain the variant data for
the strange PL110 versions that is feature-incomplete PL110 for
the ARM Integrator/CP and somewhere inbetween PL110 and PL111
for the ARM Versatile AB and Versatile PB.
We also accomodate for the custom duct-taped RGB565/BGR565 support
The early Integrator CLCD synthesized in the Integrator CP and
IM-PD1 FPGAs are broken: their vertical and next base interrupts
are not functional. Support these variants by simply disabling
the use of the vblank interrupt on these variants.
Reviewed-by: Eric Anholt
Signed-off-by: Linus Walleij
The early Integrator CLCD synthesized in the Integrator CP and
IM-PD1 FPGAs are broken: their clock dividers do not work
properly. Support disabling the clock divider and drive the
clock directly from the parent under these circumstances.
Reviewed-by: Eric Anholt
Signed-off-by: Linus Walleij
---
The ARM Versatile series can do RGB/BGR565 with an external
"PLD" (Programmable Logical Device). However the CLCD does not
have control bits for this, so it needs to be set into the
ordinary 16BPP mode, then the RGB/BGR565 handling of the pixel
data is handled by configuring the PLD through the ext
The Versatile PL110 implementations use multiple endpoints:
from the PL111 port, the lines are routed through a PLD,
and from there forked so the same lines go to a VGA DAC and
an external TFT panel connector. This is discrete wireing
so there is no way to turn of one output, i.e. this is
really tw
On Sun, Feb 4, 2018 at 12:44 AM, Eric Anholt wrote:
> Linus Walleij writes:
>
>> The early Integrator CLCD synthesized in the Integrator CP and
>> IM-PD1 FPGAs are broken: their vertical and next base interrupts
>> are not functional. Support these variants by simply disabling
>> the use of the v
Nice work, but a few comments.
First of all you need to reorder the patches. Adding the exceptions to
the restrictions should come first, then the restriction itself.
Otherwise we might break a setup in between the patches and that is bad
for bisecting.
Then make all values configurable, e.g
Hello, Ville!
Thank you very much for such a comprehensive answer.
Please see inline
On 02/05/2018 06:47 PM, Ville Syrjälä wrote:
On Mon, Feb 05, 2018 at 06:03:25PM +0200, Oleksandr Andrushchenko wrote:
Hello,
I have a DRM driver which implements display protocol for Xen [1]
and this proto
Move the new call out of ttm_mem_global_reserve() and into
ttm_page_alloc.c or ttm_page_alloc_dma.c (but keep it in ttm_memory.c).
ttm_mem_global_reserve() is called for each page allocated and
si_mem_available() is a bit to heavy for that.
Good idea! Agree with you completely, bec
Otherwise we get an EFAULT, at least on a 64-bit kernel.
Fixes: 2048a9e7 "drm: add drmSyncobjWait wrapper"
---
xf86drm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xf86drm.c b/xf86drm.c
index 74b4e230..1e87610b 100644
--- a/xf86drm.c
+++ b/xf86drm.c
@@ -4271,7 +4271,7 @@
> I found two more using "git grep 'define.*0x[0-9a-f]* < '":
I added '[0-9]\+' at the end of the regex to reduce the number of false
positives...
> drivers/net/can/m_can/m_can.c:#define RXFC_FWM_MASK (0x7f <
> RXFC_FWM_SHIFT)
> drivers/usb/gadget/udc/goku_udc.h:#define INT_EPnNAK(n)
> (0x0
Am 06.02.2018 um 11:23 schrieb Bas Nieuwenhuizen:
Otherwise we get an EFAULT, at least on a 64-bit kernel.
Fixes: 2048a9e7 "drm: add drmSyncobjWait wrapper"
Reviewed-by: Christian König
---
xf86drm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xf86drm.c b/xf86drm.
On Fri, Feb 2, 2018 at 12:59 PM, Arnd Bergmann wrote:
> On Fri, Feb 2, 2018 at 1:21 AM, Randy Dunlap wrote:
>> b. DRM configuration is a mess. You shouldn't want to follow their model. :)
>
> Right, that should also be fixed, so DRM no longer includes I2C ;-)
>
> At the moment, DRM is the most co
Instead of re-implementing the drm_atomic_helper_check() locally with just
adding drm_atomic_normalize_zpos() into it, set the
drm_mode_config->normalize_zpos.
Signed-off-by: Peter Ujfalusi
CC: Thierry Reding
Acked-by: Daniel Vetter
---
drivers/gpu/drm/tegra/drm.c | 27 +++-
Instead of re-implementing the drm_atomic_helper_check() locally with just
adding drm_atomic_normalize_zpos() into it, set the
drm_mode_config->normalize_zpos.
Signed-off-by: Peter Ujfalusi
CC: Inki Dae
CC: Joonyoung Shim
CC: Seung-Woo Kim
CC: Kyungmin Park
Acked-by: Daniel Vetter
---
drive
Instead of re-implementing the drm_atomic_helper_check() locally with just
adding drm_atomic_normalize_zpos() into it, set the
drm_mode_config->normalize_zpos.
Note: the drm_atomic_helper_check() now includes
if (state->legacy_cursor_update)
state->async_update = !drm_atomic_helper_async_
Hi,
Changes since v3:
- Moved the new normalize_zpos bool to be around another bools
- Extended the commit message for sti that the drm_atomic_helper_check() is
going to ask for async_update due to the legacy cursor usage.
Changes since v2:
- Fixed commit messages (s/drm_device/drm_mode_config)
Instead of drivers duplicating the drm_atomic_helper_check() code to be
able to normalize the zpos they can use the normalize_zpos flag to let the
drm core to do it.
Signed-off-by: Peter Ujfalusi
---
drivers/gpu/drm/drm_atomic_helper.c | 11 +++
include/drm/drm_mode_config.h | 8 +
Set the drm_mode_config->normalize_zpos and call drm_atomic_helper_check()
from rcar_du_atomic_check() instead of re implementing the function locally.
Signed-off-by: Peter Ujfalusi
CC: Laurent Pinchart
Acked-by: Daniel Vetter
---
drivers/gpu/drm/rcar-du/rcar_du_kms.c | 11 ++-
1 file
Planes with identical zpos value will result undefined behavior:
disappearing planes, screen flickering and it is not supported by the
hardware.
Use normalized zpos to make sure that we don't encounter invalid
configuration.
Signed-off-by: Peter Ujfalusi
CC: Tomi Valkeinen
Acked-by: Daniel Vett
We were previously selecting 1024x768 and 32BPP as the default
set-up for the PL111 consumers.
This does not work on elder systems: the device tree bindings
support a property "max-memory-bandwidth" in bytes/second that
states that if you exceed this the memory bus will saturate.
The result is fli
The PL110, Integrator and Versatile boards strongly prefer to
use 16 BPP even if other modes are supported, both to keep down
memory consumption and also to easier find a good match to
supported resolutions with consideration taken to the memory
bandwidth of the platforms.
Signed-off-by: Linus Wal
The PL111 needs to filter valid modes based on memory bandwidth.
I guess it is a pretty simple operation, so we can still claim
the DRM KMS helper pipeline is simple after adding this (optional)
vtable callback.
Signed-off-by: Linus Walleij
---
drivers/gpu/drm/drm_simple_kms_helper.c | 15 ++
I had to add a hook into the simple KMS helper to be able
to gate off too high bandwidths on the PL111.
Let me know what you think.
This solution is inspired by the OMAPDRM commit a7631c4b9846
"drm/omap: Filter displays mode based on bandwidth limit"
by Peter Ujfalusi.
I'm not super-happy that w
On Mon, Feb 05, 2018 at 08:05:39PM +0100, Ulf Magnusson wrote:
> The AVR32 symbol was removed in commit 26202873bb51 ("avr32: remove
> support for AVR32 architecture"). Remove the remaining references to it
> from the Kconfig files.
> drivers/spi/Kconfig | 2 +-
> drivers/video/console/
We deleted some code in e154162ef75d ("drm/amd/powerplay: refine pp code
for raven") but there were a few related bits that were missed. Let's
delete them as well.
Signed-off-by: Dan Carpenter
diff --git a/drivers/gpu/drm/amd/powerplay/inc/hwmgr.h
b/drivers/gpu/drm/amd/powerplay/inc/hwmgr.h
in
On 02/05/2018 05:03 PM, Gerd Hoffmann wrote:
On Mon, Feb 05, 2018 at 03:46:17PM +0100, Tomeu Vizoso wrote:
On 02/05/2018 01:20 PM, Gerd Hoffmann wrote:
Hi,
Why not use virtio-vsock to run the wayland protocol? I don't like
the idea to duplicate something with very simliar functionality in
On 06.02.2018 09:42, Philippe Cornu wrote:
> Add support for the Synopsys DesignWare MIPI DSI version 1.31
> Two registers need to be updated/added for supporting 1.31:
> * PHY_TMR_CFG 0x9c (updated)
> 1.30 [31:24] phy_hs2lp_time
>[23:16] phy_lp2hs_time
>[14: 0] max_rd_time
>
>
On Mon, Feb 05, 2018 at 09:09:57PM +0100, Wolfram Sang wrote:
> In one Renesas driver, I found a typo which turned an intended bit shift
> ('<<')
> into a comparison ('<'). Because this is a subtle issue, I looked tree wide
> for
> similar patterns. This small patch series is the outcome.
>
> Bu
On Tue, 6 Feb 2018, Dan Carpenter wrote:
> On Mon, Feb 05, 2018 at 09:09:57PM +0100, Wolfram Sang wrote:
> > In one Renesas driver, I found a typo which turned an intended bit shift
> > ('<<')
> > into a comparison ('<'). Because this is a subtle issue, I looked tree wide
> > for
> > similar p
On Tue, Feb 06, 2018 at 02:15:51PM +0100, Julia Lawall wrote:
>
>
> On Tue, 6 Feb 2018, Dan Carpenter wrote:
>
> > On Mon, Feb 05, 2018 at 09:09:57PM +0100, Wolfram Sang wrote:
> > > In one Renesas driver, I found a typo which turned an intended bit shift
> > > ('<<')
> > > into a comparison ('
Hi,
On 02-02-18 17:13, Ville Syrjälä wrote:
On Mon, Jan 29, 2018 at 03:47:34PM +0100, Hans de Goede wrote:
Add a new intel_bios_cleanup function to free memdup-ed bios data
structures and call it from i915_driver_unload().
Signed-off-by: Hans de Goede
---
drivers/gpu/drm/i915/i915_drv.c |
On Tue, 6 Feb 2018, Dan Carpenter wrote:
> On Tue, Feb 06, 2018 at 02:15:51PM +0100, Julia Lawall wrote:
> >
> >
> > On Tue, 6 Feb 2018, Dan Carpenter wrote:
> >
> > > On Mon, Feb 05, 2018 at 09:09:57PM +0100, Wolfram Sang wrote:
> > > > In one Renesas driver, I found a typo which turned an inte
Hi Julia,
> and got the results below. I can make a version for the kernel shortly.
It should probably take care of right-shifting, too?
Thanks,
Wolfram
signature.asc
Description: PGP signature
___
dri-devel mailing list
dri-devel@lists.freedes
On Tue, 6 Feb 2018, Wolfram Sang wrote:
> Hi Julia,
>
> > and got the results below. I can make a version for the kernel shortly.
>
> It should probably take care of right-shifting, too?
I did that too but got no results. Perhaps right shifting constants is
pretty uncommon. I can put that in
On Tue, Feb 06, 2018 at 01:10:26PM +0530, Aishwarya Pant wrote:
> Add documentation for sysfs interface of adp5520/adp5501 analog devices
> backlight driver by reading code and looking through git commit logs.
>
> Signed-off-by: Aishwarya Pant
> Acked-by: Michael Hennerich
Acked-by: Daniel Thom
On Tue, Feb 06, 2018 at 01:11:12PM +0530, Aishwarya Pant wrote:
> Add documentation for sysfs interface of adp8860 series backlight
> devices by reading through code and git commits.
>
> Signed-off-by: Aishwarya Pant
> Acked-by: Michael Hennerich
Acked-by: Daniel Thompson
> ---
> .../ABI/tes
> I did that too but got no results. Perhaps right shifting constants is
> pretty uncommon. I can put that in the complete rule though.
Please do. Even if rare, we would want this bug pointed out, right? :)
signature.asc
Description: PGP signature
That found 4 that I think Wolfram's grep missed.
arch/um/drivers/vector_user.h |2 --
drivers/gpu/drm/mxsfb/mxsfb_regs.h|2 --
drivers/video/fbdev/mxsfb.c |2 --
include/drm/drm_scdc_helper.h |3 ---
But it didn't find the two bugs tha
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #5 from ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk)
---
My best guess is the error came from
r600.c:2848:DRM_ERROR("radeon: ring %d test failed
(scratch(0x%04X)=0x%08X)\n",
I cannot reproduce the mechanic
On Tue, 6 Feb 2018, Dan Carpenter wrote:
> That found 4 that I think Wolfram's grep missed.
>
> arch/um/drivers/vector_user.h |2 --
> drivers/gpu/drm/mxsfb/mxsfb_regs.h|2 --
> drivers/video/fbdev/mxsfb.c |2 --
> include/drm/drm_scdc_helper.h
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #6 from Christian König (christian.koe...@amd.com) ---
Well the issue is triggered by the driver reading nonsense values from the
hardware.
E.g. we ask the hardware what the last good position on a 16k ring buffer is
and get 0xfff
Hi,
> > Hmm? I'm assuming the wayland client (in the guest) talks to the
> > wayland proxy, using the wayland protocol, like it would talk to a
> > wayland display server. Buffers must be passed from client to
> > server/proxy somehow, probably using fd passing, so where is the
> > problem?
>
Hello, Maarten!
On 02/01/2018 12:13 PM, Oleksandr Andrushchenko wrote:
On 02/01/2018 12:04 PM, Maarten Lankhorst wrote:
Op 01-02-18 om 08:08 schreef Oleksandr Andrushchenko:
Hi, all!
I am working on a para-virtualized frontend DRM driver for Xen [1]
which implements display device I/O interf
On Mon, 5 Feb 2018 17:03:22 +0100
Gerd Hoffmann wrote:
> On Mon, Feb 05, 2018 at 03:46:17PM +0100, Tomeu Vizoso wrote:
> > On 02/05/2018 01:20 PM, Gerd Hoffmann wrote:
> > >Hi,
> > >
>
> Hmm. I allways assumed the wayland client allocates the buffers, not
> the server. Is that wrong?
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #7 from ro...@beardandsandals.co.uk (ro...@beardandsandals.co.uk)
---
The original point I made in the bug report was that this bug is not about the
mechanical hardware glitch. It as about the driver being in what is obviously a
failu
Hi! I'm periodically getting following message in dmesg on Lenovo
Thinkpad X1 Carbon 3rd generation:
[drm] Reducing the compressed framebuffer size. This may lead to less power
savings than a non-reduced-size. Try to increase stolen memory size if
available in BIOS.
In BIOS I already set GPU si
Op 06-02-18 om 15:43 schreef Oleksandr Andrushchenko:
> Hello, Maarten!
>
>
> On 02/01/2018 12:13 PM, Oleksandr Andrushchenko wrote:
>> On 02/01/2018 12:04 PM, Maarten Lankhorst wrote:
>>> Op 01-02-18 om 08:08 schreef Oleksandr Andrushchenko:
Hi, all!
I am working on a para-virtualiz
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #8 from Christian König (christian.koe...@amd.com) ---
(In reply to ro...@beardandsandals.co.uk from comment #7)
> The original point I made in the bug report was that this bug is not about
> the mechanical hardware glitch. It as about
Quoting Tvrtko Ursulin (2018-02-06 14:31:07)
> +static u64 read_rc6_residency(struct drm_i915_private *i915)
> +{
> + u64 val;
> +
> + val = intel_rc6_residency_ns(i915, IS_VALLEYVIEW(i915) ?
> + VLV_GT_RENDER_RC6 :
> GEN6_GT_GFX_RC6);
> +
On Tue, Feb 06, 2018 at 11:59:37AM +0200, Oleksandr Andrushchenko wrote:
> Hello, Ville!
>
> Thank you very much for such a comprehensive answer.
>
> Please see inline
>
>
> On 02/05/2018 06:47 PM, Ville Syrjälä wrote:
> > On Mon, Feb 05, 2018 at 06:03:25PM +0200, Oleksandr Andrushchenko wrote:
On Tue, Feb 06, 2018 at 04:04:10PM +, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2018-02-06 14:31:07)
> > +static u64 read_rc6_residency(struct drm_i915_private *i915)
> > +{
> > + u64 val;
> > +
> > + val = intel_rc6_residency_ns(i915, IS_VALLEYVIEW(i915) ?
> > +
Hey all,
Here's a set which allows us to add an "override" mode to the simple
panel dt node. The override mode can be used for devices for which the
typical display timing is not sufficient, yet the overriding mode should
not be applied across the entire platform.
An example of this (and the moti
This patch adds the ability to override the typical display timing for a
given panel. This is useful for devices which have timing constraints
that do not apply across the entire display driver (eg: to avoid
crosstalk between panel and digitizer on certain laptops). The rules are
as follows:
- pan
Convert the sharp lq123p1jx31 from using a fixed mode to specifying a
display timing with min/typ/max values. This allows us to capture the
timings set forth in the datasheet as well as the additional values that
we've cleared with the display vendor to avoid interference with the
digitizer on the
This patch adds an override mode for kevin devices. The mode increases
both back porches to allow a pixel clock of 2kHz as opposed to the
'typical' value of 252750kHz. This is needed to avoid interference with
the touch digitizer on these laptops.
Cc: Doug Anderson
Cc: Heiko Stuebner
Cc: Jef
On 06/02/2018 16:10, Imre Deak wrote:
On Tue, Feb 06, 2018 at 04:04:10PM +, Chris Wilson wrote:
Quoting Tvrtko Ursulin (2018-02-06 14:31:07)
+static u64 read_rc6_residency(struct drm_i915_private *i915)
+{
+ u64 val;
+
+ val = intel_rc6_residency_ns(i915, IS_VALLEYVIEW(i915) ?
https://bugs.freedesktop.org/show_bug.cgi?id=104963
--- Comment #1 from Alex Deucher ---
Does booting with radeon.bapm=0 or radeon.bapm=1 on the kernel command line in
grub help?
--
You are receiving this mail because:
You are the assignee for the bug.___
On Mon, Jun 12, 2017 at 12:10:04AM +0300, Jyri Sarha wrote:
> Add a standard optional properties to support different non RGB color
> encodings in DRM planes. COLOR_ENCODING select the supported non RGB
> color encoding, for instance ITU-R BT.709 YCbCr. COLOR_RANGE selects
> the value ranges within
On 02/06/2018 06:58 PM, Ville Syrjälä wrote:
> On Mon, Jun 12, 2017 at 12:10:04AM +0300, Jyri Sarha wrote:
>> Add a standard optional properties to support different non RGB color
>> encodings in DRM planes. COLOR_ENCODING select the supported non RGB
>> color encoding, for instance ITU-R BT.709 YC
On Tue, Feb 06, 2018 at 08:16:56PM +0200, Jyri Sarha wrote:
>
> I have not been following the subject for half a year now. Just let me
> know if I can do something to help land this patch, e.g. rebase and
> resend it.
I guess I can just pick it up and repost along with my i915 stuff. I can
just t
On Tue, Feb 06, 2018 at 07:08:34PM +0100, Hans Verkuil wrote:
> On 02/06/2018 06:58 PM, Ville Syrjälä wrote:
> > On Mon, Jun 12, 2017 at 12:10:04AM +0300, Jyri Sarha wrote:
> >> Add a standard optional properties to support different non RGB color
> >> encodings in DRM planes. COLOR_ENCODING select
https://bugs.freedesktop.org/show_bug.cgi?id=100105
Bug 100105 depends on bug 100212, which changed state.
Bug 100212 Summary: Implement vload_* and vstore_* to make Theano/libgpuarray
working
https://bugs.freedesktop.org/show_bug.cgi?id=100212
What|Removed |Ad
https://bugs.freedesktop.org/show_bug.cgi?id=100212
Jan Vesely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Bug 99553 depends on bug 100212, which changed state.
Bug 100212 Summary: Implement vload_* and vstore_* to make Theano/libgpuarray
working
https://bugs.freedesktop.org/show_bug.cgi?id=100212
What|Removed |Adde
https://bugs.freedesktop.org/show_bug.cgi?id=102423
--- Comment #6 from pmarget...@gmail.com ---
Plasma updated to 5.12 today, and I no longer can reproduce this bug. I guess
this was on their end afterall.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=104194
--- Comment #3 from saunders...@wright.edu ---
I am having this issue as well on 4.15.1 without DC enabled (as well as DC
enabled) on a RX 460. Will try the cable replug on GPU side (didn't work on
monitor side.)
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=104194
--- Comment #4 from saunders...@wright.edu ---
Unplugging and replugging the cable on the GPU side causes the monitor to be
detected without DC enabled. (Haven't checked with DC.)
--
You are receiving this mail because:
You are the assignee for
On Tue, Feb 6, 2018 at 7:35 AM, Dan Carpenter wrote:
> We deleted some code in e154162ef75d ("drm/amd/powerplay: refine pp code
> for raven") but there were a few related bits that were missed. Let's
> delete them as well.
>
> Signed-off-by: Dan Carpenter
Applied. Thanks!
Alex
>
> diff --git
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #13 from Alex Deucher ---
https://lkml.org/lkml/2018/1/10/132
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedeskt
On Tue, Feb 6, 2018 at 10:56 AM, Sean Paul wrote:
> This patch adds the ability to override the typical display timing for a
> given panel. This is useful for devices which have timing constraints
> that do not apply across the entire display driver (eg: to avoid
> crosstalk between panel and digi
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #14 from Przemek ---
Yes, sorry, my bad. Wrong copy-paste action here. Thanks Alex.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri
1 - 100 of 133 matches
Mail list logo
