From: Daniel Vetter <daniel@ffwll.ch>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
devicetree@vger.kernel.org, Jyri Sarha <jsarha@ti.com>,
dri-devel@lists.freedesktop.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [Patch v2 3/6] dt-bindings: display/ti: Add plane binding to dispc node
Date: Thu, 19 Apr 2018 08:35:29 +0200 [thread overview]
Message-ID: <20180419063529.GD31310@phenom.ffwll.local> (raw)
In-Reply-To: <40918ef0-247c-595f-5f0b-81a338bfac67@ti.com>
On Wed, Apr 04, 2018 at 05:56:46PM +0300, Tomi Valkeinen wrote:
> On 04/04/18 17:36, Laurent Pinchart wrote:
> > Hi Benoit,
> >
> > Thank you for the patch.
> >
> > On Monday, 26 March 2018 19:21:25 EEST Benoit Parrot wrote:
> >> Currently all available display pipelines (i.e. plane) and output port
> >> resources are exposed to user-space. In some cases it is needed to be
> >> able to restrict which resources are actually visible from user-space.
> >> Also in cases where a display wider than 2048 pixels is to be supported
> >> more than one video pipeline is needed. In this case the 2nd hardware
> >> pipeline needed is not visible to user space applications.
> >>
> >> These video pipeline definitions must be statically defined so that
> >> the number of visible pipelines does not change from the user-space
> >> perspective.
> >>
> >> In order to allow this we are adding an optional 'plane' sub-node to
> >> the generic DISPC node.
> >
> > I'm sorry but this is really configuration data, it doesn't describe the
> > hardware. I don't think these properties belong to DT.
>
> I agree, but the question then is: where should it be? There was a
> discussion in the v1 thread about this, and as far as I see, there are
> no other usable alternatives.
Runtime configuration and atomic_check not an option? See my reply in v1.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-19 6:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 16:21 [Patch v2 0/6] drm/omap: Add virtual-planes support Benoit Parrot
2018-03-26 16:21 ` [Patch v2 1/6] drm/omap: Add ability to filter out modes which can't be supported Benoit Parrot
2018-04-04 11:12 ` Tomi Valkeinen
2018-04-04 13:15 ` Benoit Parrot
2018-04-04 14:23 ` Laurent Pinchart
2018-04-05 10:21 ` Tomi Valkeinen
2018-04-24 19:08 ` Laurent Pinchart
2018-03-26 16:21 ` [Patch v2 2/6] dt-bindings: display/ti: Move common dispc bindings to omap-dss.txt Benoit Parrot
2018-04-04 14:29 ` Laurent Pinchart
2018-04-27 13:26 ` Benoit Parrot
2018-03-26 16:21 ` [Patch v2 3/6] dt-bindings: display/ti: Add plane binding to dispc node Benoit Parrot
2018-04-04 14:36 ` Laurent Pinchart
2018-04-04 14:56 ` Tomi Valkeinen
2018-04-19 6:35 ` Daniel Vetter [this message]
2018-03-26 16:21 ` [Patch v2 4/6] drm/omap: Add virtual plane DT parsing support Benoit Parrot
2018-03-26 16:21 ` [Patch v2 5/6] drm/omap: Add virtual plane support to omap_plane Benoit Parrot
2018-04-05 11:14 ` Tomi Valkeinen
2018-03-26 16:21 ` [Patch v2 6/6] drm/omap: Allow wider display when a virtual plane is available Benoit Parrot
2018-04-05 10:40 ` Tomi Valkeinen
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=20180419063529.GD31310@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=peter.ujfalusi@ti.com \
--cc=tomi.valkeinen@ti.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