Skip to content

Alternative approach for boot_display visibility

Mario Limonciello dri-devel linux-pci lkml 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v5 Latest2 patches 0 repliesNew

Patches in v5 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2fbcon: Stop using screen_info_pci_dev()arch/x86/video/video-common.c+10 -20 replies
2/2PCI: Adjust visibility of boot_display attribute instead of creationdrivers/pci/pci-sysfs.c+20 -380 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v5 yet.

Read the v5 thread

Cover letter [PATCH v5 0/2] Alternative approach for boot_display visibility

From: Mario Limonciello <[email protected]>

The past few days there have been various discussions about what to do with the boot_display sysfs file so that it doesn't need to be made so late in startup.

Bjorn had an aha moment pointing out that there is no reason to "find" the PCI device using screen_info_pci_dev() because the device is already known. Instead we just need to check if it has the screen resources.

This series adjusts the boot_display behavior to use that and then convert boot_display into a static sysfs file that can be loaded when the device is created without needing to change visibility.

This is an ALTERNATIVE to moving it to DRM, which is what v4 does [1]. Either solution can be picked up depending upon the collective decision whether to keep boot_display file in PCI core or DRM core.

Mario Limonciello (2):
fbcon: Stop using screen_info_pci_dev()
PCI: Adjust visibility of boot_display attribute instead of creation

 arch/x86/video/video-common.c | 12 ++++++--
 drivers/pci/pci-sysfs.c       | 58 ++++++++++++-----------------------
 2 files changed, 30 insertions(+), 40 deletions(-)
Signature · 1 line
2.48.1