From: "Noralf Trønnes" <noralf@tronnes.org> To: Maxime Ripard <maxime.ripard@bootlin.com> Cc: eben@raspberrypi.org, David Airlie <airlied@linux.ie>, Maarten Lankhorst <maarten.lankhorst@linux.intel.com>, dri-devel@lists.freedesktop.org, Paul Kocialkowski <paul.kocialkowski@bootlin.com>, Sean Paul <seanpaul@chromium.org>, Thomas Petazzoni <thomas.petazzoni@bootlin.com>, Daniel Vetter <daniel.vetter@intel.com>, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v3 3/6] drm/modes: Allow to specify rotation and reflection on the commandline Date: Thu, 13 Jun 2019 16:12:05 +0200 [thread overview] Message-ID: <4169c6d9-5a64-8d05-9496-263cd9eda485@tronnes.org> (raw) In-Reply-To: <20190613125024.46yiiy6zrrqojajy@flea> Den 13.06.2019 14.50, skrev Maxime Ripard: > Hi, > > On Wed, Jun 12, 2019 at 03:21:19PM +0200, Noralf Trønnes wrote: >>>> The only way I see for that to happen, is to set >>>> ->panel_orientation. And to repeat myself, imo that makes >>>> 'orientation' a better name for this video= option. >>> >>> orientation and rotation are two different things to me. The >>> orientation of a panel for example is absolute, while the rotation is >>> a transformation. In this particular case, I think that both the >>> orientation and the rotation should be taken into account, with the >>> orientation being the default state, and the hardware / panel will >>> tell us that, while the rotation would be a transformation from that >>> default to whatever the user wants. >>> >>> More importantly, the orientation is a property of the hardware (ie, >>> how the display has been assembled), while the rotation is a software >>> construct. >>> >>> And if the property being used to expose that is the rotation, I guess >>> it would make sense to just use the same name and remain consistent. >> >> Ok, I see. Based on this, I would assume that rotation would be relative >> to the orientation, but I see that in this patch rotation doesn't take >> orintation into account, it just overwrites it. > > Yeah, that's a good point. I've updated the next version to add the > rotation on the command line to the orientation. > >> I don't how userspace deals with rotation on top of orientation. > > The orientation is exposed through the property, and the result is > available through the plane's rotation, so I guess that it's enough? > I was just wondering if Xserver/wayland applied rotation on top of orientation or not. Maybe it would make sense to treat internal drm clients the same. I understand that the DRM rotation property doesn't apply on top orientation, just wondering how mutter/wayland (whoever is in charge) does this. Not important to me, so feel free to disregard, I'm just wondering. Noralf. > Maxime > > -- > Maxime Ripard, Bootlin > Embedded Linux and Kernel engineering > https://bootlin.com > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "Noralf Trønnes" <noralf@tronnes.org> To: Maxime Ripard <maxime.ripard@bootlin.com> Cc: eben@raspberrypi.org, David Airlie <airlied@linux.ie>, dri-devel@lists.freedesktop.org, Paul Kocialkowski <paul.kocialkowski@bootlin.com>, Sean Paul <seanpaul@chromium.org>, Thomas Petazzoni <thomas.petazzoni@bootlin.com>, Daniel Vetter <daniel.vetter@intel.com>, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v3 3/6] drm/modes: Allow to specify rotation and reflection on the commandline Date: Thu, 13 Jun 2019 16:12:05 +0200 [thread overview] Message-ID: <4169c6d9-5a64-8d05-9496-263cd9eda485@tronnes.org> (raw) In-Reply-To: <20190613125024.46yiiy6zrrqojajy@flea> Den 13.06.2019 14.50, skrev Maxime Ripard: > Hi, > > On Wed, Jun 12, 2019 at 03:21:19PM +0200, Noralf Trønnes wrote: >>>> The only way I see for that to happen, is to set >>>> ->panel_orientation. And to repeat myself, imo that makes >>>> 'orientation' a better name for this video= option. >>> >>> orientation and rotation are two different things to me. The >>> orientation of a panel for example is absolute, while the rotation is >>> a transformation. In this particular case, I think that both the >>> orientation and the rotation should be taken into account, with the >>> orientation being the default state, and the hardware / panel will >>> tell us that, while the rotation would be a transformation from that >>> default to whatever the user wants. >>> >>> More importantly, the orientation is a property of the hardware (ie, >>> how the display has been assembled), while the rotation is a software >>> construct. >>> >>> And if the property being used to expose that is the rotation, I guess >>> it would make sense to just use the same name and remain consistent. >> >> Ok, I see. Based on this, I would assume that rotation would be relative >> to the orientation, but I see that in this patch rotation doesn't take >> orintation into account, it just overwrites it. > > Yeah, that's a good point. I've updated the next version to add the > rotation on the command line to the orientation. > >> I don't how userspace deals with rotation on top of orientation. > > The orientation is exposed through the property, and the result is > available through the plane's rotation, so I guess that it's enough? > I was just wondering if Xserver/wayland applied rotation on top of orientation or not. Maybe it would make sense to treat internal drm clients the same. I understand that the DRM rotation property doesn't apply on top orientation, just wondering how mutter/wayland (whoever is in charge) does this. Not important to me, so feel free to disregard, I'm just wondering. Noralf. > Maxime > > -- > Maxime Ripard, Bootlin > Embedded Linux and Kernel engineering > https://bootlin.com > _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-06-13 14:12 UTC|newest] Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-18 12:41 [PATCH v3 0/6] drm/vc4: Allow for more boot-time configuration Maxime Ripard 2019-04-18 12:41 ` Maxime Ripard 2019-04-18 12:41 ` [PATCH v3 1/6] drm/modes: Rewrite the command line parser Maxime Ripard 2019-04-18 12:41 ` Maxime Ripard 2019-04-18 16:11 ` Noralf Trønnes 2019-04-18 16:11 ` Noralf Trønnes 2019-04-18 12:41 ` [PATCH v3 2/6] drm/modes: Support modes names on the command line Maxime Ripard 2019-04-18 12:41 ` Maxime Ripard 2019-04-18 16:22 ` Noralf Trønnes 2019-04-18 16:22 ` Noralf Trønnes 2019-04-18 12:41 ` [PATCH v3 3/6] drm/modes: Allow to specify rotation and reflection on the commandline Maxime Ripard 2019-04-18 12:41 ` Maxime Ripard 2019-04-18 16:40 ` Noralf Trønnes 2019-04-18 16:40 ` Noralf Trønnes 2019-04-19 8:53 ` Noralf Trønnes 2019-04-19 8:53 ` Noralf Trønnes 2019-06-11 13:20 ` Maxime Ripard 2019-06-11 13:20 ` Maxime Ripard 2019-06-12 8:11 ` Jani Nikula 2019-06-12 8:11 ` Jani Nikula 2019-06-12 13:21 ` Noralf Trønnes 2019-06-12 13:21 ` Noralf Trønnes 2019-06-13 12:50 ` Maxime Ripard 2019-06-13 12:50 ` Maxime Ripard 2019-06-13 14:12 ` Noralf Trønnes [this message] 2019-06-13 14:12 ` Noralf Trønnes 2019-06-11 12:49 ` Maxime Ripard 2019-06-11 12:49 ` Maxime Ripard 2019-06-12 12:43 ` Noralf Trønnes 2019-06-12 12:43 ` Noralf Trønnes 2019-06-12 15:54 ` Maxime Ripard 2019-06-12 15:54 ` Maxime Ripard 2019-04-18 12:41 ` [PATCH v3 4/6] drm/modes: Parse overscan properties Maxime Ripard 2019-04-18 12:41 ` Maxime Ripard 2019-04-18 16:50 ` Noralf Trønnes 2019-04-18 16:50 ` Noralf Trønnes 2019-04-19 9:05 ` Noralf Trønnes 2019-04-19 9:05 ` Noralf Trønnes 2019-04-18 12:41 ` [PATCH v3 5/6] drm/selftests: Add command line parser selftests Maxime Ripard 2019-04-18 12:41 ` Maxime Ripard 2019-04-18 16:51 ` Noralf Trønnes 2019-04-18 16:51 ` Noralf Trønnes 2019-04-18 12:41 ` [PATCH v3 6/6] drm/vc4: hdmi: Set default state margin at reset Maxime Ripard 2019-04-18 12:41 ` Maxime Ripard 2019-04-18 16:59 ` Noralf Trønnes 2019-04-19 18:50 ` Noralf Trønnes 2019-04-19 18:50 ` Noralf Trønnes
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=4169c6d9-5a64-8d05-9496-263cd9eda485@tronnes.org \ --to=noralf@tronnes.org \ --cc=airlied@linux.ie \ --cc=daniel.vetter@intel.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=eben@raspberrypi.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=maarten.lankhorst@linux.intel.com \ --cc=maxime.ripard@bootlin.com \ --cc=paul.kocialkowski@bootlin.com \ --cc=seanpaul@chromium.org \ --cc=thomas.petazzoni@bootlin.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: linkBe 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.