From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: mpartap@gmx.net, tony@atomide.com, merlijn@wizzup.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
sre@kernel.org, nekit1000@gmail.com, Pavel Machek <pavel@ucw.cz>,
linux-omap@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: omap4: support for manually updated display
Date: Mon, 10 Sep 2018 15:24:37 +0300 [thread overview]
Message-ID: <3205865.8O8aibZXye@avalon> (raw)
In-Reply-To: <797c13fa-7a5b-a809-7dd0-14b01a3046be@ti.com>
Hello,
On Monday, 10 September 2018 14:59:23 EEST Tomi Valkeinen wrote:
> Hi Pavel,
>
> (dropping Dave, no need to spam him)
>
> On 30/08/18 12:04, Pavel Machek wrote:
> > Hi!
> >
> > There's neat series of patches on
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git/log/
> > ?h=droid4-pending-v4.19
> >
> > They enable display support for my hardware. As you can imagine,
> > display is rather important for a cellphone.
> >
> > Tomi, can you take the patches? I can resubmit them in email, or
> > shuffle them to another branch without mfd changes, or clean them up
> > etc...
>
> A large omapdrm change set from Laurent was merged into drm-next, and
> I'm certain they conflict with this series. Laurent also has continued
> that work, and while those new patches haven't been sent for review yet,
> I fear they'll also conflict with these.
>
> So in the minimum, a rebase on top of drm-next is needed.
>
> I also continue to be very worried that adding DSI support to omapdrm at
> this stage will be a huge extra burden for Laurent's work.
>
> We should transform the panel-dsi-cm.c towards the common DRM model.
> With a quick look, there seems to be a driver for Samsung's S6E63J0X03
> panel. So possibly all the DSI features are there in the DRM framework,
> but someone needs to check that and start working on panel-dsi-cm.c so
> that it's ready when we finally switch to the DRM model.
>
> In my opinion, which I've also expressed before, the above work is much
> easier to do by first changing the omapdrm to DRM model, without any DSI
> displays, and then add the DSI command mode support. But if people
> insist on adding the DSI support already now, I would appreciate the
> same people working on the DSI support so that Laurent doesn't have to
> do it all.
I want to make it clear that I don't want to claim any privilege in getting
patches merged first. I am however worried that, without an easy way to test
DSI support, and without enough time to focus on it, I would break whatever
would be merged now in future reworks. I would thus like to find out how to
collaborate on this task, hopefully to move towards usage of drm_bridge and
drm_panel for DSI-based pipelines.
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: omap4: support for manually updated display
Date: Mon, 10 Sep 2018 15:24:37 +0300 [thread overview]
Message-ID: <3205865.8O8aibZXye@avalon> (raw)
In-Reply-To: <797c13fa-7a5b-a809-7dd0-14b01a3046be@ti.com>
Hello,
On Monday, 10 September 2018 14:59:23 EEST Tomi Valkeinen wrote:
> Hi Pavel,
>
> (dropping Dave, no need to spam him)
>
> On 30/08/18 12:04, Pavel Machek wrote:
> > Hi!
> >
> > There's neat series of patches on
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git/log/
> > ?h=droid4-pending-v4.19
> >
> > They enable display support for my hardware. As you can imagine,
> > display is rather important for a cellphone.
> >
> > Tomi, can you take the patches? I can resubmit them in email, or
> > shuffle them to another branch without mfd changes, or clean them up
> > etc...
>
> A large omapdrm change set from Laurent was merged into drm-next, and
> I'm certain they conflict with this series. Laurent also has continued
> that work, and while those new patches haven't been sent for review yet,
> I fear they'll also conflict with these.
>
> So in the minimum, a rebase on top of drm-next is needed.
>
> I also continue to be very worried that adding DSI support to omapdrm at
> this stage will be a huge extra burden for Laurent's work.
>
> We should transform the panel-dsi-cm.c towards the common DRM model.
> With a quick look, there seems to be a driver for Samsung's S6E63J0X03
> panel. So possibly all the DSI features are there in the DRM framework,
> but someone needs to check that and start working on panel-dsi-cm.c so
> that it's ready when we finally switch to the DRM model.
>
> In my opinion, which I've also expressed before, the above work is much
> easier to do by first changing the omapdrm to DRM model, without any DSI
> displays, and then add the DSI command mode support. But if people
> insist on adding the DSI support already now, I would appreciate the
> same people working on the DSI support so that Laurent doesn't have to
> do it all.
I want to make it clear that I don't want to claim any privilege in getting
patches merged first. I am however worried that, without an easy way to test
DSI support, and without enough time to focus on it, I would break whatever
would be merged now in future reworks. I would thus like to find out how to
collaborate on this task, hopefully to move towards usage of drm_bridge and
drm_panel for DSI-based pipelines.
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Pavel Machek <pavel@ucw.cz>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, sre@kernel.org,
nekit1000@gmail.com, mpartap@gmx.net, merlijn@wizzup.org
Subject: Re: omap4: support for manually updated display
Date: Mon, 10 Sep 2018 15:24:37 +0300 [thread overview]
Message-ID: <3205865.8O8aibZXye@avalon> (raw)
In-Reply-To: <797c13fa-7a5b-a809-7dd0-14b01a3046be@ti.com>
Hello,
On Monday, 10 September 2018 14:59:23 EEST Tomi Valkeinen wrote:
> Hi Pavel,
>
> (dropping Dave, no need to spam him)
>
> On 30/08/18 12:04, Pavel Machek wrote:
> > Hi!
> >
> > There's neat series of patches on
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git/log/
> > ?h=droid4-pending-v4.19
> >
> > They enable display support for my hardware. As you can imagine,
> > display is rather important for a cellphone.
> >
> > Tomi, can you take the patches? I can resubmit them in email, or
> > shuffle them to another branch without mfd changes, or clean them up
> > etc...
>
> A large omapdrm change set from Laurent was merged into drm-next, and
> I'm certain they conflict with this series. Laurent also has continued
> that work, and while those new patches haven't been sent for review yet,
> I fear they'll also conflict with these.
>
> So in the minimum, a rebase on top of drm-next is needed.
>
> I also continue to be very worried that adding DSI support to omapdrm at
> this stage will be a huge extra burden for Laurent's work.
>
> We should transform the panel-dsi-cm.c towards the common DRM model.
> With a quick look, there seems to be a driver for Samsung's S6E63J0X03
> panel. So possibly all the DSI features are there in the DRM framework,
> but someone needs to check that and start working on panel-dsi-cm.c so
> that it's ready when we finally switch to the DRM model.
>
> In my opinion, which I've also expressed before, the above work is much
> easier to do by first changing the omapdrm to DRM model, without any DSI
> displays, and then add the DSI command mode support. But if people
> insist on adding the DSI support already now, I would appreciate the
> same people working on the DSI support so that Laurent doesn't have to
> do it all.
I want to make it clear that I don't want to claim any privilege in getting
patches merged first. I am however worried that, without an easy way to test
DSI support, and without enough time to focus on it, I would break whatever
would be merged now in future reworks. I would thus like to find out how to
collaborate on this task, hopefully to move towards usage of drm_bridge and
drm_panel for DSI-based pipelines.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2018-09-10 12:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 9:04 omap4: support for manually updated display Pavel Machek
2018-08-30 9:04 ` Pavel Machek
2018-09-10 11:59 ` Tomi Valkeinen
2018-09-10 11:59 ` Tomi Valkeinen
2018-09-10 11:59 ` Tomi Valkeinen
2018-09-10 12:24 ` Laurent Pinchart [this message]
2018-09-10 12:24 ` Laurent Pinchart
2018-09-10 12:24 ` Laurent Pinchart
2018-09-10 17:44 ` Tony Lindgren
2018-09-10 17:44 ` Tony Lindgren
2018-09-11 6:48 ` Tomi Valkeinen
2018-09-11 6:48 ` Tomi Valkeinen
2018-09-11 6:48 ` Tomi Valkeinen
2018-10-18 22:15 ` Pavel Machek
2018-10-18 22:15 ` Pavel Machek
2018-10-19 16:44 ` Tony Lindgren
2018-10-19 16:44 ` Tony Lindgren
2018-10-19 22:58 ` Sebastian Reichel
2018-10-19 22:58 ` Sebastian Reichel
2018-10-19 22:58 ` Sebastian Reichel
2018-10-20 0:38 ` Tony Lindgren
2018-10-20 0:38 ` Tony Lindgren
2018-10-22 8:14 ` Tomi Valkeinen
2018-10-22 8:14 ` Tomi Valkeinen
2018-10-22 8:14 ` Tomi Valkeinen
2018-10-22 16:31 ` Tony Lindgren
2018-10-22 16:31 ` Tony Lindgren
2018-10-22 18:43 ` Tony Lindgren
2018-10-22 18:43 ` Tony Lindgren
2018-10-31 13:10 ` Laurent Pinchart
2018-10-31 13:10 ` Laurent Pinchart
2018-10-31 13:10 ` Laurent Pinchart
2018-09-10 21:28 ` Sebastian Reichel
2018-09-10 21:28 ` Sebastian Reichel
2018-09-11 12:54 ` Pavel Machek
2018-09-11 12:54 ` Pavel Machek
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=3205865.8O8aibZXye@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=pavel@ucw.cz \
--cc=sre@kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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 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.