From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Stone <daniel@fooishbar.org>
Cc: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: display band (display area vs real visible area)
Date: Tue, 21 Mar 2023 14:07:43 +0200 [thread overview]
Message-ID: <87355y8fzk.fsf@intel.com> (raw)
In-Reply-To: <CAPj87rPPA9oYkZyQ=Y3MRuyJUN71WHDWHpdaRUvuXAxFSLW5SA@mail.gmail.com>
On Tue, 21 Mar 2023, Daniel Stone <daniel@fooishbar.org> wrote:
> Hi,
>
> On Tue, 21 Mar 2023 at 11:24, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>> On Tue, 21 Mar 2023, Michael Nazzareno Trimarchi <michael@amarulasolutions.com> wrote:
>> > On Tue, Mar 21, 2023 at 11:43 AM Jani Nikula
>> > <jani.nikula@linux.intel.com> wrote:
>> >> On Tue, 21 Mar 2023, Michael Nazzareno Trimarchi <michael@amarulasolutions.com> wrote:
>> >> > I would like to know the best approach in the graphics subsystem how
>> >> > deal with panels where the display area is different from the visible
>> >> > area because the display has a band left and right. I have already
>> >> > done the drm driver for the panel but from userspace point of view
>> >> > it's a pain to deal in wayland for input device and output device. Do
>> >> > you have any suggestions?
>> >>
>> >> Do you have the EDID for the panel?
>> >
>> > mipi->panel so should not have edid
>>
>> That's the kind of information you'd expect in the original question. ;)
>>
>> I've done that sort of thing in the past, but not sure if it would fly
>> upstream. Basically the kernel driver would lie about the resolution to
>> userspace, and handle the centering and the bands internally. In my
>> case, the DSI command mode panel in question had commands to set the
>> visible area, so the driver didn't have to do all that much extra to
>> make it happen.
>
> There have been some threads - mostly motivated by MacBooks and the
> Asahi team - about creating a KMS property to express invisible areas.
> This would be the same thing, and the userspace ecosystem will pick it
> up when the kernel exposes it.
In my case the kernel handled it completely internally, and the
userspace didn't even know. But I guess it depends on the display being
able to take a smaller framebuffer, otherwise I don't think it's
feasible.
I haven't checked the threads you mention but I assume it covers the
more general case of having rounded corners or holes for the camera, not
just the frame covering the edges or something like that. That couldn't
possibly be handled by kernel alone, but it's also a bunch of
infrastructure work both in kernel and userspace to make it happen.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-03-21 12:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 10:11 display band (display area vs real visible area) Michael Nazzareno Trimarchi
2023-03-21 10:43 ` Jani Nikula
2023-03-21 10:59 ` Michael Nazzareno Trimarchi
2023-03-21 11:24 ` Jani Nikula
2023-03-21 11:49 ` Daniel Stone
2023-03-21 11:50 ` Michael Nazzareno Trimarchi
2023-03-21 12:07 ` Jani Nikula [this message]
2023-03-21 12:15 ` Daniel Stone
2023-03-21 13:12 ` Michael Nazzareno Trimarchi
2023-03-21 15:17 ` Simon Ser
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=87355y8fzk.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel@fooishbar.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=michael@amarulasolutions.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.