https://bugzilla.kernel.org/show_bug.cgi?id=86011
JoaquÃn AramendÃa changed:
What|Removed |Added
Attachment #153941|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=86011
JoaquÃn AramendÃa changed:
What|Removed |Added
CC||alexdeucher at gmail.com
Kernel
https://bugzilla.kernel.org/show_bug.cgi?id=84431
JoaquÃn AramendÃa changed:
What|Removed |Added
CC||samsagax at gmail.com
--- Comment #
Hi Dave,
Resending the pull request with additional small fixes Dan.C has sent
over the last few days. Highlights:
- Fixes for sparse warnings
- Memory leak fixes
- Fix for deadlock between amdkfd and iommu
The following changes since commit 0a3d775fb2c951d1bd3f5f916eee55face0eaada:
MAINTAIN
- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141126/88afffb8/attachment.html>
On Wed, Nov 26, 2014 at 10:29 AM, Christian König
wrote:
> From: Christian König
>
> Not just the userspace relocs, otherwise we won't wait
> for a swapped out page tables to be swapped in again.
>
> Signed-off-by: Christian König
> Cc: stable at vger.kernel.org
Pulled into my -next tree. U
Rockchip RK3288 hdmi is compatible with dw_hdmi
this patch is depend on patch by Mark Yao Add drm
driver for Rockchip Socs
see https://lkml.org/lkml/2014/11/19/1153
Signed-off-by: Andy Yan
---
Changes in v13: None
Changes in v12:
- add comment for the depend on patch
Changes in v11: None
Cha
Signed-off-by: Andy Yan
---
Changes in v13: None
Changes in v12: None
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8:
- Add documentation for rockchip dw hdmi
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
.../d
RK3288 HDMI will not work without the spare bit of
HDMI_PHY_CONF0 enable
Signed-off-by: Andy Yan
---
Changes in v13: None
Changes in v12: None
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8: None
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in
HDMI_IH_I2CMPHY_STAT0 is a clear on write register, which indicates i2cm
operation status(i2c transfer done or error), every hdmi phy register
configuration must check this register to make sure the configuration
has complete. But the indication bit should be cleared after check, otherwise
the corr
some platform may not support all the display mode,
add mode_valid interface check it
also add drm_connector_register which add a debugfs
interface for dump display modes and edid information
Signed-off-by: Andy Yan
---
Changes in v13: None
Changes in v12: None
Changes in v11: None
Changes in v
On rockchip rk3288, only word(32-bit) accesses are
permitted for hdmi registers. Byte width accesses (writeb,
readb) generate an imprecise external abort.
Signed-off-by: Andy Yan
---
Changes in v13: None
Changes in v12: None
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes
Signed-off-by: Andy Yan
---
Changes in v13: None
Changes in v12: None
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8:
- correct some spelling mistake
- modify ddc-i2c-bus and interrupt description
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes i
the original imx hdmi driver is under drm/imx/,
which depends on imx-drm, so move the imx hdmi
driver out to drm/bridge and rename it to dw_hdmi
Signed-off-by: Andy Yan
---
Changes in v13: None
Changes in v12: None
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8: None
hdmi phy configuration is platform specific, which can be adusted
according to the board to get the best SI
Signed-off-by: Andy Yan
---
Changes in v13:
- split phy configuration from patch#4
Changes in v12: None
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8: None
On Tue, Nov 25, 2014 at 10:25 PM, Dave Airlie wrote:
> From: Dave Airlie
>
> At least on two MST devices I've tested with, when
> they are link training downstream, they are totally
> unable to handle aux ch msgs, so they defer like nuts.
> I tried 16, it wasn't enough, 32 seems better.
>
> This
IMX6 and Rockchip RK3288 and JZ4780 (Ingenic Xburst/MIPS)
use the interface compatible Designware HDMI IP, but they
also have some lightly differences, such as phy pll configuration,
register width, 4K support, clk useage, and the crtc mux configuration
is also platform specific.
To reuse the imx
drm driver may probe before the i2c bus, so the driver should
defer probing until it is available
Signed-off-by: Andy Yan
Reviewed-by: Daniel Kurtz
---
Changes in v13: None
Changes in v12:
- refactor of_node_put(ddc_node)
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes i
CHECK: Alignment should match open parenthesis
+ if ((hdmi->vic == 10) || (hdmi->vic == 11) ||
+ (hdmi->vic == 12) || (hdmi->vic == 13) ||
CHECK: braces {} should be used on all arms of this statement
+ if (hdmi->hdmi_data.video_mode.mdvi)
[...]
+ else {
[...]
Sign
We found Freescale imx6 and Rockchip rk3288 and Ingenic JZ4780 (Xburst/MIPS)
use the interface compatible Designware HDMI IP, but they also have some
lightly differences, such as phy pll configuration, register width(imx hdmi
register is one byte, but rk3288 is 4 bytes width and can only be access
On Tue, Nov 25, 2014 at 3:11 PM, Takashi Iwai wrote:
> At Fri, 14 Nov 2014 20:39:15 +0100,
> Takashi Iwai wrote:
>>
>> At Fri, 14 Nov 2014 12:29:17 -0500,
>> Alex Deucher wrote:
>> >
>> > On Fri, Nov 14, 2014 at 11:14 AM, Takashi Iwai wrote:
>> > > At Fri, 14 Nov 2014 10:40:08 -0500,
>> > > Alex
Hi Dave,
Just one small fix for PX laptops.
The following changes since commit a0fc608178a9b38a5f782331909fcc208b742a7b:
Merge branch 'drm-fixes-3.18' of git://people.freedesktop.org/~agd5f/linux
into drm-fixes (2014-11-21 12:19:19 +1000)
are available in the git repository at:
git://peo
Hi Rob,
On Tuesday 25 November 2014 19:38:47 Rob Clark wrote:
> On Tue, Nov 25, 2014 at 6:47 PM, Laurent Pinchart wrote:
> > From: Lars-Peter Clausen
> >
> > The drm_get_edid() function performs direct I2C accesses to read EDID
> > blocks, assuming that the monitor DDC interface is directly conn
Replace the internal EDID read implementation by a call to the new EDID
read core function.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/i2c/tda998x_drv.c | 86 ---
1 file changed, 18 insertions(+), 68 deletions(-)
This patch has been compile-tested on
On 2014ë
11ì 25ì¼ 23:02, Ajay kumar wrote:
> On Tue, Nov 25, 2014 at 6:59 PM, Inki Dae wrote:
>> On 2014ë
11ì 25ì¼ 22:08, Ajay kumar wrote:
>>> Hi Inki,
>>>
>>> On Tue, Nov 25, 2014 at 6:30 PM, Inki Dae wrote:
On 2014ë
11ì 25ì¼ 21:17, Ajay kumar wrote:
> ping.
>
>
Hi Dave,
Here's an updated pull request that adds HDMI support to the R-Car DU driver,
including a new slave encoder driver for the adv7511. Could you please pull it
for v3.19 ?
The branch is based on a merge of drm-next and Simon's tags/renesas-dt-du-for-
v3.19 available at
git://git.kernel.o
Keep property pointer, instead of id, in per mode-object attachments.
This will simplify things in later patches.
---
Does anyone care about the lifetime issue and dangling property ptrs?
Currently properties are destroyed during drm_mode_config_cleanup(),
so it doesn't really matter.. if someone
From: Gustavo Padovan
exynos_drm_manager was just a redundant struct to represent the crtc as
well. In this commit we merge exynos_drm_manager into exynos_drm_crtc to
remove an unnecessary level of indirection easing the understand of the
flow on exynos.
Signed-off-by: Gustavo Padovan
---
driv
From: Gustavo Padovan
manager-drm_dev is only accessed by exynos_drm_crtc_create() so this patch
pass drm_dev as argument on exynos_drm_crtc_create() and remove it from
struct exynos_drm_manager.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 9 +
drivers
From: Gustavo Padovan
'type' is now part of the struct exynos_drm_crtc. This is just another
step in the struct exynos_drm_manager removal.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 6 --
drivers/gpu/drm/exynos/exynos_drm_crtc.h | 3 ++-
drivers/gpu/drm/
From: Gustavo Padovan
It is not longer used. This is part of the process of removing
struct exynos_drm_manager entirely.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 2 +-
drivers/gpu/drm/exynos/exynos_drm_drv.h | 2 --
drivers/gpu/drm/exynos/exynos_drm_fimd.c
From: Gustavo Padovan
Get the pipe value from a parameter instead of getting it from
manager->pipe. We are removing manager->pipe.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 8
drivers/gpu/drm/exynos/exynos_drm_crtc.h | 2 +-
drivers/gpu/drm/exynos/e
From: Gustavo Padovan
'base' is more widely used name in the drm subsystem for the base object.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 4 ++--
drivers/gpu/drm/exynos/exynos_drm_drv.h | 7 +++
2 files changed, 5 insertions(+), 6 deletions(-)
diff --g
From: Gustavo Padovan
Following the removal of struct exynos_drm_overlay we now remove the manager
one as well. This remove another abstrastraction layer from exynos drm.
We can now use known names like CRTC and Planes instead of manager and overlay.
This patchset along with the ones I sent befo
_object_find() is not supposed to check for refcnt'd objects, that is
done in drm_mode_object_find().
Signed-off-by: Rob Clark
---
drivers/gpu/drm/drm_crtc.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c
index 9972cc8..3ba84df 10064
Otherwise we'd still end up w/ the plane attached to the CRTC, and
seemingly active, but without an FB. Which ends up going *boom*
in the drivers.
Slightly modified version of Daniel's irc suggestion.
CC: Daniel Vetter
Signed-off-by: Rob Clark
---
drivers/gpu/drm/drm_atomic_helper.c | 19
This essentially reverts
commit 934ce1c23624526d9d784e0499190bb48113e6f4
Author: Rob Clark
Date: Wed Nov 19 16:41:33 2014 -0500
drm/atomic: check mode_changed *after* atomic_check
Depending upon the driver both orders (or maybe even interleaving) is
required:
- If ->atomic_check updates -
The default call sequence for these two parts won't fit for all
drivers. So export the two pieces and explain with a bit of kerneldoc
when each should be called.
Cc: Rob Clark
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/drm_atomic_helper.c | 65 -
1 file
On Wed, Nov 26, 2014 at 10:52:24AM -0500, Sean Paul wrote:
> On Tue, Nov 25, 2014 at 5:50 PM, Daniel Vetter
> wrote:
> > So the problem with async commit (especially async modeset commit) is
> > that the legacy pointers only get updated after the point of no
> > return, in the async part of the m
On Wed, Nov 19, 2014 at 05:47:07PM -0200, Paulo Zanoni wrote:
> From: Paulo Zanoni
>
> Hi
>
> ---
> TL;DR summary:
> I wrote patches. Help me choose the best implementation and interface.
> ---
>
> So the i915.ko driver could use some mechanism to run functions after a given
> number of vblanks
receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141126/9daadaa0/attachment.html>
Am Mittwoch, den 26.11.2014, 09:43 +1000 schrieb Dave Airlie:
> On 25 November 2014 at 01:33, Philipp Zabel wrote:
> > The imx-drm driver was put into staging mostly for the following reasons,
> > all of which have been addressed or superseded:
> > - convert the irq driver to use linear irq domai
Am Mittwoch, den 26.11.2014, 21:32 +0800 schrieb Andy Yan:
> On rockchip rk3288, only word(32-bit) accesses are
> permitted for hdmi registers. Byte width accesses (writeb,
> readb) generate an imprecise external abort.
>
> Signed-off-by: Andy Yan
>
> ---
>
> Changes in v13: None
> Changes in v
Am Mittwoch, den 26.11.2014, 21:33 +0800 schrieb Andy Yan:
> some platform may not support all the display mode,
> add mode_valid interface check it
>
> also add drm_connector_register which add a debugfs
> interface for dump display modes and edid information
>
> Signed-off-by: Andy Yan
> ---
>
Hi Andy,
I have yet to look at this in more detail, but from a quick test
starting with patch 3, the HDMI display stays black on Nitrogen6X,
and starting with patch 8 I get the following error.
imx-drm display-subsystem: [CONNECTOR:21:HDMI-A-1] drm_connector_register
failed: -12
[ cu
ng this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141126/eed44ca0/attachment-0001.html>
> -Original Message-
> From: Cheng, Yao
> Sent: Saturday, November 22, 2014 3:07
> To: intel-gfx at lists.freedesktop.org; dri-devel at lists.freedesktop.org;
> daniel.vetter at ffwll.ch; Kelley, Sean V; Chehab, John
> Cc: Jiang, Fei; dh.herrmann at gmail.com; jani.nikula at linux.intel.com
From: Christian König
Not just the userspace relocs, otherwise we won't wait
for a swapped out page tables to be swapped in again.
Signed-off-by: Christian König
Cc: stable at vger.kernel.org
---
drivers/gpu/drm/radeon/radeon_cs.c | 19 +++
1 file changed, 7 insertions(+), 12
From: Gustavo Padovan
vidi_commit does nothing, remove it and its callers.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_vidi.c | 12
1 file changed, 12 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_vidi.c
b/drivers/gpu/drm/exynos/exynos_drm_
From: Gustavo Padovan
We set it in the beginning of the function, thus no need to set it at
initialization.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimd.c
From: Gustavo Padovan
This was just as extra chain in the call stack. We just rename it to
_set_base() and let it do everything alone.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/drivers/
From: Gustavo Padovan
Avoid an extra call to exynos_drm_crtc_mode_set_commit() that only calls
exynos_update_plane().
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/exynos/e
From: Gustavo Padovan
We can safely use the exynos_update_plane() to update the plane
framebuffer for both the overlay and primary planes.
Note that this patch removes a call to manager->ops->commit() in
exynos_drm_crtc_mode_set_commit(). The commit() call is used only by the
fimd driver to set
From: Gustavo Padovan
It's doing nothing but calling exynos_crtc->ops->win_commit(), so let's
call this directly to avoid extra layers of abstraction.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_crtc.c | 4 +++-
drivers/gpu/drm/exynos/exynos_drm_plane.c | 15 +---
From: Gustavo Padovan
DPMS only makes sense when the mode changes, for plane update changes do
not perform any dpms operation.
This move places the win_commit() and commit() calls directly in the code
instead of calling exynos_drm_crtc_commit() thus avoiding DPMS operations.
Signed-off-by: Gust
From: Gustavo Padovan
DPMS settings should only be changed by a full modeset.
exynos_plane_update() should only care about updating the planes itself
and nothing else.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_plane.c | 1 -
1 file changed, 1 deletion(-)
diff --git
From: Gustavo Padovan
This series is try to unify all the paths on exynos DRM that handle plane
updates. Now SetPlane, PageFlip and SetCrtc (fb changed only) are all
processed by the same function: exynos_update_plane().
In the unify process the DPMS operations were removed since we are not in f
On Wed, Nov 26, 2014 at 12:15 PM, Jilai Wang wrote:
> HPD interrupt can be tracked for each connector, so don't need
> to poll the connector status for state change.
>
> Change-Id: I2c062838af5922d32ce87a50676a45dcaedb44f2
Please remove the Change-Id when sending patches to the kernel.
Regards,
On 20.11.2014 09:58, Andy Lutomirski wrote:
> On Wed, Nov 19, 2014 at 4:07 PM, Andy Lutomirski
> wrote:
>> On Tue, Nov 18, 2014 at 11:19 PM, Michel Dänzer
>> wrote:
>>> On 19.11.2014 09:21, Andy Lutomirski wrote:
On Mon, Nov 17, 2014 at 1:51 AM, Michel Dänzer
wrote:
>
>>>
clock driver can support dynamic rate settings for HDMI
pixelclock, so don't need to use clk_round_rate to check if the
clockrate for specific mode is supported therefore more display
modes can be supported.
Change-Id: I308df4eb604438c24df463619571d8e18cc956b6
Signed-off-by: Jilai Wang
---
drive
Disable the HPD interrupt when acking it, to avoid spurious
interrupt.
Change-Id: Icb64d7fa813380c7ffa3047058503ebab13ff4c4
Signed-off-by: Jilai Wang
---
drivers/gpu/drm/msm/hdmi/hdmi_connector.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/msm/hdmi
HPD regulators need to be enabled before clocks, otherwise clock
driver will report warning.
Change-Id: Ieca41722ae3b15873e6290649a21bbd13e1a4278
Signed-off-by: Jilai Wang
---
drivers/gpu/drm/msm/hdmi/hdmi_connector.c | 45 +--
1 file changed, 18 insertions(+), 27 del
HPD interrupt can be tracked for each connector, so don't need
to poll the connector status for state change.
Change-Id: I2c062838af5922d32ce87a50676a45dcaedb44f2
Signed-off-by: Jilai Wang
---
drivers/gpu/drm/msm/hdmi/hdmi_connector.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
di
On Wed, Nov 26, 2014 at 2:04 PM, Laurent Pinchart
wrote:
> Replace the internal EDID read implementation by a call to the new EDID
> read core function.
>
> Signed-off-by: Laurent Pinchart
Thanks!
Reviewed-by: Rob Clark
> ---
> drivers/gpu/drm/i2c/tda998x_drv.c | 86
> --
From: Dave Airlie
At least on two MST devices I've tested with, when
they are link training downstream, they are totally
unable to handle aux ch msgs, so they defer like nuts.
I tried 16, it wasn't enough, 32 seems better.
This fixes one Dell 4k monitor and one of the
MST hubs.
v1.1: fixup comm
On 26 November 2014 at 13:20, Tom Stellard wrote:
> On Wed, Nov 26, 2014 at 01:17:22PM +1000, Dave Airlie wrote:
>> From: Dave Airlie
>>
>> At least on two MST devices I've tested with, when
>> they are link training downstream, they are totally
>> unable to handle aux ch msgs, so they defer like
From: Dave Airlie
On MST systems the monitors don't appear when we set the fb up,
but plymouth opens the drm device and holds it open while they
come up, when plymouth finishes and lastclose gets called we
don't do the delayed fb probe, so the monitor never appears on the
console.
Fix this by mo
From: Dave Airlie
At least on two MST devices I've tested with, when
they are link training downstream, they are totally
unable to handle aux ch msgs, so they defer like nuts.
I tried 16, it wasn't enough, 32 seems better.
This fixes one Dell 4k monitor and one of the
MST hubs.
Signed-off-by: D
On Mon, Nov 24, 2014 at 11:43 PM, Maarten Lankhorst
wrote:
> Hey,
>
> Op 22-11-14 om 21:16 schreef Michael Marineau:
>> On Nov 22, 2014 11:45 AM, "Michael Marineau" wrote:
>>>
>>> On Nov 22, 2014 8:56 AM, "Maarten Lankhorst" <
>> maarten.lankhorst at canonical.com> wrote:
Hey,
Op 2
tldr: works now, without patch, without GRUB, with efi-stub
Am Tue, Nov 25, 2014 at 05:25:50PM + schrieb Matthew Garrett:
> On Tue, Nov 25, 2014 at 12:14:21PM -0500, Alex Deucher wrote:
> > The vbios image is available via ACPI prior to the OS taking over.
> > IIRC, Matthew Garret fixed up the
Hey Inki,
Could you or one of the exynos folks have a look at ipp_get_event()?
That handling of file_priv->event_space looks rather suspect. I don't
see where event_space is decremented in the first place. I'm not sure
if that is just broken, or if there is something subtle going on.. but
I gues
On Wed, 26 Nov 2014, Dave Airlie wrote:
> From: Dave Airlie
>
> At least on two MST devices I've tested with, when
> they are link training downstream, they are totally
> unable to handle aux ch msgs, so they defer like nuts.
> I tried 16, it wasn't enough, 32 seems better.
I think we have a bug
ttp://lists.freedesktop.org/archives/dri-devel/attachments/20141126/99274ab4/attachment-0001.html>
On 11/25/2014 06:43 PM, Dan Carpenter wrote:
> This is dead code. We don't need to unbind here, we can just return
> directly.
>
> Signed-off-by: Dan Carpenter
>
Patch is:
Reviewed-by: Oded Gabbay
And applied to my 3.19-next-wip tree.
Thanks!
Oded
> diff --git a/drivers/gpu/drm/amd/amd
On Tue, Nov 25, 2014 at 5:50 PM, Daniel Vetter
wrote:
> So the problem with async commit (especially async modeset commit) is
> that the legacy pointers only get updated after the point of no
> return, in the async part of the modeset sequence. At least as
> implemented by the current helper func
Hi Fabio:
On 2014å¹´11æ26æ¥ 10:14, Fabio Estevam wrote:
> Hi Andy,
>
> On Mon, Nov 17, 2014 at 8:53 AM, Andy Yan wrote:
>
>> Andy Yan (11):
>>staging: imx-drm: imx-hdmi: make checkpatch happy
>>staging: imx-drm: imx-hdmi: return defer if can't get ddc i2c adapter
>>staging: imx-drm
tachments/20141126/f951af0c/attachment.html>
On 25 November 2014 at 01:33, Philipp Zabel wrote:
> The imx-drm driver was put into staging mostly for the following reasons,
> all of which have been addressed or superseded:
> - convert the irq driver to use linear irq domains
> - work out the device tree bindings, this lead to the common of_
On 26 November 2014 at 02:38, Heiko Stübner wrote:
> Mark,
>
> Am Donnerstag, 20. November 2014, 09:46:34 schrieb Mark Yao:
>> This a series of patches is a DRM Driver for Rockchip Socs, add support
>> for vop devices. Future patches will add additional encoders/connectors,
>> such as eDP, HDMI.
dri-devel/attachments/20141126/5b76feef/attachment.html>
On Wed, Nov 26, 2014 at 01:17:23PM +1000, Dave Airlie wrote:
> From: Dave Airlie
>
> On MST systems the monitors don't appear when we set the fb up,
> but plymouth opens the drm device and holds it open while they
> come up, when plymouth finishes and lastclose gets called we
> don't do the delay
On Wed, Nov 26, 2014 at 01:37:51AM +0100, Heiko Stübner wrote:
>
> Joerg, is your arm/rockchip branch [0] considered stable?
>
> [0]
> https://git.kernel.org/cgit/linux/kernel/git/joro/iommu.git/log/?h=arm/rockchip
>
Yes, this branch will not be rebased. It can be pulled into another
tree.
On Tue, Nov 25, 2014 at 08:33:09PM -0500, Rob Clark wrote:
> A couple small OCD cleanups I noticed, which my other work-in-progress
> propertification/atomic-ioctl patches are on top of. No dependency on
> any atomic stuff, so might as well hit 'send'.
Both merged into my fixup pile, thanks.
-Dan
On Tue, Nov 25, 2014 at 08:29:47PM -0500, Rob Clark wrote:
> Signed-off-by: Rob Clark
Merged this and the iterator patch (I've had the planemask one already)
into my fixup pile.
Thanks, Daniel
> ---
> drivers/gpu/drm/msm/mdp/mdp4/mdp4_crtc.c | 6 +++---
> drivers/gpu/drm/msm/mdp/mdp5/mdp5_crtc
On Wed, Nov 26, 2014 at 01:47:27AM +0200, Laurent Pinchart wrote:
> From: Lars-Peter Clausen
>
> The drm_get_edid() function performs direct I2C accesses to read EDID
> blocks, assuming that the monitor DDC interface is directly connected to
> the I2C bus. It can't thus be used with HDMI encoders
On Tue, Nov 25, 2014 at 10:42 PM, Michel Dänzer wrote:
> On 20.11.2014 09:58, Andy Lutomirski wrote:
>>
>> On Wed, Nov 19, 2014 at 4:07 PM, Andy Lutomirski
>> wrote:
>>>
>>> On Tue, Nov 18, 2014 at 11:19 PM, Michel Dänzer
>>> wrote:
On 19.11.2014 09:21, Andy Lutomirski wrote:
>
>
EBUG_INFO=y too, so i guess that config
option is not an issue.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141126/d7a6c2a8/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #17 from Dave Airlie ---
this looks like a PCI regresion
Ð¾ÐºÑ 03 03:49:35 localhost.localdomain kernel: pci :01:00.0: can't claim
BAR
0 [mem 0xc000-0xcfff pref]: no compatible bridge window
Ð¾ÐºÑ 03 03:49:35 localhost
https://bugzilla.kernel.org/show_bug.cgi?id=88911
--- Comment #1 from Michel Dänzer ---
Duplicate of bug 88481 (and bug 88781).
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #16 from Michel Dänzer ---
(In reply to Marek from comment #15)
> The result of bisection is that the first bad commit is:
>
> e5558d1a516fa6924fa8d53152b665d4c26f142e Merge branches 'dma-api',
> 'pci/virtualization', 'pci/msi', 'pc
ttp://lists.freedesktop.org/archives/dri-devel/attachments/20141126/8cc5a69c/attachment.html>
is mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141126/f27e4ac6/attachment.html>
---
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141126/f2c2c7a3/attachment.html>
top.org/archives/dri-devel/attachments/20141126/90965c54/attachment-0001.html>
From: Lars-Peter Clausen
The drm_get_edid() function performs direct I2C accesses to read EDID
blocks, assuming that the monitor DDC interface is directly connected to
the I2C bus. It can't thus be used with HDMI encoders that control the
DDC bus and expose EDID blocks through a different interfa
Hi Joerg, Dave,
Am Mittwoch, 26. November 2014, 09:12:56 schrieb Dave Airlie:
> On 26 November 2014 at 02:38, Heiko Stübner wrote:
> > Mark,
> >
> > Am Donnerstag, 20. November 2014, 09:46:34 schrieb Mark Yao:
> >> This a series of patches is a DRM Driver for Rockchip Socs, add support
> >> for
ktop.org/archives/dri-devel/attachments/20141126/575c29eb/attachment-0001.html>
Hi Andy,
On Mon, Nov 17, 2014 at 8:53 AM, Andy Yan wrote:
> Andy Yan (11):
> staging: imx-drm: imx-hdmi: make checkpatch happy
> staging: imx-drm: imx-hdmi: return defer if can't get ddc i2c adapter
> staging: imx-drm: imx-hdmi: convert imx-hdmi to drm_bridge mode
> staging: imx-drm: imx
--
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20141126/2e05a47e/attachment.html>
99 matches
Mail list logo
