From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <lars.povlsen@microchip.com>,
<Steen.Hegelund@microchip.com>, <daniel.machon@microchip.com>,
<richardcochran@gmail.com>, <UNGLinuxDriver@microchip.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [PATCH net-next 0/4] net: lan966x: Enable PTP on bridge interfaces
Date: Wed, 30 Nov 2022 15:35:21 +0100 [thread overview]
Message-ID: <20221130143525.934906-1-horatiu.vultur@microchip.com> (raw)
Before it was not allowed to run ptp on ports that are part of a bridge
because in case of transparent clock the HW will still forward the frames
so there would be duplicate frames.
Now that there is VCAP support, it is possible to add entries in the VCAP
to trap frames to the CPU and the CPU will forward these frames.
The first part of the patch series, extends the VCAP support to be able to
modify and get the rule, while the last patch uses the VCAP to trap the ptp
frames.
Horatiu Vultur (4):
net: microchip: vcap: Add vcap_get_rule
net: microchip: vcap: Add vcap_mod_rule
net: microchip: vcap: Add vcap_rule_get_key_u32
net: lan966x: Add ptp trap rules
.../ethernet/microchip/lan966x/lan966x_main.c | 19 +-
.../ethernet/microchip/lan966x/lan966x_main.h | 14 +
.../ethernet/microchip/lan966x/lan966x_ptp.c | 237 ++++-
.../microchip/lan966x/lan966x_tc_flower.c | 8 -
.../microchip/lan966x/lan966x_vcap_impl.c | 11 +-
.../net/ethernet/microchip/vcap/vcap_api.c | 824 ++++++++++++++++++
.../ethernet/microchip/vcap/vcap_api_client.h | 8 +
.../microchip/vcap/vcap_api_debugfs.c | 492 ++---------
.../microchip/vcap/vcap_api_private.h | 14 +
9 files changed, 1172 insertions(+), 455 deletions(-)
--
2.38.0
next reply other threads:[~2022-11-30 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 14:35 Horatiu Vultur [this message]
2022-11-30 14:35 ` [PATCH net-next 1/4] net: microchip: vcap: Add vcap_get_rule Horatiu Vultur
2022-11-30 14:35 ` [PATCH net-next 2/4] net: microchip: vcap: Add vcap_mod_rule Horatiu Vultur
2022-11-30 14:35 ` [PATCH net-next 3/4] net: microchip: vcap: Add vcap_rule_get_key_u32 Horatiu Vultur
2022-11-30 14:35 ` [PATCH net-next 4/4] net: lan966x: Add ptp trap rules Horatiu Vultur
2022-11-30 16:54 ` Vladimir Oltean
2022-12-01 9:53 ` 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=20221130143525.934906-1-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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