public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Raphaël Gallais-Pou" <rgallaispou@gmail.com>
To: Patrick DELAUNAY <patrick.delaunay@foss.st.com>,
	uboot-stm32@st-md-mailman.stormreply.com, u-boot@lists.denx.de
Cc: Anatolij Gustschin <ag.dev.uboot@gmail.com>,
	Patrice Chotard <patrice.chotard@foss.st.com>,
	Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] video: stm32: dsi: add .of_to_plat callback
Date: Mon, 2 Mar 2026 17:23:23 +0100	[thread overview]
Message-ID: <beec85d9-a580-4ae3-854d-3c957b888eb2@gmail.com> (raw)
In-Reply-To: <50a9f6c3-4284-460c-a429-49b4a53c836e@foss.st.com>

Hi,

Can this one be picked up for v2026.04 or is there something I should do ?

Best regards,
Raphaël

On 2/24/26 11:01, Patrick DELAUNAY wrote:
> Hi,
> 
> On 2/5/26 00:35, Raphael Gallais-Pou wrote:
>> Drivers should extract device-tree data before probing via the
>> .of_to_plat hook.
>>
>> Implement it for stm32_dsi driver.  By doing so, it also solve a
>> variable shadowing in stm32_dsi_probe() where &clk was used as
>> peripheral clock and ref clock.
>>
>> For readability some struct have been renamed such as:
>>
>>    * struct stm32_dsi_priv *dsi -> struct stm32_dsi_priv *priv
>>    * struct clk clk -> struct clk pclk
>>
>> Signed-off-by: Raphael Gallais-Pou <rgallaispou@gmail.com>
>> ---
>> This patch has been tested on stm32mp157c-dk2 board.
>> ---
>>   drivers/video/stm32/stm32_dsi.c | 168 +++++++++++++++++++++ 
>> +------------------
>>   1 file changed, 91 insertions(+), 77 deletions(-)
>>
> 
> 
> Reviewed-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
> 
> Thanks
> Patrick
> 


  reply	other threads:[~2026-03-02 16:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-04 23:35 [PATCH] video: stm32: dsi: add .of_to_plat callback Raphael Gallais-Pou
2026-02-24 10:01 ` Patrick DELAUNAY
2026-03-02 16:23   ` Raphaël Gallais-Pou [this message]
2026-03-06 22:33     ` Tom Rini
2026-03-09  6:48       ` Patrice CHOTARD
2026-03-09 16:57 ` Tom Rini

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=beec85d9-a580-4ae3-854d-3c957b888eb2@gmail.com \
    --to=rgallaispou@gmail.com \
    --cc=ag.dev.uboot@gmail.com \
    --cc=patrice.chotard@foss.st.com \
    --cc=patrick.delaunay@foss.st.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-stm32@st-md-mailman.stormreply.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