Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: George McCollister <george.mccollister@gmail.com>
Cc: Richard Cochran <richardcochran@gmail.com>,
	netdev <netdev@vger.kernel.org>
Subject: Re: net: dsa: mv88e6xxx: no multicasts rx'd after enabling hw time stamping
Date: Thu, 29 Jul 2021 15:42:54 +0200	[thread overview]
Message-ID: <YQKwXj8v+NFQs4dw@lunn.ch> (raw)
In-Reply-To: <CAFSKS=OtAgLCo0MLe8CORUgkapZLRbe6hRiKU7QWSd5a70wgrw@mail.gmail.com>

> Thanks for the feedback. The datasheet covers the 88E6390X, 88E6390,
> 88E6290, 88E6190X, 88E6190 so I expect those work similarly but if
> only the 6352 has been tested that could explain it. It certainly
> helps to know that I'm working with something that may have never
> worked rather than I'm just doing something dumb.

I don't think you are doing something dumb.

What i find interesting is that multicast works, until it does not
work. I would try to find out what call into the driver causes that
change.

Also, general multicast traffic should not really be involved
here. The switch should be identifying PTP packets as management, and
sending them to the CPU port, independent of whatever multicast rules
are set, flooding of unknown multicast etc. This is needed so that PTP
frames get through a bridge which is in STP blocking mode. Do you see
any other problems with management traffic? Do bridge PDUs also not
work?

	Andrew

  reply	other threads:[~2021-07-29 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 20:44 George McCollister
2021-07-28 21:04 ` Andrew Lunn
2021-07-28 22:24   ` Richard Cochran
2021-07-29 13:22     ` George McCollister
2021-07-29 13:42       ` Andrew Lunn [this message]
2021-08-11 15:49         ` George McCollister
2021-07-29 13:09   ` George McCollister

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=YQKwXj8v+NFQs4dw@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=george.mccollister@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --subject='Re: net: dsa: mv88e6xxx: no multicasts rx'\''d after enabling hw time stamping' \
    /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

This is a public inbox, see mirroring instructions
on how to clone and mirror all data and code used for this inbox