From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Karol Kolacinski <karol.kolacinski@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: netdev@vger.kernel.org, anthony.l.nguyen@intel.com,
jesse.brandeburg@intel.com, Yochai Hagvi <yochai.hagvi@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next 2/2] ice: Enable SW interrupt from FW for LL TS
Date: Fri, 24 Nov 2023 12:46:32 +0100 [thread overview]
Message-ID: <2916e3e2-4222-ebf5-0ae0-4982ce57f1ef@intel.com> (raw)
In-Reply-To: <20231124114155.251360-2-karol.kolacinski@intel.com>
On 11/24/23 12:41, Karol Kolacinski wrote:
> Introduce new capability - Low Latency Timestamping with Interrupt.
> On supported devices, driver can request a single timestamp from FW
> without polling the register afterwards. Instead, FW can issue
> a dedicated interrupt when the timestamp was read from the PHY register
> and its value is available to read from the register.
> This eliminates the need of bottom half scheduling, which results in
> minimal delay for timestamping.
>
> For this mode, allocate TS indices sequentially, so that timestamps are
> always completed in FIFO manner.
>
> Co-developed-by: Yochai Hagvi <yochai.hagvi@intel.com>
> Signed-off-by: Yochai Hagvi <yochai.hagvi@intel.com>
> Signed-off-by: Karol Kolacinski <karol.kolacinski@intel.com>
> ---
> drivers/net/ethernet/intel/ice/ice.h | 2 +
> drivers/net/ethernet/intel/ice/ice_common.c | 3 +
> .../net/ethernet/intel/ice/ice_hw_autogen.h | 2 +
> drivers/net/ethernet/intel/ice/ice_main.c | 120 +++++++++++--
> drivers/net/ethernet/intel/ice/ice_ptp.c | 163 ++++++++++++++++--
> drivers/net/ethernet/intel/ice/ice_ptp.h | 9 +
> drivers/net/ethernet/intel/ice/ice_ptp_hw.h | 1 +
> drivers/net/ethernet/intel/ice/ice_type.h | 2 +
> 8 files changed, 274 insertions(+), 28 deletions(-)
Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-11-24 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 11:41 [Intel-wired-lan] [PATCH iwl-next 1/2] ice: Schedule service task in IRQ top half Karol Kolacinski
2023-11-24 11:41 ` [Intel-wired-lan] [PATCH iwl-next 2/2] ice: Enable SW interrupt from FW for LL TS Karol Kolacinski
2023-11-24 11:46 ` Przemek Kitszel [this message]
2023-11-24 11:46 ` [Intel-wired-lan] [PATCH iwl-next 1/2] ice: Schedule service task in IRQ top half Przemek Kitszel
2023-11-27 16:46 ` Simon Horman
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=2916e3e2-4222-ebf5-0ae0-4982ce57f1ef@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=karol.kolacinski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=yochai.hagvi@intel.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