From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: marvell: 8040-mcbin: Enable 1GB Ethernet
Date: Tue, 6 Jun 2017 11:36:26 +0200 [thread overview]
Message-ID: <20170606113626.197efbf7@free-electrons.com> (raw)
In-Reply-To: <87h8ztjwz0.fsf@arm.com>
Hello,
On Tue, 06 Jun 2017 10:18:11 +0100, Marc Zyngier wrote:
> > So perhaps we should indeed keep Marc's patch, enabling just the 1GB
> > Ethernet interface.
>
> Whichever patch we merge, Andrew's comment remains. Should we stick with
> "phy", or switch to "phy-handle" everywhere?
Since the binding says to use phy-handle, we should use phy-handle for
your patch. Of course, progressively, we should migrate all our
bindings to this new property name, but I don't think this should be a
prerequisite for your patch to go in.
Side note: I don't understand this change from "phy" to "phy-handle".
It really doesn't make sense to me to encode the type of the property
in the name of the property. Are we going to use:
phy-mode-string = "sgmii";
pinctrl-0-handle = <&foo>;
reg-u32s = <0xdeadbeef 0xbadcafe>;
is there a pointer to the reasoning for this change?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-06-06 9:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 20:01 [PATCH] arm64: dts: marvell: 8040-mcbin: Enable 1GB Ethernet Marc Zyngier
2017-06-05 21:16 ` Andrew Lunn
2017-06-06 8:21 ` Marc Zyngier
2017-06-06 12:10 ` Andrew Lunn
2017-06-06 9:02 ` Thomas Petazzoni
2017-06-06 9:06 ` Thomas Petazzoni
2017-06-06 9:18 ` Marc Zyngier
2017-06-06 9:36 ` Thomas Petazzoni [this message]
2017-06-06 9:57 ` Russell King - ARM Linux
2017-06-06 9:16 ` Marc Zyngier
2017-06-06 9:19 ` Thomas Petazzoni
2017-06-06 12:52 ` Thomas Petazzoni
2017-06-06 13:34 ` Russell King - ARM Linux
2017-06-06 13:48 ` Marc Zyngier
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=20170606113626.197efbf7@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).