[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <546470BC.4020104@samsung.com>
Date: Thu, 13 Nov 2014 17:50:04 +0900
From: Inki Dae <inki.dae@...sung.com>
To: Andrzej Hajda <a.hajda@...sung.com>
Cc: Marek Szyprowski <m.szyprowski@...sung.com>,
Joonyoung Shim <jy0922.shim@...sung.com>,
Seung-Woo Kim <sw0312.kim@...sung.com>,
Kyungmin Park <kyungmin.park@...sung.com>,
Kukjin Kim <kgene.kim@...sung.com>,
"open list:DRM DRIVERS FOR E..." <dri-devel@...ts.freedesktop.org>,
"moderated list:ARM/S5P EXYNOS AR..."
<linux-samsung-soc@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] drm/exynos/dsi: remove global display variable
On 2014년 10월 07일 21:01, Andrzej Hajda wrote:
> Hi Inki,
>
> Many Exynos DRM drivers uses global variables to represent associated devices
> in Exynos DRM internal framework. It is quite confusing, it adds data duplication
> and finally it does not allow to handle more than one device in system.
> It seems better to embed such structures in private context of the device.
>
> The patchset is based on exynos_drm_next plus my patch [1]:
> 'drm/exynos: remove explicit encoder/connector de-initialization'.
>
> If the patchset is OK for you I can prepare similar patches for other Exynos DRM components.
Sorry for late. Applied. Can you prepare similar patches for other? If
so, I'd happy.
Thanks,
Inki Dae
>
> [1]: https://lkml.org/lkml/2014/9/22/148
>
> Regards
> Andrzej
>
>
> Andrzej Hajda (4):
> drm/exynos/dsi: remove global variable exynos_dsi_display
> drm/exynos/dsi: simplify device pointer evaluation
> drm/exynos/dsi: remove redundant encoder field
> drm/exynos/dsi: stop using display->ctx pointer
>
> drivers/gpu/drm/exynos/exynos_drm_dsi.c | 96 ++++++++++++++++-----------------
> 1 file changed, 47 insertions(+), 49 deletions(-)
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists