From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <UNGLinuxDriver@microchip.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [PATCH net 0/3] net: lan966x: Fixes for when MTU is changed
Date: Sun, 23 Oct 2022 20:48:35 +0200 [thread overview]
Message-ID: <20221023184838.4128061-1-horatiu.vultur@microchip.com> (raw)
There were multiple problems in different parts of the driver when
the MTU was changed.
The first problem was that the HW was missing to configure the correct
value, it was missing ETH_HLEN and ETH_FCS_LEN. The second problem was
when vlan filtering was enabled/disabled, the MRU was not adjusted
corretly. While the last issue was that the FDMA was calculated wrongly
the correct maximum MTU.
Horatiu Vultur (3):
net: lan966x: Fix the MTU calculation
net: lan966x: Adjust maximum frame size when vlan is enabled/disabled
net: lan966x: Fix FDMA when MTU is changed
.../net/ethernet/microchip/lan966x/lan966x_fdma.c | 7 +++++--
.../net/ethernet/microchip/lan966x/lan966x_main.c | 4 ++--
.../net/ethernet/microchip/lan966x/lan966x_main.h | 2 ++
.../net/ethernet/microchip/lan966x/lan966x_regs.h | 15 +++++++++++++++
.../net/ethernet/microchip/lan966x/lan966x_vlan.c | 6 ++++++
5 files changed, 30 insertions(+), 4 deletions(-)
--
2.38.0
next reply other threads:[~2022-10-23 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 18:48 Horatiu Vultur [this message]
2022-10-23 18:48 ` [PATCH net 1/3] net: lan966x: Fix the MTU calculation Horatiu Vultur
2022-10-23 18:48 ` [PATCH net 2/3] net: lan966x: Adjust maximum frame size when vlan is enabled/disabled Horatiu Vultur
2022-10-23 18:48 ` [PATCH net 3/3] net: lan966x: Fix FDMA when MTU is changed Horatiu Vultur
2022-10-26 2:34 ` Jakub Kicinski
2022-10-26 18:35 ` Horatiu Vultur
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=20221023184838.4128061-1-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).