All of lore.kernel.org
 help / color / mirror / Atom feed
From: Meng Yi <meng.yi@nxp.com>
To: Stefan Agner <stefan@agner.ch>
Cc: Jianwei Wang <jianwei.wang.chn@gmail.com>,
	Xiubo Li <lixiubo@cmss.chinamobile.com>,
	Huan Wang <alison.wang@nxp.com>,
	"emil.l.velikov@gmail.com" <emil.l.velikov@gmail.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"maxime.ripard@free-electrons.com"
	<maxime.ripard@free-electrons.com>,
	"alexander.stein@systec-electronic.com"
	<alexander.stein@systec-electronic.com>
Subject: RE: [PATCH v2 1/2] drm/fsl-dcu: Add HDMI driver for freescale DCU
Date: Mon, 20 Jun 2016 07:02:08 +0000	[thread overview]
Message-ID: <HE1PR04MB1051CAAC4DC880CFFC8F2528EC2A0@HE1PR04MB1051.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <75453188206f2fc756711cbd34c6dc85@agner.ch>

Hi Stefan,

Thank for your reply.

> I took a bit more time to understand what it is all about with this patchset and
> the DRM bridge infrastructure in general.
> 
> I agree with Boris Brezillions comment of the first version of this
> patchset: You "only" want to add DRM bridge support here, it doesn't has
> anything to do with HDMI. So there should not be a file called
> fsl_dcu_drm_hdmi.c for instance....
> 
> In fact, you should fold the DRM bridge code into fsl_dcu_drm_rgb.c.
> Have a look at Boris patch which added such support to the Atmel HLDCD
> driver:
> https://lists.freedesktop.org/archives/dri-devel/2016-January/098050.html
> 
> However, the HLDCD driver already supported the endpoint syntax for panels
> at that time, which is not the case for the DCU driver.
> 
> Panel support with endpoint DT syntax seems to be more generic and is a
> easier first step towards DRM bridge support. Hence I suggest to take this two
> steps:
> 
> 1. Extend the current code to support panels through endpoint syntax
> (of_graph..)
> 2. Extend the endpoint support to also support DRM bridges
> 
> During 1 you should be careful to not remove the old fsl,panel support
> (backward compatibility). But it shouldn't be a big deal, just check if the
> fsl,panel property is there, if it is, do not parse the endpoints.
> Such backward compatibility has been implemented here:
> https://patchwork.kernel.org/patch/7706481/
> 

That's more reasonable. Thank much for your information and guidance!
I will working on that and send the patch later.

Best Regards,
Meng Yi



_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2016-06-20  7:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14  9:20 [PATCH v2 1/2] drm/fsl-dcu: Add HDMI driver for freescale DCU Meng Yi
2016-06-14  9:20 ` [PATCH v2 2/2] Add DT binding doc for DCU for ls1021a-twr Meng Yi
2016-06-14  9:54 ` [PATCH v2 1/2] drm/fsl-dcu: Add HDMI driver for freescale DCU Alexander Stein
2016-06-15  2:25   ` Meng Yi
2016-06-19  3:00 ` Stefan Agner
2016-06-20  7:02   ` Meng Yi [this message]

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=HE1PR04MB1051CAAC4DC880CFFC8F2528EC2A0@HE1PR04MB1051.eurprd04.prod.outlook.com \
    --to=meng.yi@nxp.com \
    --cc=alexander.stein@systec-electronic.com \
    --cc=alison.wang@nxp.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=jianwei.wang.chn@gmail.com \
    --cc=lixiubo@cmss.chinamobile.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=stefan@agner.ch \
    /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.