From: Sam Ravnborg <sam@ravnborg.org>
To: Jyri Sarha <jsarha@ti.com>
Cc: yamonkar@cadence.com, praneeth@ti.com, subhajit_paul@ti.com,
dri-devel@lists.freedesktop.org, peter.ujfalusi@ti.com,
tomi.valkeinen@ti.com, laurent.pinchart@ideasonboard.com,
sjakhade@cadence.com
Subject: Re: [PATCH 4/5] drm/tidss: New driver for TI Keystone platform Display SubSystem
Date: Sat, 30 Nov 2019 19:30:33 +0100 [thread overview]
Message-ID: <20191130183033.GA24722@ravnborg.org> (raw)
In-Reply-To: <66b7051a-5e16-e81c-cf78-4b99a802fd1b@ti.com>
Hi Jyri
> I am not so sure if the DSS go-bit functionality (hw support to commit
> changes to display during next vertical blank) so widely used concept
> that it would make sense to make drm wide helpers to handle it.
The question was the other way around.
I was just wondering if there is some of the present helpers
that the driver can benefit from.
It is not that I found something - it was just a drive-by comment.
Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-11-30 18:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 9:53 [PATCH 0/5] drm/tidss: New driver for TI Keystone platform Display SubSystem Jyri Sarha
2019-11-26 9:53 ` Jyri Sarha
2019-11-26 9:53 ` [PATCH 4/5] " Jyri Sarha
2019-11-26 9:53 ` Jyri Sarha
2019-11-26 21:26 ` Sam Ravnborg
2019-11-27 15:01 ` Jyri Sarha
2019-11-30 18:30 ` Sam Ravnborg [this message]
2019-11-26 9:53 ` [PATCH 5/5] MAINTAINERS: add entry for tidss Jyri Sarha
2019-11-26 9:53 ` Jyri Sarha
2019-11-26 9:54 ` [PATCH 1/5] dt-bindings: display: ti, k2g-dss: Add dt-schema yaml binding Jyri Sarha
2019-11-26 9:54 ` Jyri Sarha
2019-11-26 9:54 ` [PATCH 2/5] dt-bindings: display: ti, am65x-dss: " Jyri Sarha
2019-11-26 9:54 ` Jyri Sarha
2019-11-26 9:54 ` [PATCH 3/5] dt-bindings: display: ti, j721e-dss: " Jyri Sarha
2019-11-26 9:54 ` Jyri Sarha
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=20191130183033.GA24722@ravnborg.org \
--to=sam@ravnborg.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=peter.ujfalusi@ti.com \
--cc=praneeth@ti.com \
--cc=sjakhade@cadence.com \
--cc=subhajit_paul@ti.com \
--cc=tomi.valkeinen@ti.com \
--cc=yamonkar@cadence.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