From: Andrew Lunn <andrew@lunn.ch>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@savoirfairelinux.com,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH net-next 3/3] net: dsa: mv88e6xxx: make global2 code optional
Date: Fri, 2 Sep 2016 16:55:11 +0200 [thread overview]
Message-ID: <20160902145511.GH16864@lunn.ch> (raw)
In-Reply-To: <20160902120819.10773-4-vivien.didelot@savoirfairelinux.com>
On Fri, Sep 02, 2016 at 08:08:19AM -0400, Vivien Didelot wrote:
> Since not every chip has a Global2 set of registers, make its support
> optional, in which case the related functions will return -EOPNOTSUPP.
>
> This also allows to reduce the size of the mv88e6xxx driver for devices
> such as home routers embedding Ethernet chips without Global2 support.
Hi Vivien
I've no problems with splitting this out.
However, making it optional? I don't think that is a good idea.
1) If you don't have this, and you should, it looks like the PHYs stop
working, and since you cannot set the switch MAC address, maybe Pause
frames are broken.
2) Distros won't build a kernel per target hardware. They probably
build a kernel per SoC vendor. That means, they will have this
optional code built all the time. Very few builds will leave it out.
So the only way i think making this optional, is if it is a kernel
module, and it gets loaded if needed.
Andrew
next prev parent reply other threads:[~2016-09-02 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 12:08 [PATCH net-next 0/3] net: dsa: mv88e6xxx: isolate Global2 support Vivien Didelot
2016-09-02 12:08 ` [PATCH net-next 1/3] net: dsa: mv88e6xxx: fix module naming Vivien Didelot
2016-09-02 12:08 ` [PATCH net-next 2/3] net: dsa: mv88e6xxx: move Global2 code Vivien Didelot
2016-09-02 12:08 ` [PATCH net-next 3/3] net: dsa: mv88e6xxx: make global2 code optional Vivien Didelot
2016-09-02 14:55 ` Andrew Lunn [this message]
2016-09-02 15:22 ` Vivien Didelot
2016-09-02 16:11 ` Andrew Lunn
2016-09-02 17:13 ` Vivien Didelot
2016-09-02 17:19 ` Andrew Lunn
2016-09-02 17:32 ` Vivien Didelot
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=20160902145511.GH16864@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kernel@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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).