public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Josua Mayer <josua@solid-run.com>,
	Arnd Bergman <arnd.bergmann@linaro.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Josua Mayer <josua@solid-run.com>
Subject: Re: [PATCH v2] arm64: dts: marvell: cn9130-sr-som: fix cp0 mdio pin numbers
Date: Mon, 07 Oct 2024 10:13:59 +0200	[thread overview]
Message-ID: <874j5oe3eg.fsf@BLaptop.bootlin.com> (raw)
In-Reply-To: <20241002-cn9130-som-mdio-v2-1-ec798e4a83ff@solid-run.com>

Hi Josua and Arnd,

> SolidRun CN9130 SoM actually uses CP_MPP[0:1] for mdio. CP_MPP[40]
> provides reference clock for dsa switch and ethernet phy on Clearfog
> Pro, wheras MPP[41] controls efuse programming voltage "VHV".
>
> Update the cp0 mdio pinctrl node to specify mpp0, mpp1.


Applied on mvebu/fixes

Thanks,

Arnd,

I've applied it on an mvebu branch and I'll create a PR for it this
week. However, since we don't have many fixes, you might prefer to apply
this patch directly to your trees?

Gregory

>
> Fixes: 1c510c7d82e5 ("arm64: dts: add description for solidrun cn9130 som and clearfog boards")
> Cc: stable@vger.kernel.org # 6.11.x
> Signed-off-by: Josua Mayer <josua@solid-run.com>
> ---
> Changes in v2:
> - corrected Cc: stable list address
> - removed duplicate "mdio" from commit message
> - added Fixes: tag
> - Link to v1: https://lore.kernel.org/r/20241002-cn9130-som-mdio-v1-1-0942be4dc550@solid-run.com
> ---
>  arch/arm64/boot/dts/marvell/cn9130-sr-som.dtsi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/marvell/cn9130-sr-som.dtsi b/arch/arm64/boot/dts/marvell/cn9130-sr-som.dtsi
> index 4676e3488f54d53041696d877b510b8d51dcd984..cb8d54895a77753c760b58b8b5103149e21e2094 100644
> --- a/arch/arm64/boot/dts/marvell/cn9130-sr-som.dtsi
> +++ b/arch/arm64/boot/dts/marvell/cn9130-sr-som.dtsi
> @@ -136,7 +136,7 @@ cp0_i2c0_pins: cp0-i2c0-pins {
>  		};
>  
>  		cp0_mdio_pins: cp0-mdio-pins {
> -			marvell,pins = "mpp40", "mpp41";
> +			marvell,pins = "mpp0", "mpp1";
>  			marvell,function = "ge";
>  		};
>  
>
> ---
> base-commit: 9852d85ec9d492ebef56dc5f229416c925758edc
> change-id: 20241002-cn9130-som-mdio-4a519e6dc7df
>
> Best regards,
> -- 
> Josua Mayer <josua@solid-run.com>

      parent reply	other threads:[~2024-10-07  8:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 13:07 [PATCH v2] arm64: dts: marvell: cn9130-sr-som: fix cp0 mdio pin numbers Josua Mayer
2024-10-02 13:50 ` Andrew Lunn
2024-10-07  8:13 ` Gregory CLEMENT [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=874j5oe3eg.fsf@BLaptop.bootlin.com \
    --to=gregory.clement@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=arnd.bergmann@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=josua@solid-run.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox