public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Broken H3 EMAC Driver
Date: Tue, 31 May 2016 06:53:22 +0200	[thread overview]
Message-ID: <574D18C2.5030602@xilinx.com> (raw)
In-Reply-To: <CABHD4K-UxP4poevCSV5Wos8oR6qT518UitkmcGbKsfcZ3_YYtA@mail.gmail.com>

Hi,

On 30.5.2016 16:12, Amit Tomer wrote:
> Hello,
> 
> Trying to add support for H3 EMAC driver.
> 
> http://comments.gmane.org/gmane.comp.boot-loaders.u-boot/261544
> 
> It was working well until commit "
> b733c278d7adc48c71bd06faf359db3d9e385185" was introduced.
> 
> net: phy: Handle phy_startup() error codes properly
> 
> -       genphy_update_link(phydev);
> -       genphy_parse_link(phydev);
> +       int ret;
> -       return 0;
> +       ret = genphy_update_link(phydev);
> +       if (ret)
> +               return ret;
> 
> H3 based SoC's has an internal PHY which is different from having on board
> external PHY and its operations doesn't depends upon the success of normal
> PHY auto negotiation(Driver works well even if there is a PHY auto
> negotiation TIMEOUT).

It looks like that your driver doesn't use phy code correctly. My patch
just handles errors which are reported by the core.
If you have any internal phy you should consider to create your own phy
driver to handle it or remove phy code from your driver if phy is
already setup.

Thanks,
Michal

      reply	other threads:[~2016-05-31  4:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30 14:12 [U-Boot] Broken H3 EMAC Driver Amit Tomer
2016-05-31  4:53 ` Michal Simek [this message]

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=574D18C2.5030602@xilinx.com \
    --to=michal.simek@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox