From: "Marek Behún" <kabel@kernel.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: arm@kernel.org, "Andrew Lunn" <andrew@lunn.ch>,
"Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Jason Cooper" <jason@lakedaemon.net>,
"Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
"Gregory CLEMENT" <gregory.clement@bootlin.com>
Subject: Re: [PATCH mvebu-dt v2 6/6] ARM: dts: turris-omnia: update ethernet-phy node and handle name
Date: Sun, 15 Nov 2020 00:30:15 +0100 [thread overview]
Message-ID: <20201115003015.03ec06d5@kernel.org> (raw)
In-Reply-To: <46bf04e0-febb-f9f2-454c-770b08a9d560@suse.de>
On Sat, 14 Nov 2020 23:04:41 +0100
Andreas Färber <afaerber@suse.de> wrote:
Hi Andreas,
> > - phy1: phy@1 {
> > + phy1: ethernet-phy@1 {
>
> This one I had noticed in the DT binding and verified that mainline
> U-Boot does not rely on it. So ACK for this.
>
> > status = "okay";
>
> Unrelated: This property is theoretically superfluous, as unlike eth2
> this node is new and doesn't overwrite a pre-existing property.
Yes, status = "okay" is not needed if there isn't status = "disabled"
before (somewhere in include files). Maybe I will send a patch removing
all unneeded status="okay" properties in the future.
> I believe in my testing overriding with status = "disabled" was not
> enough to get the SFP to work, I needed to comment out the referencing
> phy(-handle) property.
Yes, as I wrote in reply to your question in patch 4/6, U-Boot needs to:
- remove phy-handle property
- add managed = in-band-status property
- enable sfp node
>
> > - compatible = "ethernet-phy-id0141.0DD1", "ethernet-phy-ieee802.3-c22";
> > + compatible = "ethernet-phy-ieee802.3-c22";
>
> Does it do any harm to leave it in though?
No, but lets remove it anyway :)
Marek
prev parent reply other threads:[~2020-11-14 23:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 18:32 [PATCH mvebu-dt v2 0/6] Turris Omnia device-tree changes Marek Behún
2020-11-14 18:32 ` [PATCH mvebu-dt v2 1/6] ARM: dts: turris-omnia: enable HW buffer management Marek Behún
2020-11-14 18:32 ` [PATCH mvebu-dt v2 2/6] ARM: dts: turris-omnia: add comphy handle to eth2 Marek Behún
2020-11-14 21:25 ` Andreas Färber
2020-11-14 18:32 ` [PATCH mvebu-dt v2 3/6] ARM: dts: turris-omnia: describe switch interrupt Marek Behún
2020-11-14 18:32 ` [PATCH mvebu-dt v2 4/6] ARM: dts: turris-omnia: add SFP node Marek Behún
2020-11-14 21:36 ` Andreas Färber
2020-11-14 21:42 ` Russell King - ARM Linux admin
2020-11-14 21:46 ` Andreas Färber
2020-11-14 22:55 ` Marek Behún
2020-11-15 11:28 ` Russell King - ARM Linux admin
2020-11-14 22:57 ` Marek Behún
2020-11-14 23:16 ` Andreas Färber
2020-11-15 0:32 ` Marek Behún
2020-11-15 0:38 ` Marek Behún
2020-11-14 23:27 ` Andreas Färber
2020-11-15 0:11 ` Marek Behún
2020-11-14 18:32 ` [PATCH mvebu-dt v2 5/6] ARM: dts: turris-omnia: add LED controller node Marek Behún
2020-11-14 21:58 ` Andreas Färber
2020-11-14 23:23 ` Marek Behún
2020-11-14 18:32 ` [PATCH mvebu-dt v2 6/6] ARM: dts: turris-omnia: update ethernet-phy node and handle name Marek Behún
2020-11-14 22:04 ` Andreas Färber
2020-11-14 23:30 ` Marek Behún [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=20201115003015.03ec06d5@kernel.org \
--to=kabel@kernel.org \
--cc=afaerber@suse.de \
--cc=andrew@lunn.ch \
--cc=arm@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=robh+dt@kernel.org \
--cc=uwe@kleine-koenig.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;
as well as URLs for NNTP newsgroup(s).