From: Thierry Reding <thierry.reding@gmail.com>
To: yannick fertre <yannick.fertre@st.com>,
Vikas Manocha <vikas.manocha@st.com>,
Tom Rini <trini@konsulko.com>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Philippe Cornu <philippe.cornu@st.com>,
Patrice Chotard <patrice.chotard@st.com>,
Patrick DELAUNAY <patrick.delaunay@st.com>,
Christophe KERELLO <christophe.kerello@st.com>,
Archit Taneja <architt@codeaurora.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
David Airlie <airlied@linux.ie>,
Brian Norris <briannorris@chromium.org>,
Bhumika Goyal <bhumirks@gmail.com>,
Gustavo Padovan <gustavo@padovan.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Sean Paul <seanpaul@chromium.org>,
Albert Aribaud <albert.u.boot@aribaud.net>,
Simon Glass <sjg@chromium.org>,
Anatolij Gustschin <agust@denx.de>,
u-boot@lists.denx.de, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 00/10] splash screen on the stm32f769 disco board
Date: Tue, 13 Mar 2018 23:50:14 +0100 [thread overview]
Message-ID: <20180313225013.GB23414@mithrandir> (raw)
In-Reply-To: <20180313152310.GJ4788@phenom.ffwll.local>
[-- Attachment #1: Type: text/plain, Size: 1647 bytes --]
On Tue, Mar 13, 2018 at 04:23:10PM +0100, Daniel Vetter wrote:
> On Tue, Mar 13, 2018 at 02:49:59PM +0100, yannick fertre wrote:
> > Version 3:
> > - Replace some pr_error, pr_warn or pr_info by dev_error, dev_warn & dev_info.
> > - Refresh stm32f769-disco_defconfig with last modification done on v2018.3-rc4.
> > - rework include files ordering.
> >
> > Version 2:
> > - Replace debug log by pr_error, pr_warn or pr_info.
> > - Rework bridge between ltdc & dsi panel
> > - Rework backligh management (with or witout gpio)
> > - Rework panel otm8009a
> > - Add new panel raydium rm68200
> >
> > Version 1:
> > - Initial commit
> >
> > This serie contains all patchsets needed for displaying a splash screen
> > on the stm32f769 disco board.
> > A new config has been created configs/stm32f769-disco_defconfig.
> > This is necessary due to the difference of panels between stm32f769-disco &
> > stm32f746-disco boards.
>
> Shouldn't we patch the drivers/gpu/drm/stm driver instead of the
> drivers/video one? fbdev is kinda a dead end and not for adding new hw
> support ...
This is confusing, but by the looks of it this is code for U-Boot
display support and has nothing to do with the Linux kernel. I don't
know why dri-devel was on Cc.
Yannick, it's not customary to cross-post U-Boot display drivers to
Linux mailing lists, unless there's some need to coordinate or discuss
across the boundaries (for example if you were proposing a way to do
seamless handover from U-Boot to kernel). If you do cross-post, perhaps
make sure to mark these patches as targetting U-Boot to avoid confusion.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-03-13 22:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 13:49 [PATCH v3 00/10] splash screen on the stm32f769 disco board yannick fertre
2018-03-13 13:50 ` [PATCH v3 01/10] video: stm32: stm32_ltdc: add bridge to display controller yannick fertre
2018-03-13 13:50 ` [PATCH v3 01/10] video: stm32: stm32_ltdc: update debug log yannick fertre
2018-03-13 13:50 ` [PATCH v3 02/10] video: add support of MIPI DSI interface yannick fertre
2018-03-13 15:30 ` Simon Glass
2018-03-13 13:50 ` [PATCH v3 02/10] video: stm32: stm32_ltdc: update debug log yannick fertre
2018-03-13 13:50 ` [PATCH v3 03/10] video: add support of MIPI DSI interface yannick fertre
2018-03-13 13:50 ` [PATCH v3 03/10] video: add support of panel OTM8009A yannick fertre
2018-03-13 13:50 ` [PATCH v3 04/10] otm yannick fertre
2018-03-13 14:12 ` Patrice CHOTARD
2018-03-13 14:36 ` Yannick FERTRE
2018-03-13 13:50 ` [PATCH v3 04/10] video: add support of panel OTM8009A yannick fertre
2018-03-13 13:50 ` [PATCH v3 05/10] video: add MIPI DSI host controller bridge yannick fertre
2018-03-13 13:50 ` [PATCH v3 06/10] video: add support of STM32 MIPI DSI controller driver yannick fertre
2018-03-13 13:50 ` [PATCH v3 07/10] video: add support of panel rm68200 yannick fertre
2018-03-13 13:50 ` [PATCH v3 08/10] arm: dts: stm32: add dsi for STM32F746 yannick fertre
2018-03-13 13:50 ` [PATCH v3 09/10] arm: dts: stm32: add display for STM32F769 disco board yannick fertre
2018-03-13 13:50 ` [PATCH v3 10/10] board: Add STM32F769 SoC, discovery board support yannick fertre
2018-03-13 14:10 ` Patrice CHOTARD
2018-03-13 15:23 ` [PATCH v3 00/10] splash screen on the stm32f769 disco board Daniel Vetter
2018-03-13 20:50 ` Anatolij Gustschin
2018-03-13 21:00 ` Brian Norris
2018-03-13 22:50 ` Thierry Reding [this message]
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=20180313225013.GB23414@mithrandir \
--to=thierry.reding@gmail.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=agust@denx.de \
--cc=airlied@linux.ie \
--cc=albert.u.boot@aribaud.net \
--cc=architt@codeaurora.org \
--cc=benjamin.gaignard@linaro.org \
--cc=bhumirks@gmail.com \
--cc=briannorris@chromium.org \
--cc=christophe.kerello@st.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=patrice.chotard@st.com \
--cc=patrick.delaunay@st.com \
--cc=philippe.cornu@st.com \
--cc=seanpaul@chromium.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vikas.manocha@st.com \
--cc=yannick.fertre@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;
as well as URLs for NNTP newsgroup(s).