From: "Raphaël Gallais-Pou" <rgallaispou@gmail.com>
To: Alain Volmat <alain.volmat@foss.st.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Patrice Chotard <patrice.chotard@foss.st.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/4] STi device-tree display subsystem rework
Date: Wed, 17 Sep 2025 00:03:43 +0200 [thread overview]
Message-ID: <235312e0-b912-4e10-874a-e6364131aaee@gmail.com> (raw)
In-Reply-To: <20250717-sti-rework-v1-0-46d516fb1ebb@gmail.com>
Le 17/07/2025 à 21:15, Raphael Gallais-Pou a écrit :
> This serie aims to rework the display-subsystem node, which was
> previously included directly within the SoC node. This was wrong
> because it is an abstraction and describes how IPs behave together, not
> what the hardware is. Instead, extract display-subsystem outside of the
> SoC node, and let IPs describe their connections. Doing so helps the
> readability, and eases the understanding of the hardware.
>
> Several nodes have been renamed to stick to the generic names defined in
> the device-tree specification.
>
> This series depends on another sent a few days ago. It is not critical
> though, since not having it only triggers warnings when building
> deprecated device-trees. Please see link below.
>
> Link: https://lore.kernel.org/lkml/20250714-sti-rework-v2-0-f4274920858b@gmail.com
>
> Signed-off-by: Raphael Gallais-Pou <rgallaispou@gmail.com>
> ---
> Raphael Gallais-Pou (4):
> drm/sti: check dma_set_coherent_mask return value
> drm/sti: make use of drm_of_component_probe
> ARM: dts: sti: extract display subsystem out of soc
> ARM: dts: sti: remove useless cells fields
>
Hi,
@Patrice
Would you agree to make the device-tree patches go through drm-misc
instead of your tree ? So that the breaking change lands in -next in the
same time as the driver changes.
I will send another series to convert display subsystem bindings to DT
schema as soon as the series is merged.
@Alain
Do you prefer to merge it yourself or you rather let me do it ?
Best regards,
Raphaël> arch/arm/boot/dts/st/stih410.dtsi | 316
++++++++++++++++++++++----------------
> drivers/gpu/drm/sti/sti_drv.c | 18 +--
> 2 files changed, 192 insertions(+), 142 deletions(-)
> ---
> base-commit: b9a572f471993d3e8bf874fcb57f331d66650440
> change-id: 20250401-sti-rework-b009551a362c
>
> Best regards,
next prev parent reply other threads:[~2025-09-16 22:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 19:15 [PATCH 0/4] STi device-tree display subsystem rework Raphael Gallais-Pou
2025-07-17 19:15 ` [PATCH 1/4] drm/sti: check dma_set_coherent_mask return value Raphael Gallais-Pou
2025-09-12 14:28 ` Alain Volmat
2025-07-17 19:15 ` [PATCH 2/4] drm/sti: make use of drm_of_component_probe Raphael Gallais-Pou
2025-09-12 14:31 ` Alain Volmat
2025-07-17 19:15 ` [PATCH 3/4] ARM: dts: sti: extract display subsystem out of soc Raphael Gallais-Pou
2025-09-12 14:34 ` Alain Volmat
2025-10-30 7:42 ` Patrice CHOTARD
2025-07-17 19:15 ` [PATCH 4/4] ARM: dts: sti: remove useless cells fields Raphael Gallais-Pou
2025-09-12 14:34 ` Alain Volmat
2025-10-30 7:43 ` Patrice CHOTARD
2025-07-20 23:06 ` [PATCH 0/4] STi device-tree display subsystem rework Rob Herring (Arm)
2025-09-16 22:03 ` Raphaël Gallais-Pou [this message]
2025-09-17 6:05 ` Patrice CHOTARD
2025-09-23 9:12 ` Alain Volmat
2025-10-30 12:24 ` Raphael Gallais-Pou
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=235312e0-b912-4e10-874a-e6364131aaee@gmail.com \
--to=rgallaispou@gmail.com \
--cc=airlied@gmail.com \
--cc=alain.volmat@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=patrice.chotard@foss.st.com \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).