From: Yannick FERTRE <yannick.fertre@st.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/2] video: stm32_ltdc: Convert to use APIs which support live DT
Date: Thu, 10 Sep 2020 14:06:38 +0000 [thread overview]
Message-ID: <4ed7e372-b468-3858-c765-89b93ecd3422@st.com> (raw)
In-Reply-To: <20200909154413.28064-1-patrick.delaunay@st.com>
Reviewed-by: Yannick Fertr? <yannick.fertre@st.com>
On 9/9/20 5:44 PM, Patrick Delaunay wrote:
> Use ofnode_ or dev_ APIs instead of fdt_ and fdtdec_ APIs so that the
> driver can support live DT.
>
> Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
> ---
>
> drivers/video/stm32/stm32_ltdc.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/video/stm32/stm32_ltdc.c b/drivers/video/stm32/stm32_ltdc.c
> index 2f3427a32e..7fff735930 100644
> --- a/drivers/video/stm32/stm32_ltdc.c
> +++ b/drivers/video/stm32/stm32_ltdc.c
> @@ -366,8 +366,7 @@ static int stm32_ltdc_probe(struct udevice *dev)
>
> ret = panel_get_display_timing(panel, &timings);
> if (ret) {
> - ret = fdtdec_decode_display_timing(gd->fdt_blob,
> - dev_of_offset(panel),
> + ret = ofnode_decode_display_timing(dev_ofnode(panel),
> 0, &timings);
> if (ret) {
> dev_err(dev, "decode display timing error %d\n", ret);
>
next prev parent reply other threads:[~2020-09-10 14:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 15:44 [PATCH 1/2] video: stm32_ltdc: Convert to use APIs which support live DT Patrick Delaunay
2020-09-09 15:44 ` [PATCH 2/2] video: stm32_dsi: " Patrick Delaunay
2020-09-10 13:38 ` Simon Glass
2020-09-10 14:06 ` Yannick FERTRE
2020-10-02 13:10 ` Patrick DELAUNAY
2020-09-10 14:06 ` Yannick FERTRE [this message]
2020-10-02 9:43 ` [PATCH 1/2] video: stm32_ltdc: " Patrice CHOTARD
2020-10-02 13:09 ` Patrick DELAUNAY
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=4ed7e372-b468-3858-c765-89b93ecd3422@st.com \
--to=yannick.fertre@st.com \
--cc=u-boot@lists.denx.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