From: Dario Binacchi <dario.binacchi@amarulasolutions.com>
To: linux-kernel@vger.kernel.org
Cc: Amarula patchwork <linux-amarula@amarulasolutions.com>,
michael@amarulasolutions.com,
Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Conor Dooley <conor+dt@kernel.org>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Philippe Cornu <philippe.cornu@foss.st.com>,
Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>,
Rob Herring <robh+dt@kernel.org>, Sam Ravnborg <sam@ravnborg.org>,
Thierry Reding <thierry.reding@gmail.com>,
Yannick Fertre <yannick.fertre@foss.st.com>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: [PATCH 0/6] Add display support on the stm32f746-disco board
Date: Thu, 1 Jun 2023 19:03:14 +0200 [thread overview]
Message-ID: <20230601170320.2845218-1-dario.binacchi@amarulasolutions.com> (raw)
The series adds support for the display on the stm32f746-disco board,
along with a generic patch that adds the "bpp" parameter to the stm-drm
module. The intention is to allow users to size, within certain limits,
the memory footprint required by the framebuffer.
Dario Binacchi (6):
ARM: dts: stm32: add ltdc support on stm32f746 MCU
ARM: dts: stm32: add pin map for LTDC on stm32f7
ARM: dts: stm32: support display on stm32f746-disco board
dt-bindings: display: simple: add Rocktech RK043FN48H
drm/panel: simple: add support for Rocktech RK043FN48H panel
drm/stm: add an option to change FB bpp
.../bindings/display/panel/panel-simple.yaml | 2 +
arch/arm/boot/dts/stm32f7-pinctrl.dtsi | 35 +++++++++++++
arch/arm/boot/dts/stm32f746-disco.dts | 51 +++++++++++++++++++
arch/arm/boot/dts/stm32f746.dtsi | 10 ++++
drivers/gpu/drm/panel/panel-simple.c | 29 +++++++++++
drivers/gpu/drm/stm/drv.c | 8 ++-
6 files changed, 134 insertions(+), 1 deletion(-)
--
2.32.0
next reply other threads:[~2023-06-01 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 17:03 Dario Binacchi [this message]
2023-06-01 17:03 ` [PATCH 1/6] ARM: dts: stm32: add ltdc support on stm32f746 MCU Dario Binacchi
2023-06-01 17:03 ` [PATCH 2/6] ARM: dts: stm32: add pin map for LTDC on stm32f7 Dario Binacchi
2023-06-01 17:03 ` [PATCH 3/6] ARM: dts: stm32: support display on stm32f746-disco board Dario Binacchi
2023-06-01 17:03 ` [PATCH 4/6] dt-bindings: display: simple: add Rocktech RK043FN48H Dario Binacchi
2023-06-01 18:15 ` Conor Dooley
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=20230601170320.2845218-1-dario.binacchi@amarulasolutions.com \
--to=dario.binacchi@amarulasolutions.com \
--cc=airlied@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=michael@amarulasolutions.com \
--cc=neil.armstrong@linaro.org \
--cc=philippe.cornu@foss.st.com \
--cc=raphael.gallais-pou@foss.st.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
--cc=yannick.fertre@foss.st.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