From: Javier Martinez Canillas <javierm@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>, linux-kernel@vger.kernel.org
Cc: Albert Ou <aou@eecs.berkeley.edu>,
David Airlie <airlied@linux.ie>,
Catalin Marinas <catalin.marinas@arm.com>,
Russell King <linux@armlinux.org.uk>,
dri-devel@lists.freedesktop.org,
Hans de Goede <hdegoede@redhat.com>,
linux-efi@vger.kernel.org, Palmer Dabbelt <palmer@dabbelt.com>,
Peter Robinson <pbrobinson@gmail.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, Will Deacon <will@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] drivers/firmware: consolidate EFI framebuffer setup for all arches
Date: Wed, 23 Jun 2021 13:13:35 +0200 [thread overview]
Message-ID: <07745425-8d1b-5c0a-1622-cb08828d396c@redhat.com> (raw)
In-Reply-To: <9700697f-747c-fe36-d480-69762e845f30@suse.de>
Hello Thomas,
Thanks a lot for your feedback!
On 6/23/21 12:06 PM, Thomas Zimmermann wrote:
[snip]
>> config SYSFB
>> bool
>> default y
>> - depends on X86 || COMPILE_TEST
>> + depends on X86 || ARM || ARM64 || RISCV || COMPILE_TEST
>>
>> -config X86_SYSFB
>> +config SYSFB_SIMPLEFB
>
> You should also update the help text for simpledrm to reflect this
> change. See drivers/gpu/drm/tiny/Kconfig.
>
Indeed, I missed that. I'll update it in v3.
[snip]
>> +
>> +__init void sysfb_apply_efi_quirks(struct platform_device *pd)
>> {
>> if (screen_info.orig_video_isVGA != VIDEO_TYPE_EFI ||
>> !(screen_info.capabilities & VIDEO_CAPABILITY_SKIP_QUIRKS))
>> @@ -281,4 +348,10 @@ __init void sysfb_apply_efi_quirks(void)
>> screen_info.lfb_height = temp;
>> screen_info.lfb_linelength = 4 * screen_info.lfb_width;
>> }
>> +
>> + if (screen_info.orig_video_isVGA == VIDEO_TYPE_EFI &&
>> + IS_ENABLED(CONFIG_PCI)) {
>
> We have a 100-character limit now. This should (?) fit onto a single line.
>
>
Oh, I didn't know the character limit was extended to 100 chars now.
[snip]
>>
>> /* if the FB is incompatible, create a legacy framebuffer device */
>> if (si->orig_video_isVGA == VIDEO_TYPE_EFI)
>> - name = "efi-framebuffer";
>> + pd->name = "efi-framebuffer";
>> else if (si->orig_video_isVGA == VIDEO_TYPE_VLFB)
>> - name = "vesa-framebuffer";
>> + pd->name = "vesa-framebuffer";
>> else
>> - name = "platform-framebuffer";
>> + pd->name = "platform-framebuffer";
>
> You're allocating the platform device with an empty name string. And
> here you're overwriting the pointer. Can you rearrange the code to first
> detect a proper name and then allocate the device with that name? It
> takes a few bytes more memory, but seems in the spirit of the interface.
>
Right, I'll change that in v3 as well.
> Best regards
> Thomas
>
Best regards,
--
Javier Martinez Canillas
Software Engineer
New Platform Technologies Enablement team
RHEL Engineering
prev parent reply other threads:[~2021-06-23 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 15:00 Javier Martinez Canillas
2021-06-23 10:06 ` Thomas Zimmermann
2021-06-23 11:13 ` Javier Martinez Canillas [this message]
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=07745425-8d1b-5c0a-1622-cb08828d396c@redhat.com \
--to=javierm@redhat.com \
--cc=airlied@linux.ie \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pbrobinson@gmail.com \
--cc=tzimmermann@suse.de \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®