From: Shawn Guo <shawnguo@kernel.org>
To: Laurentiu Palcu <laurentiu.palcu@nxp.com>
Cc: "David Airlie" <airlied@linux.ie>,
"Guido Günther" <agx@sigxcpu.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
dl-linux-imx <linux-imx@nxp.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Robert Chiras" <robert.chiras@nxp.com>
Subject: Re: [EXT] Re: [PATCH 0/2] drm: imx: Add NWL MIPI DSI host controller support
Date: Tue, 28 May 2019 16:15:21 +0800 [thread overview]
Message-ID: <20190528081520.GC6885@dragon> (raw)
In-Reply-To: <20190528070353.GA14871@fsr-ub1664-121>
Hi Laurentiu,
On Tue, May 28, 2019 at 07:03:54AM +0000, Laurentiu Palcu wrote:
> Hi Shawn, Lucas,
>
> On Tue, May 28, 2019 at 09:38:02AM +0800, Shawn Guo wrote:
> > Caution: EXT Email
> >
> > Hi Lucas,
> >
> > On Mon, May 27, 2019 at 03:36:53PM +0200, Lucas Stach wrote:
> > > We have been looking at how to support DCSS in mainline for a while,
> > > but most of the actual work got pushed behind in schedule due to other
> > > priorities.
> >
> > I have some time to contribute. Would you suggest how I should help
> > here?
> >
> > 1. You guys already have something close to completion and do not need
> > more hands.
> > 2. You guys already have some preliminary code and can use help from
> > others.
> > 3. You guys haven't got anything to start with, but just some design
> > principles that anyone who wants to work on it should consider.
> >
> > Which is the one that you want me to read?
>
> We're already working on clearing up the DCSS code and preparing it for
> upstreaming. It should be done in the following weeks.
Great! I will stay away from this then :)
> The reason we've
> been delaying this is because neither HDMI nor MIPI support was present
> and, until these are upstream, testing DCSS would be quite impossible.
Well, they have to be done one by one, and I guess DCSS should be the
first one. I think it's fine to test DCSS with out-of-tree HDMI or
MIPI driver which is not ready for submission yet.
Shawn
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-28 8:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 10:30 [PATCH 0/2] drm: imx: Add NWL MIPI DSI host controller support Guido Günther
2019-03-07 10:30 ` [PATCH 1/2] dt-bindings: imx: Add binding for IMX NWL mipi dsi host controller Guido Günther
2019-03-07 10:30 ` [PATCH 2/2] drm/imx: Add NWL MIPI DSI host controller support Guido Günther
2019-05-08 17:18 ` [PATCH 0/2] drm: imx: " Guido Günther
2019-05-27 2:24 ` Shawn Guo
2019-05-27 11:51 ` Guido Günther
2019-05-27 13:36 ` Lucas Stach
2019-05-27 17:54 ` Guido Günther
2019-05-28 1:38 ` Shawn Guo
2019-05-28 7:03 ` [EXT] " Laurentiu Palcu
2019-05-28 8:15 ` Shawn Guo [this message]
2019-05-28 9:33 ` Guido Günther
2019-05-28 10:10 ` Laurentiu Palcu
2019-06-05 8:13 ` Guido Günther
2019-07-31 11:10 ` Guido Günther
2019-05-28 8:19 ` Lucas Stach
2019-05-28 8:36 ` Daniel Vetter
2019-05-28 10:04 ` [EXT] " Laurentiu Palcu
2019-05-28 10:16 ` Lucas Stach
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=20190528081520.GC6885@dragon \
--to=shawnguo@kernel.org \
--cc=agx@sigxcpu.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=laurentiu.palcu@nxp.com \
--cc=linux-imx@nxp.com \
--cc=robert.chiras@nxp.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox