From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <andrew@lunn.ch>, <hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <richardcochran@gmail.com>
Subject: Re: [PATCH net-next v2 0/2] net: micrel: Change how to read TX timestamp
Date: Tue, 13 Jun 2023 13:38:08 +0200 [thread overview]
Message-ID: <20230613113808.mqasva7fuoxuurab@soft-dev3-1> (raw)
In-Reply-To: <20230613094526.69532-1-horatiu.vultur@microchip.com>
The 06/13/2023 11:45, Horatiu Vultur wrote:
Argh... I forgot add Richard to this thread. Therefore CC him now.
> Change how to read the timestamp of the received frames. Currently it is
> required to read over the MDIO bus each of the timestamps but it is
> possible to change to receive the timestamp (the nanosecond part and the
> least significant two bits of the second) in the frame.
> The first patch makes this change, while the second patch optimized the
> read of second part. Because it is not required to read the second part
> of the timestmap for each received frame but it is OK to read the second
> part twice per second and then cache it.
>
> v1->v2:
> - create a patch series instead of single patch
> - add optimization for reading the second part of the received timestamp,
> read the second twice per second instead of for each frame
>
> Horatiu Vultur (2):
> net: micrel: Change to receive timestamp in the frame for lan8841
> net: micrel: Schedule work to read seconds for lan8841
>
> drivers/net/phy/micrel.c | 272 ++++++++++++++++++++++++++-------------
> 1 file changed, 180 insertions(+), 92 deletions(-)
>
> --
> 2.38.0
>
--
/Horatiu
prev parent reply other threads:[~2023-06-13 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 9:45 [PATCH net-next v2 0/2] net: micrel: Change how to read TX timestamp Horatiu Vultur
2023-06-13 9:45 ` [PATCH net-next v2 1/2] net: micrel: Change to receive timestamp in the frame for lan8841 Horatiu Vultur
2023-06-14 5:06 ` Richard Cochran
2023-06-13 9:45 ` [PATCH net-next v2 2/2] net: micrel: Schedule work to read seconds " Horatiu Vultur
2023-06-14 4:49 ` Richard Cochran
2023-06-14 9:19 ` Horatiu Vultur
2023-06-13 11:38 ` Horatiu Vultur [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=20230613113808.mqasva7fuoxuurab@soft-dev3-1 \
--to=horatiu.vultur@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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