From: Tomasz Figa <tomasz.figa@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org,
linux-samsung-soc@vger.kernel.org,
Dave Airlie <airlied@gmail.com>
Subject: Re: [PATCH] drm/exynos: fimd: Get signal polarities from device tree
Date: Sun, 19 May 2013 13:32:53 +0200 [thread overview]
Message-ID: <2077448.BOZFWf0KVq@flatron> (raw)
In-Reply-To: <20130501200025.GE5763@phenom.ffwll.local>
Hi,
On Wednesday 01 of May 2013 22:00:25 Daniel Vetter wrote:
> On Wed, May 01, 2013 at 09:06:09PM +0200, Tomasz Figa wrote:
> > This patch modifies the driver to perform two stage parsing of video
> > timings from device tree, to get timing information as struct
> > videomode, which contains more data than struct fb_videomode.
> >
> > Thanks to this change, information about polarity of control signals
> > (VSYNC, HSYNC, VDEN, VCLK) can be retrieved, in addition to standard
> > video timings.
> >
> > Signed-off-by: Tomasz Figa <tomasz.figa@gmail.com>
>
> Since the drm mode struct also contains flags for sync polarity ... why
> is there no direct of -> drm_mode function? Going through an fb
> videomode in a kms drm driver looks _really_ backwards to me.
>
> Cc'in Dave for the fun of it ;-)
Struct fb_videomode is what exynos_drm_fimd driver uses internally. Sure
it should use drm_mode, but this is not really related to this patch,
because the code added in this patch only fills in the pdata struct, which
for compatibility reasons (the same structure is used for both fbdev and
drm drivers) contains struct fb_videomode.
OK, now after having a bit of fun, could we merge this patch to at least
have usable support of parallel displays using this driver?
Best regards,
Tomasz
> Cheers, Daniel
>
> > ---
> >
> > drivers/gpu/drm/exynos/exynos_drm_fimd.c | 18 ++++++++++++++++--
> > 1 file changed, 16 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/exynos/exynos_drm_fimd.c
> > b/drivers/gpu/drm/exynos/exynos_drm_fimd.c index a1669d4..9023efa
> > 100644
> > --- a/drivers/gpu/drm/exynos/exynos_drm_fimd.c
> > +++ b/drivers/gpu/drm/exynos/exynos_drm_fimd.c
> > @@ -21,7 +21,9 @@
> >
> > #include <linux/pm_runtime.h>
> >
> > #include <video/of_display_timing.h>
> >
> > +#include <video/of_videomode.h>
> >
> > #include <video/samsung_fimd.h>
> >
> > +#include <video/videomode.h>
> >
> > #include <drm/exynos_drm.h>
> >
> > #include "exynos_drm_drv.h"
> >
> > @@ -928,18 +930,30 @@ static int fimd_probe(struct platform_device
> > *pdev)>
> > DRM_DEBUG_KMS("%s\n", __FILE__);
> >
> > if (pdev->dev.of_node) {
> >
> > + struct videomode vm;
> > +
> >
> > pdata = devm_kzalloc(dev, sizeof(*pdata), GFP_KERNEL);
> > if (!pdata) {
> >
> > DRM_ERROR("memory allocation for pdata failed\n");
> > return -ENOMEM;
> >
> > }
> >
> > - ret = of_get_fb_videomode(dev->of_node, &pdata-
>panel.timing,
> > - OF_USE_NATIVE_MODE);
> > + ret = of_get_videomode(dev->of_node, &vm,
OF_USE_NATIVE_MODE);
> >
> > if (ret) {
> >
> > DRM_ERROR("failed: of_get_fb_videomode() : %d\n",
ret);
> > return ret;
> >
> > }
> >
> > +
> > + fb_videomode_from_videomode(&vm, &pdata->panel.timing);
> > +
> > + if (vm.flags & DISPLAY_FLAGS_VSYNC_LOW)
> > + pdata->vidcon1 |= VIDCON1_INV_VSYNC;
> > + if (vm.flags & DISPLAY_FLAGS_HSYNC_LOW)
> > + pdata->vidcon1 |= VIDCON1_INV_HSYNC;
> > + if (vm.flags & DISPLAY_FLAGS_DE_LOW)
> > + pdata->vidcon1 |= VIDCON1_INV_VDEN;
> > + if (vm.flags & DISPLAY_FLAGS_PIXDATA_NEGEDGE)
> > + pdata->vidcon1 |= VIDCON1_INV_VCLK;
> >
> > } else {
> >
> > pdata = pdev->dev.platform_data;
> > if (!pdata) {
next prev parent reply other threads:[~2013-05-19 11:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 19:06 [PATCH] drm/exynos: fimd: Get signal polarities from device tree Tomasz Figa
2013-05-01 20:00 ` Daniel Vetter
2013-05-19 11:32 ` Tomasz Figa [this message]
2013-06-06 4:30 ` Joonyoung Shim
2013-06-06 9:47 ` Tomasz Figa
2013-06-07 0:27 ` Joonyoung Shim
2013-06-05 18:13 ` Tomasz Figa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2077448.BOZFWf0KVq@flatron \
--to=tomasz.figa@gmail.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-samsung-soc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.