Netdev List
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Selvamani Rajagopal <Selvamani.Rajagopal@onsemi.com>
Cc: Piergiorgio Beruto <Pier.Beruto@onsemi.com>,
	"parthiban.veerasooran@microchip.com"
	<parthiban.veerasooran@microchip.com>,
	"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v2 6/9] net: ethernet: oa_tc6: Hardware timestamp support for OA TC6 framework
Date: Mon, 11 May 2026 21:49:10 +0200	[thread overview]
Message-ID: <46a6321a-408f-4c63-8835-86ee9c4bdcd6@lunn.ch> (raw)
In-Reply-To: <CY8PR02MB9249D813205563D5C64ACEFF83382@CY8PR02MB9249.namprd02.prod.outlook.com>

On Mon, May 11, 2026 at 06:19:31PM +0000, Selvamani Rajagopal wrote:
> Added hardware timestamp support as defined in Open Alliance
> 10BASET1x MACPHY_Serial_Interface specification. ioctl interface
> added for ethtool to report and set the hardware timestamp feature

7.8 Frame Timestamp Capture

The MAC-PHY may optionally support the capturing of timestamps on
Ethernet frames received from and transmitted to the network. Support
for this option is indicated by the Frame Timestamp Capability (FTSC)
bit in the STDCAP register

I don't see anything in this patch looking for FTSC.

> +/**
> + * oa_tc6_hwtstamp_ioctl - ioctl interface for hardware timestamp
> + * @tc6: oa_tc6 struct.
> + * @rq: request from socket interface
> + * @cmd: value to set/get timestamp configuration
> + *
> + * Return: 0 on success otherwise failed.
> + */
> +int oa_tc6_hwtstamp_ioctl(struct oa_tc6 *tc6, struct ifreq *rq, int cmd)
> +{

It would be better to add a generic ioctl handler. It can call
phy_do_ioctl_running(), and can check if time stamping is support in
the hardware, and if so, also support the time stamping IOCTL calls.

    Andrew

      reply	other threads:[~2026-05-11 19:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 18:19 [PATCH net-next v2 6/9] net: ethernet: oa_tc6: Hardware timestamp support for OA TC6 framework Selvamani Rajagopal
2026-05-11 19:49 ` Andrew Lunn [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=46a6321a-408f-4c63-8835-86ee9c4bdcd6@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Pier.Beruto@onsemi.com \
    --cc=Selvamani.Rajagopal@onsemi.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=parthiban.veerasooran@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