From: Vladimir Oltean <olteanv@gmail.com>
To: Brian Hutchinson <b.hutchman@gmail.com>,
Tristram.Ha@microchip.com, Woojung.Huh@microchip.com
Cc: Christian Eggers <ceggers@arri.de>,
netdev@vger.kernel.org, arun.ramadoss@microchip.com,
rakesh.sankaranarayanan@microchip.com
Subject: Re: Microchip net DSA with ptp4l getting tx_timeout failed msg using 6.3.12 kernel and KSZ9567 switch
Date: Sat, 26 Aug 2023 14:43:04 +0300 [thread overview]
Message-ID: <20230826114304.tb7dm3tr5gun5acs@skbuf> (raw)
In-Reply-To: <CAFZh4h_ueji_KucLdPx9PtTQP1g29PbcjNDFGzLBJYpYK8Rt3w@mail.gmail.com>
On Thu, Aug 24, 2023 at 03:03:32PM -0400, Brian Hutchinson wrote:
> Update. Top posting because I think this is my issue.
>
> I dug further into my problem. I'm using E2E and it looks like the
> mainlined Microchip KSZ DSA PTP code is only supporting P2P.
>
> The 5.10.69 kernel that I was first able to get working with
> Christian's early pre-mainlined patches had:
> 0016-net-dsa-microchip-ksz9477-add-E2E-support.patch
>
> ... which gets into the "sticky" bits of why these patches weren't
> accepted in the first place due to some Microchip specific
> implementation if I recall correctly.
>
> Regards,
>
> Brian
+Tristram Ha, Woojung Huh
prev parent reply other threads:[~2023-08-26 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 21:49 Microchip net DSA with ptp4l getting tx_timeout failed msg using 6.3.12 kernel and KSZ9567 switch Brian Hutchinson
2023-08-23 8:22 ` Christian Eggers
2023-08-23 18:12 ` Brian Hutchinson
[not found] ` <CAFZh4h-6yWvpvzJyv06zy8MbtMmXG==V0h2vU=uUN8iMMcb=ig@mail.gmail.com>
2023-08-24 18:26 ` Brian Hutchinson
2023-08-24 19:03 ` Brian Hutchinson
2023-08-25 15:49 ` Christian Eggers
2023-08-26 11:43 ` Vladimir Oltean [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=20230826114304.tb7dm3tr5gun5acs@skbuf \
--to=olteanv@gmail.com \
--cc=Tristram.Ha@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=arun.ramadoss@microchip.com \
--cc=b.hutchman@gmail.com \
--cc=ceggers@arri.de \
--cc=netdev@vger.kernel.org \
--cc=rakesh.sankaranarayanan@microchip.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