[PATCH] drm/exynos: Add device tree based discovery support for Exynos G2D

This patch adds device tree match table for Exynos G2D controller. Signed-off-by: Ajay Kumar --- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/drivers/gpu/drm/exynos/exynos_drm_g2d.c b/drivers/gpu/drm/exynos/exynos_drm_g2d.c index

[PATCH] drm/exynos: fix gem buffer allocation type checking

reedesktop.org/mailman/listinfo/dri-devel >> > > > ___ > 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/20121227/9948b578/attachment-0001.html>

[RFC v2 0/5] Common Display Framework

On Thu, Dec 27, 2012 at 10:04:22AM -0600, Rob Clark wrote: > On Mon, Dec 24, 2012 at 11:27 AM, Laurent Pinchart > wrote: > > On Wednesday 19 December 2012 16:57:56 Jani Nikula wrote: > >> It just seems to me that, at least from a DRM/KMS perspective, adding > >> another layer (=CDF) for HDMI or

[RFC v2 0/5] Common Display Framework

On Thu, Dec 27, 2012 at 09:54:55AM -0600, Rob Clark wrote: > On Mon, Dec 24, 2012 at 7:37 AM, Laurent Pinchart > wrote: > > Hi Rob, > > > > On Tuesday 18 December 2012 00:21:32 Rob Clark wrote: > >> On Mon, Dec 17, 2012 at 11:04 PM, Dave Airlie wrote: > >> >> Many developers showed interest in

[PATCH] drm/exynos: fix gem buffer allocation type checking

This patch fixes gem buffer allocation type checking. EXYNOS_BO_CONTIG has 0 so the checking should be fixed to 'if (!(flags & EXYNOS_BO_NONCONTIG))' Signed-off-by: Inki Dae Signed-off-by: Kyungmin Park --- drivers/gpu/drm/exynos/exynos_drm_buf.c |2 +- 1 files changed, 1 insertions(+), 1

[PATCH 04/10] drm/exynos: Use devm_clk_get in exynos_drm_fimc.c

; platform_device *pdev) > >> IRQF_ONESHOT, "drm_fimc", ctx); > >> if (ret < 0) { > >> dev_err(dev, "failed to request irq.\n"); > >> - goto err_clk; > >> + return ret; > >> } > >> > >> /* context initailization */ > >> @@ -1867,11 +1851,6 @@ err_ippdrv_register: > >> pm_runtime_disable(dev); > >> err_get_irq: > >> free_irq(ctx->irq, ctx); > >> -err_clk: > >> - clk_put(ctx->sclk_fimc_clk); > >> - clk_put(ctx->fimc_clk); > >> - clk_put(ctx->wb_clk); > >> - clk_put(ctx->wb_b_clk); > >> > >> return ret; > >> } > >> @@ -1891,11 +1870,6 @@ static int __devexit fimc_remove(struct > platform_device *pdev) > >> > >> free_irq(ctx->irq, ctx); > >> > >> - clk_put(ctx->sclk_fimc_clk); > >> - clk_put(ctx->fimc_clk); > >> - clk_put(ctx->wb_clk); > >> - clk_put(ctx->wb_b_clk); > >> - > >> return 0; > >> } > >> > >> -- > >> 1.7.4.1 > >> > >> ___ > >> dri-devel mailing list > >> dri-devel at lists.freedesktop.org > >> http://lists.freedesktop.org/mailman/listinfo/dri-devel > > > > > > -- > With warm regards, > Sachin > > > ___ > 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/20121227/8b567a0e/attachment-0001.html>

[Bug 49981] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!

https://bugzilla.kernel.org/show_bug.cgi?id=49981 --- Comment #4 from Apostolos B. 2012-12-27 18:16:42 --- I chasnged my DE from gnome 3 to E17 and i don't get that error anymore? Could it be related? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You

[Bug 43167] X intel driver causes wrong wraparound of console command line

e assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121227/4d4a6112/attachment.html>

Display resolutions missing on external VGA display [regressing]

On Mon, 24 Dec 2012, John wrote: > On launchpad they requested to report this bug upstream. Please let me know > if any information is missing. Please file a bug on DRM/Intel at [1]. Please reference your mail and the launchpad bug, no need to attach all the info there again. What's the latest

[Bug 43167] X intel driver causes wrong wraparound of console command line

t;http://lists.freedesktop.org/archives/dri-devel/attachments/20121227/f376c819/attachment.html>

[PATCH] drm/exynos: fix gem buffer allocation type checking

-- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121227/99de06c0/attachment.html>

[PATCH 04/10] drm/exynos: Use devm_clk_get in exynos_drm_fimc.c

On 27 December 2012 15:43, Inki Dae wrote: > > > 2012/12/26 Sachin Kamat >> >> >> >> On Wednesday, 26 December 2012, Inki Dae wrote: >> > >> > >> > 2012/12/24 Sachin Kamat >> >> >> >> This eliminates the need for explicit clk_put and makes the >> >> cleanup and exit path code simpler. >> >> >>

[RFC v2 0/5] Common Display Framework

Hi Laurent, On Monday 24 of December 2012 15:12:28 Laurent Pinchart wrote: > Hi Tomasz, > > On Friday 21 December 2012 11:00:52 Tomasz Figa wrote: > > On Tuesday 18 of December 2012 08:31:30 Vikas Sajjan wrote: > > > On 17 December 2012 20:55, Laurent Pinchart wrote: > > > > Hi Vikas, > > > > >

[PATCH] video: drm: exynos: mie bypass enable for fimd

mie_bypass_for_fimd(bypass_data); > + } > + } > if (!pdata) { > dev_err(dev, "no platform data specified\n"); > return -EINVAL; > -- > 1.8.0 > > ___ > 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/20121227/1e9d044c/attachment.html>

[RFC v2 0/5] Common Display Framework

On Thu, Dec 27, 2012 at 1:18 PM, Sascha Hauer wrote: > On Thu, Dec 27, 2012 at 09:54:55AM -0600, Rob Clark wrote: >> On Mon, Dec 24, 2012 at 7:37 AM, Laurent Pinchart >> wrote: >> > Hi Rob, >> > >> > On Tuesday 18 December 2012 00:21:32 Rob Clark wrote: >> >> On Mon, Dec 17, 2012 at 11:04 PM,

[Bug 57875] Second Life viewer bad rendering with git-ec83535

um/drivers/r300' gmake[3]: *** [all-recursive] Error 1 ... -- 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/20121227/3f996185/attachment.html>

[RFC v2 0/5] Common Display Framework

On Mon, Dec 24, 2012 at 11:35 AM, Laurent Pinchart wrote: > On Wednesday 19 December 2012 09:26:40 Rob Clark wrote: >> And, there are also external HDMI encoders (for example connected over >> i2c) that can also be shared between boards. So I think there will be >> a number of cases where CDF is

[RFC v2 0/5] Common Display Framework

On Mon, Dec 24, 2012 at 11:27 AM, Laurent Pinchart wrote: > On Wednesday 19 December 2012 16:57:56 Jani Nikula wrote: >> It just seems to me that, at least from a DRM/KMS perspective, adding >> another layer (=CDF) for HDMI or DP (or legacy outputs) would be >> overengineering it. They are pretty

[RFC v2 0/5] Common Display Framework

On Mon, Dec 24, 2012 at 11:09 AM, Laurent Pinchart wrote: > On the topic of discussions, would anyone be interested in a > BoF/brainstorming/whatever session during the FOSDEM ? I will be at FOSDEM.. and from http://wiki.x.org/wiki/fosdem2013 it looks like at least Daniel will be there. If

[RFC v2 0/5] Common Display Framework

On Mon, Dec 24, 2012 at 7:37 AM, Laurent Pinchart wrote: > Hi Rob, > > On Tuesday 18 December 2012 00:21:32 Rob Clark wrote: >> On Mon, Dec 17, 2012 at 11:04 PM, Dave Airlie wrote: >> >> Many developers showed interest in the first RFC, and I've had the >> >> opportunity to discuss it with most

[PATCH] drm: make frame duration time calculation more precise

It is a bit more precise to compute the total number of pixels first and then divide, rather than multiplying the line pixel count by the already-rounded line duration. Signed-off-by: Daniel Kurtz --- drivers/gpu/drm/drm_irq.c |6 +- 1 files changed, 5 insertions(+), 1 deletions(-)

[PATCH] drm: fixed access to PCI host bridges

On Thu, Dec 27, 2012 at 8:40 AM, Bjorn Helgaas wrote: > On Sat, Dec 22, 2012 at 12:01 PM, Lucas Kannebley Tavares > wrote: >> During the process of obtaining the speed cap for the device, it >> attempts go get the PCI Host bus. However on architectures such as PPC >> or IA64, those do not appear

[PATCH] drm/exynos: fimd: modify condition in fimd resume

If fimd is runtime suspended (by DPMS OFF), fimd_suspend does not call fimd_activate(false) and just returns. Similarily the check in fimd_resume should not resume if previously runtime_suspended. Instead the existing check does the opposite. So if fimd was not runtime suspended, suspend will turn

[PATCH 4/4] drm/exynos: hdmi: support extra resolutions using drm_display_mode timings

From: Sean Paul This patch programs the core and timing generator registers using the timing data provided in drm_display_mode and not using hard-coded configurations. Additional PHY configs has been added. This allows us to support more permissible resolutions and

[PATCH 3/4] drm/exynos: mixer: set correct mode for range of resolutions

With this patch, mixer driver find the correct resolution mode for the range of resolutions, upto 1080 vertical lines. Resolution will be categorized to NTSC SD, PAL SD or HD and the correct mode is set to the mixer configuration register. Signed-off-by: Rahul Sharma Signed-off-by: Sean Paul

[PATCH 2/4] drm/exynos: implement display-mode-check callback in mixer driver

This patch adds the implementation of check_mode callback in the mixer driver. Based on the mixer version, correct set of restrictions will be exposed by the mixer driver. A resolution will be acceptable only if passes the criteria set by mixer and hdmi IPs. Signed-off-by: Rahul Sharma

[PATCH 1/4] drm/exynos: add display-mode-check operation to exynos_mixer_ops struct

This patch adds the display mode check operation to exynos_mixer_ops in drm-common-hdmi. In Exynos SoCs, mixer IP can put certain restrictions on the proposed display modes. These restriction needs to be considered during mode negotiation, which happens immediately after edid parsing. Both, mixer

[PATCH 0/4] drm/exynos: add support for extra resolutions to exynos5

This patch set adds support for more resolutions and refresh rates to Samsung Exynos5 SoC series which contains hdmi transmitter (hdmi v1.4a compliant). Given resolution will be supported or not, is decided by two factors: 1) Corresponding pixel clock is supported by hdmi PHY. 2) Mixer supports

[PATCH] drm/exynos: Add device tree based discovery support for Exynos G2D

This patch adds device tree match table for Exynos G2D controller. Signed-off-by: Ajay Kumar --- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/drivers/gpu/drm/exynos/exynos_drm_g2d.c b/drivers/gpu/drm/exynos/exynos_drm_g2d.c index

Re: [PATCH 04/10] drm/exynos: Use devm_clk_get in exynos_drm_fimc.c

On Wednesday, 26 December 2012, Inki Dae inki@samsung.com wrote: 2012/12/24 Sachin Kamat sachin.ka...@linaro.org This eliminates the need for explicit clk_put and makes the cleanup and exit path code simpler. Cc: Eunchul Kim chulspro@samsung.com Signed-off-by: Sachin Kamat

[PATCH 04/10] drm/exynos: Use devm_clk_get in exynos_drm_fimc.c

On Wednesday, 26 December 2012, Inki Dae inki@samsung.com wrote: 2012/12/24 Sachin Kamat sachin.ka...@linaro.org This eliminates the need for explicit clk_put and makes the cleanup and exit path code simpler. Cc: Eunchul Kim chulspro@samsung.com Signed-off-by: Sachin Kamat

Re: [PATCH 04/10] drm/exynos: Use devm_clk_get in exynos_drm_fimc.c

2012/12/26 Sachin Kamat sachin.ka...@linaro.org On Wednesday, 26 December 2012, Inki Dae inki@samsung.com wrote: 2012/12/24 Sachin Kamat sachin.ka...@linaro.org This eliminates the need for explicit clk_put and makes the cleanup and exit path code simpler. Cc: Eunchul Kim

[Bug 57875] Second Life viewer bad rendering with git-ec83535

https://bugs.freedesktop.org/show_bug.cgi?id=57875 --- Comment #18 from Piero Finizio andabat...@yahoo.it --- If i try to revert the commit e866bd1adea2c3b4971ad68e69c644752f2ab7b6 (above mentioned workaround) with git HEAD at 7c35521 mesa: add missing texel fetch code for sRGB DXT formats the

[PATCH] drm/exynos: fimd: modify condition in fimd resume

If fimd is runtime suspended (by DPMS OFF), fimd_suspend does not call fimd_activate(false) and just returns. Similarily the check in fimd_resume should not resume if previously runtime_suspended. Instead the existing check does the opposite. So if fimd was not runtime suspended, suspend will turn

Re: [PATCH] drm/exynos: fix gem buffer allocation type checking

On Thu, Dec 27, 2012 at 4:27 PM, Inki Dae inki@samsung.com wrote: This patch fixes gem buffer allocation type checking. EXYNOS_BO_CONTIG has 0 so the checking should be fixed to 'if (!(flags EXYNOS_BO_NONCONTIG))' Signed-off-by: Inki Dae inki@samsung.com Signed-off-by: Kyungmin

Re: [PATCH] drm/exynos: fix gem buffer allocation type checking

2012/12/27 Prathyush K prathy...@chromium.org On Thu, Dec 27, 2012 at 4:27 PM, Inki Dae inki@samsung.com wrote: This patch fixes gem buffer allocation type checking. EXYNOS_BO_CONTIG has 0 so the checking should be fixed to 'if (!(flags EXYNOS_BO_NONCONTIG))' Signed-off-by: Inki

Re: [RFC v2 0/5] Common Display Framework

Hi Laurent, On Monday 24 of December 2012 15:12:28 Laurent Pinchart wrote: Hi Tomasz, On Friday 21 December 2012 11:00:52 Tomasz Figa wrote: On Tuesday 18 of December 2012 08:31:30 Vikas Sajjan wrote: On 17 December 2012 20:55, Laurent Pinchart wrote: Hi Vikas, Sorry for the

Re: Display resolutions missing on external VGA display [regressing]

On Mon, 24 Dec 2012, John zendhet...@gmail.com wrote: On launchpad they requested to report this bug upstream. Please let me know if any information is missing. Please file a bug on DRM/Intel at [1]. Please reference your mail and the launchpad bug, no need to attach all the info there again.

Re: [RFC v2 0/5] Common Display Framework

On Mon, Dec 24, 2012 at 7:37 AM, Laurent Pinchart laurent.pinch...@ideasonboard.com wrote: Hi Rob, On Tuesday 18 December 2012 00:21:32 Rob Clark wrote: On Mon, Dec 17, 2012 at 11:04 PM, Dave Airlie airl...@gmail.com wrote: Many developers showed interest in the first RFC, and I've had the

Re: [RFC v2 0/5] Common Display Framework

On Mon, Dec 24, 2012 at 11:09 AM, Laurent Pinchart laurent.pinch...@ideasonboard.com wrote: On the topic of discussions, would anyone be interested in a BoF/brainstorming/whatever session during the FOSDEM ? I will be at FOSDEM.. and from http://wiki.x.org/wiki/fosdem2013 it looks like at least

Re: [RFC v2 0/5] Common Display Framework

On Mon, Dec 24, 2012 at 11:27 AM, Laurent Pinchart laurent.pinch...@ideasonboard.com wrote: On Wednesday 19 December 2012 16:57:56 Jani Nikula wrote: It just seems to me that, at least from a DRM/KMS perspective, adding another layer (=CDF) for HDMI or DP (or legacy outputs) would be

Re: [RFC v2 0/5] Common Display Framework

On Mon, Dec 24, 2012 at 11:35 AM, Laurent Pinchart laurent.pinch...@ideasonboard.com wrote: On Wednesday 19 December 2012 09:26:40 Rob Clark wrote: And, there are also external HDMI encoders (for example connected over i2c) that can also be shared between boards. So I think there will be a

[Bug 43167] X intel driver causes wrong wraparound of console command line

https://bugs.freedesktop.org/show_bug.cgi?id=43167 Jani Nikula jani.nik...@intel.com changed: What|Removed |Added CC||jani.nik...@intel.com

[Bug 43167] X intel driver causes wrong wraparound of console command line

https://bugs.freedesktop.org/show_bug.cgi?id=43167 Jani Nikula jani.nik...@intel.com changed: What|Removed |Added Status|REOPENED|NEEDINFO --- Comment

[Bug 49981] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!

https://bugzilla.kernel.org/show_bug.cgi?id=49981 --- Comment #4 from Apostolos B. barz...@gmail.com 2012-12-27 18:16:42 --- I chasnged my DE from gnome 3 to E17 and i don't get that error anymore? Could it be related? -- Configure bugmail:

Re: [RFC v2 0/5] Common Display Framework

On Thu, Dec 27, 2012 at 09:54:55AM -0600, Rob Clark wrote: On Mon, Dec 24, 2012 at 7:37 AM, Laurent Pinchart laurent.pinch...@ideasonboard.com wrote: Hi Rob, On Tuesday 18 December 2012 00:21:32 Rob Clark wrote: On Mon, Dec 17, 2012 at 11:04 PM, Dave Airlie airl...@gmail.com wrote:

Re: [RFC v2 0/5] Common Display Framework

On Thu, Dec 27, 2012 at 10:04:22AM -0600, Rob Clark wrote: On Mon, Dec 24, 2012 at 11:27 AM, Laurent Pinchart laurent.pinch...@ideasonboard.com wrote: On Wednesday 19 December 2012 16:57:56 Jani Nikula wrote: It just seems to me that, at least from a DRM/KMS perspective, adding another

Re: [RFC v2 0/5] Common Display Framework

On Thu, Dec 27, 2012 at 1:18 PM, Sascha Hauer s.ha...@pengutronix.de wrote: On Thu, Dec 27, 2012 at 09:54:55AM -0600, Rob Clark wrote: On Mon, Dec 24, 2012 at 7:37 AM, Laurent Pinchart laurent.pinch...@ideasonboard.com wrote: Hi Rob, On Tuesday 18 December 2012 00:21:32 Rob Clark wrote:

Re: [RFC v2 0/5] Common Display Framework

On Thu, Dec 27, 2012 at 01:57:56PM -0600, Rob Clark wrote: On Thu, Dec 27, 2012 at 1:18 PM, Sascha Hauer s.ha...@pengutronix.de wrote: On Thu, Dec 27, 2012 at 09:54:55AM -0600, Rob Clark wrote: On Mon, Dec 24, 2012 at 7:37 AM, Laurent Pinchart This implies that the master driver knows all

[Bug 41265] Radeon KMS does not work on thunderbolt media dock

https://bugs.freedesktop.org/show_bug.cgi?id=41265 --- Comment #53 from Gerald Nunn gerald.b.n...@gmail.com --- Does AMD need to make a change to the proprietary fglrx drivers in order for the kernel patch to work with their drivers and if so has a bug been opened with them? I'm using Ubuntu

[PATCH] drm/exynos: Add device tree based discovery support for Exynos G2D

This patch adds device tree match table for Exynos G2D controller. Signed-off-by: Ajay Kumar ajaykumar...@samsung.com --- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/drivers/gpu/drm/exynos/exynos_drm_g2d.c

Re: [PATCH] video: drm: exynos: mie bypass enable for fimd

Hello Inki Dae, On Thu, Dec 27, 2012 at 11:47 AM, Inki Dae inki@samsung.com wrote: Hi, DISP1BLK_CFG register is related to GScaler, HDCP and MIXER as well. So it's not good that this register is controlled in fimd module. And I think the function to control the register should be placed

Re: [PATCH] video: drm: exynos: mie bypass enable for fimd

2012/12/28 Leela Krishna Amudala l.kris...@samsung.com: Hello Inki Dae, On Thu, Dec 27, 2012 at 11:47 AM, Inki Dae inki@samsung.com wrote: Hi, DISP1BLK_CFG register is related to GScaler, HDCP and MIXER as well. So it's not good that this register is controlled in fimd module. And I

Re: [RFC,libdrm 1/3] tegra: Add stream library

I just skimmed the code of libdrm while I'm trying to understand the host1x driver. So below is what I found. Mark On 12/13/2012 10:01 PM, Arto Meriläinen wrote: From: Arto Merilainen amerilai...@nvidia.com This patch introduces tegra stream library. The library is used for buffer

Re: [RFC,libdrm 1/3] tegra: Add stream library

On 12/28/2012 08:47 AM, Mark Zhang wrote: +int tegra_fence_is_valid(const struct tegra_fence *fence) +{ +int valid = fence ? 1 : 0; +valid = valid fence-id != (uint32_t) -1; +valid = valid fence-id 32; Hardcode here. Assume always has 32 syncpts. Change to a micro wrapped with

Re: [RFC,libdrm 1/3] tegra: Add stream library

On 12/28/2012 03:45 PM, Arto Merilainen wrote: On 12/28/2012 08:47 AM, Mark Zhang wrote: +int tegra_fence_is_valid(const struct tegra_fence *fence) +{ +int valid = fence ? 1 : 0; +valid = valid fence-id != (uint32_t) -1; +valid = valid fence-id 32; Hardcode here. Assume