From: Hans de Goede <hdegoede@redhat.com>
To: Sebastian Reichel <sebastian.reichel@collabora.co.uk>,
Hans de Goede <j.w.r.degoede@gmail.com>
Cc: linux-fbdev@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Daniel Drake <drake@endlessm.com>,
dri-devel@lists.freedesktop.org,
Bastien Nocera <hadess@hadess.net>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH v3 1/7] fbcon: Add fbcon_rotate_hint to struct fb_info
Date: Mon, 23 Oct 2017 13:54:25 +0000 [thread overview]
Message-ID: <e67bcf49-3a08-6e6e-48a7-7e1a688394ca@redhat.com> (raw)
In-Reply-To: <20171023124326.db5mbmtseblb4fj7@earth>
Hi,
On 23-10-17 14:43, Sebastian Reichel wrote:
> Hi Hans,
>
> On Mon, Oct 23, 2017 at 09:14:19AM +0200, Hans de Goede wrote:
>> On some hardware the LCD panel is not mounted upright in the casing,
>> but upside-down or rotated 90 degrees. In this case we want the console
>> to automatically be rotated to compensate.
>>
>> The fbdev-driver may know about the need to rotate. Add a new
>> fbcon_rotate_hint field to struct fb_info, which gets initialized to -1.
>> If the fbdev-driver knows that some sort of rotation is necessary then
>> it can set this field to a FB_ROTATE_* value to tell the fbcon console
>> driver to rotate the console.
>>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>
> Thanks for your work. I will give it a try with Droid 4 and N950
> once I find some time :)
Ah, I did not even realize that this work would be useful for those
too, but yes that makes sense.
> [...]
>
>> + p->con_rotate = initial_rotation;
>> + if (p->con_rotate = -1)
>> + p->con_rotate = info->fbcon_rotate_hint;
>> + if (p->con_rotate = -1)
>> p->con_rotate = fbcon_platform_get_rotate(info);
>
> [...]
>
>> + p->con_rotate = initial_rotation;
>> + if (p->con_rotate = -1)
>> + p->con_rotate = info->fbcon_rotate_hint;
>> + if (p->con_rotate = -1)
>> p->con_rotate = fbcon_platform_get_rotate(info);
>> +
>
> maybe add a little helper function to reduce code duplication?
Maybe, I took a look and there already is a fbcon_set_rotation()
helper which does something completely different, so it might
be best to just keep this as is to avoid confusion between
2 similar named functions.
Regards,
Hans
next prev parent reply other threads:[~2017-10-23 13:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 7:14 [PATCH v3 0/7] drm/fbdev: Panel orientation connector property support Hans de Goede
2017-10-23 7:14 ` [PATCH v3 1/7] fbcon: Add fbcon_rotate_hint to struct fb_info Hans de Goede
2017-10-23 12:43 ` Sebastian Reichel
2017-10-23 13:54 ` Hans de Goede [this message]
2017-10-23 7:14 ` [PATCH v3 2/7] drm: Add panel orientation quirks Hans de Goede
2017-10-30 9:39 ` [Intel-gfx] " Daniel Vetter
2017-10-30 10:52 ` Hans de Goede
2017-10-23 7:14 ` [PATCH v3 3/7] drm: Add support for a panel-orientation connector property Hans de Goede
2017-10-30 9:43 ` [Intel-gfx] " Daniel Vetter
2017-10-30 10:57 ` Hans de Goede
2017-10-31 10:07 ` Daniel Vetter
2017-10-23 7:14 ` [PATCH v3 4/7] drm/fb-helper: Apply panel orientation connector prop to the primary plane Hans de Goede
2017-10-30 9:52 ` [Intel-gfx] [PATCH v3 4/7] drm/fb-helper: Apply panel orientation connector prop to the primary Daniel Vetter
2017-10-30 11:09 ` Hans de Goede
2017-10-31 10:14 ` Daniel Vetter
2017-10-31 10:24 ` Hans de Goede
2017-10-31 10:40 ` Daniel Vetter
2017-10-23 7:14 ` [PATCH v3 5/7] drm/i915: Add "panel orientation" property to the panel connector Hans de Goede
2017-10-23 7:14 ` [PATCH v3 6/7] efifb: Set info->fbcon_rotate_hint based on drm_get_panel_orientation_quirk Hans de Goede
2017-10-30 9:53 ` [Intel-gfx] [PATCH v3 6/7] efifb: Set info->fbcon_rotate_hint based on drm_get_panel_orientation Daniel Vetter
2017-10-30 11:10 ` Hans de Goede
2017-11-04 13:13 ` Hans de Goede
2017-10-23 7:14 ` [PATCH v3 7/7] fbcon: Remove dmi quirk table Hans de Goede
2017-10-30 9:58 ` [Intel-gfx] [PATCH v3 0/7] drm/fbdev: Panel orientation connector property support Daniel Vetter
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=e67bcf49-3a08-6e6e-48a7-7e1a688394ca@redhat.com \
--to=hdegoede@redhat.com \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.vetter@intel.com \
--cc=drake@endlessm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hadess@hadess.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=j.w.r.degoede@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=sebastian.reichel@collabora.co.uk \
/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).