public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wojciech Drewek <wojciech.drewek@intel.com>
To: Geetha sowjanya <gakula@marvell.com>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: <kuba@kernel.org>, <davem@davemloft.net>, <pabeni@redhat.com>,
	<edumazet@google.com>, <sgoutham@marvell.com>,
	<sbhatta@marvell.com>, <hkelam@marvell.com>
Subject: Re: [net PATCH 5/5] octeontx2-af: Update Tx link register range
Date: Thu, 23 Nov 2023 11:57:56 +0100	[thread overview]
Message-ID: <bf6874cc-9604-408e-abee-8c26cf680b11@intel.com> (raw)
In-Reply-To: <20231123055941.19430-6-gakula@marvell.com>



On 23.11.2023 06:59, Geetha sowjanya wrote:
> On new silicons the TX channels for transmit level has increased.

Will it still work with older silicon?

> This patch fixes the respective register offset range to
> configure the newly added channels.
> 
> Fixes: b279bbb3314e ("octeontx2-af: NIX Tx scheduler queue config support")
> Signed-off-by: Rahul Bhansali <rbhansali@marvell.com>

What Rahul's signed-off stands for?

> Signed-off-by: Geetha sowjanya <gakula@marvell.com>
> ---
>  drivers/net/ethernet/marvell/octeontx2/af/rvu_reg.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/ethernet/marvell/octeontx2/af/rvu_reg.c b/drivers/net/ethernet/marvell/octeontx2/af/rvu_reg.c
> index b3150f053291..d46ac29adb96 100644
> --- a/drivers/net/ethernet/marvell/octeontx2/af/rvu_reg.c
> +++ b/drivers/net/ethernet/marvell/octeontx2/af/rvu_reg.c
> @@ -31,8 +31,8 @@ static struct hw_reg_map txsch_reg_map[NIX_TXSCH_LVL_CNT] = {
>  	{NIX_TXSCH_LVL_TL4, 3, 0xFFFF, {{0x0B00, 0x0B08}, {0x0B10, 0x0B18},
>  			      {0x1200, 0x12E0} } },
>  	{NIX_TXSCH_LVL_TL3, 4, 0xFFFF, {{0x1000, 0x10E0}, {0x1600, 0x1608},
> -			      {0x1610, 0x1618}, {0x1700, 0x17B0} } },
> -	{NIX_TXSCH_LVL_TL2, 2, 0xFFFF, {{0x0E00, 0x0EE0}, {0x1700, 0x17B0} } },
> +			      {0x1610, 0x1618}, {0x1700, 0x17C8} } },
> +	{NIX_TXSCH_LVL_TL2, 2, 0xFFFF, {{0x0E00, 0x0EE0}, {0x1700, 0x17C8} } },
>  	{NIX_TXSCH_LVL_TL1, 1, 0xFFFF, {{0x0C00, 0x0D98} } },
>  };
>  

  reply	other threads:[~2023-11-23 10:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23  5:59 [net PATCH 0/5] octeontx2-af: miscellaneous fixes Geetha sowjanya
2023-11-23  5:59 ` [net PATCH 1/5] octeontx2-af: Adjust Tx credits when MCS external bypass is disabled Geetha sowjanya
2023-11-23 10:45   ` Wojciech Drewek
2023-11-23 12:34     ` [EXT] " Geethasowjanya Akula
2023-11-23 12:47       ` Wojciech Drewek
2023-11-23  5:59 ` [net PATCH 2/5] octeontx2-af: Fix mcs sa cam entries size Geetha sowjanya
2023-11-23 10:47   ` Wojciech Drewek
2023-11-23  5:59 ` [net PATCH 3/5] octeontx2-af: Fix mcs stats register address Geetha sowjanya
2023-11-23 10:53   ` Wojciech Drewek
2023-11-23  5:59 ` [net PATCH 4/5] octeontx2-af: Add missing mcs flr handler call Geetha sowjanya
2023-11-23 10:55   ` Wojciech Drewek
2023-11-23  5:59 ` [net PATCH 5/5] octeontx2-af: Update Tx link register range Geetha sowjanya
2023-11-23 10:57   ` Wojciech Drewek [this message]
2023-11-23 12:45     ` [EXT] " Geethasowjanya Akula

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=bf6874cc-9604-408e-abee-8c26cf680b11@intel.com \
    --to=wojciech.drewek@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=hkelam@marvell.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sbhatta@marvell.com \
    --cc=sgoutham@marvell.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