From: Vladimir Oltean <olteanv@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: kuba@kernel.org, andrew@lunn.ch, netdev@vger.kernel.org,
"Steffen Bätz" <steffen@innosonix.de>,
"Fabio Estevam" <festevam@denx.de>
Subject: Re: [PATCH net-next] net: dsa: mv88e6xxx: Allow hwstamping on the master port
Date: Thu, 10 Nov 2022 14:53:22 +0200 [thread overview]
Message-ID: <20221110125322.c436jqyplxuzdvcl@skbuf> (raw)
In-Reply-To: <20221110124345.3901389-1-festevam@gmail.com>
On Thu, Nov 10, 2022 at 09:43:45AM -0300, Fabio Estevam wrote:
> From: Steffen Bätz <steffen@innosonix.de>
>
> Currently, it is not possible to run SIOCGHWTSTAMP or SIOCSHWTSTAMP
> ioctls on the dsa master interface if the port_hwtstamp_set/get()
> hooks are present, as implemented in net/dsa/master.c:
>
> static int dsa_master_ioctl(struct net_device *dev, struct ifreq *ifr, int cmd)
> {
> ...
> case SIOCGHWTSTAMP:
> case SIOCSHWTSTAMP:
> /* Deny PTP operations on master if there is at least one
> * switch in the tree that is PTP capable.
> */
> list_for_each_entry(dp, &dst->ports, list)
> if (dp->ds->ops->port_hwtstamp_get ||
> dp->ds->ops->port_hwtstamp_set)
> return -EBUSY;
> break;
> }
>
> Even if the hwtstamping functionality is disabled in the mv88e6xxx driver
> by not setting CONFIG_NET_DSA_MV88E6XXX_PTP, the functions port_hwtstamp_set()
> port_hwtstamp_get() are still present due to their stub declarations.
>
> Fix this problem, by removing the stub declarations and guarding these
> functions wih CONFIG_NET_DSA_MV88E6XXX_PTP.
>
> Without this change:
>
> # hwstamp_ctl -i eth0
> SIOCGHWTSTAMP failed: Device or resource busy
>
> With the change applied, it is possible to set and get the timestamping
> options:
>
> # hwstamp_ctl -i eth0
> current settings:
> tx_type 0
> rx_filter 0
>
> # hwstamp_ctl -i eth0 -r 1 -t 1
> current settings:
> tx_type 0
> rx_filter 0
> new settings:
> tx_type 1
> rx_filter 1
>
> Tested on a custom i.MX8MN board with a 88E6320 switch.
>
> Signed-off-by: Steffen Bätz <steffen@innosonix.de>
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> ---
NACK.
Please extend dsa_master_ioctl() to "see through" the dp->ds->ops->port_hwtstamp_get()
pointer, similar to what dsa_port_can_configure_learning() does. Create
a fake struct ifreq, call port_hwtstamp_get(), see if it returned
-EOPNOTSUPP, and wrap that into a dsa_port_supports_hwtstamp() function,
and call that instead of the current simplistic checks for the function
pointers.
next prev parent reply other threads:[~2022-11-10 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 12:43 [PATCH net-next] net: dsa: mv88e6xxx: Allow hwstamping on the master port Fabio Estevam
2022-11-10 12:53 ` Vladimir Oltean [this message]
2022-11-11 11:13 ` Fabio Estevam
2022-11-11 21:41 ` Vladimir Oltean
2022-11-12 0:06 ` Fabio Estevam
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=20221110125322.c436jqyplxuzdvcl@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen@innosonix.de \
/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