All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com,
	Muhammad Husaini Zulkifli <muhammad.husaini.zulkifli@intel.com>,
	netdev@vger.kernel.org, sasha.neftin@intel.com,
	Tan Tee Min <tee.min.tan@linux.intel.com>,
	Naama Meir <naamax.meir@linux.intel.com>
Subject: Re: [PATCH net-next 1/3] igc: remove I226 Qbv BaseTime restriction
Date: Wed, 4 Jan 2023 09:30:48 +0200	[thread overview]
Message-ID: <Y7UrKJn54RQPaxJu@unreal> (raw)
In-Reply-To: <20230103230503.1102426-2-anthony.l.nguyen@intel.com>

On Tue, Jan 03, 2023 at 03:05:01PM -0800, Tony Nguyen wrote:
> From: Muhammad Husaini Zulkifli <muhammad.husaini.zulkifli@intel.com>
> 
> Remove the Qbv BaseTime restriction for I226 so that the BaseTime can be
> scheduled to the future time. A new register bit of Tx Qav Control
> (Bit-7: FutScdDis) was introduced to allow I226 scheduling future time as
> Qbv BaseTime and not having the Tx hang timeout issue.
> 
> Besides, according to datasheet section 7.5.2.9.3.3, FutScdDis bit has to
> be configured first before the cycle time and base time.
> 
> Indeed the FutScdDis bit is only active on re-configuration, thus we have
> to set the BASET_L to zero and then only set it to the desired value.
> 
> Please also note that the Qbv configuration flow is moved around based on
> the Qbv programming guideline that is documented in the latest datasheet.
> 
> Co-developed-by: Tan Tee Min <tee.min.tan@linux.intel.com>
> Signed-off-by: Tan Tee Min <tee.min.tan@linux.intel.com>
> Signed-off-by: Muhammad Husaini Zulkifli <muhammad.husaini.zulkifli@intel.com>
> Tested-by: Naama Meir <naamax.meir@linux.intel.com>
> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
> ---
>  drivers/net/ethernet/intel/igc/igc_base.c    | 29 +++++++++++++
>  drivers/net/ethernet/intel/igc/igc_base.h    |  2 +
>  drivers/net/ethernet/intel/igc/igc_defines.h |  1 +
>  drivers/net/ethernet/intel/igc/igc_main.c    |  5 ++-
>  drivers/net/ethernet/intel/igc/igc_tsn.c     | 44 +++++++++++++-------
>  5 files changed, 65 insertions(+), 16 deletions(-)
> 

Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>

  reply	other threads:[~2023-01-04  7:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 23:05 [PATCH net-next 0/3][pull request] Intel Wired LAN Driver Updates 2023-01-03 (igc) Tony Nguyen
2023-01-03 23:05 ` [PATCH net-next 1/3] igc: remove I226 Qbv BaseTime restriction Tony Nguyen
2023-01-04  7:30   ` Leon Romanovsky [this message]
2023-01-03 23:05 ` [PATCH net-next 2/3] igc: enable Qbv configuration for 2nd GCL Tony Nguyen
2023-01-04  7:31   ` Leon Romanovsky
2023-01-03 23:05 ` [PATCH net-next 3/3] igc: Remove reset adapter task for i226 during disable tsn config Tony Nguyen
2023-01-04  7:31   ` Leon Romanovsky
2023-01-04  9:00 ` [PATCH net-next 0/3][pull request] Intel Wired LAN Driver Updates 2023-01-03 (igc) patchwork-bot+netdevbpf

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=Y7UrKJn54RQPaxJu@unreal \
    --to=leon@kernel.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=muhammad.husaini.zulkifli@intel.com \
    --cc=naamax.meir@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sasha.neftin@intel.com \
    --cc=tee.min.tan@linux.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 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.