From: Jakub Kicinski <kuba@kernel.org>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH net-next 4/4] net: renesas: rswitch: Improve TX timestamp accuracy
Date: Wed, 8 Feb 2023 16:06:34 -0800 [thread overview]
Message-ID: <20230208160634.33d2abfd@kernel.org> (raw)
In-Reply-To: <20230208073445.2317192-5-yoshihiro.shimoda.uh@renesas.com>
On Wed, 8 Feb 2023 16:34:45 +0900 Yoshihiro Shimoda wrote:
> In the previous code, TX timestamp accuracy was bad because the irq
> handler got the timestamp from the timestamp register at that time.
>
> This hardware has "Timestamp capture" feature which can store
> each TX timestamp into the timestamp descriptors. To improve
> TX timestamp accuracy, implement timestamp descriptors' handling.
2 new sparse warnings here:
drivers/net/ethernet/renesas/rswitch.c:917:24: warning: restricted __le32 degrades to integer
drivers/net/ethernet/renesas/rswitch.c:918:23: warning: restricted __le32 degrades to integer
next prev parent reply other threads:[~2023-02-09 0:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 7:34 [PATCH net-next 0/4] net: renesas: rswitch: Improve TX timestamp accuracy Yoshihiro Shimoda
2023-02-08 7:34 ` [PATCH net-next 1/4] net: renesas: rswitch: Rename rings in struct rswitch_gwca_queue Yoshihiro Shimoda
2023-02-08 7:34 ` [PATCH net-next 2/4] net: renesas: rswitch: Move linkfix variables to rswitch_gwca Yoshihiro Shimoda
2023-02-08 7:34 ` [PATCH net-next 3/4] net: renesas: rswitch: Remove gptp flag from rswitch_gwca_queue Yoshihiro Shimoda
2023-02-08 16:06 ` Alexander H Duyck
2023-02-08 23:33 ` Yoshihiro Shimoda
2023-02-09 1:01 ` Alexander Duyck
2023-02-09 1:13 ` Yoshihiro Shimoda
2023-02-08 7:34 ` [PATCH net-next 4/4] net: renesas: rswitch: Improve TX timestamp accuracy Yoshihiro Shimoda
2023-02-09 0:06 ` Jakub Kicinski [this message]
2023-02-09 1:06 ` Yoshihiro Shimoda
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=20230208160634.33d2abfd@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yoshihiro.shimoda.uh@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.