From: Robin Murphy <robin.murphy@arm.com>
To: Javier Martinez Canillas <javierm@redhat.com>, liviu.dudau@arm.com
Cc: linux-arm-kernel@lists.infradead.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/arm/hdlcd: Take over EFI framebuffer properly
Date: Tue, 14 Jun 2022 14:36:41 +0100 [thread overview]
Message-ID: <f97d32f4-8391-cfdb-d1c7-2043634db83b@arm.com> (raw)
In-Reply-To: <e0468244-f1bc-e593-0840-252a92a900dd@redhat.com>
On 2022-06-14 14:26, Javier Martinez Canillas wrote:
> Hello Robin,
>
> On 6/14/22 15:04, Robin Murphy wrote:
>> The Arm Juno board EDK2 port has provided an EFI GOP display via HDLCD0
>> for some time now, which works nicely as an early framebuffer. However,
>> once the HDLCD driver probes and takes over the hardware, it should
>> take over the logical framebuffer as well, otherwise the now-defunct GOP
>> device hangs about and virtual console output inevitably disappears into
>> the wrong place most of the time.
>>
>> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
>> ---
>> drivers/gpu/drm/arm/hdlcd_drv.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/arm/hdlcd_drv.c b/drivers/gpu/drm/arm/hdlcd_drv.c
>> index af59077a5481..a5d04884658b 100644
>> --- a/drivers/gpu/drm/arm/hdlcd_drv.c
>> +++ b/drivers/gpu/drm/arm/hdlcd_drv.c
>> @@ -331,6 +331,8 @@ static int hdlcd_drm_bind(struct device *dev)
>> goto err_vblank;
>> }
>>
>> + drm_fb_helper_remove_conflicting_framebuffers(NULL, "hdlcd", false);
>> +
>
> Seems you are using an older base, since this function doesn't exist anymore
> after commit 603dc7ed917f ("drm/aperture: Inline fbdev conflict helpers into
> aperture helpers").
Ah, you got me! I'm having to work with a 5.10 kernel at the moment, but
the randomly-disappearing console had finally sufficiently annoyed me
into figuring out and fixing it.
> Instead, you should use the drm_aperture_remove_framebuffers() function, i.e:
>
> + drm_aperture_remove_framebuffers(false, &hdlcd_driver);
>
> If you do that and re-spin the patch, feel free to add:
>
> Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Thanks for the advice and review - I'll send a v2 later once I've had
time to build and boot test 5.19-rc.
Cheers,
Robin.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-14 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 13:04 [PATCH] drm/arm/hdlcd: Take over EFI framebuffer properly Robin Murphy
2022-06-14 13:26 ` Javier Martinez Canillas
2022-06-14 13:36 ` Robin Murphy [this message]
2022-06-14 13:48 ` Thomas Zimmermann
2022-06-14 21:06 ` Robin Murphy
2022-06-15 7:39 ` Thomas Zimmermann
2022-06-15 7:50 ` Javier Martinez Canillas
2022-06-15 7:53 ` Thomas Zimmermann
2022-06-15 8:00 ` Javier Martinez Canillas
2022-06-15 10:26 ` Liviu Dudau
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=f97d32f4-8391-cfdb-d1c7-2043634db83b@arm.com \
--to=robin.murphy@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liviu.dudau@arm.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