linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Ninad Palsule <ninad@linux.ibm.com>
To: minyard@acm.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	openipmi-developer@lists.sourceforge.net, netdev@vger.kernel.org,
	joel@jms.id.au, andrew@codeconstruct.com.au,
	devicetree@vger.kernel.org, eajames@linux.ibm.com,
	linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Ninad Palsule <ninad@linux.ibm.com>
Subject: [PATCH v4 1/9] dt-bindings: net: faraday,ftgmac100: Add phys mode
Date: Mon, 13 Jan 2025 13:48:11 -0600	[thread overview]
Message-ID: <20250113194822.571884-2-ninad@linux.ibm.com> (raw)
In-Reply-To: <20250113194822.571884-1-ninad@linux.ibm.com>

Aspeed device supports rgmii, rgmii-id, rgmii-rxid, rgmii-txid so
document them.

Acked-by: Rob Herring (Arm) <robh@kernel.org>
Signed-off-by: Ninad Palsule <ninad@linux.ibm.com>
---
 Documentation/devicetree/bindings/net/faraday,ftgmac100.yaml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/devicetree/bindings/net/faraday,ftgmac100.yaml b/Documentation/devicetree/bindings/net/faraday,ftgmac100.yaml
index 9bcbacb6640d..55d6a8379025 100644
--- a/Documentation/devicetree/bindings/net/faraday,ftgmac100.yaml
+++ b/Documentation/devicetree/bindings/net/faraday,ftgmac100.yaml
@@ -44,6 +44,9 @@ properties:
   phy-mode:
     enum:
       - rgmii
+      - rgmii-id
+      - rgmii-rxid
+      - rgmii-txid
       - rmii
 
   phy-handle: true
-- 
2.43.0



  reply	other threads:[~2025-01-13 19:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13 19:48 [PATCH v4 0/9] DTS updates for system1 BMC Ninad Palsule
2025-01-13 19:48 ` Ninad Palsule [this message]
2025-01-13 19:48 ` [PATCH v4 2/9] bindings: ipmi: Add binding for IPMB device intf Ninad Palsule
2025-01-14 16:46   ` Corey Minyard
2025-01-14 22:07     ` Ninad Palsule
2025-01-13 19:48 ` [PATCH v4 3/9] ARM: dts: aspeed: system1: Add IPMB device Ninad Palsule
2025-01-13 19:48 ` [PATCH v4 4/9] ARM: dts: aspeed: system1: Add GPIO line name Ninad Palsule
2025-01-13 19:48 ` [PATCH v4 5/9] ARM: dts: aspeed: system1: Reduce sgpio speed Ninad Palsule
2025-01-13 19:48 ` [PATCH v4 6/9] ARM: dts: aspeed: system1: Update LED gpio name Ninad Palsule
2025-01-13 19:48 ` [PATCH v4 7/9] ARM: dts: aspeed: system1: Remove VRs max8952 Ninad Palsule
2025-01-13 19:48 ` [PATCH v4 8/9] ARM: dts: aspeed: system1: Mark GPIO line high/low Ninad Palsule
2025-01-13 19:48 ` [PATCH v4 9/9] ARM: dts: aspeed: system1: Disable gpio pull down Ninad Palsule

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=20250113194822.571884-2-ninad@linux.ibm.com \
    --to=ninad@linux.ibm.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@codeconstruct.com.au \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=eajames@linux.ibm.com \
    --cc=edumazet@google.com \
    --cc=joel@jms.id.au \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minyard@acm.org \
    --cc=netdev@vger.kernel.org \
    --cc=openipmi-developer@lists.sourceforge.net \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.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).