From: Shawn Guo <shawnguo2@yeah.net>
To: Fabio Estevam <festevam@gmail.com>
Cc: shawnguo@kernel.org, linux-arm-kernel@lists.infradead.org,
rmfrfs@gmail.com, Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH] ARM: dts: imx7s-warp: Fix OV2680 supply names
Date: Tue, 2 Apr 2024 18:58:33 +0800 [thread overview]
Message-ID: <Zgvk2ao9wwT2s/36@dragon> (raw)
In-Reply-To: <20240323125327.1398102-1-festevam@gmail.com>
On Sat, Mar 23, 2024 at 09:53:27AM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
>
> Fix the OV2680 supply names according to ovti,ov2680.yaml.
>
> Signed-off-by: Fabio Estevam <festevam@denx.de>
Do we want to have a Fixes tag for it?
Shawn
> ---
> arch/arm/boot/dts/nxp/imx/imx7s-warp.dts | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/boot/dts/nxp/imx/imx7s-warp.dts b/arch/arm/boot/dts/nxp/imx/imx7s-warp.dts
> index ba7231b364bb..c26888b7af3f 100644
> --- a/arch/arm/boot/dts/nxp/imx/imx7s-warp.dts
> +++ b/arch/arm/boot/dts/nxp/imx/imx7s-warp.dts
> @@ -201,9 +201,9 @@ ov2680: camera@36 {
> clocks = <&osc>;
> clock-names = "xvclk";
> reset-gpios = <&gpio1 3 GPIO_ACTIVE_LOW>;
> - DOVDD-supply = <&sw2_reg>;
> - DVDD-supply = <&sw2_reg>;
> - AVDD-supply = <®_peri_3p15v>;
> + dovdd-supply = <&sw2_reg>;
> + dvdd-supply = <&sw2_reg>;
> + avdd-supply = <®_peri_3p15v>;
>
> port {
> ov2680_to_mipi: endpoint {
> --
> 2.34.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-04-02 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 12:53 [PATCH] ARM: dts: imx7s-warp: Fix OV2680 supply names Fabio Estevam
2024-04-02 10:58 ` Shawn Guo [this message]
2024-04-02 11:11 ` Fabio Estevam
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=Zgvk2ao9wwT2s/36@dragon \
--to=shawnguo2@yeah.net \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rmfrfs@gmail.com \
--cc=shawnguo@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.