From: Baruch Siach <baruch@tkos.co.il>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Fabio Estevam <festevam@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
tinywrkb <tinywrkb@gmail.com>,
Russell King <linux@armlinux.org.uk>,
open list <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: imx6dl: SolidRun: add phy node with 100Mb/s max-speed
Date: Sun, 15 Sep 2019 09:30:00 +0300 [thread overview]
Message-ID: <87muf6oyvr.fsf@tarshish> (raw)
In-Reply-To: <20190910185033.GD9761@lunn.ch>
Hi Andrew,
On Tue, Sep 10 2019, Andrew Lunn wrote:
> On Tue, Sep 10, 2019 at 06:55:07PM +0300, tinywrkb wrote:
>> Cubox-i Solo/DualLite carrier board has 100Mb/s magnetics while the
>> Atheros AR8035 PHY on the MicroSoM v1.3 CPU module is a 1GbE PHY device.
>>
>> Since commit 5502b218e001 ("net: phy: use phy_resolve_aneg_linkmode in
>> genphy_read_status") ethernet is broken on Cubox-i Solo/DualLite devices.
>
> Hi Tinywrkb
>
> You emailed lots of people, but missed the PHY maintainers :-(
>
> Are you sure this is the patch which broken it? Did you do a git
> bisect.
Tinywrkb confirmed to me in private communication that revert of
5502b218e001 fixes Ethernet for him on effected system.
He also referred me to an old Cubox-i spec that lists 10/100 Ethernet
only for i.MX6 Solo/DualLite variants of Cubox-i. It turns out that
there was a plan to use a different 10/100 PHY for Solo/DualLite
SOMs. This plan never materialized. All SolidRun i.MX6 SOMs use the same
AR8035 PHY that supports 1Gb.
Commit 5502b218e001 might be triggering a hardware issue on the affected
Cubox-i. I could not reproduce the issue here with Cubox-i and a Dual
SOM variant running v5.3-rc8. I have no Solo/DualLite variant handy at
the moment.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Baruch Siach <baruch@tkos.co.il>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Fabio Estevam <festevam@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
tinywrkb <tinywrkb@gmail.com>,
Russell King <linux@armlinux.org.uk>,
open list <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: imx6dl: SolidRun: add phy node with 100Mb/s max-speed
Date: Sun, 15 Sep 2019 09:30:00 +0300 [thread overview]
Message-ID: <87muf6oyvr.fsf@tarshish> (raw)
In-Reply-To: <20190910185033.GD9761@lunn.ch>
Hi Andrew,
On Tue, Sep 10 2019, Andrew Lunn wrote:
> On Tue, Sep 10, 2019 at 06:55:07PM +0300, tinywrkb wrote:
>> Cubox-i Solo/DualLite carrier board has 100Mb/s magnetics while the
>> Atheros AR8035 PHY on the MicroSoM v1.3 CPU module is a 1GbE PHY device.
>>
>> Since commit 5502b218e001 ("net: phy: use phy_resolve_aneg_linkmode in
>> genphy_read_status") ethernet is broken on Cubox-i Solo/DualLite devices.
>
> Hi Tinywrkb
>
> You emailed lots of people, but missed the PHY maintainers :-(
>
> Are you sure this is the patch which broken it? Did you do a git
> bisect.
Tinywrkb confirmed to me in private communication that revert of
5502b218e001 fixes Ethernet for him on effected system.
He also referred me to an old Cubox-i spec that lists 10/100 Ethernet
only for i.MX6 Solo/DualLite variants of Cubox-i. It turns out that
there was a plan to use a different 10/100 PHY for Solo/DualLite
SOMs. This plan never materialized. All SolidRun i.MX6 SOMs use the same
AR8035 PHY that supports 1Gb.
Commit 5502b218e001 might be triggering a hardware issue on the affected
Cubox-i. I could not reproduce the issue here with Cubox-i and a Dual
SOM variant running v5.3-rc8. I have no Solo/DualLite variant handy at
the moment.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
WARNING: multiple messages have this Message-ID (diff)
From: Baruch Siach <baruch@tkos.co.il>
To: Andrew Lunn <andrew@lunn.ch>
Cc: tinywrkb <tinywrkb@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
"open list\:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Russell King <linux@armlinux.org.uk>,
open list <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: imx6dl: SolidRun: add phy node with 100Mb/s max-speed
Date: Sun, 15 Sep 2019 09:30:00 +0300 [thread overview]
Message-ID: <87muf6oyvr.fsf@tarshish> (raw)
In-Reply-To: <20190910185033.GD9761@lunn.ch>
Hi Andrew,
On Tue, Sep 10 2019, Andrew Lunn wrote:
> On Tue, Sep 10, 2019 at 06:55:07PM +0300, tinywrkb wrote:
>> Cubox-i Solo/DualLite carrier board has 100Mb/s magnetics while the
>> Atheros AR8035 PHY on the MicroSoM v1.3 CPU module is a 1GbE PHY device.
>>
>> Since commit 5502b218e001 ("net: phy: use phy_resolve_aneg_linkmode in
>> genphy_read_status") ethernet is broken on Cubox-i Solo/DualLite devices.
>
> Hi Tinywrkb
>
> You emailed lots of people, but missed the PHY maintainers :-(
>
> Are you sure this is the patch which broken it? Did you do a git
> bisect.
Tinywrkb confirmed to me in private communication that revert of
5502b218e001 fixes Ethernet for him on effected system.
He also referred me to an old Cubox-i spec that lists 10/100 Ethernet
only for i.MX6 Solo/DualLite variants of Cubox-i. It turns out that
there was a plan to use a different 10/100 PHY for Solo/DualLite
SOMs. This plan never materialized. All SolidRun i.MX6 SOMs use the same
AR8035 PHY that supports 1Gb.
Commit 5502b218e001 might be triggering a hardware issue on the affected
Cubox-i. I could not reproduce the issue here with Cubox-i and a Dual
SOM variant running v5.3-rc8. I have no Solo/DualLite variant handy at
the moment.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2019-09-15 6:30 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 15:55 [PATCH] ARM: dts: imx6dl: SolidRun: add phy node with 100Mb/s max-speed tinywrkb
2019-09-10 15:55 ` tinywrkb
2019-09-10 15:55 ` tinywrkb
2019-09-10 16:10 ` Fabio Estevam
2019-09-10 16:10 ` Fabio Estevam
2019-09-10 16:10 ` Fabio Estevam
2019-09-10 16:17 ` Baruch Siach
2019-09-10 16:17 ` Baruch Siach
2019-09-10 16:46 ` Russell King - ARM Linux admin
2019-09-10 16:46 ` Russell King - ARM Linux admin
2019-09-10 18:50 ` Andrew Lunn
2019-09-10 18:50 ` Andrew Lunn
2019-09-15 6:30 ` Baruch Siach [this message]
2019-09-15 6:30 ` Baruch Siach
2019-09-15 6:30 ` Baruch Siach
2019-09-15 12:29 ` Russell King - ARM Linux admin
2019-09-15 12:29 ` Russell King - ARM Linux admin
2019-09-15 13:56 ` Andrew Lunn
2019-09-15 13:56 ` Andrew Lunn
2019-09-15 14:06 ` Russell King - ARM Linux admin
2019-09-15 14:06 ` Russell King - ARM Linux admin
2019-09-15 14:15 ` Russell King - ARM Linux admin
2019-09-15 14:15 ` Russell King - ARM Linux admin
2019-09-15 14:42 ` Andrew Lunn
2019-09-15 14:42 ` Andrew Lunn
2019-09-15 14:42 ` Andrew Lunn
2019-09-15 14:58 ` Russell King - ARM Linux admin
2019-09-15 14:58 ` Russell King - ARM Linux admin
2019-09-17 12:41 ` tinywrkb
2019-09-17 12:41 ` tinywrkb
2019-09-17 12:54 ` Andrew Lunn
2019-09-17 12:54 ` Andrew Lunn
2019-09-17 13:32 ` tinywrkb
2019-09-17 13:32 ` tinywrkb
2019-09-17 13:39 ` Russell King - ARM Linux admin
2019-09-17 13:39 ` Russell King - ARM Linux admin
2019-09-17 15:17 ` Russell King - ARM Linux admin
2019-09-17 15:17 ` Russell King - ARM Linux admin
2019-09-17 15:30 ` Russell King - ARM Linux admin
2019-09-17 15:30 ` Russell King - ARM Linux admin
2019-09-17 16:34 ` tinywrkb
2019-09-17 16:34 ` tinywrkb
2019-09-17 17:04 ` Russell King - ARM Linux admin
2019-09-17 17:04 ` Russell King - ARM Linux admin
2019-09-17 17:19 ` Russell King - ARM Linux admin
2019-09-17 17:19 ` Russell King - ARM Linux admin
2019-09-17 17:26 ` Andrew Lunn
2019-09-17 17:26 ` Andrew Lunn
2019-09-17 17:37 ` Russell King - ARM Linux admin
2019-09-17 17:37 ` Russell King - ARM Linux admin
2019-09-17 18:19 ` Russell King - ARM Linux admin
2019-09-17 18:19 ` Russell King - ARM Linux admin
2019-09-17 18:39 ` Andrew Lunn
2019-09-17 18:39 ` Andrew Lunn
2019-09-20 10:36 ` Russell King - ARM Linux admin
2019-09-20 10:36 ` Russell King - ARM Linux admin
2019-09-17 21:42 ` Russell King - ARM Linux admin
2019-09-17 21:42 ` Russell King - ARM Linux admin
2019-09-20 13:42 ` Russell King - ARM Linux admin
2019-09-20 13:42 ` Russell King - ARM Linux admin
2019-09-17 22:30 ` Russell King - ARM Linux admin
2019-09-17 22:30 ` Russell King - ARM Linux admin
2019-09-17 22:43 ` Russell King - ARM Linux admin
2019-09-17 22:43 ` Russell King - ARM Linux admin
2019-09-18 14:45 ` tinywrkb
2019-09-18 14:45 ` tinywrkb
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=87muf6oyvr.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tinywrkb@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.