From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Murali Karicheri <m-karicheri2@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Tero Kristo <t-kristo@ti.com>,
"David S . Miller" <davem@davemloft.net>
Cc: Sekhar Nori <nsekhar@ti.com>, Rob Herring <robh+dt@kernel.org>,
netdev <netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>
Subject: [for-next PATCH v2 2/5] dt-bindings: phy: ti: gmii-sel: add support for am654x/j721e soc
Date: Tue, 3 Mar 2020 18:00:26 +0200 [thread overview]
Message-ID: <20200303160029.345-3-grygorii.strashko@ti.com> (raw)
In-Reply-To: <20200303160029.345-1-grygorii.strashko@ti.com>
TI AM654x/J721E SoCs have the same PHY interface selection mechanism for
CPSWx subsystem as TI SoCs (AM3/4/5/DRA7), but registers and bit-fields
placement is different.
This patch adds corresponding compatible strings to enable support for TI
AM654x/J721E SoCs.
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
Acked-by: Rob Herring <robh@kernel.org>
---
Documentation/devicetree/bindings/phy/ti-phy-gmii-sel.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/phy/ti-phy-gmii-sel.txt b/Documentation/devicetree/bindings/phy/ti-phy-gmii-sel.txt
index 50ce9ae0f7a5..83b78c1c0644 100644
--- a/Documentation/devicetree/bindings/phy/ti-phy-gmii-sel.txt
+++ b/Documentation/devicetree/bindings/phy/ti-phy-gmii-sel.txt
@@ -40,6 +40,7 @@ Required properties:
"ti,dra7xx-phy-gmii-sel" for dra7xx/am57xx platform
"ti,am43xx-phy-gmii-sel" for am43xx platform
"ti,dm814-phy-gmii-sel" for dm814x platform
+ "ti,am654-phy-gmii-sel" for AM654x/J721E platform
- reg : Address and length of the register set for the device
- #phy-cells : must be 2.
cell 1 - CPSW port number (starting from 1)
--
2.17.1
next prev parent reply other threads:[~2020-03-03 16:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 16:00 [for-next PATCH v2 0/5] phy: ti: gmii-sel: add support for am654x/j721e soc Grygorii Strashko
2020-03-03 16:00 ` [for-next PATCH v2 1/5] phy: ti: gmii-sel: simplify config dependencies between net drivers and gmii phy Grygorii Strashko
2020-03-05 11:06 ` Kishon Vijay Abraham I
2020-03-13 15:07 ` Grygorii Strashko
[not found] ` <20200316140859.GA30922@a0393678ub>
2020-03-16 21:16 ` Grygorii Strashko
2020-03-03 16:00 ` Grygorii Strashko [this message]
2020-03-03 16:00 ` [for-next PATCH v2 3/5] phy: ti: gmii-sel: add support for am654x/j721e soc Grygorii Strashko
2020-03-03 16:00 ` [for-next PATCH v2 4/5] arm64: dts: ti: k3-am65-mcu: add phy-gmii-sel node Grygorii Strashko
2020-03-03 16:00 ` [for-next PATCH v2 5/5] arm64: dts: ti: k3-j721e-mcu: add scm node and phy-gmii-sel nodes Grygorii Strashko
2020-03-04 22:39 ` [for-next PATCH v2 0/5] phy: ti: gmii-sel: add support for am654x/j721e soc David Miller
2020-03-05 5:17 ` Kishon Vijay Abraham I
2020-03-05 10:55 ` Grygorii Strashko
2020-03-20 9:08 ` Tero Kristo
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=20200303160029.345-3-grygorii.strashko@ti.com \
--to=grygorii.strashko@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.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).