public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Vince Bridgers <vbridger@opensource.altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] net: phy: Add ability to program the ksz9031 skew values from the uboot env
Date: Fri, 13 Feb 2015 16:17:13 +0000	[thread overview]
Message-ID: <1423844232599.30262@opensource.altera.com> (raw)
In-Reply-To: <CANr=Z=YxN4kKccdAyQfNDkZknKs_4wNYQ5PO+heJKAgmOPYhBA@mail.gmail.com>

Hi Joe!

...
> > +1 from me as well.
...
> > Joe, whats your opinion on this?
...
> Do we really think this is a strong use-case?  This seem like the type of thing I
> would expect to tweak for testing through mii / mdio commands and then
> configure the device tree based on that.  This is pretty much a one-time thing for a
> given board it seems to me.
>
> If we really want a polished interface to it, we should define a sub-command /
> new command that phy drivers can implement.  I'm not sure an
> undiscoverable,  un-"help"-able list of env vars will be apparent to users.  Do you have a
> feeling for how close to universal any of these parameters are across phys?

I don't believe this is a strong use case for debugged and working boards. The intent was to support our downstream customers, that do develop their own boards and could use a method to help them with initial bringup. Many of these engineers in bringup are hardware/board developers and are not as comfortable as we are using uboot. It helps to support skewing these signals, especially if it can save a board spin  (having said this - this capability is not a substitute for a well designed board). The debug/bringup use case can be supported by describing to non-expert users how to make use of the mii command as Marek had originally suggested, so I'm fine with that solution.

On the question of how universal these parameters are across phys? Not so much. I've only encountered these on the two Micrel phys - the ksz9021 and ksz9031. And these have different signals that can be skewed.

Thanks for the comments and feedback! I'll focus on working out a solution through devicetree, and a README type of description of how to skew the signals for debug/bringup purposes using the mii command.

All the best!

Vince

  parent reply	other threads:[~2015-02-13 16:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 14:44 [U-Boot] [PATCH 0/2] Add getenv_long and Micrel ksz9031 skew settings Vince Bridgers
2015-02-09 14:44 ` [U-Boot] [PATCH 1/2] cmd: Add getenv_long to support reading signed integers from the uboot env Vince Bridgers
2015-02-09 19:12   ` Marek Vasut
2015-02-09 14:44 ` [U-Boot] [PATCH 2/2] net: phy: Add ability to program the ksz9031 skew values " Vince Bridgers
2015-02-09 19:18   ` Marek Vasut
2015-02-09 21:31     ` Vince Bridgers
2015-02-10 18:51       ` Marek Vasut
2015-02-11  7:08         ` Stefan Roese
2015-02-11  8:07           ` Joe Hershberger
2015-02-11  8:26             ` Stefan Roese
2015-02-13 16:19               ` Vince Bridgers
2015-02-13 16:44                 ` Stefan Roese
2015-02-15 14:43                   ` Marek Vasut
2015-02-13 16:17             ` Vince Bridgers [this message]
2015-02-13 16:05           ` Vince Bridgers
2015-02-13 15:57         ` Vince Bridgers

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=1423844232599.30262@opensource.altera.com \
    --to=vbridger@opensource.altera.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