Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Ard Biesheuvel <ardb@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: Javier Martinez Canillas <javierm@redhat.com>,
	x86@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
	loongarch@lists.linux.dev, linux-riscv@lists.infradead.org,
	dri-devel@lists.freedesktop.org, linux-hyperv@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 0/6] arch, sysfb: Move screen and edid info into single place
Date: Fri, 21 Nov 2025 16:53:49 +0100	[thread overview]
Message-ID: <199e7538-5b4a-483b-8976-84e4a8a0f2fd@suse.de> (raw)
In-Reply-To: <CAMj1kXF1Dh0RbuqYc0fhAPf-CM0mdYh8BhenM8-ugKVHfwnhBg@mail.gmail.com>

Hi

Am 21.11.25 um 16:16 schrieb Ard Biesheuvel:
> On Fri, 21 Nov 2025 at 16:10, Arnd Bergmann <arnd@arndb.de> wrote:
>> On Fri, Nov 21, 2025, at 14:36, Thomas Zimmermann wrote:
>>> Replace screen_info and edid_info with sysfb_primary_device of type
>>> struct sysfb_display_info. Update all users.
>>>
>>> Sysfb DRM drivers currently fetch the global edid_info directly, when
>>> they should get that information together with the screen_info from their
>>> device. Wrapping screen_info and edid_info in sysfb_primary_display and
>>> passing this to drivers enables this.
>>>
>>> Replacing both with sysfb_primary_display has been motivate by the EFI
>>> stub. EFI wants to transfer EDID via config table in a single entry.
>>> Using struct sysfb_display_info this will become easily possible. Hence
>>> accept some churn in architecture code for the long-term improvements.
>> This all looks good to me,
>>
>> Acked-by: Arnd Bergmann <arnd@arndb.de>

Thanks

>>
>> It should also bring us one step closer to eventually
>> disconnecting the x86 boot ABI from the kernel-internal
>> sysfb_primary_display.
>>
> Agreed
>
> Acked-by: Ard Biesheuvel <ardb@kernel.org>

Thanks

>
> I can take patches 1-2 right away, if that helps during the next cycle.

 From my sysfb-focused POV, these patches would ideally all go through 
the same tree, say efi or generic arch, or whatever fits best. Most of 
the other code is only renames anyway.

Best regards
Thomas


-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2025-11-21 15:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21 13:36 [PATCH 0/6] arch,sysfb: Move screen and edid info into single place Thomas Zimmermann
2025-11-21 13:36 ` [PATCH 1/6] efi: earlycon: Reduce number of references to global screen_info Thomas Zimmermann
2025-11-24  9:28   ` Richard Lyu
2025-11-21 13:36 ` [PATCH 2/6] efi: sysfb_efi: " Thomas Zimmermann
2025-11-24  9:30   ` Richard Lyu
2025-11-21 13:36 ` [PATCH 3/6] sysfb: Add struct sysfb_display_info Thomas Zimmermann
2025-11-21 13:36 ` [PATCH 4/6] sysfb: Replace screen_info with sysfb_primary_display Thomas Zimmermann
2025-11-21 13:36 ` [PATCH 5/6] sysfb: Pass sysfb_primary_display to devices Thomas Zimmermann
2025-11-21 13:36 ` [PATCH 6/6] sysfb: Move edid_info into sysfb_primary_display Thomas Zimmermann
2025-11-21 15:56   ` Thomas Zimmermann
2025-11-21 15:09 ` [PATCH 0/6] arch,sysfb: Move screen and edid info into single place Arnd Bergmann
2025-11-21 15:16   ` Ard Biesheuvel
2025-11-21 15:53     ` Thomas Zimmermann [this message]
2025-11-21 15:56       ` [PATCH 0/6] arch, sysfb: " Ard Biesheuvel
2025-11-21 16:08         ` Thomas Zimmermann
2025-11-21 16:09           ` Thomas Zimmermann
2025-11-21 16:19             ` Ard Biesheuvel
2025-11-21 16:26               ` Thomas Zimmermann
2025-11-21 16:31                 ` Ard Biesheuvel
2025-11-22 10:52                   ` Thomas Zimmermann
2025-11-22 11:42                     ` Ard Biesheuvel

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=199e7538-5b4a-483b-8976-84e4a8a0f2fd@suse.de \
    --to=tzimmermann@suse.de \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=loongarch@lists.linux.dev \
    --cc=x86@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