Hi Linus,
Just back online for a couple of days, gathered up the remaining fixes
pull requests, fixes
for a few ARM platforms (msm, tilcdc, meson), and one core atomic fix. The AMD
pull has some new hardware support (Polaris12) in it, but this is
pretty limited to just
hw enablement and shouldn't
On 7 January 2017 at 00:56, Vincent Abriou wrote:
> Hi Dave,
>
> Here is an update of the STI drm driver.
> It contains file cleanup and various fixes.
>
> Regard,
> Vincent
>
> The following changes since commit 2cf026ae85c42f253feb9f420d1b4bc99bd5503d:
>
> Merge branch 'linux-4.10' of
.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/24e3914c/attachment-0001.html>
--
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/633b5c1f/attachment.html>
tps://lists.freedesktop.org/archives/dri-devel/attachments/20170109/0ea9237a/attachment.html>
.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/cafd0959/attachment.html>
:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/63e45589/attachment.html>
Regards
Shashank
On 12/30/2016 10:23 PM, Jose Abreu wrote:
> HDMI 2.0 introduces a new sampling mode called YCbCr 4:2:0.
> According to the spec the EDID may contain two blocks that
> signal this sampling mode:
> - YCbCr 4:2:0 Video Data Block
> - YCbCr 4:2:0 Video Capability Map
Hello all,
I'm experiencing display noise in the form of 8x1 pixel bars spuriously
appearing in random locations. This doesn't happen on 4.9, the machine
is an X61s, a Core2Duo 1.8Ghz w/XGA via LVDS.
I was able to bisect the issue to a6a7cc4b7:
commit a6a7cc4b7db6deaeca11cdd38844ea147a354c7a
On Sunday 08 January 2017 01:14 AM, Chris Wilson wrote:
> On Sat, Jan 07, 2017 at 11:42:04PM +0530, vathsala nagaraju wrote:
>> As per bpsec, CHICKEN_TRANS_EDP bit 12 ,15
>> must be programmed.
>> Enable bit 12 for programmable header packet.
>> Enable bit 15 for Y cordinate support.
>>
>> v2:
--
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/11a7d58b/attachment.html>
:
You are on the CC list for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/be1dc8b3/attachment.html>
next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/380b4fe8/attachment.html>
From: Shawn Guo
ZTE DRM driver uses drm_display_mode_to_videomode() in function
zx_crtc_enable(). Select VIDEOMODE_HELPERS in Kconfig to fix the
following link error.
LD vmlinux.o
MODPOST vmlinux.o
drivers/built-in.o: In function `zx_crtc_enable':
From: Shawn Guo
ZTE DRM driver uses drm_display_mode_to_videomode() in function
zx_crtc_enable(). Select VIDEOMODE_HELPERS in Kconfig to fix the
following link error.
LD vmlinux.o
MODPOST vmlinux.o
drivers/built-in.o: In function `zx_crtc_enable':
On 06.01.2017 09:36, Inki Dae wrote:
>
> 2017ë
01ì 06ì¼ 17:18ì Andi Shyti ì´(ê°) ì´ ê¸:
>> Hi Inki,
>>
>> Thanks for the reply, but...
>>
> +static const struct drm_display_mode default_mode = {
> + .clock = 222372,
> + .hdisplay = 1440,
> + .hsync_start = 1440 + 1,
On Fri, Dec 30, 2016 at 12:16:43PM +0100, Daniel Vetter wrote:
> Entire series applied. I suspect that there's more drivers open-coding
> something like this in their vblank code, might be worth it to grep for
> them all and do a quick audit.
I did a round of audit on all drivers vblank code, and
On 6 January 2017 at 16:56, Sean Paul wrote:
> On Fri, Jan 6, 2017 at 9:30 AM, Tomeu Vizoso
> wrote:
>> This backpointer allows DP helpers to access the connector it's being
>> used for.
>>
>> Signed-off-by: Tomeu Vizoso
>> ---
>>
>> include/drm/drm_dp_helper.h | 2 ++
>> 1 file changed, 2
2017ë
01ì 09ì¼ 16:37ì Andrzej Hajda ì´(ê°) ì´ ê¸:
> On 06.01.2017 09:36, Inki Dae wrote:
>>
>> 2017ë
01ì 06ì¼ 17:18ì Andi Shyti ì´(ê°) ì´ ê¸:
>>> Hi Inki,
>>>
>>> Thanks for the reply, but...
>>>
>> +static const struct drm_display_mode default_mode = {
>> +
ment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/f8156cd4/attachment.sig>
On 01/05/2017 01:01 PM, Sean Paul wrote:
> On Fri, Dec 30, 2016 at 4:57 AM, Marek Szyprowski
> wrote:
>> Analogix_dp_bind() can be called from component framework, which doesn't
>> guarantee proper runtime PM state of the device during bind operation,
>> so ensure that device is runtime active
On 09.01.2017 10:19, Inki Dae wrote:
>
> 2017ë
01ì 09ì¼ 16:37ì Andrzej Hajda ì´(ê°) ì´ ê¸:
>> On 06.01.2017 09:36, Inki Dae wrote:
>>> 2017ë
01ì 06ì¼ 17:18ì Andi Shyti ì´(ê°) ì´ ê¸:
Hi Inki,
Thanks for the reply, but...
>>> +static const struct
On Mon, Jan 09, 2017 at 05:03:35PM +0800, Shawn Guo wrote:
> On Fri, Dec 30, 2016 at 12:16:43PM +0100, Daniel Vetter wrote:
> > Entire series applied. I suspect that there's more drivers open-coding
> > something like this in their vblank code, might be worth it to grep for
> > them all and do a
On Fri, Jan 06, 2017 at 03:39:40PM -0500, Andrey Grodzovsky wrote:
> Allows usage of the new page_flip_target hook for drivers implementing
> the atomic path.
> Provides default atomic helper for the new hook.
>
> v2:
> Update code sharing logic between exsiting and the new flip hooks.
> Improve
On Thu, Jan 05, 2017 at 03:23:24PM +, Fabien DESSENNE wrote:
> Hi Daniel
>
>
> I come to the conclusion that (only) Atomic Weston will solve all of my
> troubles, so let's forget these patches (and work for atomic weston).
>
> By the way, is the expected behavior (Vblank - sync'ed or not)
https://bugzilla.kernel.org/show_bug.cgi?id=192161
Bug ID: 192161
Summary: Amdgpu UVD init failures at boot
Product: Drivers
Version: 2.5
Kernel Version: 4.10-rc2
Hardware: x86-64
OS: Linux
Tree: Mainline
On Thu, Jan 05, 2017 at 11:03:44AM -0800, Dave Hansen wrote:
> My Thinkpad x260 doesn't like to be unplugged from its dock. I don't
> think this is a new bug. It's happening on my distro's 4.4 kernel
> as well.
>
> The actual oops is in device_del(). It appears to have been passed a
> null
On Thu, Jan 05, 2017 at 05:45:23PM -0600, Nicholas Sielicki wrote:
> As per the HDMI 1.3 and 1.4 spec, "deep color modes" are color depths
> greater than 24 bits per pixel. The spec explicitly states, "All Deep
> Color modes are optional though if an HDMI Source or Sink supports any
> Deep Color
On Fri, Jan 06, 2017 at 01:04:55PM -0800, Chad Versace wrote:
> Was this a mistake in the API? If so, can we fix this ABI mistake before
> kernel consumers rely on this?
>
> I naïvely expected that OUT_FENCE_PTR would be a pointer to, obviously, a
> fence
> fd (s32 __user *). But it's not. It's
On Sat, Jan 07, 2017 at 04:52:11PM +0800, Shawn Guo wrote:
> From: Shawn Guo
>
> Add a bit more document for function drm_crtc_from_index() to cross
> link it with drm_crtc_from_index(), and explain that the function is
> useful in vblank code.
>
> While at it, add cross link comment for
On Fri, Jan 06, 2017 at 05:44:43PM +0100, Vincent Abriou wrote:
> drm_pick_cmdline_mode width and height parameters are useless.
> Just remove them.
>
> Cc: Daniel Vetter
> Cc: Jani Nikula
> Signed-off-by: Vincent Abriou
Applied, thanks a lot. I'll wait for someone else to review patch 2
On Sat, Jan 07, 2017 at 12:39:11PM +0100, Benjamin Gaignard wrote:
> Removing MMU configuration flag from DRM make few automatic
> build failed when they answer yes to all flags.
>
> Add asm/vga.h file on Blackfin architecture to not broke compilation.
>
> Signed-off-by: Benjamin Gaignard
On Thu, 05 Jan 2017, Randy Dunlap wrote:
> That particular circular/recursive dependency is ugly. I spent about
> one hour trying/testing various fixes and don't have one.
I didn't really look at this one all that much, but when I face problems
with kconfig, it's almost invariably because of
From: Shawn Guo
This is a follow-up series for "[PATCH 0/3] Add CRTC helper
drm_crtc_from_index()" per Daniel's comment [1].
Basically, it changes some drivers to use helper drm_crtc_from_index()
for the vblank code, so that either they do not need to store CRTC
pointers
From: Shawn Guo
Use drm_crtc_from_index() to find drm_crtc for given index, so that we
do not need to maintain a pointer array in struct kirin_drm_private.
Signed-off-by: Shawn Guo
Cc: Xinliang Liu
---
drivers/gpu/drm/hisilicon/kirin/kirin_drm_ade.c | 10 --
From: Shawn Guo
Use drm_crtc_from_index() to find drm_crtc for given index, so that we
do not need to maintain a pointer array in struct exynos_drm_private.
Signed-off-by: Shawn Guo
Cc: Inki Dae
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 6 --
From: Shawn Guo
Use drm_crtc_from_index() to find drm_crtc for given index.
Signed-off-by: Shawn Guo
Cc: Ben Skeggs
---
drivers/gpu/drm/nouveau/nouveau_display.c | 33 +--
1 file changed, 18 insertions(+), 15 deletions(-)
diff --git
From: Shawn Guo
Use drm_crtc_from_index() to find drm_crtc for given index, so that we
do not need to maintain a pointer array in struct mtk_drm_private.
Signed-off-by: Shawn Guo
Cc: CK Hu
---
drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 9 -
From: Shawn Guo
Use drm_crtc_from_index() to find drm_crtc for given index, so that we
do not need to maintain a pointer array in struct vc4_dev.
Signed-off-by: Shawn Guo
Cc: Eric Anholt
---
drivers/gpu/drm/vc4/vc4_crtc.c | 17 +++--
From: Shawn Guo
Function tegra_crtc_from_pipe() does the exactly same thing as what
crtc helper drm_crtc_from_index() provides. Use the helper to save
some code.
Signed-off-by: Shawn Guo
Cc: Thierry Reding
---
drivers/gpu/drm/tegra/drm.c | 19 +++
1
From: Shawn Guo
Although it can help to clean up driver code quite a bit, I'm not sure
it's been done in the right way. So the series can be treated as RFC.
When I was going through DRM drivers for candidates of using
drm_crtc_from_index() helper, I found vblank handling
From: Shawn Guo
The vblank is mostly CRTC specific and implemented as part of CRTC
driver. So having vblank hooks in struct drm_crtc_funcs should
generally help to reduce code from client drivers in implementing
drm_driver's vblank callbacks.
Signed-off-by: Shawn Guo
---
From: Shawn Guo
With the vblank hooks in struct drm_crtc_funcs, we can directly use the
drm_crtc pointer passed in as parameter and make the functions static.
The functions are moved around to save forward delarations.
Signed-off-by: Shawn Guo
---
From: Shawn Guo
With the vblank hooks in struct drm_crtc_funcs, we do not need to
maintain the CRTC specific vblank callbacks with struct
imx_drm_crtc_helper_funcs any more. By moving the stuff that we
currently do in imx_drm_add_crtc(), like of_node setting and
From: Shawn Guo
With the vblank hooks in struct drm_crtc_funcs, we do not need to
maintain struct rockchip_crtc_funcs and the related registration
functions. Remove them.
Signed-off-by: Shawn Guo
Cc: Mark Yao
---
drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 53
Regards
Shashank
On 1/9/2017 4:41 PM, Jose Abreu wrote:
> Hi Shashank,
>
>
> Thanks for the review.
>
>
> On 09-01-2017 05:22, Sharma, Shashank wrote:
>> Regards
>>
>> Shashank
>>
>>
>> On 12/30/2016 10:23 PM, Jose Abreu wrote:
>>> HDMI 2.0 introduces a new sampling mode called YCbCr 4:2:0.
>>>
On 6 January 2017 at 16:56, Sean Paul wrote:
> On Fri, Jan 6, 2017 at 9:30 AM, Tomeu Vizoso
> wrote:
>> Adds helpers for starting and stopping capture of frame CRCs through the
>> DPCD. When capture is on, a worker waits for vblanks and retrieves the
>> frame CRC to put it in the queue on the
On 6 January 2017 at 16:56, Sean Paul wrote:
> On Fri, Jan 6, 2017 at 9:30 AM, Tomeu Vizoso
> wrote:
>> Implement the .set_crc_source() callback and call the DP helpers
>> accordingly to start and stop CRC capture.
>>
>> This is only done if this CRTC is currently using the eDP connector.
>>
>>
Regards
Shashank
On 1/9/2017 6:53 PM, Jose Abreu wrote:
> Hi Shashank,
>
>
> On 09-01-2017 12:45, Sharma, Shashank wrote:
>> Regards
>>
>> Shashank
>>
>>
>> On 1/9/2017 4:41 PM, Jose Abreu wrote:
>>> Hi Shashank,
>>>
>>>
>>> Thanks for the review.
>>>
>>>
>>> On 09-01-2017 05:22, Sharma,
Hi,
this series builds up on the API for exposing captured CRCs through
debugfs.
It adds new DP helpers for starting and stopping CRC capture and gets
the Rockchip driver to use it.
Also had to add a connector backpointer to the drm_dp_aux struct so we could
wait for the right vblank and store
Set the backpointer so that the DP helpers are able to access the
connector that the drm_dp_aux is associated with.
Signed-off-by: Tomeu Vizoso
---
drivers/gpu/drm/bridge/analogix/analogix_dp_core.c | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git
Implement the .set_crc_source() callback and call the DP helpers
accordingly to start and stop CRC capture.
This is only done if this CRTC is currently using the eDP connector.
v3: Remove superfluous check on rockchip_crtc_state->output_type
Signed-off-by: Tomeu Vizoso
---
Add two simple functions that just take the drm_dp_aux from our struct
and calls the corresponding DP helpers with it.
Signed-off-by: Tomeu Vizoso
---
drivers/gpu/drm/bridge/analogix/analogix_dp_core.c | 16
include/drm/bridge/analogix_dp.h | 3 +++
2 files
This backpointer allows DP helpers to access the connector it's being
used for.
Signed-off-by: Tomeu Vizoso
---
include/drm/drm_dp_helper.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/drm/drm_dp_helper.h b/include/drm/drm_dp_helper.h
index 55bbeb0ff594..4fa77b434594 100644
Adds helpers for starting and stopping capture of frame CRCs through the
DPCD. When capture is on, a worker waits for vblanks and retrieves the
frame CRC to put it in the queue on the CRTC that is using the
eDP connector, so it's passed to userspace.
v2: Reuse drm_crtc_wait_one_vblank
Update
On Mon, 09 Jan 2017, vcaputo at pengaru.com wrote:
> Hi All,
>
> Booted 4.10-rc2 today, and the display shows random spots of flickering
> short horizontal bars 1px tall, maybe 8 or 16px wide. Machine is the
> venerable X61s thinkpad, 1.8ghz, XGA. Problem was not present on 4.9.0,
> same kernel
was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/266907c5/attachment.html>
On Thu, Jan 05, 2017 at 02:26:30AM -0500, Sean Paul wrote:
> > +static u32 zx_vl_get_fmt(uint32_t format)
> > +{
> > + u32 val = 0;
> > +
> > + switch (format) {
> > + case DRM_FORMAT_NV12:
> > + val = VL_FMT_YUV420;
> > + break;
> > + case
Improper usage of DECON_UPDATE register leads to subtle errors.
If it set in decon_commit when there are no active windows it results
in slow registry updates - all subsequent shadow registry updates takes more
than full vblank. On the other side if it is not set when there are
active windows it
From: Shawn Guo
Changes for v4:
- Instead of using val, return value directly for zx_vl_get_fmt() and
zx_vl_rsz_get_fmt().
- Fix typo of 'heigth'
- Add 'enabled' in struct zx_plane to track layer enabling state, and
check the state in zx_plane_set_update(), so that
From: Shawn Guo
Move struct zx_plane from zx_plane.c to zx_plane.h, so that it can be
accessed from zx_vou driver, and we can save the use of struct
zx_layer_data completely. More importantly, those additional data used
by VOU controller to enable/disable graphic and video
From: Shawn Guo
There are a few hardware bits for each graphic layer to control main/aux
channel and clock selection, as well as the layer enabling. These bits
sit outside the layer block itself, but in VOU control glue block. We
currently set these bits up at CRTC
From: Shawn Guo
It enables VOU VL (Video Layer) to support overlay plane with scaling
function. VL0 has some quirks on scaling support. We choose to skip it
and only adds VL1 and VL2 into DRM core for now.
Function zx_plane_atomic_disable() gets moved around with no
Hi Chris,
On 4 January 2017 at 19:42, Chris Wilson wrote:
> The dma_fence.error field (formerly known as dma_fence.status) is an
> optional field that may be set by drivers before calling
> dma_fence_signal(). The field can be used to indicate that the fence was
> completed in err rather than
I noticed that the VT switch doesn't work any longer with a Dell
laptop with 1366x768 eDP when the machine is connected with a DP
monitor. It behaves as if VT were switched, but the graphics remain
frozen. Actually the keyboard works, so I could switch back to VT7
again.
I tried to track down
On Mon, Jan 09, 2017 at 08:13:11PM +0530, Sumit Semwal wrote:
> Hi Chris,
>
> On 4 January 2017 at 19:42, Chris Wilson wrote:
> > The dma_fence.error field (formerly known as dma_fence.status) is an
> > optional field that may be set by drivers before calling
> > dma_fence_signal(). The field
:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/4efec96e/attachment.html>
-
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/63c34214/attachment.html>
normally and while inverted?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/2c3af6f9/attachment.html>
bug.
>
>
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/cb273f15/attachment-0001.html>
...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/eec21687/attachment.html>
On Mon, Jan 9, 2017 at 6:25 AM, Shawn Guo wrote:
> From: Shawn Guo
>
> This is a follow-up series for "[PATCH 0/3] Add CRTC helper
> drm_crtc_from_index()" per Daniel's comment [1].
>
> Basically, it changes some drivers to use helper drm_crtc_from_index()
> for the vblank code, so that either
On Mon, Jan 9, 2017 at 9:35 AM, Shawn Guo wrote:
> From: Shawn Guo
>
> It enables VOU VL (Video Layer) to support overlay plane with scaling
> function. VL0 has some quirks on scaling support. We choose to skip it
> and only adds VL1 and VL2 into DRM core for now.
>
> Function
On Mon, Jan 9, 2017 at 2:40 PM, Dave Hansen wrote:
> Well, now I found where the -2 comes from.
> intel_dp_register_mst_connector() calls drm_connector_register(), which
> fails to add the kobject (warning below). But, it does zero error
> checking on the drm_connector_register() call and leaves
On Mon, Jan 9, 2017 at 4:03 AM, Tomeu Vizoso
wrote:
> On 6 January 2017 at 16:56, Sean Paul wrote:
>> On Fri, Jan 6, 2017 at 9:30 AM, Tomeu Vizoso
>> wrote:
>>> This backpointer allows DP helpers to access the connector it's being
>>> used for.
>>>
>>> Signed-off-by: Tomeu Vizoso
>>> ---
>>>
On Mon, Jan 9, 2017 at 8:32 AM, Tomeu Vizoso
wrote:
> Adds helpers for starting and stopping capture of frame CRCs through the
> DPCD. When capture is on, a worker waits for vblanks and retrieves the
> frame CRC to put it in the queue on the CRTC that is using the
> eDP connector, so it's passed
On Mon, Jan 9, 2017 at 9:31 AM, Peter Ujfalusi wrote:
> Instead of scheduling the work to handle the initial delayed event, use 1s
> delay.
>
> This delay should not be needed, but Optimus/nouveau will fail in a
> mysterious way if the delayed event is handled as soon as possible like it
Has
On 2 January 2017 at 13:53, Thierry Reding wrote:
> On Sat, Dec 24, 2016 at 05:00:27PM +, Emil Velikov wrote:
>> On 23 December 2016 at 17:49, Thierry Reding
>> wrote:
>> > From: Thierry Reding
>> >
>> > ARM SoCs usually have their DRM/KMS devices on the platform bus, so add
>> > support
On Mon, Jan 9, 2017 at 5:50 PM, Dave Hansen wrote:
> On 01/09/2017 08:41 AM, Daniel Vetter wrote:
>> On Mon, Jan 9, 2017 at 2:40 PM, Dave Hansen wrote:
>>> Well, now I found where the -2 comes from.
>>> intel_dp_register_mst_connector() calls drm_connector_register(), which
>>> fails to add the
e the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/52ce6e29/attachment.html>
This will allow i915 to perform a wait on pending modeset using the
same code.
Signed-off-by: Maarten Lankhorst
---
drivers/gpu/drm/drm_atomic_helper.c | 51 +++--
include/drm/drm_atomic_helper.h | 1 +
2 files changed, 38 insertions(+), 14 deletions(-)
Fix hw_done in i915 and make nouveau use drm_atomic_helper_disable_all()
after fixing it to properly disable everything.
Maarten Lankhorst (3):
drm/atomic: move waiting for hw_done to a helper
drm/i915: Wait for pending modesets to complete before trying link
training
drm/atomic: Make
It seems that nouveau requires this, so best to do this in the helper.
This allows nouveau to use the atomic suspend helper.
Cc: nouveau at lists.freedesktop.org
Signed-off-by: Maarten Lankhorst
---
drivers/gpu/drm/drm_atomic_helper.c | 51 ++
We're protected by the connection_mutex lock against blocking modesets,
but nonblocking modesets are performed without any locking. This is
causing WARN in drm_wait_for_vblank and in general it's better to wait
before modeset completes before trying anything.
Signed-off-by: Maarten Lankhorst
---
On Mon, 2017-01-09 at 18:26 +0530, vathsala nagaraju wrote:
> Psr1 and psr2 are mutually exclusive,ie when psr2 is enabled,
> psr1 should be disabled.When psr2 is exited , bit 31 of reg
> PSR2_CTL must be set to 0 but currently bit 31 of SRD_CTL
> (psr1 control register)is set to 0.
> Also
ail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/e8d84d78/attachment.html>
On 01/09/2017 02:15 AM, Daniel Vetter wrote:
...
> Can you pls do some printk tracing to make sure that without your patch
> we're indeed releasing the same connector twice from this loop? I suspect
> you're just ever-so-slightly shifting the timing and things blow up
> somewhre else. But no idea
Well, now I found where the -2 comes from.
intel_dp_register_mst_connector() calls drm_connector_register(), which
fails to add the kobject (warning below). But, it does zero error
checking on the drm_connector_register() call and leaves the
partially-constructed connector in place.
The next
On 01/09/2017 08:59 AM, Daniel Vetter wrote:
> On Mon, Jan 9, 2017 at 5:50 PM, Dave Hansen wrote:
>> On 01/09/2017 08:41 AM, Daniel Vetter wrote:
>>> On Mon, Jan 9, 2017 at 2:40 PM, Dave Hansen
>>> wrote:
Well, now I found where the -2 comes from.
intel_dp_register_mst_connector()
On 01/09/2017 08:59 AM, Daniel Vetter wrote:
> On Mon, Jan 9, 2017 at 5:50 PM, Dave Hansen wrote:
>> On 01/09/2017 08:41 AM, Daniel Vetter wrote:
>>> On Mon, Jan 9, 2017 at 2:40 PM, Dave Hansen
>>> wrote:
Well, now I found where the -2 comes from.
intel_dp_register_mst_connector()
Instead of scheduling the work to handle the initial delayed event, use 1s
delay.
This delay should not be needed, but Optimus/nouveau will fail in a
mysterious way if the delayed event is handled as soon as possible like it
is done in drm_helper_probe_single_connector_modes() in case the poll
Psr1 and psr2 are mutually exclusive,ie when psr2 is enabled,
psr1 should be disabled.When psr2 is exited , bit 31 of reg
PSR2_CTL must be set to 0 but currently bit 31 of SRD_CTL
(psr1 control register)is set to 0.
Also ,PSR2_IDLE state is looked up from SRD_STATUS(psr1 register)
instead of
As per bpsec, CHICKEN_TRANS_EDP bit 12 ,15 must be programmed in
psr2 enable sequence.
Program Transcoder EDP VSC DIP header with a valid setting for PSR2
and Set CHICKEN_TRANS_EDP(0x420cc) bit 12 for programmable header
packet.
Set CHICKEN_TRANS_EDP(0x420cc) bit 15 if Y coordinate is supported
On 01/09/2017 08:41 AM, Daniel Vetter wrote:
> On Mon, Jan 9, 2017 at 2:40 PM, Dave Hansen wrote:
>> Well, now I found where the -2 comes from.
>> intel_dp_register_mst_connector() calls drm_connector_register(), which
>> fails to add the kobject (warning below). But, it does zero error
>>
On 01/09/2017 05:40 AM, Dave Hansen wrote:
> Is there some stable code to go back to here? Or, is there something
> about my configuration that's unique? I really wonder why nobody else
> is running into this.
Here are a couple of similar-looking reports, if that helps:
Hi Shashank,
Thanks for the review.
On 09-01-2017 05:22, Sharma, Shashank wrote:
> Regards
>
> Shashank
>
>
> On 12/30/2016 10:23 PM, Jose Abreu wrote:
>> HDMI 2.0 introduces a new sampling mode called YCbCr 4:2:0.
>> According to the spec the EDID may contain two blocks that
>> signal this
Hi Shashank,
On 09-01-2017 12:45, Sharma, Shashank wrote:
> Regards
>
> Shashank
>
>
> On 1/9/2017 4:41 PM, Jose Abreu wrote:
>> Hi Shashank,
>>
>>
>> Thanks for the review.
>>
>>
>> On 09-01-2017 05:22, Sharma, Shashank wrote:
>>> Regards
>>>
>>> Shashank
>>>
>>>
>>> On 12/30/2016 10:23 PM,
Declare exynos_drm_crtc_ops structures as const as they are only passed
as an argument to the function exynos_drm_crtc_create. This argument is
of type const struct exynos_drm_crtc_ops *, so exynos_drm_crtc_ops
structures having this property can be declared const.
Done using Coccinelle:
@r
for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20170109/d8e3a459/attachment.html>
Hi Dave,
Back to regular -misc pulls with reasonable sizes:
- dma_fence error clarification (Chris)
- drm_crtc_from_index helper (Shawn), pile more patches on the m-l to roll
this out to drivers
- mmu-less support for fbdev helpers from Benjamin
- piles of kerneldoc work
- some polish for crc
1 - 100 of 118 matches
Mail list logo