From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Blumenstingl Subject: Re: [PATCH 0/5] meson-gx: reset RGMII PHYs and configure TX delay Date: Wed, 18 Jan 2017 20:40:34 +0100 Message-ID: References: <20161202234739.22929-1-martin.blumenstingl@googlemail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: 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 To: Kevin Hilman Cc: mark.rutland@arm.com, devicetree@vger.kernel.org, catalin.marinas@arm.com, will.deacon@arm.com, robh+dt@kernel.org, carlo@caione.org, linux-amlogic@lists.infradead.org, linux-arm-kernel@lists.infradead.org List-Id: devicetree@vger.kernel.org Kevin, On Wed, Jan 18, 2017 at 8:28 PM, Kevin Hilman wrote: > Martin Blumenstingl writes: > >> This partially fixes the 1000Mbit/s ethernet TX throughput issues (on >> networks which are not affected by the EEE problem, as reported here: > > Based on the discussions with Jerome, I'm dropping this series from the > v4.11/dt64 branch for now. what is you opinion on having the MDIO node in meson-gx (and keeping GXBB and GXL/GXM consistent) vs not having PHY autodetection for GXBB (= not having the MDIO in meson-gx)? I cannot send a v2 until we have a decision for this > This series also had a small conflict with Jerome's fix[1] for the > odroid-c2, so please rebase any updates here on my v4.10/fixes branch. will keep that in mind, noted. From mboxrd@z Thu Jan 1 00:00:00 1970 From: martin.blumenstingl@googlemail.com (Martin Blumenstingl) Date: Wed, 18 Jan 2017 20:40:34 +0100 Subject: [PATCH 0/5] meson-gx: reset RGMII PHYs and configure TX delay In-Reply-To: References: <20161202234739.22929-1-martin.blumenstingl@googlemail.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Kevin, On Wed, Jan 18, 2017 at 8:28 PM, Kevin Hilman wrote: > Martin Blumenstingl writes: > >> This partially fixes the 1000Mbit/s ethernet TX throughput issues (on >> networks which are not affected by the EEE problem, as reported here: > > Based on the discussions with Jerome, I'm dropping this series from the > v4.11/dt64 branch for now. what is you opinion on having the MDIO node in meson-gx (and keeping GXBB and GXL/GXM consistent) vs not having PHY autodetection for GXBB (= not having the MDIO in meson-gx)? I cannot send a v2 until we have a decision for this > This series also had a small conflict with Jerome's fix[1] for the > odroid-c2, so please rebase any updates here on my v4.10/fixes branch. will keep that in mind, noted. From mboxrd@z Thu Jan 1 00:00:00 1970 From: martin.blumenstingl@googlemail.com (Martin Blumenstingl) Date: Wed, 18 Jan 2017 20:40:34 +0100 Subject: [PATCH 0/5] meson-gx: reset RGMII PHYs and configure TX delay In-Reply-To: References: <20161202234739.22929-1-martin.blumenstingl@googlemail.com> Message-ID: To: linus-amlogic@lists.infradead.org List-Id: linus-amlogic.lists.infradead.org Kevin, On Wed, Jan 18, 2017 at 8:28 PM, Kevin Hilman wrote: > Martin Blumenstingl writes: > >> This partially fixes the 1000Mbit/s ethernet TX throughput issues (on >> networks which are not affected by the EEE problem, as reported here: > > Based on the discussions with Jerome, I'm dropping this series from the > v4.11/dt64 branch for now. what is you opinion on having the MDIO node in meson-gx (and keeping GXBB and GXL/GXM consistent) vs not having PHY autodetection for GXBB (= not having the MDIO in meson-gx)? I cannot send a v2 until we have a decision for this > This series also had a small conflict with Jerome's fix[1] for the > odroid-c2, so please rebase any updates here on my v4.10/fixes branch. will keep that in mind, noted.