From: Giuseppe Pagano <giuseppe.pagano@seco.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] udoo: Add Ethernet support.
Date: Thu, 07 Nov 2013 13:37:29 +0100 [thread overview]
Message-ID: <1383827849.3371.90.camel@localhost> (raw)
In-Reply-To: <527B5174.8040605@denx.de>
Hi Stefano,
On Thu, 2013-11-07 at 09:38 +0100, Stefano Babic wrote:
> Hi Giuseppe,
>
> On 06/11/2013 21:33, Giuseppe Pagano wrote:
> > Add Ethernet and networking support on uDoo board (FEC + phy Micrel)
> >
> >
> > Signed-off-by: Giuseppe Pagano <giuseppe.pagano@seco.com>
> > Cc: sbabic at denx.de
> >
> > +int mx6_rgmii_rework(struct phy_device *phydev)
> > +{
> > + /* To advertise only 10 Mbs */
> > + phy_write(phydev, MDIO_DEVAD_NONE, 0x4, 0x61);
> > + phy_write(phydev, MDIO_DEVAD_NONE, 0x9, 0x0c00);
> > +
>
> Why only 10 Mb/s ? I think the Micrel 9031 allows 1Gb/s.
I will check again, I remember this solves an issue present also in
sabrelite board; but not sure. Maybe we can remove.
> Generally, use defines instead of hard coded values.
Ok
> > + /* min rx data delay */
> > + ksz9021_phy_extended_write(phydev,
> > + MII_KSZ9021_EXT_RGMII_RX_DATA_SKEW, 0x0);
>
> Is is 9021 or 9031 ?
uDoo adopt a Micrel KSZ9031 phy.
Most of the register address are common to ksz9021 and ksz9031, and have
the same value. Maybe we should rename some variable to MII_KSZ90XX_...
> > +
> > + gpio_set_value(IMX_GPIO_NR(3, 23), 1); /* SABRE Lite PHY rst */
>
> SABRE as comment is maybe wrong
>
> > +#define CONFIG_PHY_MICREL_KSZ9021
>
> Ok, it is 9021 - please be consistent with the comments avoiding mixing
> 9031 and 9021.
No, it is 9031. I will create a new define.
>
> Best regards,
> Stefano Babic
Best regards,
Giuseppe Pagano
next prev parent reply other threads:[~2013-11-07 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 20:33 [U-Boot] [PATCH 1/4] udoo: Add Ethernet support Giuseppe Pagano
2013-11-07 8:38 ` Stefano Babic
2013-11-07 12:37 ` Giuseppe Pagano [this message]
2013-11-07 14:57 ` Stefano Babic
2013-11-07 14:58 ` Stefano Babic
2013-11-07 15:28 ` 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=1383827849.3371.90.camel@localhost \
--to=giuseppe.pagano@seco.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