From: Andrew Lunn <andrew@lunn.ch>
To: Mickey Rachamim <mickeyr@marvell.com>
Cc: Vadym Kochan <vadym.kochan@plvision.eu>,
Jonathan McDowell <noodles@earth.li>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Jiri Pirko <jiri@mellanox.com>,
Ido Schimmel <idosch@mellanox.com>,
Oleksandr Mazur <oleksandr.mazur@plvision.eu>,
Serhiy Boiko <serhiy.boiko@plvision.eu>,
Serhiy Pshyk <serhiy.pshyk@plvision.eu>,
Volodymyr Mytnyk <volodymyr.mytnyk@plvision.eu>,
Taras Chornyi <taras.chornyi@plvision.eu>,
Andrii Savka <andrii.savka@plvision.eu>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [EXT] Re: [net-next v4 1/6] net: marvell: prestera: Add driver for Prestera family ASIC devices
Date: Sat, 22 Aug 2020 18:34:08 +0200 [thread overview]
Message-ID: <20200822163408.GG2347062@lunn.ch> (raw)
In-Reply-To: <BN6PR18MB1587EB225C6B80BF35A44EBFBA5A0@BN6PR18MB1587.namprd18.prod.outlook.com>
On Thu, Aug 20, 2020 at 10:00:21AM +0000, Mickey Rachamim wrote:
> > ASIC device specific handling is serviced by the firmware, current
> > driver's logic does not have PP specific code and relies on the FW
> > ABI which is PP-generic, and it looks like this how it should work
> > for boards with other ASICs, of course these boards should follow
> > the Marvell's Switchdev board design. >
>
> All Marvell Prestera (DX) devices are all based on CPSS SDK. This is one SDK
> and one build procedure that enables the Prestera driver to support all devices.
> This unified support enables us (and our customers) to have one SW
> implementation that will support variety of Prestera devices in same build/real-time
> execution.
> This approach also lead us with the implementation of the Prestera Switchdev drivers.
> As having detailed familiarity (20Y) with Marvell Prestera old/current/future devices -
> this approach will be kept strictly also on the future.
So if i understand this correctly, the compatibility is not to
Prestera, but to the firmware running on the Prestera? You want to
express a compatibility to the ABI this firmware supports for the
switchdev driver to use?
Andrew
next prev parent reply other threads:[~2020-08-22 16:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 12:22 [net-next v4 0/6] net: marvell: prestera: Add Switchdev driver for Prestera family ASIC device 98DX326x (AC3x) Vadym Kochan
2020-07-27 12:22 ` [net-next v4 1/6] net: marvell: prestera: Add driver for Prestera family ASIC devices Vadym Kochan
2020-07-27 12:59 ` Andy Shevchenko
2020-07-31 15:22 ` Vadym Kochan
2020-07-31 16:02 ` Andy Shevchenko
2020-07-31 20:55 ` Vadym Kochan
2020-07-27 19:32 ` David Miller
2020-08-13 8:03 ` Jonathan McDowell
2020-08-14 8:20 ` Vadym Kochan
2020-08-14 12:05 ` Jonathan McDowell
2020-08-14 12:27 ` Vadym Kochan
2020-08-14 13:18 ` Andrew Lunn
2020-08-20 8:31 ` Vadym Kochan
2020-08-20 10:00 ` [EXT] " Mickey Rachamim
2020-08-22 16:34 ` Andrew Lunn [this message]
2020-08-25 11:36 ` Vadym Kochan
2020-07-27 12:22 ` [net-next v4 2/6] net: marvell: prestera: Add PCI interface support Vadym Kochan
2020-07-27 12:32 ` Jiri Pirko
2020-07-27 12:35 ` Vadym Kochan
2020-07-27 13:02 ` Jiri Pirko
2020-07-27 13:29 ` Andy Shevchenko
2020-07-27 14:11 ` Jiri Pirko
2020-07-27 15:33 ` Andy Shevchenko
2020-07-27 12:22 ` [net-next v4 3/6] net: marvell: prestera: Add basic devlink support Vadym Kochan
2020-07-27 13:07 ` Andy Shevchenko
2020-07-28 12:30 ` Vadym Kochan
2020-07-28 13:24 ` Andy Shevchenko
2020-07-27 12:22 ` [net-next v4 4/6] net: marvell: prestera: Add ethtool interface support Vadym Kochan
2020-07-27 13:17 ` Andy Shevchenko
2020-07-27 12:22 ` [net-next v4 5/6] net: marvell: prestera: Add Switchdev driver implementation Vadym Kochan
2020-07-27 12:22 ` [net-next v4 6/6] dt-bindings: marvell,prestera: Add description for device-tree bindings Vadym Kochan
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=20200822163408.GG2347062@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrii.savka@plvision.eu \
--cc=andy.shevchenko@gmail.com \
--cc=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mickeyr@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=noodles@earth.li \
--cc=oleksandr.mazur@plvision.eu \
--cc=serhiy.boiko@plvision.eu \
--cc=serhiy.pshyk@plvision.eu \
--cc=taras.chornyi@plvision.eu \
--cc=vadym.kochan@plvision.eu \
--cc=volodymyr.mytnyk@plvision.eu \
/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