From: Andrew Lunn <andrew@lunn.ch>
To: Steve Twiss <stwiss.opensource@diasemi.com>
Cc: "Fabio Estevam" <festevam@gmail.com>,
"Shawn Guo" <shawnguo@kernel.org>,
"Michal Vokáč" <michal.vokac@ysoft.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Abel Vesa" <abel.vesa@nxp.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
dl-linux-imx <linux-imx@nxp.com>,
DEVICETREE <devicetree@vger.kernel.org>,
LINUX-ARM-KERNEL <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
"Support Opensource" <Support.Opensource@diasemi.com>
Subject: Re: [PATCH] ARM: dts: imx6qdl-sabresd: change phy-mode to use rgmii-id
Date: Fri, 22 Mar 2019 11:59:59 +0100 [thread overview]
Message-ID: <20190322105959.GD24801@lunn.ch> (raw)
In-Reply-To: <DB7PR10MB2348358D285E2560F5B5E699FE430@DB7PR10MB2348.EURPRD10.PROD.OUTLOOK.COM>
> There is a way of doing this to preserve backwards compatibility I think.
> Maybe deprecating the previous DTS phy-mode and replacing it with a new one,
> phy-mode-v2 instead?
Hi Steve
It needs to be a vendor specific property, atheros,phy-mode, for
example.
Andrew
prev parent reply other threads:[~2019-03-22 10:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 11:03 [PATCH] ARM: dts: imx6qdl-sabresd: change phy-mode to use rgmii-id Steve Twiss
2019-03-20 12:16 ` Fabio Estevam
2019-03-20 16:03 ` Steve Twiss
2019-03-20 17:04 ` Fabio Estevam
2019-03-21 8:42 ` Abel Vesa
2019-03-21 11:17 ` Fabio Estevam
2019-03-21 11:32 ` Steve Twiss
2019-03-21 11:50 ` Andrew Lunn
2019-03-21 11:45 ` Andrew Lunn
2019-03-21 12:43 ` Lucas Stach
2019-03-22 1:11 ` Shawn Guo
2019-03-22 2:00 ` Fabio Estevam
2019-03-22 2:15 ` Shawn Guo
2019-03-22 2:24 ` Fabio Estevam
2019-03-22 10:20 ` Michal Vokáč
2019-03-22 10:50 ` Steve Twiss
2019-03-22 10:59 ` Andrew Lunn [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=20190322105959.GD24801@lunn.ch \
--to=andrew@lunn.ch \
--cc=Support.Opensource@diasemi.com \
--cc=abel.vesa@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.vokac@ysoft.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stwiss.opensource@diasemi.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;
as well as URLs for NNTP newsgroup(s).