netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jiawen Wu" <jiawenwu@trustnetic.com>
To: "'Vadim Fedorenko'" <vadim.fedorenko@linux.dev>,
	<andrew+netdev@lunn.ch>, <davem@davemloft.net>,
	<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
	<richardcochran@gmail.com>, <linux@armlinux.org.uk>,
	<horms@kernel.org>, <jacob.e.keller@intel.com>,
	<netdev@vger.kernel.org>
Cc: <mengyuanlou@net-swift.com>
Subject: RE: [PATCH net-next 2/4] net: wangxun: Implement get_ts_info
Date: Mon, 6 Jan 2025 10:35:10 +0800	[thread overview]
Message-ID: <032601db5fe3$9b96d550$d2c47ff0$@trustnetic.com> (raw)
In-Reply-To: <00a642f0-5e80-4aa7-b1e5-219fa0fcb973@linux.dev>

> > +int wx_get_ts_info(struct net_device *dev,
> > +		   struct kernel_ethtool_ts_info *info)
> > +{
> > +	struct wx *wx = netdev_priv(dev);
> > +
> > +	info->rx_filters = BIT(HWTSTAMP_FILTER_NONE) |
> > +			   BIT(HWTSTAMP_FILTER_PTP_V1_L4_SYNC) |
> > +			   BIT(HWTSTAMP_FILTER_PTP_V1_L4_DELAY_REQ) |
> > +			   BIT(HWTSTAMP_FILTER_PTP_V2_L2_EVENT) |
> > +			   BIT(HWTSTAMP_FILTER_PTP_V2_L4_EVENT) |
> > +			   BIT(HWTSTAMP_FILTER_PTP_V2_SYNC) |
> > +			   BIT(HWTSTAMP_FILTER_PTP_V2_L2_SYNC) |
> > +			   BIT(HWTSTAMP_FILTER_PTP_V2_L4_SYNC) |
> > +			   BIT(HWTSTAMP_FILTER_PTP_V2_DELAY_REQ) |
> > +			   BIT(HWTSTAMP_FILTER_PTP_V2_L2_DELAY_REQ) |
> > +			   BIT(HWTSTAMP_FILTER_PTP_V2_L4_DELAY_REQ) |
> > +			   BIT(HWTSTAMP_FILTER_PTP_V2_EVENT);
> > +
> > +	info->so_timestamping = SOF_TIMESTAMPING_TX_SOFTWARE |
> > +				SOF_TIMESTAMPING_RX_SOFTWARE |
> 
> SOF_TIMESTAMPING_RX_SOFTWARE is now moved to core networking and there
> is no need to report it from driver
> 
> > +				SOF_TIMESTAMPING_SOFTWARE |
> 
> SOF_TIMESTAMPING_SOFTWARE means "software-system-clock". What kind of
> software clock is provided by the driver?

I think I should remove it.


  reply	other threads:[~2025-01-06  2:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 10:30 [PATCH net-next 0/4] Support PTP clock for Wangxun NICs Jiawen Wu
2025-01-02 10:30 ` [PATCH net-next 1/4] net: wangxun: Add support for PTP clock Jiawen Wu
2025-01-02 14:13   ` Andrew Lunn
2025-01-06  7:42     ` Jiawen Wu
2025-01-06 14:26       ` Andrew Lunn
2025-01-07  2:24         ` Jiawen Wu
2025-01-07 13:33           ` Andrew Lunn
2025-01-08  0:34             ` Keller, Jacob E
2025-01-08  7:26               ` Jiawen Wu
2025-01-08 18:32                 ` Andrew Lunn
2025-01-02 16:16   ` kernel test robot
2025-01-02 17:33   ` Vadim Fedorenko
2025-01-06 21:29   ` Keller, Jacob E
2025-01-02 10:30 ` [PATCH net-next 2/4] net: wangxun: Implement get_ts_info Jiawen Wu
2025-01-02 17:44   ` Vadim Fedorenko
2025-01-06  2:35     ` Jiawen Wu [this message]
2025-01-02 10:30 ` [PATCH net-next 3/4] net: wangxun: Add watchdog task for PTP clock Jiawen Wu
2025-01-02 17:53   ` Vadim Fedorenko
2025-01-03  8:45     ` Richard Cochran
2025-01-02 10:30 ` [PATCH net-next 4/4] net: ngbe: Add support for 1PPS and TOD Jiawen Wu

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='032601db5fe3$9b96d550$d2c47ff0$@trustnetic.com' \
    --to=jiawenwu@trustnetic.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jacob.e.keller@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mengyuanlou@net-swift.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardcochran@gmail.com \
    --cc=vadim.fedorenko@linux.dev \
    /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).