Hi,
2014-12-18 22:58 GMT+09:00 Gustavo Padovan :
> From: Gustavo Padovan
>
> Hi,
>
> In this series:
>
> - fix to FIMD pageflips, only finish pageflips if START == START_S.
>
> - remove struct exynos_drm_overlay and struct exynos_drm_manager.
> exynos_drm_overlay was merged with exynos_drm_pla
On Sun, Jan 11, 2015 at 11:53 PM, Rickard Strandqvist
wrote:
Hey Rickard,
> Remove the function nvif_device_new() that is not used anywhere.
It's used, just not by the kernel. All the code under core/ and nvif/
is also built into a userspace library (not in the kernel tree,
obviously) and used
s zoomed in. Vram usage is
pretty flat, usually around 450mb.
--
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/20150112/f178efc9/attachment.html>
This fixes reset codes to support memory mapped hdmi phy as well as hdmi
phy dedicated i2c lines.
Signed-off-by: Joonyoung Shim
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_hdmi.c
b/drivers/gpu
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/20150112/876f005b/attachment.html>
In general, the data in drm/rockchip GEM objects is never accessed by
the kernel. The objects are either accessed by a GPU, by display
controller DMA, or by mmap'ing them to user space. Thus, these
buffers need not be mapped into kernel address space.
The only exception is the fbdev framebuffer(
Am Freitag, den 09.01.2015, 20:01 + schrieb Russell King - ARM
Linux:
[...]
> Neither; we know that there are TDA998x devices which allow SPDIF to be
> input via two separate pins, but only one to be active at any one time.
> Given that the hardware is flexible in that regard, a binding which
>
On 2015ë
01ì 12ì¼ 18:12, Kukjin Kim wrote:
> On 01/03/15 15:50, Inki Dae wrote:
>> On 2014ë
11ì 28ì¼ 20:39, Inki Dae wrote:
>>> This patch adds fimd device node which is a display controller
>>> for Exynos3250 Rinato board.
>>
>> Hi Kukjin,
>>
>> Please, ping~
>>
>> Thanks,
>> Inki Dae
>>
On Sat, 10 Jan 2015, Jeremiah Mahler wrote:
> Commit 6dda730e55f4 introduced a bug which resulted in inconsistent
> brightness levels on different machines. If a suspended was entered
> with the screen off some machines would resume with the screen
> at minimum brightness and others at maximum bri
Hi Thierry,
On 12/19/2014 01:14 PM, Hans Verkuil wrote:
> This patch series adds new HDMI 2.0/CEA-861-F defines to hdmi.h and
> adds unpacking and logging functions to hdmi.c. It also uses those
> in the V4L2 adv7842 driver (and they will be used in other HDMI drivers
> once this functionality is
On 12/23/2014 03:32 PM, Kamil Debski wrote:
> From: Hans Verkuil
>
> Add the CEC framework.
>
> Signed-off-by: Hans Verkuil
> [k.debski at samsung.com: Merged CEC Updates commit by Hans Verkuil]
> [k.debski at samsung.com: Merged Update author commit by Hans Verkuil]
> [k.debski at samsung.com:
On 12/23/2014 03:32 PM, Kamil Debski wrote:
> From: Hans Verkuil
>
> Add the CEC framework.
>
> Signed-off-by: Hans Verkuil
> [k.debski at samsung.com: Merged CEC Updates commit by Hans Verkuil]
> [k.debski at samsung.com: Merged Update author commit by Hans Verkuil]
> [k.debski at samsung.com:
On Mon, Jan 12, 2015 at 10:25:28AM +0100, Philipp Zabel wrote:
> Jean-Francois' reply already reflects this, but the 'port' nodes should
> correspond to physical ports of the device if possible. If you can
> configure the device to have dedicated input pins for I2S, SPDIF0, and
> SPDIF1 at the same
ttp://lists.freedesktop.org/archives/dri-devel/attachments/20150112/7d53d51d/attachment.html>
On Sat, 2015-01-10 at 23:31 -0500, Nicholas Krause wrote:
> Changes various calls in the functions,send_pkg_prepare and send_pkg_done
> for mdelay to msleep. These changes are needed due to use working with
> various sleep modes supported by this hardware and thus needing to sleep
> for a small dur
If CONFIG_BUG=n __WARN_printf won't be defined leading to the below
build failure. The double underscores should have told us to steer clear
of it anyway.
drivers/gpu/drm/i915/intel_display.c: In function âassert_pllâ:
drivers/gpu/drm/i915/intel_display.c:1027:2: error: implicit declaration
of
Am Montag, den 12.01.2015, 12:25 + schrieb Russell King - ARM Linux:
> On Mon, Jan 12, 2015 at 10:25:28AM +0100, Philipp Zabel wrote:
> > Jean-Francois' reply already reflects this, but the 'port' nodes should
> > correspond to physical ports of the device if possible. If you can
> > configure
On Mon, Jan 12, 2015 at 02:59:57PM +0100, Philipp Zabel wrote:
> Am Montag, den 12.01.2015, 12:25 + schrieb Russell King - ARM Linux:
> > It's not quite that simple, because the SPDIF AP pins are multiplexed
> > with the I2S pins - and there is variation between chip models and
> > packages.
>
the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150112/d592c9d6/attachment.html>
are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150112/da499cc4/attachment.html>
On Mon, 2015-01-12 at 17:12 +0100, Thierry Reding wrote:
> On Mon, Jan 12, 2015 at 01:29:27PM +, Alan Cox wrote:
> > On Sat, 2015-01-10 at 23:31 -0500, Nicholas Krause wrote:
> > > Changes various calls in the functions,send_pkg_prepare and send_pkg_done
> > > for mdelay to msleep. These change
https://bugzilla.kernel.org/show_bug.cgi?id=90851
--- Comment #3 from Christoph Haag ---
Hm, interesting. I compiled 3.19-rc4 with debug symbols.
I'm also testing Tom Stellard's VGPR register spilling llvm and mesa branches.
After a while of playing skyrim I got the familiar hang where skyrim j
On Mon, 12 Jan 2015 14:04:56 +
Russell King - ARM Linux wrote:
> On Mon, Jan 12, 2015 at 02:59:57PM +0100, Philipp Zabel wrote:
> > Am Montag, den 12.01.2015, 12:25 + schrieb Russell King - ARM Linux:
> > > It's not quite that simple, because the SPDIF AP pins are multiplexed
> > > with t
On Mon, Jan 12, 2015 at 06:13:41PM +0100, Jean-Francois Moine wrote:
> On Mon, 12 Jan 2015 14:04:56 +
> Russell King - ARM Linux wrote:
> > On Mon, Jan 12, 2015 at 02:59:57PM +0100, Philipp Zabel wrote:
> > > Note that of_graph_parse_endpoint interprets the port node's reg
> > > property as po
From: Gustavo Padovan
The drm_file event_list hasn't been used anymore by exynos, so we don't
need any code to clean it.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/exynos/exynos_drm_drv.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_drv.c
b
From: Mandeep Singh Baines
The goal of the change is to make sure we send the vblank event on the
current vblank. My hope is to fix any races that might be causing flicker.
After this change I only see a flicker in the transition plymouth and
X11.
Simplified the code by tracking vblank events on
Hi Greg, stable team,
Please apply this patch to stable (3.18 and 3.17).
It is commit ff4c0d5213b015e60aa87c1352604f10ba9c3e12 in linus's tree:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ff4c0d5213b015e60aa87c1352604f10ba9c3e12
Thanks,
Bruno
On Sun, 21 Decembe
On Mon, 12 Jan 2015 17:57:06 +
Russell King - ARM Linux wrote:
> I don't particularly like that - that makes the assumption that AP0
> always means I2S. What if a future chip decides to allow SPDIF on
> AP0? Why should we need to re-invent the binding?
>
> IMHO, it would be much better to
.org/archives/dri-devel/attachments/20150112/db7492c3/attachment.html>
commit 765d5b9c2b72f5b99722cdfcf4bf8f88c556cf92 ("fbdev: fbcon: select
VT_HW_CONSOLE_BINDING") made FRAMEBUFFER_CONSOLE always select
VT_HW_CONSOLE_BINDING, but forgot to remove
select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
from the individual drivers' sections that already did this
commit 765d5b9c2b72f5b9 ("fbdev: fbcon: select VT_HW_CONSOLE_BINDING")
made FRAMEBUFFER_CONSOLE always select VT_HW_CONSOLE_BINDING, but forgot
to remove
select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
from the individual drivers' sections that already did this before.
Remove it, als
2014-12-30 Inki Dae :
> On 2014ë
12ì 18ì¼ 22:58, Gustavo Padovan wrote:
> > From: Daniel Kurtz
> >
> > A framebuffer gets committed to FIMD's default window like this:
> > exynos_drm_crtc_update()
> > exynos_plane_commit()
> >fimd_win_commit()
> >
> > fimd_win_commit() programs BUF_
On Thu, Jan 8, 2015 at 11:15 AM, Oded Gabbay wrote:
> This patch-set starts to prepare amdkfd so it could support VI APU.
>
> 1. As newer H/W will be handled by amdgpu, we need to eliminate amdkfd's
>include of radeon header files.
>
> 2. MQDs are different between CI and VI, so we need to spl
On Sun, Jan 11, 2015 at 3:27 PM, Federico wrote:
> Ubuntu 14.10 (kernel is 3.16.0) with nomodeset also boots. But it seems to
> be using the a generic driver
Right. As I mentioned, using nomodeset disables the gfx driver and
you end up with fw drivers (vesa of efifb). Do you still have the
issu
https://bugzilla.kernel.org/show_bug.cgi?id=86351
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #5 fr
ong
with the higher mclk.
--
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/20150112/aee6bce9/attachment-0001.html>
Hi Takashi,
So here's the stable tag with Imre's i915/hda componentized refactoring,
based upon 3.19-rc4. I'll pull in the same tag into drm-intel-next.
Cheers, Daniel
The following changes since commit eaa27f34e91a14cdceed26ed6c6793ec1d186115:
linux 3.19-rc4 (2015-01-11 12:44:53 -0800)
are
On Mon, Jan 12, 2015 at 09:10:12PM +0100, Geert Uytterhoeven wrote:
> commit 765d5b9c2b72f5b9 ("fbdev: fbcon: select VT_HW_CONSOLE_BINDING")
> made FRAMEBUFFER_CONSOLE always select VT_HW_CONSOLE_BINDING, but forgot
> to remove
>
> select VT_HW_CONSOLE_BINDING if FRAMEBUFFER_CONSOLE
>
> from the in
use.
> >>
> >> I will try to boot Ubuntu 14.10 live image with nomodeset to see if I
> can
> >> get some error messages there.
> >
> >
> >
> > ___
> > dri-devel mailing list
> > dri-devel at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/dri-devel
> >
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150112/7cc0f763/attachment.html>
On 01/03/15 15:50, Inki Dae wrote:
> On 2014ë
11ì 28ì¼ 20:39, Inki Dae wrote:
>> This patch adds fimd device node which is a display controller
>> for Exynos3250 Rinato board.
>
> Hi Kukjin,
>
> Please, ping~
>
> Thanks,
> Inki Dae
>
>>
>> Signed-off-by: Inki Dae
>> Acked-by: Kyungmin Par
For scenarios where OF is not available, we can use panel identification by
name.
Signed-off-by: Shobhit Kumar
---
drivers/gpu/drm/drm_panel.c | 18 ++
include/drm/drm_panel.h | 3 +++
2 files changed, 21 insertions(+)
diff --git a/drivers/gpu/drm/drm_panel.c b/drivers/gpu/
On Mon, Jan 12, 2015 at 01:29:27PM +, Alan Cox wrote:
> On Sat, 2015-01-10 at 23:31 -0500, Nicholas Krause wrote:
> > Changes various calls in the functions,send_pkg_prepare and send_pkg_done
> > for mdelay to msleep. These changes are needed due to use working with
> > various sleep modes supp
Jani,
On Mon, Jan 12, 2015 at 12:31:09PM +0200, Jani Nikula wrote:
> On Sat, 10 Jan 2015, Jeremiah Mahler wrote:
[...]
>
> I think part of the problem is that the userspace sets brightness to
> minimum before suspend, but apparently does not restore it after
> resume. The dmesg would confirm thi
Commit 6dda730e55f4 introduced a bug which resulted in inconsistent
brightness levels on different machines. If a suspended was entered
with the screen off some machines would resume with the screen
at minimum brightness and others at maximum brightness.
The following commands can be used to produ
Copying 64 bit data from user space using get_user is not supported
on all architectures, and may result in the following build error.
ERROR: "__get_user_bad" [drivers/gpu/drm/drm.ko] undefined!
Avoid the problem by using copy_from_user.
Fixes: d34f20d6e2f2 ("drm: Atomic modeset ioctl")
Cc: Rob
45 matches
Mail list logo
