From: Joe Hershberger <joe.hershberger@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 1/7] net: mvpp2x: fix traffic stuck after PHY start error
Date: Wed, 14 Aug 2019 10:59:48 -0500 [thread overview]
Message-ID: <CANr=Z=bDG722wKehSTuzwJ9X+iPvxgrNgCZwYk+2iB9KjC99hw@mail.gmail.com> (raw)
In-Reply-To: <20190806155144.19301-2-nhed+uboot@starry.com>
On Tue, Aug 6, 2019 at 10:52 AM <nhed+uboot@starry.com> wrote:
>
> From: Stefan Chulski <stefanc@marvell.com>
>
> Issue:
> - Network stuck if autonegotion fails.
>
> Issue root cause:
>
> - When autonegotiation fails during port open procedure, the packet
> processor configuration does not finish and open procedure exits
> with error.
> - However, this doesn't prevent u-boot network framework from
> calling send and receive procedures.
> - Using transmit and receive functions of misconfigured packet
> processor will cause traffic to get stuck.
>
> Fix:
>
> - Continue packet processor configuration even if autonegotiation
> fails. Only error message is triggered in this case.
> - Exit transmit and receive functions if there is no PHY link
> indication.
> - U-boot network framework now calls open procedure again during next
> transmit initiation.
>
> Signed-off-by: Stefan Chulski <stefanc@marvell.com>
> Reviewed-by: Igal Liberman <igall@marvell.com>
> Tested-by: Igal Liberman <igall@marvell.com>
Acked-by: Joe Hershberger <joe.hershberger@ni.com>
next prev parent reply other threads:[~2019-08-14 15:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 15:51 [U-Boot] [PATCH v3 0/7] Switch MVPP2 to use new MVMDIO nhed+uboot at starry.com
2019-08-06 15:51 ` [U-Boot] [PATCH v3 1/7] net: mvpp2x: fix traffic stuck after PHY start error nhed+uboot at starry.com
2019-08-07 17:50 ` Ramon Fried
2019-08-14 15:59 ` Joe Hershberger [this message]
2019-08-06 15:51 ` [U-Boot] [PATCH v3 2/7] net: mvpp2: Replace SMI implementation with marvell MDIO API nhed+uboot at starry.com
2019-08-07 17:52 ` Ramon Fried
2019-08-06 15:51 ` [U-Boot] [PATCH v3 3/7] net: mvpp2: mark phy as invalid in case of missing appropriate driver nhed+uboot at starry.com
2019-08-07 17:52 ` Ramon Fried
2019-08-06 15:51 ` [U-Boot] [PATCH v3 4/7] net: mvpp2: no deref null nhed+uboot at starry.com
2019-08-07 14:57 ` Ramon Fried
2019-08-06 15:51 ` [U-Boot] [PATCH v3 5/7] arm: dts: armada-cp110-*dtsi: add xmdio nodes nhed+uboot at starry.com
2019-08-07 17:54 ` Ramon Fried
2019-08-14 15:55 ` Joe Hershberger
2019-08-06 15:51 ` [U-Boot] [PATCH v3 6/7] net: mvpp2: use new MVMDIO driver nhed+uboot at starry.com
2019-08-14 15:59 ` Joe Hershberger
2019-08-06 15:51 ` [U-Boot] [PATCH v3 7/7] net: mvpp2: MVPP2 now needs MVMDIO nhed+uboot at starry.com
2019-08-07 14:56 ` Ramon Fried
2019-08-14 15:49 ` Joe Hershberger
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='CANr=Z=bDG722wKehSTuzwJ9X+iPvxgrNgCZwYk+2iB9KjC99hw@mail.gmail.com' \
--to=joe.hershberger@gmail.com \
--cc=u-boot@lists.denx.de \
/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.