public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Andrew Lunn <andrew@lunn.ch>,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: armada388-clearfog: add missing phy-modes
Date: Mon, 15 May 2023 09:50:30 +0200	[thread overview]
Message-ID: <87mt26xcc9.fsf@BL-laptop> (raw)
In-Reply-To: <7e9ac2ac-19e2-4664-8f47-7aa82ea1885e@lunn.ch>

Andrew Lunn <andrew@lunn.ch> writes:

> On Sat, May 13, 2023 at 11:21:24AM +0100, Russell King (Oracle) wrote:
>> The DSA framework has got more picky about always having a phy-mode,
>> particularly for the CPU port. Add the missing phy-mode properties
>> for every port which does not have an integrated PHY.
>> 
>> Add a phy-mode property to the ethernet interface facing the switch
>> as this was configured using SGMII - as the switch is actually
>> using 1000base-x, let's have some consistency between the two link
>> partners.
>> 
>> Additionally, the cpu label has never actually been used in the
>> binding, so remove it.
>> 
>> Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
>
> Thanks Russell
>
> The changes for most of the IMX board where merged recently. So
> hopefully by the merge window, we will have all boards updated.
>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
>
>     Andrew

Applied on mvebu/dt

Thanks,

Gregory

-- 
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com

      reply	other threads:[~2023-05-15  7:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-13 10:21 [PATCH] ARM: dts: armada388-clearfog: add missing phy-modes Russell King (Oracle)
2023-05-13 13:53 ` Andrew Lunn
2023-05-15  7:50   ` 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=87mt26xcc9.fsf@BL-laptop \
    --to=gregory.clement@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.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