From: Andrew Lunn <andrew@lunn.ch>
To: Stefan Chulski <stefanc@marvell.com>
Cc: "kuba@kernel.org" <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
"davem@davemloft.net" <davem@davemloft.net>,
Nadav Haklai <nadavh@marvell.com>,
Yan Markman <ymarkman@marvell.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"mw@semihalf.com" <mw@semihalf.com>,
"rmk+kernel@armlinux.org.uk" <rmk+kernel@armlinux.org.uk>,
"atenart@kernel.org" <atenart@kernel.org>,
"rabeeh@solid-run.com" <rabeeh@solid-run.com>
Subject: Re: [EXT] Re: [V2 net-next] net: mvpp2: Add reserved port private flag configuration
Date: Thu, 18 Mar 2021 21:53:14 +0100 [thread overview]
Message-ID: <YFO9ug0gZp8viEHn@lunn.ch> (raw)
In-Reply-To: <CO6PR18MB38733E25F6B3194D4858147BB06B9@CO6PR18MB3873.namprd18.prod.outlook.com>
> 2. CM3 code has very small footprint requirement, we cannot
> implement the complete Serdes and PHY infrastructure that kernel
> provides as part of CM3 application. Therefore I would like to
> continue relying on kernel configuration for that.
How can that work? How does Linux know when CM3 has up'ed the
interface? How does CM3 know the status of the link? How does CM3 set
its flow control depending on what auto-neg determines, etc?
> 3. In some cases we need to dynamically switch the port "user"
> between CM3 and kernel. So I would like to preserve this
> functionality.
And how do you synchronize between Linux and CM3 so you know how is
using it and who cannot use it?
Andrew
next prev parent reply other threads:[~2021-03-18 20:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 16:43 [V2 net-next] net: mvpp2: Add reserved port private flag configuration stefanc
2021-03-11 16:59 ` Andrew Lunn
2021-03-16 15:28 ` [EXT] " Stefan Chulski
2021-03-16 15:41 ` Russell King - ARM Linux admin
2021-03-16 16:51 ` Stefan Chulski
2021-03-18 20:53 ` Andrew Lunn [this message]
2021-03-22 15:59 ` Stefan Chulski
2021-03-22 16:28 ` Andrew Lunn
2021-03-22 18:24 ` Stefan Chulski
2021-03-11 20:33 ` Jakub Kicinski
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=YFO9ug0gZp8viEHn@lunn.ch \
--to=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=rabeeh@solid-run.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=stefanc@marvell.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=ymarkman@marvell.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).