Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752778AbbKVVdZ (ORCPT ); Sun, 22 Nov 2015 16:33:25 -0500 Received: from mout.kundenserver.de ([217.72.192.74]:58399 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752335AbbKVVdX (ORCPT ); Sun, 22 Nov 2015 16:33:23 -0500 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Marcin Wojtas , Thomas Petazzoni , Andrew Lunn , Russell King - ARM Linux , Jason Cooper , netdev@vger.kernel.org, Simon Guinot , linux-kernel@vger.kernel.org, Evan Wang , nadavh@marvell.com, nitroshift@yahoo.com, Lior Amsalem , "stable@vger.kernel.org" , Grzegorz Jaszczyk , Gregory =?ISO-8859-1?Q?Cl=E9ment?= , Tomasz Nowicki , Sebastian Hesselbarth , "David S. Miller" , Yair Mahalalel Subject: Re: [PATCH 02/13] net: mvneta: enable IP checksum with jumbo frames for Armada 38x on Port0 Date: Sun, 22 Nov 2015 22:32:33 +0100 Message-ID: <5578695.0ahxvoVWDX@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: References: <1448178839-3541-1-git-send-email-mw@semihalf.com> <4040597.3hXVb3XDMS@wuerfel> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:Im3BrJV+e4W+MAF0IVUJaf/QBhC1O8y9wvnGavAr0YaKEsPmxBI 53h4KRtSBa6QF/ZanpVPkWYqjYBhBcMA0T0M9N8zYJVhyS+4bcia89ziUJ68PRYeJB29myM z91jMkQ2q6McC4Ii8MOwR3327TjiSPrng9hoN/7xhrx6e2D6TJApGnfHfiMzkvgaBylxJ9h BXBj56zBBWNzosD06Xeog== X-UI-Out-Filterresults: notjunk:1;V01:K0:Nqk95AYeoXQ=:6FGa+24i85eB2X9+H9rIgR /cfjd6/LHThwOErbCuJ34i/Tx8HEzUnqCEipWcXZTpxS3tOO136TERB4tzU4TTI6O+AQvR/0W BhYBJ1kVNIReFn+RN7lo2mVPTUILLzKwrJeo6u36mW8GVTjmPTTSYrS5Nlc1sAqMDp1AFyrzH oLwI3BKBQRxrcCEx78vzYEJJmdyxpvwIM4BFcsBeyBxcvDqM8aDaRnX3kz2rtwk94IjFXzbC8 ZI29VCemlOl9BWuKPXwWxArQTVf9b6GQqB4ofLJbrSO0kevOiAhz4Oc2W3osVs+zjU5BwamTZ FHQyVvsjrH7NilN4+c9Hxfk1SyBX3yN8opXebh16iPX2J+mTSpDPI0i8YDlCy70wAp2U80est gqhd5XsNQ0h/dHWNaA5s1DIEZTiHvjdoNhbPtt0CxfijBuQjpMqFis7ut979nPL9YIMuHCRUi AkG+Z1n8IbSS+4anLt4AwDJN+RBubB5viHAw3XRcVuTQN1EOncwQrKklg4kAAVnGkoCEPdcoI Hvp8Ev/MhcjH4Ay42yJEi/qoBh/QPLIakaIDNdjB46dzBhvBqEmndBomDcQX7Nbqh+97iQPMI HIVYswNfQKfimILYS3cGTCjoLFkkK0ZIxi2qEmnsu5FNjkyeKrdmEgVfjuIwHwHM4N9kwyzra 1ahWsHwT75cZsZ5oVH77oBFvSy6+7jflLMi5Ff5OMyMofU4U2bmD1MXc1Xq7cyRnBqPRCwEPr O4bSuNGEUWfkG1YA Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2876 Lines: 68 On Sunday 22 November 2015 22:04:38 Marcin Wojtas wrote: > 2015-11-22 21:00 GMT+01:00 Arnd Bergmann : > > On Sunday 22 November 2015 08:53:48 Marcin Wojtas wrote: > >> The Ethernet controller found in the Armada 38x SoC's family support > >> TCP/IP checksumming with frame sizes larger than 1600 bytes, however > >> only on port 0. > >> > >> This commit enables this feature by using 'marvell,armada-xp-neta' in > >> 'ethernet@70000' node. > >> > >> Signed-off-by: Marcin Wojtas > >> Cc: # v3.18+ > >> --- > >> arch/arm/boot/dts/armada-38x.dtsi | 2 +- > >> 1 file changed, 1 insertion(+), 1 deletion(-) > >> > >> diff --git a/arch/arm/boot/dts/armada-38x.dtsi b/arch/arm/boot/dts/armada-38x.dtsi > >> index c6a0e9d..b7868b2 100644 > >> --- a/arch/arm/boot/dts/armada-38x.dtsi > >> +++ b/arch/arm/boot/dts/armada-38x.dtsi > >> @@ -494,7 +494,7 @@ > >> }; > >> > >> eth0: ethernet@70000 { > >> - compatible = "marvell,armada-370-neta"; > >> + compatible = "marvell,armada-xp-neta"; > >> reg = <0x70000 0x4000>; > >> interrupts-extended = <&mpic 8>; > >> clocks = <&gateclk 4>; > >> > > > > As it's clear that they are not 100% backwards compatible, please > > add a SoC specific compatible string here as well, like > > > > compatible = "marvell,armada-380-neta", "marvell,armada-xp-neta"; > > > > Wouldn't be one sufficient ("marvell,armada-380-neta")? If they are basically compatible, you want to the original one in, to make sure it keeps running on operating systems that only know about the older string. > > Maybe also leave the 370 string in place. > > > > Now 370 string disables ip checksum for jumbo frames, so I don't think > it's appropriate to keep it for port 0. Ok, I see. We should probably have done it the other way round and kept the default as checksum-disabled and only override it when the newer compatible string is also present. Basically the device *is* compatible to an Armada 370, it just has additional features that work correctly. If the feature set depends on the port number, we should think about the way it gets handled again, as this is probably better not described as something that depends (just) on the SoC, but on the way it gets integrated. Maybe we can introduce an additional property for the checksums on jumbo frames and use that if present but fall back to identifying by compatible string otherwise. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/