From: Pekka Paalanen <ppaalanen@gmail.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: "Noralf Trønnes" <noralf@tronnes.org>,
"Maxime Ripard" <maxime@cerno.tech>,
dri-devel@lists.freedesktop.org,
"Mateusz Kwiatkowski" <kfyatek+publicgit@gmail.com>
Subject: Re: [PATCH] drm: document TV margin properties
Date: Tue, 28 Feb 2023 14:24:23 +0200 [thread overview]
Message-ID: <20230228142423.08213444@eldfell> (raw)
In-Reply-To: <Y/3lcEq5y2SrUYyA@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
On Tue, 28 Feb 2023 13:28:48 +0200
Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Tue, Feb 28, 2023 at 12:12:22PM +0200, Pekka Paalanen wrote:
> > Oh! That would be really good to mention in the doc. Maybe even prefer
> > plane props over this? Or is this for analog TV, and plane props for
> > digital TV?
>
> Plane properties would be pointless for this. CRTC properties might
> make sense. But what is more accurate kinda depends on the hardware
> design.
I meant the existing plane properties CRTC_X,Y,W,H. They can already
describe e.g. a primary plane that does not cover the whole CRTC area,
which is essentially the same as margins, scaling included even.
> Some hardware has scalers and all kinds of fancy stuff in the
> encoder essentially. Quite common in old TV encoder chips.
> That's pretty much where these properties came from I think.
>
> And eDP/LVDS/etc. also do scaling in the connector in the
> current model since that's where the 'scaling mode' property
> lives.
Ok, that makes sense.
Thanks,
pq
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-02-28 12:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 12:21 [PATCH] drm: document TV margin properties Simon Ser
2023-02-27 12:27 ` Maxime Ripard
2023-02-27 14:18 ` Dave Stevenson
2023-02-28 8:46 ` Pekka Paalanen
2023-02-28 9:53 ` Simon Ser
2023-02-28 10:12 ` Pekka Paalanen
2023-02-28 11:28 ` Ville Syrjälä
2023-02-28 12:21 ` Simon Ser
2023-02-28 12:24 ` Pekka Paalanen [this message]
2023-02-28 12:30 ` Ville Syrjälä
2023-02-28 11:37 ` Dave Stevenson
2023-02-28 11:45 ` Ville Syrjälä
2023-02-28 11:52 ` Dave Stevenson
2023-02-28 12:08 ` Ville Syrjälä
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=20230228142423.08213444@eldfell \
--to=ppaalanen@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kfyatek+publicgit@gmail.com \
--cc=maxime@cerno.tech \
--cc=noralf@tronnes.org \
--cc=ville.syrjala@linux.intel.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.