From: Andrew Lunn <andrew@lunn.ch>
To: Daniel Machon <daniel.machon@microchip.com>
Cc: UNGLinuxDriver@microchip.com, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Russell King <linux@armlinux.org.uk>,
jacob.e.keller@intel.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, robert.marko@sartura.hr
Subject: Re: [PATCH net-next v5 9/9] dt-bindings: net: sparx5: document RGMII delays
Date: Fri, 20 Dec 2024 18:23:27 +0100 [thread overview]
Message-ID: <cb42f0d7-d2fd-460b-9f38-3b9ebfec7607@lunn.ch> (raw)
In-Reply-To: <20241220-sparx5-lan969x-switch-driver-4-v5-9-fa8ba5dff732@microchip.com>
On Fri, Dec 20, 2024 at 02:48:48PM +0100, Daniel Machon wrote:
> The lan969x switch device supports two RGMII port interfaces that can be
> configured for MAC level rx and tx delays. Document two new properties
> {rx,tx}-internal-delay-ps in the bindings, used to select these delays.
>
> Tested-by: Robert Marko <robert.marko@sartura.hr>
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> Signed-off-by: Daniel Machon <daniel.machon@microchip.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2024-12-20 17:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 13:48 [PATCH net-next v5 0/9] net: lan969x: add RGMII support Daniel Machon
2024-12-20 13:48 ` [PATCH net-next v5 1/9] net: sparx5: do some preparation work Daniel Machon
2024-12-20 13:48 ` [PATCH net-next v5 2/9] net: sparx5: add function for RGMII port check Daniel Machon
2024-12-20 13:48 ` [PATCH net-next v5 3/9] net: sparx5: use is_port_rgmii() throughout Daniel Machon
2024-12-20 13:48 ` [PATCH net-next v5 4/9] net: sparx5: skip low-speed configuration when port is RGMII Daniel Machon
2024-12-20 13:48 ` [PATCH net-next v5 5/9] net: sparx5: only return PCS for modes that require it Daniel Machon
2024-12-20 13:48 ` [PATCH net-next v5 6/9] net: sparx5: verify RGMII speeds Daniel Machon
2024-12-20 13:48 ` [PATCH net-next v5 7/9] net: lan969x: add RGMII registers Daniel Machon
2024-12-20 13:48 ` [PATCH net-next v5 8/9] net: lan969x: add RGMII implementation Daniel Machon
2024-12-20 13:48 ` [PATCH net-next v5 9/9] dt-bindings: net: sparx5: document RGMII delays Daniel Machon
2024-12-20 17:23 ` Andrew Lunn [this message]
2024-12-23 19:10 ` [PATCH net-next v5 0/9] net: lan969x: add RGMII support patchwork-bot+netdevbpf
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=cb42f0d7-d2fd-460b-9f38-3b9ebfec7607@lunn.ch \
--to=andrew@lunn.ch \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=jacob.e.keller@intel.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robert.marko@sartura.hr \
--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
all inboxes | Powered by JetHome®