MAINTAINERS | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)
Multiple DRM Rust drivers (e.g. nova-core, nova-drm, Tyr, rvkms) are in
development, with at least Nova and (soon) Tyr already upstream. Having a
shared tree will ease and accelerate development, since all drivers can
consume new infrastructure in the same release cycle.
This includes infrastructure shared with other subsystem trees (e.g. Rust
or driver-core). By consolidating in drm-rust, we avoid adding extra
burden to drm-misc maintainers, e.g. dealing with cross-tree topic
branches.
The drm-misc tree is not a good fit for this stage of development, since
its documented scope is small drivers with occasional large series.
Rust drivers in development upstream, however, regularly involve large
patch series, new infrastructure, and shared topic branches, which may
not align well with drm-misc at this stage.
The drm-rust tree may not be a permanent solution. Once the core Rust,
DRM, and KMS infrastructure have stabilized, drivers and infrastructure
changes are expected to transition into drm-misc or standalone driver
trees respectively. Until then, drm-rust provides a dedicated place to
coordinate development without disrupting existing workflows too much.
Cc: Alice Ryhl <aliceryhl@google.com>
Cc: David Airlie <airlied@gmail.com>
Cc: Simona Vetter <simona@ffwll.ch>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Maxime Ripard <mripard@kernel.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Alexandre Courbot <acourbot@nvidia.com>
Cc: Daniel Almeida <daniel.almeida@collabora.com>
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
---
MAINTAINERS | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index fe168477caa4..1cd6597c7f1d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8079,7 +8079,6 @@ F: Documentation/devicetree/bindings/gpu/
F: Documentation/gpu/
F: drivers/gpu/drm/
F: drivers/gpu/vga/
-F: rust/kernel/drm/
F: include/drm/drm
F: include/linux/vga*
F: include/uapi/drm/
@@ -8096,6 +8095,16 @@ X: drivers/gpu/drm/radeon/
X: drivers/gpu/drm/tegra/
X: drivers/gpu/drm/xe/
+DRM DRIVERS AND COMMON INFRASTRUCTURE [RUST]
+M: Danilo Krummrich <dakr@kernel.org>
+M: Alice Ryhl <aliceryhl@google.com>
+S: Supported
+W: https://drm.pages.freedesktop.org/maintainer-tools/drm-rust.html
+T: git https://gitlab.freedesktop.org/drm/rust/kernel.git
+F: drivers/gpu/drm/nova/
+F: drivers/gpu/nova-core/
+F: rust/kernel/drm/
+
DRM DRIVERS FOR ALLWINNER A10
M: Maxime Ripard <mripard@kernel.org>
M: Chen-Yu Tsai <wens@csie.org>
base-commit: 8f5ae30d69d7543eee0d70083daf4de8fe15d585
--
2.51.0On Mon, Sep 01, 2025 at 10:26:39PM +0200, Danilo Krummrich wrote: > Multiple DRM Rust drivers (e.g. nova-core, nova-drm, Tyr, rvkms) are in > development, with at least Nova and (soon) Tyr already upstream. Having a > shared tree will ease and accelerate development, since all drivers can > consume new infrastructure in the same release cycle. > > This includes infrastructure shared with other subsystem trees (e.g. Rust > or driver-core). By consolidating in drm-rust, we avoid adding extra > burden to drm-misc maintainers, e.g. dealing with cross-tree topic > branches. > > The drm-misc tree is not a good fit for this stage of development, since > its documented scope is small drivers with occasional large series. > > Rust drivers in development upstream, however, regularly involve large > patch series, new infrastructure, and shared topic branches, which may > not align well with drm-misc at this stage. > > The drm-rust tree may not be a permanent solution. Once the core Rust, > DRM, and KMS infrastructure have stabilized, drivers and infrastructure > changes are expected to transition into drm-misc or standalone driver > trees respectively. Until then, drm-rust provides a dedicated place to > coordinate development without disrupting existing workflows too much. > > Cc: Alice Ryhl <aliceryhl@google.com> > Cc: David Airlie <airlied@gmail.com> > Cc: Simona Vetter <simona@ffwll.ch> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> > Cc: Maxime Ripard <mripard@kernel.org> > Cc: Thomas Zimmermann <tzimmermann@suse.de> > Cc: Alexandre Courbot <acourbot@nvidia.com> > Cc: Daniel Almeida <daniel.almeida@collabora.com> > Signed-off-by: Danilo Krummrich <dakr@kernel.org> Applied to drm-rust-fixes. Thanks!
On Mon, Sep 01, 2025 at 10:26:39PM +0200, Danilo Krummrich wrote: > Multiple DRM Rust drivers (e.g. nova-core, nova-drm, Tyr, rvkms) are in > development, with at least Nova and (soon) Tyr already upstream. Having a > shared tree will ease and accelerate development, since all drivers can > consume new infrastructure in the same release cycle. > > This includes infrastructure shared with other subsystem trees (e.g. Rust > or driver-core). By consolidating in drm-rust, we avoid adding extra > burden to drm-misc maintainers, e.g. dealing with cross-tree topic > branches. > > The drm-misc tree is not a good fit for this stage of development, since > its documented scope is small drivers with occasional large series. > > Rust drivers in development upstream, however, regularly involve large > patch series, new infrastructure, and shared topic branches, which may > not align well with drm-misc at this stage. > > The drm-rust tree may not be a permanent solution. Once the core Rust, > DRM, and KMS infrastructure have stabilized, drivers and infrastructure > changes are expected to transition into drm-misc or standalone driver > trees respectively. Until then, drm-rust provides a dedicated place to > coordinate development without disrupting existing workflows too much. > > Cc: Alice Ryhl <aliceryhl@google.com> > Cc: David Airlie <airlied@gmail.com> > Cc: Simona Vetter <simona@ffwll.ch> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> > Cc: Maxime Ripard <mripard@kernel.org> > Cc: Thomas Zimmermann <tzimmermann@suse.de> > Cc: Alexandre Courbot <acourbot@nvidia.com> > Cc: Daniel Almeida <daniel.almeida@collabora.com> > Signed-off-by: Danilo Krummrich <dakr@kernel.org> > --- > MAINTAINERS | 11 ++++++++++- > 1 file changed, 10 insertions(+), 1 deletion(-) > > diff --git a/MAINTAINERS b/MAINTAINERS > index fe168477caa4..1cd6597c7f1d 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -8079,7 +8079,6 @@ F: Documentation/devicetree/bindings/gpu/ > F: Documentation/gpu/ > F: drivers/gpu/drm/ > F: drivers/gpu/vga/ > -F: rust/kernel/drm/ > F: include/drm/drm > F: include/linux/vga* > F: include/uapi/drm/ > @@ -8096,6 +8095,16 @@ X: drivers/gpu/drm/radeon/ > X: drivers/gpu/drm/tegra/ > X: drivers/gpu/drm/xe/ > > +DRM DRIVERS AND COMMON INFRASTRUCTURE [RUST] > +M: Danilo Krummrich <dakr@kernel.org> > +M: Alice Ryhl <aliceryhl@google.com> > +S: Supported > +W: https://drm.pages.freedesktop.org/maintainer-tools/drm-rust.html It looks like the right path is: https://drm.pages.freedesktop.org/maintainer-tools/repositories/drm-rust.html Alice
(Cc: Jani) On 9/4/25 12:40 PM, Alice Ryhl wrote: > On Mon, Sep 01, 2025 at 10:26:39PM +0200, Danilo Krummrich wrote: >> +DRM DRIVERS AND COMMON INFRASTRUCTURE [RUST] >> +M: Danilo Krummrich <dakr@kernel.org> >> +M: Alice Ryhl <aliceryhl@google.com> >> +S: Supported >> +W: https://drm.pages.freedesktop.org/maintainer-tools/drm-rust.html > > It looks like the right path is: > https://drm.pages.freedesktop.org/maintainer-tools/repositories/drm-rust.html Heh, seems like there's an explicit redirect for drm-misc: https://drm.pages.freedesktop.org/maintainer-tools/drm-misc.html I think we should get the same redirect, so the links in MAINTAINERS are consistent with each other.
On Thu Sep 4, 2025 at 1:09 PM CEST, Danilo Krummrich wrote: > I think we should get the same redirect, so the links in MAINTAINERS are > consistent with each other. https://gitlab.freedesktop.org/drm/maintainer-tools/-/merge_requests/89
Hej, On Mon, Sep 1, 2025, at 22:26, Danilo Krummrich wrote: > Multiple DRM Rust drivers (e.g. nova-core, nova-drm, Tyr, rvkms) are in > development, with at least Nova and (soon) Tyr already upstream. Having a > shared tree will ease and accelerate development, since all drivers can > consume new infrastructure in the same release cycle. > > This includes infrastructure shared with other subsystem trees (e.g. Rust > or driver-core). By consolidating in drm-rust, we avoid adding extra > burden to drm-misc maintainers, e.g. dealing with cross-tree topic > branches. > > The drm-misc tree is not a good fit for this stage of development, since > its documented scope is small drivers with occasional large series. > > Rust drivers in development upstream, however, regularly involve large > patch series, new infrastructure, and shared topic branches, which may > not align well with drm-misc at this stage. > > The drm-rust tree may not be a permanent solution. Once the core Rust, > DRM, and KMS infrastructure have stabilized, drivers and infrastructure > changes are expected to transition into drm-misc or standalone driver > trees respectively. Until then, drm-rust provides a dedicated place to > coordinate development without disrupting existing workflows too much. I think this good idea. I plan to make an initial asahi submission based on v6.18-rc1. Feel free to add asahi to the list. Acked-by: Janne Grunau <j@jannau.net>
On Mon, Sep 01, 2025 at 10:26:39PM +0200, Danilo Krummrich wrote: > Multiple DRM Rust drivers (e.g. nova-core, nova-drm, Tyr, rvkms) are in > development, with at least Nova and (soon) Tyr already upstream. Having a > shared tree will ease and accelerate development, since all drivers can > consume new infrastructure in the same release cycle. > > This includes infrastructure shared with other subsystem trees (e.g. Rust > or driver-core). By consolidating in drm-rust, we avoid adding extra > burden to drm-misc maintainers, e.g. dealing with cross-tree topic > branches. > > The drm-misc tree is not a good fit for this stage of development, since > its documented scope is small drivers with occasional large series. > > Rust drivers in development upstream, however, regularly involve large > patch series, new infrastructure, and shared topic branches, which may > not align well with drm-misc at this stage. > > The drm-rust tree may not be a permanent solution. Once the core Rust, > DRM, and KMS infrastructure have stabilized, drivers and infrastructure > changes are expected to transition into drm-misc or standalone driver > trees respectively. Until then, drm-rust provides a dedicated place to > coordinate development without disrupting existing workflows too much. > > Cc: Alice Ryhl <aliceryhl@google.com> > Cc: David Airlie <airlied@gmail.com> > Cc: Simona Vetter <simona@ffwll.ch> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> > Cc: Maxime Ripard <mripard@kernel.org> > Cc: Thomas Zimmermann <tzimmermann@suse.de> > Cc: Alexandre Courbot <acourbot@nvidia.com> > Cc: Daniel Almeida <daniel.almeida@collabora.com> > Signed-off-by: Danilo Krummrich <dakr@kernel.org> > --- > MAINTAINERS | 11 ++++++++++- > 1 file changed, 10 insertions(+), 1 deletion(-) > > diff --git a/MAINTAINERS b/MAINTAINERS > index fe168477caa4..1cd6597c7f1d 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -8079,7 +8079,6 @@ F: Documentation/devicetree/bindings/gpu/ > F: Documentation/gpu/ > F: drivers/gpu/drm/ > F: drivers/gpu/vga/ > -F: rust/kernel/drm/ > F: include/drm/drm > F: include/linux/vga* > F: include/uapi/drm/ > @@ -8096,6 +8095,16 @@ X: drivers/gpu/drm/radeon/ > X: drivers/gpu/drm/tegra/ > X: drivers/gpu/drm/xe/ > > +DRM DRIVERS AND COMMON INFRASTRUCTURE [RUST] > +M: Danilo Krummrich <dakr@kernel.org> > +M: Alice Ryhl <aliceryhl@google.com> > +S: Supported > +W: https://drm.pages.freedesktop.org/maintainer-tools/drm-rust.html > +T: git https://gitlab.freedesktop.org/drm/rust/kernel.git > +F: drivers/gpu/drm/nova/ > +F: drivers/gpu/nova-core/ > +F: rust/kernel/drm/ > + Would it make sense to add the drm-misc maintainers as reviewers for the bindings? Either way, Acked-by: Maxime Ripard <mripard@kernel.org> Maxime
On Tue Sep 2, 2025 at 7:40 PM CEST, Maxime Ripard wrote: > On Mon, Sep 01, 2025 at 10:26:39PM +0200, Danilo Krummrich wrote: >> Multiple DRM Rust drivers (e.g. nova-core, nova-drm, Tyr, rvkms) are in >> development, with at least Nova and (soon) Tyr already upstream. Having a >> shared tree will ease and accelerate development, since all drivers can >> consume new infrastructure in the same release cycle. >> >> This includes infrastructure shared with other subsystem trees (e.g. Rust >> or driver-core). By consolidating in drm-rust, we avoid adding extra >> burden to drm-misc maintainers, e.g. dealing with cross-tree topic >> branches. >> >> The drm-misc tree is not a good fit for this stage of development, since >> its documented scope is small drivers with occasional large series. >> >> Rust drivers in development upstream, however, regularly involve large >> patch series, new infrastructure, and shared topic branches, which may >> not align well with drm-misc at this stage. >> >> The drm-rust tree may not be a permanent solution. Once the core Rust, >> DRM, and KMS infrastructure have stabilized, drivers and infrastructure >> changes are expected to transition into drm-misc or standalone driver >> trees respectively. Until then, drm-rust provides a dedicated place to >> coordinate development without disrupting existing workflows too much. >> >> Cc: Alice Ryhl <aliceryhl@google.com> >> Cc: David Airlie <airlied@gmail.com> >> Cc: Simona Vetter <simona@ffwll.ch> >> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> >> Cc: Maxime Ripard <mripard@kernel.org> >> Cc: Thomas Zimmermann <tzimmermann@suse.de> >> Cc: Alexandre Courbot <acourbot@nvidia.com> >> Cc: Daniel Almeida <daniel.almeida@collabora.com> >> Signed-off-by: Danilo Krummrich <dakr@kernel.org> >> --- >> MAINTAINERS | 11 ++++++++++- >> 1 file changed, 10 insertions(+), 1 deletion(-) >> >> diff --git a/MAINTAINERS b/MAINTAINERS >> index fe168477caa4..1cd6597c7f1d 100644 >> --- a/MAINTAINERS >> +++ b/MAINTAINERS >> @@ -8079,7 +8079,6 @@ F: Documentation/devicetree/bindings/gpu/ >> F: Documentation/gpu/ >> F: drivers/gpu/drm/ >> F: drivers/gpu/vga/ >> -F: rust/kernel/drm/ >> F: include/drm/drm >> F: include/linux/vga* >> F: include/uapi/drm/ >> @@ -8096,6 +8095,16 @@ X: drivers/gpu/drm/radeon/ >> X: drivers/gpu/drm/tegra/ >> X: drivers/gpu/drm/xe/ >> >> +DRM DRIVERS AND COMMON INFRASTRUCTURE [RUST] >> +M: Danilo Krummrich <dakr@kernel.org> >> +M: Alice Ryhl <aliceryhl@google.com> >> +S: Supported >> +W: https://drm.pages.freedesktop.org/maintainer-tools/drm-rust.html >> +T: git https://gitlab.freedesktop.org/drm/rust/kernel.git >> +F: drivers/gpu/drm/nova/ >> +F: drivers/gpu/nova-core/ >> +F: rust/kernel/drm/ >> + > > Would it make sense to add the drm-misc maintainers as reviewers for the > bindings? This will get you all the driver patches in your inbox as well, maybe discarding the following hunk is what we want instead? @@ -8079,7 +8079,6 @@ F: Documentation/devicetree/bindings/gpu/ F: Documentation/gpu/ F: drivers/gpu/drm/ F: drivers/gpu/vga/ -F: rust/kernel/drm/ F: include/drm/drm F: include/linux/vga* F: include/uapi/drm/ > Either way, > > Acked-by: Maxime Ripard <mripard@kernel.org> > > Maxime
On Tue, Sep 02, 2025 at 07:49:56PM +0200, Danilo Krummrich wrote: > On Tue Sep 2, 2025 at 7:40 PM CEST, Maxime Ripard wrote: > > On Mon, Sep 01, 2025 at 10:26:39PM +0200, Danilo Krummrich wrote: > >> Multiple DRM Rust drivers (e.g. nova-core, nova-drm, Tyr, rvkms) are in > >> development, with at least Nova and (soon) Tyr already upstream. Having a > >> shared tree will ease and accelerate development, since all drivers can > >> consume new infrastructure in the same release cycle. > >> > >> This includes infrastructure shared with other subsystem trees (e.g. Rust > >> or driver-core). By consolidating in drm-rust, we avoid adding extra > >> burden to drm-misc maintainers, e.g. dealing with cross-tree topic > >> branches. > >> > >> The drm-misc tree is not a good fit for this stage of development, since > >> its documented scope is small drivers with occasional large series. > >> > >> Rust drivers in development upstream, however, regularly involve large > >> patch series, new infrastructure, and shared topic branches, which may > >> not align well with drm-misc at this stage. > >> > >> The drm-rust tree may not be a permanent solution. Once the core Rust, > >> DRM, and KMS infrastructure have stabilized, drivers and infrastructure > >> changes are expected to transition into drm-misc or standalone driver > >> trees respectively. Until then, drm-rust provides a dedicated place to > >> coordinate development without disrupting existing workflows too much. > >> > >> Cc: Alice Ryhl <aliceryhl@google.com> > >> Cc: David Airlie <airlied@gmail.com> > >> Cc: Simona Vetter <simona@ffwll.ch> > >> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> > >> Cc: Maxime Ripard <mripard@kernel.org> > >> Cc: Thomas Zimmermann <tzimmermann@suse.de> > >> Cc: Alexandre Courbot <acourbot@nvidia.com> > >> Cc: Daniel Almeida <daniel.almeida@collabora.com> > >> Signed-off-by: Danilo Krummrich <dakr@kernel.org> > >> --- > >> MAINTAINERS | 11 ++++++++++- > >> 1 file changed, 10 insertions(+), 1 deletion(-) > >> > >> diff --git a/MAINTAINERS b/MAINTAINERS > >> index fe168477caa4..1cd6597c7f1d 100644 > >> --- a/MAINTAINERS > >> +++ b/MAINTAINERS > >> @@ -8079,7 +8079,6 @@ F: Documentation/devicetree/bindings/gpu/ > >> F: Documentation/gpu/ > >> F: drivers/gpu/drm/ > >> F: drivers/gpu/vga/ > >> -F: rust/kernel/drm/ > >> F: include/drm/drm > >> F: include/linux/vga* > >> F: include/uapi/drm/ > >> @@ -8096,6 +8095,16 @@ X: drivers/gpu/drm/radeon/ > >> X: drivers/gpu/drm/tegra/ > >> X: drivers/gpu/drm/xe/ > >> > >> +DRM DRIVERS AND COMMON INFRASTRUCTURE [RUST] > >> +M: Danilo Krummrich <dakr@kernel.org> > >> +M: Alice Ryhl <aliceryhl@google.com> > >> +S: Supported > >> +W: https://drm.pages.freedesktop.org/maintainer-tools/drm-rust.html > >> +T: git https://gitlab.freedesktop.org/drm/rust/kernel.git > >> +F: drivers/gpu/drm/nova/ > >> +F: drivers/gpu/nova-core/ > >> +F: rust/kernel/drm/ > >> + > > > > Would it make sense to add the drm-misc maintainers as reviewers for the > > bindings? > > This will get you all the driver patches in your inbox as well, maybe > discarding the following hunk is what we want instead? I guess we would receive just as many patches as we do today :) > @@ -8079,7 +8079,6 @@ F: Documentation/devicetree/bindings/gpu/ > F: Documentation/gpu/ > F: drivers/gpu/drm/ > F: drivers/gpu/vga/ > -F: rust/kernel/drm/ > F: include/drm/drm > F: include/linux/vga* > F: include/uapi/drm/ That's not really what I meant, what I meant was that rust/kernel/drm/ is the only thing I'm really interested on, but we don't need to maintain it if it makes more sense to do so separately. BTW, we should probably add to drm-misc X: drivers/gpu/drm/nova because we have a catch-all at the moment. Maxime
On Tue Sep 2, 2025 at 7:57 PM CEST, Maxime Ripard wrote: > On Tue, Sep 02, 2025 at 07:49:56PM +0200, Danilo Krummrich wrote: >> On Tue Sep 2, 2025 at 7:40 PM CEST, Maxime Ripard wrote: >> > Would it make sense to add the drm-misc maintainers as reviewers for the >> > bindings? >> >> This will get you all the driver patches in your inbox as well, maybe >> discarding the following hunk is what we want instead? > > I guess we would receive just as many patches as we do today :) > >> @@ -8079,7 +8079,6 @@ F: Documentation/devicetree/bindings/gpu/ >> F: Documentation/gpu/ >> F: drivers/gpu/drm/ >> F: drivers/gpu/vga/ >> -F: rust/kernel/drm/ >> F: include/drm/drm >> F: include/linux/vga* >> F: include/uapi/drm/ > > That's not really what I meant, what I meant was that rust/kernel/drm/ > is the only thing I'm really interested on, but we don't need to > maintain it if it makes more sense to do so separately. Yeah, the idea was to discard the hunk above and still keep rust/kernel/drm/ on this new entry, so you get *only* that, but not all the driver patches. As far as file maintainership is concerned, we have group maintainership on the commmon infrastructure anyways. Your call, happy to add you as reviewers to the new entry too. :) > BTW, we should probably add to drm-misc > > X: drivers/gpu/drm/nova Makes sense. > because we have a catch-all at the moment. > > Maxime
On Tue Sep 2, 2025 at 5:26 AM JST, Danilo Krummrich wrote: > Multiple DRM Rust drivers (e.g. nova-core, nova-drm, Tyr, rvkms) are in > development, with at least Nova and (soon) Tyr already upstream. Having a > shared tree will ease and accelerate development, since all drivers can > consume new infrastructure in the same release cycle. > > This includes infrastructure shared with other subsystem trees (e.g. Rust > or driver-core). By consolidating in drm-rust, we avoid adding extra > burden to drm-misc maintainers, e.g. dealing with cross-tree topic > branches. > > The drm-misc tree is not a good fit for this stage of development, since > its documented scope is small drivers with occasional large series. > > Rust drivers in development upstream, however, regularly involve large > patch series, new infrastructure, and shared topic branches, which may > not align well with drm-misc at this stage. > > The drm-rust tree may not be a permanent solution. Once the core Rust, > DRM, and KMS infrastructure have stabilized, drivers and infrastructure > changes are expected to transition into drm-misc or standalone driver > trees respectively. Until then, drm-rust provides a dedicated place to > coordinate development without disrupting existing workflows too much. > > Cc: Alice Ryhl <aliceryhl@google.com> > Cc: David Airlie <airlied@gmail.com> > Cc: Simona Vetter <simona@ffwll.ch> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> > Cc: Maxime Ripard <mripard@kernel.org> > Cc: Thomas Zimmermann <tzimmermann@suse.de> > Cc: Alexandre Courbot <acourbot@nvidia.com> > Cc: Daniel Almeida <daniel.almeida@collabora.com> > Signed-off-by: Danilo Krummrich <dakr@kernel.org> Acked-by: Alexandre Courbot <acourbot@nvidia.com>
On Mon, 01 Sep 2025, Danilo Krummrich <dakr@kernel.org> wrote: > Multiple DRM Rust drivers (e.g. nova-core, nova-drm, Tyr, rvkms) are in > development, with at least Nova and (soon) Tyr already upstream. Having a > shared tree will ease and accelerate development, since all drivers can > consume new infrastructure in the same release cycle. > > This includes infrastructure shared with other subsystem trees (e.g. Rust > or driver-core). By consolidating in drm-rust, we avoid adding extra > burden to drm-misc maintainers, e.g. dealing with cross-tree topic > branches. > > The drm-misc tree is not a good fit for this stage of development, since > its documented scope is small drivers with occasional large series. > > Rust drivers in development upstream, however, regularly involve large > patch series, new infrastructure, and shared topic branches, which may > not align well with drm-misc at this stage. > > The drm-rust tree may not be a permanent solution. Once the core Rust, > DRM, and KMS infrastructure have stabilized, drivers and infrastructure > changes are expected to transition into drm-misc or standalone driver > trees respectively. Until then, drm-rust provides a dedicated place to > coordinate development without disrupting existing workflows too much. > > Cc: Alice Ryhl <aliceryhl@google.com> > Cc: David Airlie <airlied@gmail.com> > Cc: Simona Vetter <simona@ffwll.ch> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> > Cc: Maxime Ripard <mripard@kernel.org> > Cc: Thomas Zimmermann <tzimmermann@suse.de> > Cc: Alexandre Courbot <acourbot@nvidia.com> > Cc: Daniel Almeida <daniel.almeida@collabora.com> > Signed-off-by: Danilo Krummrich <dakr@kernel.org> FWIW, Acked-by: Jani Nikula <jani.nikula@intel.com> > --- > MAINTAINERS | 11 ++++++++++- > 1 file changed, 10 insertions(+), 1 deletion(-) > > diff --git a/MAINTAINERS b/MAINTAINERS > index fe168477caa4..1cd6597c7f1d 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -8079,7 +8079,6 @@ F: Documentation/devicetree/bindings/gpu/ > F: Documentation/gpu/ > F: drivers/gpu/drm/ > F: drivers/gpu/vga/ > -F: rust/kernel/drm/ > F: include/drm/drm > F: include/linux/vga* > F: include/uapi/drm/ > @@ -8096,6 +8095,16 @@ X: drivers/gpu/drm/radeon/ > X: drivers/gpu/drm/tegra/ > X: drivers/gpu/drm/xe/ > > +DRM DRIVERS AND COMMON INFRASTRUCTURE [RUST] > +M: Danilo Krummrich <dakr@kernel.org> > +M: Alice Ryhl <aliceryhl@google.com> > +S: Supported > +W: https://drm.pages.freedesktop.org/maintainer-tools/drm-rust.html > +T: git https://gitlab.freedesktop.org/drm/rust/kernel.git > +F: drivers/gpu/drm/nova/ > +F: drivers/gpu/nova-core/ > +F: rust/kernel/drm/ > + > DRM DRIVERS FOR ALLWINNER A10 > M: Maxime Ripard <mripard@kernel.org> > M: Chen-Yu Tsai <wens@csie.org> > > base-commit: 8f5ae30d69d7543eee0d70083daf4de8fe15d585 -- Jani Nikula, Intel
> On 1 Sep 2025, at 17:26, Danilo Krummrich <dakr@kernel.org> wrote: > > Multiple DRM Rust drivers (e.g. nova-core, nova-drm, Tyr, rvkms) are in > development, with at least Nova and (soon) Tyr already upstream. Having a > shared tree will ease and accelerate development, since all drivers can > consume new infrastructure in the same release cycle. > > This includes infrastructure shared with other subsystem trees (e.g. Rust > or driver-core). By consolidating in drm-rust, we avoid adding extra > burden to drm-misc maintainers, e.g. dealing with cross-tree topic > branches. > > The drm-misc tree is not a good fit for this stage of development, since > its documented scope is small drivers with occasional large series. > > Rust drivers in development upstream, however, regularly involve large > patch series, new infrastructure, and shared topic branches, which may > not align well with drm-misc at this stage. > > The drm-rust tree may not be a permanent solution. Once the core Rust, > DRM, and KMS infrastructure have stabilized, drivers and infrastructure > changes are expected to transition into drm-misc or standalone driver > trees respectively. Until then, drm-rust provides a dedicated place to > coordinate development without disrupting existing workflows too much. > > Cc: Alice Ryhl <aliceryhl@google.com> > Cc: David Airlie <airlied@gmail.com> > Cc: Simona Vetter <simona@ffwll.ch> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> > Cc: Maxime Ripard <mripard@kernel.org> > Cc: Thomas Zimmermann <tzimmermann@suse.de> > Cc: Alexandre Courbot <acourbot@nvidia.com> > Cc: Daniel Almeida <daniel.almeida@collabora.com> > Signed-off-by: Danilo Krummrich <dakr@kernel.org> > --- > MAINTAINERS | 11 ++++++++++- > 1 file changed, 10 insertions(+), 1 deletion(-) > > diff --git a/MAINTAINERS b/MAINTAINERS > index fe168477caa4..1cd6597c7f1d 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -8079,7 +8079,6 @@ F: Documentation/devicetree/bindings/gpu/ > F: Documentation/gpu/ > F: drivers/gpu/drm/ > F: drivers/gpu/vga/ > -F: rust/kernel/drm/ > F: include/drm/drm > F: include/linux/vga* > F: include/uapi/drm/ > @@ -8096,6 +8095,16 @@ X: drivers/gpu/drm/radeon/ > X: drivers/gpu/drm/tegra/ > X: drivers/gpu/drm/xe/ > > +DRM DRIVERS AND COMMON INFRASTRUCTURE [RUST] > +M: Danilo Krummrich <dakr@kernel.org> > +M: Alice Ryhl <aliceryhl@google.com> > +S: Supported > +W: https://drm.pages.freedesktop.org/maintainer-tools/drm-rust.html > +T: git https://gitlab.freedesktop.org/drm/rust/kernel.git > +F: drivers/gpu/drm/nova/ > +F: drivers/gpu/nova-core/ > +F: rust/kernel/drm/ > + > DRM DRIVERS FOR ALLWINNER A10 > M: Maxime Ripard <mripard@kernel.org> > M: Chen-Yu Tsai <wens@csie.org> > > base-commit: 8f5ae30d69d7543eee0d70083daf4de8fe15d585 > -- > 2.51.0 > Acked-by: Daniel Almeida <daniel.almeida@collabora.com>
On Mon, Sep 01, 2025 at 10:26:39PM +0200, Danilo Krummrich wrote: > Multiple DRM Rust drivers (e.g. nova-core, nova-drm, Tyr, rvkms) are in > development, with at least Nova and (soon) Tyr already upstream. Having a > shared tree will ease and accelerate development, since all drivers can > consume new infrastructure in the same release cycle. > > This includes infrastructure shared with other subsystem trees (e.g. Rust > or driver-core). By consolidating in drm-rust, we avoid adding extra > burden to drm-misc maintainers, e.g. dealing with cross-tree topic > branches. > > The drm-misc tree is not a good fit for this stage of development, since > its documented scope is small drivers with occasional large series. > > Rust drivers in development upstream, however, regularly involve large > patch series, new infrastructure, and shared topic branches, which may > not align well with drm-misc at this stage. > > The drm-rust tree may not be a permanent solution. Once the core Rust, > DRM, and KMS infrastructure have stabilized, drivers and infrastructure > changes are expected to transition into drm-misc or standalone driver > trees respectively. Until then, drm-rust provides a dedicated place to > coordinate development without disrupting existing workflows too much. > > Cc: Alice Ryhl <aliceryhl@google.com> > Cc: David Airlie <airlied@gmail.com> > Cc: Simona Vetter <simona@ffwll.ch> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> > Cc: Maxime Ripard <mripard@kernel.org> > Cc: Thomas Zimmermann <tzimmermann@suse.de> > Cc: Alexandre Courbot <acourbot@nvidia.com> > Cc: Daniel Almeida <daniel.almeida@collabora.com> > Signed-off-by: Danilo Krummrich <dakr@kernel.org> Acked-by: Alice Ryhl <aliceryhl@google.com>
© 2016 - 2025 Red Hat, Inc.