From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935671AbcKWLGK (ORCPT ); Wed, 23 Nov 2016 06:06:10 -0500 Received: from mx07-00178001.pphosted.com ([62.209.51.94]:20513 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934841AbcKWLGI (ORCPT ); Wed, 23 Nov 2016 06:06:08 -0500 Subject: Re: Synopsys Ethernet QoS Driver To: Joao Pinto , Lars Persson References: <1dbb6047-2bbb-4d56-2a62-ab65a0254844@synopsys.com> <20161119135654.GA14079@lnxartpec.se.axis.com> <1248f4ce-4859-10e6-fef9-342ea543f8d4@synopsys.com> <87c8a24b-0812-7850-cb3f-7be691bab432@st.com> <7c7798b5-8cd4-ba99-f526-22d3e06e05db@synopsys.com> <2eefdb8f-7e87-6009-6e50-c536d4b95dd6@synopsys.com> CC: Rayagond Kokatanur , Rabin Vincent , mued dib , David Miller , Jeff Kirsher , "jiri@mellanox.com" , "saeedm@mellanox.com" , "idosch@mellanox.com" , netdev , "linux-kernel@vger.kernel.org" , "CARLOS.PALMINHA@synopsys.com" , =?UTF-8?Q?Andreas_Irest=c3=a5l?= , "alexandre.torgue@st.com" , "linux-arm-kernel@lists.infradead.org" From: Giuseppe CAVALLARO Message-ID: Date: Wed, 23 Nov 2016 11:59:57 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <2eefdb8f-7e87-6009-6e50-c536d4b95dd6@synopsys.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.52.139.54] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-11-23_01:,, signatures=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Joao, Lars. On 11/22/2016 3:16 PM, Joao Pinto wrote: >> Ok, it makes sense. >> > Just for curiosity the target setup is the following: >> > https://www.youtube.com/watch?v=8V-LB5y2Cos >> > but instead of using internal drivers, we desire to use mainline drivers only. >> > >> > Thanks! > Regarding this subject, I am thinking of making the following adaption: > > a) delete ethernet/synopsys > b) rename ethernet/stmicro/stmmac to ethernet/synopsys > > and send you a patch for you to evaluate. Both agree with the approach? > To have a new work base would be important, because I will add to the "new" > structure some missing QoS features like Multichannel support, CBS and later TSN. IMO, we have to agree on a common strategy making the change for net-next; I imaged the following steps: - to port missing feature or fixes from ethernet/synopsys inside the stmmac taking care about the documentation too. - remove ethernet/synopsys - rename ethernet/stmicro/stmmac to ethernet/synopsys These latest two have some relevant impacts. This change should be propagated to all the platforms that are using: CONFIG_SYNOPSYS_DWC_ETH_QOS and CONFIG_STMMAC_ETH plus device-tree compatibility. - enhance the stmmac with new features and new glue (part of these can be anticipated for sure). what do you think? does it make sense? If yes, we can also understand how/who starts. Regards, Peppe > Thanks. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Giuseppe CAVALLARO Subject: Re: Synopsys Ethernet QoS Driver Date: Wed, 23 Nov 2016 11:59:57 +0100 Message-ID: References: <1dbb6047-2bbb-4d56-2a62-ab65a0254844@synopsys.com> <20161119135654.GA14079@lnxartpec.se.axis.com> <1248f4ce-4859-10e6-fef9-342ea543f8d4@synopsys.com> <87c8a24b-0812-7850-cb3f-7be691bab432@st.com> <7c7798b5-8cd4-ba99-f526-22d3e06e05db@synopsys.com> <2eefdb8f-7e87-6009-6e50-c536d4b95dd6@synopsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Cc: "idosch@mellanox.com" , "alexandre.torgue@st.com" , "saeedm@mellanox.com" , netdev , "linux-kernel@vger.kernel.org" , "CARLOS.PALMINHA@synopsys.com" , Rabin Vincent , mued dib , "jiri@mellanox.com" , Rayagond Kokatanur , Jeff Kirsher , =?UTF-8?Q?Andreas_Irest=c3=a5l?= , David Miller , "linux-arm-kernel@lists.infradead.org" To: Joao Pinto , Lars Persson Return-path: In-Reply-To: <2eefdb8f-7e87-6009-6e50-c536d4b95dd6@synopsys.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org List-Id: netdev.vger.kernel.org Hello Joao, Lars. On 11/22/2016 3:16 PM, Joao Pinto wrote: >> Ok, it makes sense. >> > Just for curiosity the target setup is the following: >> > https://www.youtube.com/watch?v=8V-LB5y2Cos >> > but instead of using internal drivers, we desire to use mainline drivers only. >> > >> > Thanks! > Regarding this subject, I am thinking of making the following adaption: > > a) delete ethernet/synopsys > b) rename ethernet/stmicro/stmmac to ethernet/synopsys > > and send you a patch for you to evaluate. Both agree with the approach? > To have a new work base would be important, because I will add to the "new" > structure some missing QoS features like Multichannel support, CBS and later TSN. IMO, we have to agree on a common strategy making the change for net-next; I imaged the following steps: - to port missing feature or fixes from ethernet/synopsys inside the stmmac taking care about the documentation too. - remove ethernet/synopsys - rename ethernet/stmicro/stmmac to ethernet/synopsys These latest two have some relevant impacts. This change should be propagated to all the platforms that are using: CONFIG_SYNOPSYS_DWC_ETH_QOS and CONFIG_STMMAC_ETH plus device-tree compatibility. - enhance the stmmac with new features and new glue (part of these can be anticipated for sure). what do you think? does it make sense? If yes, we can also understand how/who starts. Regards, Peppe > Thanks. From mboxrd@z Thu Jan 1 00:00:00 1970 From: peppe.cavallaro@st.com (Giuseppe CAVALLARO) Date: Wed, 23 Nov 2016 11:59:57 +0100 Subject: Synopsys Ethernet QoS Driver In-Reply-To: <2eefdb8f-7e87-6009-6e50-c536d4b95dd6@synopsys.com> References: <1dbb6047-2bbb-4d56-2a62-ab65a0254844@synopsys.com> <20161119135654.GA14079@lnxartpec.se.axis.com> <1248f4ce-4859-10e6-fef9-342ea543f8d4@synopsys.com> <87c8a24b-0812-7850-cb3f-7be691bab432@st.com> <7c7798b5-8cd4-ba99-f526-22d3e06e05db@synopsys.com> <2eefdb8f-7e87-6009-6e50-c536d4b95dd6@synopsys.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hello Joao, Lars. On 11/22/2016 3:16 PM, Joao Pinto wrote: >> Ok, it makes sense. >> > Just for curiosity the target setup is the following: >> > https://www.youtube.com/watch?v=8V-LB5y2Cos >> > but instead of using internal drivers, we desire to use mainline drivers only. >> > >> > Thanks! > Regarding this subject, I am thinking of making the following adaption: > > a) delete ethernet/synopsys > b) rename ethernet/stmicro/stmmac to ethernet/synopsys > > and send you a patch for you to evaluate. Both agree with the approach? > To have a new work base would be important, because I will add to the "new" > structure some missing QoS features like Multichannel support, CBS and later TSN. IMO, we have to agree on a common strategy making the change for net-next; I imaged the following steps: - to port missing feature or fixes from ethernet/synopsys inside the stmmac taking care about the documentation too. - remove ethernet/synopsys - rename ethernet/stmicro/stmmac to ethernet/synopsys These latest two have some relevant impacts. This change should be propagated to all the platforms that are using: CONFIG_SYNOPSYS_DWC_ETH_QOS and CONFIG_STMMAC_ETH plus device-tree compatibility. - enhance the stmmac with new features and new glue (part of these can be anticipated for sure). what do you think? does it make sense? If yes, we can also understand how/who starts. Regards, Peppe > Thanks.