public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] arm: socfpga: set skew settings for ethernet phy
Date: Sat, 15 Nov 2014 22:29:00 +0100	[thread overview]
Message-ID: <201411152229.01053.marex@denx.de> (raw)
In-Reply-To: <20141115195406.GA9677@amd>

On Saturday, November 15, 2014 at 08:54:06 PM, Pavel Machek wrote:
> On Fri 2014-11-14 21:02:48, Marek Vasut wrote:
> > On Friday, November 14, 2014 at 11:23:27 AM, Pavel Machek wrote:
> > > On Thu 2014-11-13 11:23:41, dinguyen at opensource.altera.com wrote:
> > > > From: Dinh Nguyen <dinguyen@opensource.altera.com>
> > > > 
> > > > Set the PHY skew settings for the ethernet phy on the SOCFPGA
> > > > Cyclone5 hardware.
> > > 
> > > Is it to need similar settings for all ksz9021 phys? Should this go to
> > > drivers/ as I suggested with a patch?
> > 
> > This is board specific, but with the driver model, this should be moved
> > into the PHY driver and the values should be passed via platform data or
> > DT.
> > 
> > I will apply this now, since it fixes real issue.
> 
> Hmm, could you apply the patch I posted, instead? It has configuration
> in socfpga_config.h -- "platform data".

Hi!

The patch you provided (if we're referring to the same patch, Message-ID: 
<20141113120956.GB30779@amd>) breaks every board which uses the Micrel PHY, 
doesn't it ? The problem for all other boards would be the new CONFIG_* options
which are added into the Micrel driver by that patch. Furthermore, the patch 
doesn't even apply, it was decided that the patch was an RFC, wasn't it ?
Please correct me if I'm wrong.

The way forward here would be for you to prepare a patch for the Micrel PHY
driver, submit that one (make sure to CC Joe, the network custodian) and
in the next step clean up the writes into PHY configuration from both the
SoCFPGA CV and from Nitrogen 6x support (I recall I saw the same thing done
for that board).

Oh, and btw., the new CONFIG_* options should be documented somewhere, so
please keep that in mind. Otherwise, the amount of various CONFIG_* options
become an unmanagable mess.

Thanks!

Best regards,
Marek Vasut

  reply	other threads:[~2014-11-15 21:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 17:23 [U-Boot] [PATCH v2] arm: socfpga: set skew settings for ethernet phy dinguyen at opensource.altera.com
2014-11-14 10:23 ` Pavel Machek
2014-11-14 20:02   ` Marek Vasut
2014-11-15 19:54     ` Pavel Machek
2014-11-15 21:29       ` Marek Vasut [this message]
2014-11-15 22:20         ` Pavel Machek
2014-11-15 23:36           ` Marek Vasut
2014-11-14 20:06 ` Marek Vasut

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=201411152229.01053.marex@denx.de \
    --to=marex@denx.de \
    --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