From: Mario Limonciello <superm1@kernel.org>
To: David Airlie <airlied@gmail.com>, Bjorn Helgaas <bhelgaas@google.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org (open list:DRM DRIVERS),
linux-kernel@vger.kernel.org (open list),
linux-pci@vger.kernel.org (open list:PCI SUBSYSTEM),
"Daniel Dadap" <ddadap@nvidia.com>,
"Mario Limonciello" <mario.limonciello@amd.com>
Subject: [PATCH v4 0/1] Move `boot_display` from PCI to DRM
Date: Mon, 21 Jul 2025 13:57:25 -0500 [thread overview]
Message-ID: <20250721185726.1264909-1-superm1@kernel.org> (raw)
From: Mario Limonciello <mario.limonciello@amd.com>
Shortly after the series for introducing boot_display was merged
Manivannan Sadhasivam suggested that it's better not to introduce
new top level PCI attributes where possible.
He proposed that the boot_display attribute should be provided by DRM
instead and that userspace should look for that.
Change the owner of `boot_display` from the PCI device to the DRM card.
This should also have the side effect that non-PCI DRM drivers can
add support more easily.
NOTE: If acceptable this should be merged through the PCI tree as it
depends upon changes and symbols from the boot_display series.
Mario Limonciello (1):
PCI: Move boot display attribute to drm
Documentation/ABI/testing/sysfs-bus-pci | 9 -----
drivers/gpu/drm/drm_sysfs.c | 41 ++++++++++++++++++++++
drivers/pci/pci-sysfs.c | 45 -------------------------
3 files changed, 41 insertions(+), 54 deletions(-)
base-commit: c4f2dc1e5293c4383844d8161d9922adda534e7c
--
2.43.0
next reply other threads:[~2025-07-21 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 18:57 Mario Limonciello [this message]
2025-07-21 18:57 ` [PATCH v4 1/1] PCI: Move boot display attribute " Mario Limonciello
2025-07-22 16:00 ` Manivannan Sadhasivam
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=20250721185726.1264909-1-superm1@kernel.org \
--to=superm1@kernel.org \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=ddadap@nvidia.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mario.limonciello@amd.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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®