From: Yannick FERTRE <yannick.fertre@foss.st.com>
To: "Raphael Gallais-Pou" <raphael.gallais-pou@foss.st.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Philippe Cornu" <philippe.cornu@foss.st.com>,
"Raphaël Gallais-Pou" <rgallaispou@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: defconfig: Enable STMicroelectronics STM32 display support
Date: Thu, 5 Mar 2026 14:02:45 +0100 [thread overview]
Message-ID: <dd9b02e4-c6b8-478d-936a-dc8a749a7ef0@foss.st.com> (raw)
In-Reply-To: <20260205-master-v1-1-dcefcabc2934@foss.st.com>
Tested-by: Yannick Fertre <yannick.fertre@foss.st.com>
Thanks for the patch.
Yannick Fertré
Le 05/02/2026 à 16:03, Raphael Gallais-Pou a écrit :
> Enable STMicroelectronics STM32 display support as module.
> This includes:
> * DRM_STM
> * DRM_STM_LVDS
> * BACKLIGHT_GPIO
> * TOUCHSCREEN_ILI210X
>
> This display is used on several SoCs and boards such as STM32MP257F-EV1
> and STM32MP257F-DK.
>
> Signed-off-by: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
> ---
> arch/arm64/configs/defconfig | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 35e9eb180c9a1ce3310086230ec52e93b320afeb..deb14f638d7d1f9b3d6aa24043242662734ce68e 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -467,6 +467,7 @@ CONFIG_INPUT_TOUCHSCREEN=y
> CONFIG_TOUCHSCREEN_ATMEL_MXT=m
> CONFIG_TOUCHSCREEN_GOODIX=m
> CONFIG_TOUCHSCREEN_GOODIX_BERLIN_SPI=m
> +CONFIG_TOUCHSCREEN_ILI210X=m
> CONFIG_TOUCHSCREEN_ELAN=m
> CONFIG_TOUCHSCREEN_EDT_FT5X06=m
> CONFIG_TOUCHSCREEN_HIMAX_HX83112B=m
> @@ -942,6 +943,8 @@ CONFIG_DRM_SUN8I_DW_HDMI=m
> CONFIG_DRM_SUN8I_MIXER=m
> CONFIG_DRM_MSM=m
> CONFIG_DRM_TEGRA=m
> +CONFIG_DRM_STM=m
> +CONFIG_DRM_STM_LVDS=m
> CONFIG_DRM_PANEL_BOE_TV101WUM_NL6=m
> CONFIG_DRM_PANEL_LVDS=m
> CONFIG_DRM_PANEL_SIMPLE=m
> @@ -1013,6 +1016,7 @@ CONFIG_FB_MODE_HELPERS=y
> CONFIG_BACKLIGHT_PWM=m
> CONFIG_BACKLIGHT_QCOM_WLED=m
> CONFIG_BACKLIGHT_LP855X=m
> +CONFIG_BACKLIGHT_GPIO=m
> CONFIG_LOGO=y
> # CONFIG_LOGO_LINUX_MONO is not set
> # CONFIG_LOGO_LINUX_VGA16 is not set
>
> ---
> base-commit: f14faaf3a1fb3b9e4cf2e56269711fb85fba9458
> change-id: 20260205-master-f1abc06cf651
>
> Best regards,
next prev parent reply other threads:[~2026-03-05 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 15:03 Raphael Gallais-Pou
2026-02-08 11:16 ` Krzysztof Kozlowski
2026-03-05 13:02 ` Yannick FERTRE [this message]
2026-03-25 14:48 ` Alexandre TORGUE
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=dd9b02e4-c6b8-478d-936a-dc8a749a7ef0@foss.st.com \
--to=yannick.fertre@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philippe.cornu@foss.st.com \
--cc=raphael.gallais-pou@foss.st.com \
--cc=rgallaispou@gmail.com \
/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®