From: Fuxbrumer, Dvora <dvorax.fuxbrumer@linux.intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH next-queue v3 1/3] igc: Use default cycle 'start' and 'end' values for queues
Date: Thu, 19 Aug 2021 00:09:09 +0300 [thread overview]
Message-ID: <02a5627b-7f03-2578-c853-aba58d327cfa@linux.intel.com> (raw)
In-Reply-To: <1628520820-28907-2-git-send-email-aravindhan.gunasekaran@intel.com>
On 8/9/2021 17:53, aravindhan.gunasekaran at intel.com wrote:
> From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
>
> Sets default values for each queue cycle start and cycle end.
> This allows some simplification in the handling of these
> configurations as most TSN features in i225 require a cycle
> to be configured.
>
> In i225, cycle start and end time is required to be programmed
> for CBS to work properly.
>
> Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
> Signed-off-by: Aravindhan Gunasekaran <aravindhan.gunasekaran@intel.com>
> Signed-off-by: Mallikarjuna Chilakala <mallikarjuna.chilakala@intel.com>
> ---
> drivers/net/ethernet/intel/igc/igc_main.c | 37 ++++++++++++++++++-------------
> drivers/net/ethernet/intel/igc/igc_tsn.c | 6 -----
> 2 files changed, 21 insertions(+), 22 deletions(-)
>
Tested-by: Dvora Fuxbrumer <dvorax.fuxbrumer@linux.intel.com>
next prev parent reply other threads:[~2021-08-18 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 14:53 [Intel-wired-lan] [PATCH next-queue v3 0/3] igc: Add support for CBS offload aravindhan.gunasekaran
2021-08-09 14:53 ` [Intel-wired-lan] [PATCH next-queue v3 1/3] igc: Use default cycle 'start' and 'end' values for queues aravindhan.gunasekaran
2021-08-18 21:09 ` Fuxbrumer, Dvora [this message]
2021-08-09 14:53 ` [Intel-wired-lan] [PATCH next-queue v3 2/3] igc: Simplify TSN flags handling aravindhan.gunasekaran
2021-08-18 21:10 ` Fuxbrumer, Dvora
2021-08-09 14:53 ` [Intel-wired-lan] [PATCH next-queue v3 3/3] igc: Add support for CBS offloading aravindhan.gunasekaran
2021-08-18 21:11 ` Fuxbrumer, Dvora
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=02a5627b-7f03-2578-c853-aba58d327cfa@linux.intel.com \
--to=dvorax.fuxbrumer@linux.intel.com \
--cc=intel-wired-lan@osuosl.org \
/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