All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Wojtas <mw@semihalf.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
	Mark Rutland <mark.rutland@arm.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Michael Turquette <mturquette@baylibre.com>,
	Laxman Dewangan <ldewangan@nvidia.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Juri Lelli <juri.lelli@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	Thierry Reding <treding@nvidia.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Jason Cooper <jason@lakedaemon.net>,
	Arnd Bergmann <arnd@arndb.de>,
	Kalyan Kinthada <Kalyan.Kinthada@alliedtelesis.co.nz>,
	Rob Herring <robh+dt@kernel.org>, Gregory Clement <gre>
Subject: Re: [PATCHv2 0/5] Support for Marvell switches with integrated CPUs
Date: Thu, 5 Jan 2017 15:07:02 +0100	[thread overview]
Message-ID: <CAPv3WKdsiGis6gG0SmLT1mg+LYA8i5p4u9KJiYJxng8jrLsj+w@mail.gmail.com> (raw)
In-Reply-To: <20170105130945.GA18033@lunn.ch>

Hi Andrew,

2017-01-05 14:09 GMT+01:00 Andrew Lunn <andrew@lunn.ch>:
>> I'd love to see a switchdev driver but it's a huge task (and no I'm not
>> committing to writing it). As it stands Marvell ship a switch SDK
>> largely executes in userspace with a small kernel module providing some
>> linkage to the underlying hardware.
>
> Is there any similarity to the mv88e6xxx family?

Prestera switches (they are sold as standalone devices and with
integrated CPU's, like ones submitted) are as far from mv88e6xxx as
possible. There are various mix of 1/2.5/10/40G ports, depending on
model.

>
> If it was similar registers, just a different access mechanising, we
> could probably extend the mv88e6xxx to support MMIO as well as MDIO.
>

The difference is huge, nothing existing in the mainline can fit. The
driver, that exposes resources to the userspace SDK (called CPSS, it's
huge and complex piece of code) is existing in Marvell internal
branches (kernel v4.4 is the latest one), but I doubt such solution
(despite it's really small) is upstreamable. I believe it can be
shipped to the customers along with the SDK as a kernel module. Having
the CPU's support in the mainline is IMO sufficient.

Best regards,
Marcin

WARNING: multiple messages have this Message-ID (diff)
From: Marcin Wojtas <mw@semihalf.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
	Mark Rutland <mark.rutland@arm.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Michael Turquette <mturquette@baylibre.com>,
	Laxman Dewangan <ldewangan@nvidia.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Juri Lelli <juri.lelli@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	Thierry Reding <treding@nvidia.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Jason Cooper <jason@lakedaemon.net>,
	Arnd Bergmann <arnd@arndb.de>,
	Kalyan Kinthada <Kalyan.Kinthada@alliedtelesis.co.nz>,
	Rob Herring <robh+dt@kernel.org>,
	Gregory Clement <gregory.clement@free-electrons.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCHv2 0/5] Support for Marvell switches with integrated CPUs
Date: Thu, 5 Jan 2017 15:07:02 +0100	[thread overview]
Message-ID: <CAPv3WKdsiGis6gG0SmLT1mg+LYA8i5p4u9KJiYJxng8jrLsj+w@mail.gmail.com> (raw)
In-Reply-To: <20170105130945.GA18033@lunn.ch>

Hi Andrew,

2017-01-05 14:09 GMT+01:00 Andrew Lunn <andrew@lunn.ch>:
>> I'd love to see a switchdev driver but it's a huge task (and no I'm not
>> committing to writing it). As it stands Marvell ship a switch SDK
>> largely executes in userspace with a small kernel module providing some
>> linkage to the underlying hardware.
>
> Is there any similarity to the mv88e6xxx family?

Prestera switches (they are sold as standalone devices and with
integrated CPU's, like ones submitted) are as far from mv88e6xxx as
possible. There are various mix of 1/2.5/10/40G ports, depending on
model.

>
> If it was similar registers, just a different access mechanising, we
> could probably extend the mv88e6xxx to support MMIO as well as MDIO.
>

The difference is huge, nothing existing in the mainline can fit. The
driver, that exposes resources to the userspace SDK (called CPSS, it's
huge and complex piece of code) is existing in Marvell internal
branches (kernel v4.4 is the latest one), but I doubt such solution
(despite it's really small) is upstreamable. I believe it can be
shipped to the customers along with the SDK as a kernel module. Having
the CPU's support in the mainline is IMO sufficient.

Best regards,
Marcin

WARNING: multiple messages have this Message-ID (diff)
From: Marcin Wojtas <mw@semihalf.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
	Mark Rutland <mark.rutland@arm.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Michael Turquette <mturquette@baylibre.com>,
	Laxman Dewangan <ldewangan@nvidia.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Juri Lelli <juri.lelli@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	Thierry Reding <treding@nvidia.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Jason Cooper <jason@lakedaemon.net>,
	Arnd Bergmann <arnd@arndb.de>,
	Kalyan Kinthada <Kalyan.Kinthada@alliedtelesis.co.nz>,
	Rob Herring <robh+dt@kernel.org>,
	Gregory Clement <gregory.clement@free-electrons.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCHv2 0/5] Support for Marvell switches with integrated CPUs
Date: Thu, 5 Jan 2017 15:07:02 +0100	[thread overview]
Message-ID: <CAPv3WKdsiGis6gG0SmLT1mg+LYA8i5p4u9KJiYJxng8jrLsj+w@mail.gmail.com> (raw)
In-Reply-To: <20170105130945.GA18033@lunn.ch>

Hi Andrew,

2017-01-05 14:09 GMT+01:00 Andrew Lunn <andrew@lunn.ch>:
>> I'd love to see a switchdev driver but it's a huge task (and no I'm not
>> committing to writing it). As it stands Marvell ship a switch SDK
>> largely executes in userspace with a small kernel module providing some
>> linkage to the underlying hardware.
>
> Is there any similarity to the mv88e6xxx family?

Prestera switches (they are sold as standalone devices and with
integrated CPU's, like ones submitted) are as far from mv88e6xxx as
possible. There are various mix of 1/2.5/10/40G ports, depending on
model.

>
> If it was similar registers, just a different access mechanising, we
> could probably extend the mv88e6xxx to support MMIO as well as MDIO.
>

The difference is huge, nothing existing in the mainline can fit. The
driver, that exposes resources to the userspace SDK (called CPSS, it's
huge and complex piece of code) is existing in Marvell internal
branches (kernel v4.4 is the latest one), but I doubt such solution
(despite it's really small) is upstreamable. I believe it can be
shipped to the customers along with the SDK as a kernel module. Having
the CPU's support in the mainline is IMO sufficient.

Best regards,
Marcin

WARNING: multiple messages have this Message-ID (diff)
From: mw@semihalf.com (Marcin Wojtas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/5] Support for Marvell switches with integrated CPUs
Date: Thu, 5 Jan 2017 15:07:02 +0100	[thread overview]
Message-ID: <CAPv3WKdsiGis6gG0SmLT1mg+LYA8i5p4u9KJiYJxng8jrLsj+w@mail.gmail.com> (raw)
In-Reply-To: <20170105130945.GA18033@lunn.ch>

Hi Andrew,

2017-01-05 14:09 GMT+01:00 Andrew Lunn <andrew@lunn.ch>:
>> I'd love to see a switchdev driver but it's a huge task (and no I'm not
>> committing to writing it). As it stands Marvell ship a switch SDK
>> largely executes in userspace with a small kernel module providing some
>> linkage to the underlying hardware.
>
> Is there any similarity to the mv88e6xxx family?

Prestera switches (they are sold as standalone devices and with
integrated CPU's, like ones submitted) are as far from mv88e6xxx as
possible. There are various mix of 1/2.5/10/40G ports, depending on
model.

>
> If it was similar registers, just a different access mechanising, we
> could probably extend the mv88e6xxx to support MMIO as well as MDIO.
>

The difference is huge, nothing existing in the mainline can fit. The
driver, that exposes resources to the userspace SDK (called CPSS, it's
huge and complex piece of code) is existing in Marvell internal
branches (kernel v4.4 is the latest one), but I doubt such solution
(despite it's really small) is upstreamable. I believe it can be
shipped to the customers along with the SDK as a kernel module. Having
the CPU's support in the mainline is IMO sufficient.

Best regards,
Marcin

  reply	other threads:[~2017-01-05 14:07 UTC|newest]

Thread overview: 135+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05  3:36 [PATCHv2 0/5] Support for Marvell switches with integrated CPUs Chris Packham
2017-01-05  3:36 ` Chris Packham
2017-01-05  3:36 ` Chris Packham
2017-01-05  3:36 ` [PATCHv2 1/5] clk: mvebu: support for 98DX3236 SoC Chris Packham
2017-01-05  3:36   ` Chris Packham
2017-01-05  3:36   ` Chris Packham
2017-01-05 13:53   ` Mark Rutland
2017-01-05 13:53     ` Mark Rutland
2017-01-05 13:53     ` Mark Rutland
2017-01-05 23:05     ` Chris Packham
2017-01-05 23:05       ` Chris Packham
2017-01-05 23:05       ` Chris Packham
2017-01-05 23:05       ` Chris Packham
2017-01-05  3:36 ` [PATCHv2 2/5] arm: mvebu: support for SMP on 98DX3336 SoC Chris Packham
2017-01-05  3:36   ` Chris Packham
2017-01-05  3:36   ` Chris Packham
2017-01-05  4:04   ` Florian Fainelli
2017-01-05  4:04     ` Florian Fainelli
2017-01-05  4:04     ` Florian Fainelli
2017-01-05  4:46     ` Chris Packham
2017-01-05  4:46       ` Chris Packham
2017-01-05  4:46       ` Chris Packham
2017-01-05 20:49       ` Chris Packham
2017-01-05 20:49         ` Chris Packham
2017-01-05 20:49         ` Chris Packham
2017-01-05  3:36 ` [PATCHv2 3/5] pinctrl: mvebu: pinctrl driver for 98DX3236 SoC Chris Packham
2017-01-05  3:36   ` Chris Packham
2017-01-05  3:36 ` [PATCHv2 4/5] arm: mvebu: Add device tree for 98DX3236 SoCs Chris Packham
2017-01-05  3:36   ` Chris Packham
2017-01-05  3:36   ` Chris Packham
2017-01-05  4:06   ` Florian Fainelli
2017-01-05  4:06     ` Florian Fainelli
2017-01-05  4:06     ` Florian Fainelli
2017-01-05  4:34     ` Chris Packham
2017-01-05  4:34       ` Chris Packham
2017-01-05  4:34       ` Chris Packham
2017-01-05 13:58   ` Mark Rutland
2017-01-05 13:58     ` Mark Rutland
2017-01-05 13:58     ` Mark Rutland
2017-01-05 20:10     ` Chris Packham
2017-01-05 20:10       ` Chris Packham
2017-01-05 20:10       ` Chris Packham
2017-01-05  3:36 ` [PATCHv2 5/5] arm: mvebu: Add device tree for db-dxbc2 and db-xc3-24g4xg boards Chris Packham
2017-01-05  3:36   ` Chris Packham
2017-01-05  3:36   ` Chris Packham
2017-01-05  4:07 ` [PATCHv2 0/5] Support for Marvell switches with integrated CPUs Florian Fainelli
2017-01-05  4:07   ` Florian Fainelli
2017-01-05  4:07   ` Florian Fainelli
2017-01-05  4:24   ` Chris Packham
2017-01-05  4:24     ` Chris Packham
2017-01-05  4:24     ` Chris Packham
2017-01-05  4:24     ` Chris Packham
2017-01-05 13:09     ` Andrew Lunn
2017-01-05 13:09       ` Andrew Lunn
2017-01-05 13:09       ` Andrew Lunn
2017-01-05 13:09       ` Andrew Lunn
2017-01-05 14:07       ` Marcin Wojtas [this message]
2017-01-05 14:07         ` Marcin Wojtas
2017-01-05 14:07         ` Marcin Wojtas
2017-01-05 14:07         ` Marcin Wojtas
2017-01-05 19:46       ` Chris Packham
2017-01-05 19:46         ` Chris Packham
2017-01-05 19:46         ` Chris Packham
2017-01-05 19:46         ` Chris Packham
2017-01-05 19:52         ` Florian Fainelli
2017-01-05 19:52           ` Florian Fainelli
2017-01-05 19:52           ` Florian Fainelli
2017-01-05 19:52           ` Florian Fainelli
2017-01-05 14:09 ` Marcin Wojtas
2017-01-05 14:09   ` Marcin Wojtas
2017-01-05 14:09   ` Marcin Wojtas
2017-01-05 14:09   ` Marcin Wojtas
2017-01-05 20:02   ` Chris Packham
2017-01-05 20:02     ` Chris Packham
2017-01-05 20:02     ` Chris Packham
2017-01-05 20:02     ` Chris Packham
2017-01-06  4:14 ` Chris Packham
2017-01-06  4:14   ` Chris Packham
2017-01-06  4:14   ` Chris Packham
2017-01-06  4:14   ` Chris Packham
2017-01-06  4:14   ` [PATCHv3 1/5] clk: mvebu: support for 98DX3236 SoC Chris Packham
2017-01-06  4:14     ` Chris Packham
2017-01-06  4:14     ` Chris Packham
2017-01-09 18:39     ` Rob Herring
2017-01-09 18:39       ` Rob Herring
2017-01-06  4:14   ` [PATCHv3 2/5] arm: mvebu: support for SMP on 98DX3336 SoC Chris Packham
2017-01-06  4:14     ` Chris Packham
2017-01-06  4:14     ` Chris Packham
2017-01-06  6:36     ` Stephen Boyd
2017-01-06  6:36       ` Stephen Boyd
2017-01-06  6:36       ` Stephen Boyd
2017-01-06  8:41       ` Chris Packham
2017-01-06  8:41         ` Chris Packham
2017-01-06  8:41         ` Chris Packham
2017-01-09 18:40     ` Rob Herring
2017-01-09 18:40       ` Rob Herring
2017-01-09 18:40       ` Rob Herring
2017-01-06  4:15   ` [PATCHv3 3/5] pinctrl: mvebu: pinctrl driver for 98DX3236 SoC Chris Packham
2017-01-06  4:15     ` Chris Packham
2017-01-06  4:15     ` Chris Packham
     [not found]     ` <20170106041517.9589-4-chris.packham-6g8wRflRTwXFdCa3tKVlE6U/zSkkHjvu@public.gmane.org>
2017-01-09 18:41       ` Rob Herring
2017-01-09 18:41         ` Rob Herring
2017-01-09 18:41         ` Rob Herring
2017-01-11 14:44     ` Linus Walleij
2017-01-11 14:44       ` Linus Walleij
2017-01-11 14:44       ` Linus Walleij
2017-01-11 20:55       ` Sebastian Hesselbarth
2017-01-11 20:55         ` Sebastian Hesselbarth
2017-01-11 20:55         ` Sebastian Hesselbarth
2017-01-12  9:13         ` Chris Packham
2017-01-12  9:13           ` Chris Packham
2017-01-12  9:13           ` Chris Packham
2017-01-06  4:15   ` [PATCHv3 4/5] arm: mvebu: Add device tree for 98DX3236 SoCs Chris Packham
2017-01-06  4:15     ` Chris Packham
2017-01-06  4:15     ` Chris Packham
2017-01-09 18:44     ` Rob Herring
2017-01-09 18:44       ` Rob Herring
2017-01-26 15:09     ` Gregory CLEMENT
2017-01-26 15:09       ` Gregory CLEMENT
2017-01-26 15:09       ` Gregory CLEMENT
2017-01-26 20:07       ` Chris Packham
2017-01-26 20:07         ` Chris Packham
2017-01-26 20:07         ` Chris Packham
2017-01-26 20:24       ` Chris Packham
2017-01-26 20:24         ` Chris Packham
2017-01-26 20:24         ` Chris Packham
2017-01-26 22:52         ` Chris Packham
2017-01-26 22:52           ` Chris Packham
2017-01-26 22:52           ` Chris Packham
2017-01-06  4:15   ` [PATCHv3 5/5] arm: mvebu: Add device tree for db-dxbc2 and db-xc3-24g4xg boards Chris Packham
2017-01-06  4:15     ` Chris Packham
2017-01-06  4:15     ` Chris Packham
2017-01-26 15:12     ` Gregory CLEMENT
2017-01-26 15:12       ` Gregory CLEMENT
2017-01-26 15:12       ` Gregory CLEMENT

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=CAPv3WKdsiGis6gG0SmLT1mg+LYA8i5p4u9KJiYJxng8jrLsj+w@mail.gmail.com \
    --to=mw@semihalf.com \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=Kalyan.Kinthada@alliedtelesis.co.nz \
    --cc=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=jason@lakedaemon.net \
    --cc=juri.lelli@arm.com \
    --cc=ldewangan@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=treding@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.