-----Original Message-----
From: Andrew Lunn <andrew@lunn.ch>
Sent: 06 June 2024 18:56
To: Swathi K S <redacted>
Cc: davem@davemloft.net; edumazet@google.com; kuba@kernel.org;
pabeni@redhat.com; robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org;
conor+dt@kernel.org; richardcochran@gmail.com;
alexandre.torgue@foss.st.com; joabreu@synopsys.com;
mcoquelin.stm32@gmail.com; alim.akhtar@samsung.com; linux-
fsd@tesla.com; pankaj.dubey@samsung.com; ravi.patel@samsung.com;
netdev@vger.kernel.org; devicetree@vger.kernel.org; linux-
kernel@vger.kernel.org; linux-samsung-soc@vger.kernel.org; linux-arm-
kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/4] dt-bindings: net: Add FSD EQoS device tree

bindings

quoted

quoted

quoted

+  fsd-rx-clock-skew:
+    $ref: /schemas/types.yaml#/definitions/phandle-array
+    items:
+      - items:
+          - description: phandle to the syscon node
+          - description: offset of the control register
+    description:
+      Should be phandle/offset pair. The phandle to the syscon

node.

quoted

quoted

What clock are you skew-ing here? And why?

As per customer's requirement, we need 2ns delay in fsys block both in
TX and RX path.

Lots of people get RGMII delays wrong. Please look back at the mailing

list

where there is plenty of discussion about this. I don't want to have to

repeat

myself yet again...

Sorry for the delay.
We took time to confirm with the board designer regarding this delay.
This is not a mandatory one to have and hence we are dropping clock-skewing
here.

     Andrew

Thanks,
Swathi