From: Florian Fainelli <f.fainelli@gmail.com>
To: Jie Deng <Jie.Deng1@synopsys.com>,
Joao Pinto <Joao.Pinto@synopsys.com>,
davem@davemloft.net
Cc: lars.persson@axis.com, niklass@axis.com, peppe.cavallaro@st.com,
alexandre.torgue@st.com, netdev@vger.kernel.org,
CARLOS.PALMINHA@synopsys.com
Subject: Re: [PATCH v2 2/2] stmmac: rename it to synopsys
Date: Wed, 11 Jan 2017 21:05:10 -0800 [thread overview]
Message-ID: <43126ae9-dc03-a323-2376-b6d72ad5ebc5@gmail.com> (raw)
In-Reply-To: <03c4bef3-de38-0e51-e20d-2c9fc4bb6f8d@synopsys.com>
On 01/11/2017 07:44 PM, Jie Deng wrote:
> Hi Joao,
>
> On 2017/1/11 18:35, Joao Pinto wrote:
>> Hi Jie,
>>
>> Às 4:00 AM de 1/11/2017, Jie Deng escreveu:
>>> Hi Joao,
>>>
>>>
>>> On 2017/1/10 22:52, Joao Pinto wrote:
>>>> This patch renames stmicro/stmmac to synopsys/ since it is a standard
>>>> ethernet software package regarding synopsys ethernet controllers, supporting
>>>> the majority of Synopsys Ethernet IPs. The config IDs remain the same, for
>>>> retro-compatibility, only the description was changed.
>>>>
>>>> Signed-off-by: Joao Pinto <jpinto@synopsys.com>
>>>> ---
>>>> changes v1->v2:
>>>> - nothing changed. Just to keep up with patch set version
>>>>
>>>> @@ -1,5 +1,5 @@
>>>> config STMMAC_ETH
>>>> - tristate "STMicroelectronics 10/100/1000 Ethernet driver"
>>>> + tristate "Synopsys Ethernet drivers"
>>>> depends on HAS_IOMEM && HAS_DMA
>>>> select MII
>>>> select PHYLIB
>>>> @@ -14,7 +14,7 @@ config STMMAC_ETH
>>>> if STMMAC_ETH
>>>>
>>> "Synopsys Ethernet drivers" is too generic. The name should reflect the
>>> controller. This driver is for Synopsys GMAC 10M/100M/1G IPs. We will submit a
>>> driver for the new 25G/40G/50G/100G XLGMAC IP in the future.
>> As you know Synopsys is an IP vendor that as a wide range of IPs related to
>> Ethernet. stmmac is a driver that was well built and well maintained and
>> supports most of those Ethernet IPs, so it has the potential to be the official
>> Synopsys Ethernet driver suite in the future.
>>
>> Let's make baby steps. For now stmmac supports 10M/100M/1G and also QoS which is
>> a separated IP and the different IP cores are selected by device tree.
>>
>> In the future it would be usefull to be selectable by Kconfig options, making it
>> more clear to the kernel user. For example:
>>
>> Synopsys Ethernet drivers
>> eQoS Core
>> 10M Core
>> 100M Core
>> 1G Core
>> 25G Core
>> ....
>>
>> The XLGMAC will be great for our users and I will be 100% available to help you
>> with it.
>>
>> Thanks,
>> Joao
>>
> Currently, Synopsys has three series IPs cores. They are
> 1. 10M/100M/1G (GMAC, QoS)
> 2. 1G/2.5G/5G/10G (XGMAC)
> 3. 10G/25G/40G/50G/100G (XLGMAC)
> More info: https://www.synopsys.com/designware-ip/interface-ip/ethernet.html
>
> You have successfully merged dwc_eth_qos.c into stmmac. stmmac now fully
> supports the 10M/100M/1G series IPs. Personally, I do support Florian's
> suggestion not to rename stmmac.
> considering to avoid future confusion and make easy maintenance, Following is
> my suggestions
> 1. not to do any rename
> 2. keep all 10M/100M/1G IPs (GMAC, QoS) development in stmmac.
> 3. keep all 1G/2.5G/5G/10G IP (XGMAC) development in amd-xgbe.
> 4. submit a new driver under synopsys/ for the new 10G/25G/40G/50G/100G
> (XLGMAC) IP.
>
> Welcome opinions from others.
Seems like a reasonable plan to me. If it helps avoid confusion, you
could always add an entry under Documentation/networking/ which
describes the history of the various drivers, and the reasons why they
are not consolidated under a synopsys directory.
Cheers
--
Florian
next prev parent reply other threads:[~2017-01-12 5:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 14:52 [PATCH v2 0/2] remove dwc_eth_qos and rename stmicro/stmmac Joao Pinto
2017-01-10 14:52 ` [PATCH v2 1/2] synopsys: remove dwc_eth_qos driver Joao Pinto
2017-01-10 15:15 ` Lars Persson
2017-01-10 14:52 ` [PATCH v2 2/2] stmmac: rename it to synopsys Joao Pinto
2017-01-11 4:00 ` Jie Deng
2017-01-11 10:35 ` Joao Pinto
2017-01-12 3:44 ` Jie Deng
2017-01-12 5:05 ` Florian Fainelli [this message]
2017-01-11 10:00 ` kbuild test robot
2017-01-11 21:14 ` Florian Fainelli
2017-01-11 21:32 ` David Miller
2017-01-12 9:43 ` Joao Pinto
2017-01-12 10:11 ` Alexandre Torgue
2017-01-12 11:09 ` Joao Pinto
2017-01-12 15:26 ` David Miller
2017-01-12 15:39 ` Joao Pinto
2017-01-12 15:45 ` David Miller
2017-01-12 16:04 ` Joao Pinto
2017-01-12 19:42 ` Florian Fainelli
2017-01-13 11:20 ` Joao Pinto
2017-01-11 11:39 ` [PATCH v2 0/2] remove dwc_eth_qos and rename stmicro/stmmac Alexandre Torgue
2017-01-11 11:54 ` Joao Pinto
2017-01-11 14:25 ` Alexandre Torgue
2017-01-11 14:29 ` Joao Pinto
2017-01-11 14:39 ` Alexandre Torgue
2017-01-11 14:54 ` Joao Pinto
2017-01-11 14:52 ` David Miller
2017-01-11 15:06 ` Joao Pinto
2017-01-11 15:20 ` David Miller
2017-01-11 16:17 ` Joao Pinto
2017-01-11 16:19 ` Joao Pinto
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=43126ae9-dc03-a323-2376-b6d72ad5ebc5@gmail.com \
--to=f.fainelli@gmail.com \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=Jie.Deng1@synopsys.com \
--cc=Joao.Pinto@synopsys.com \
--cc=alexandre.torgue@st.com \
--cc=davem@davemloft.net \
--cc=lars.persson@axis.com \
--cc=netdev@vger.kernel.org \
--cc=niklass@axis.com \
--cc=peppe.cavallaro@st.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).