From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: omap4: support for manually updated display
Date: Fri, 19 Oct 2018 09:44:50 -0700 [thread overview]
Message-ID: <20181019164450.GD43338@atomide.com> (raw)
In-Reply-To: <20181018221549.GB6364@amd>
* Pavel Machek <pavel@ucw.cz> [181018 22:15]:
> Hi!
>
> > > 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.
> >
> > Real users with mainline kernel with a real product should
> > always have priority over any ongoing clean-up.
> >
> > And for testing, a bunch of real users is something you can't
> > beat for proper testing of code on ongoing basis!
> >
> > Naturally the burden of getting the patches ready is on the people
> > using them for rebase and fixing comments. And Sebastian has
> > already agreed help with maintaining it.
> >
> > I've been actually using DSI command mode support and testing
> > Linux next several times a week to prevent regressions from
> > sneaking into -rc1 in general. So now I can't test omapdrm with
> > next until Sebastian is done with rebasing.. Back to headless
> > testing then.
> >
> > Anyways, I'd say let's add the DSI command mode support ASAP after
> > rebasing, there are at least Sebastian, Pavel and I then testing
> > and helping with further ongoing panel conversion work.
>
> Are there any news here? Does someone have a patch set that actually
> works?
I was wondering about that too.. I only have the v4.19-rc1 based
patches and can no longer test with Linux next. Sebastian, any
update?
> Are there any in-progress patches I could help with?
I can put in some effort too if needed.
Regards,
Tony
next prev parent reply other threads:[~2018-10-19 16:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 9:04 omap4: support for manually updated display Pavel Machek
2018-09-10 11:59 ` Tomi Valkeinen
2018-09-10 12:24 ` Laurent Pinchart
2018-09-10 17:44 ` Tony Lindgren
2018-09-11 6:48 ` Tomi Valkeinen
2018-10-18 22:15 ` Pavel Machek
2018-10-19 16:44 ` Tony Lindgren [this message]
2018-10-19 22:58 ` Sebastian Reichel
2018-10-20 0:38 ` Tony Lindgren
2018-10-22 8:14 ` Tomi Valkeinen
2018-10-22 16:31 ` Tony Lindgren
2018-10-22 18:43 ` Tony Lindgren
2018-10-31 13:10 ` Laurent Pinchart
2018-09-10 21:28 ` Sebastian Reichel
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=20181019164450.GD43338@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).