Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
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>,
        <UNGLinuxDriver@microchip.com>,
        Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [PATCH net-next 0/3] net: lan966x: Add support for ES0 VCAP
Date:   Tue, 9 May 2023 09:26:42 +0200
Message-ID: <20230509072645.3245949-1-horatiu.vultur@microchip.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain
Precedence: bulk

Provide the Egress Stage 0 (ES0) VCAP (Versatile Content-Aware
Processor) support for the lan966x platform.

The ES0 VCAP has only 1 lookup which is accessible with a TC chain
id 10000000.

Currently only one action is support which is vlan pop. Also it is
possible to link the IS1 to ES0 using 'goto chain 10000000'.

Horatiu Vultur (3):
  net: lan966x: Add ES0 VCAP model
  net: lan966x: Add ES0 VCAP keyset configuration for lan966x
  net: lan966x: Add TC support for ES0 VCAP

 .../ethernet/microchip/lan966x/lan966x_main.h |   3 +
 .../ethernet/microchip/lan966x/lan966x_regs.h |  15 +
 .../microchip/lan966x/lan966x_tc_flower.c     |  61 ++++
 .../microchip/lan966x/lan966x_vcap_ag_api.c   | 264 +++++++++++++++++-
 .../microchip/lan966x/lan966x_vcap_debugfs.c  |  23 ++
 .../microchip/lan966x/lan966x_vcap_impl.c     |  82 ++++++
 .../net/ethernet/microchip/vcap/vcap_ag_api.h |  67 +++--
 7 files changed, 485 insertions(+), 30 deletions(-)

-- 
2.38.0