public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 0/5]
Date: Mon, 02 Sep 2013 17:47:18 +0200	[thread overview]
Message-ID: <5224B306.2070007@denx.de> (raw)
In-Reply-To: <593AEF6C47F46446852B067021A273D6D983CF35@MUCSE039.lantiq.com>


Hi Thomas,

On 02/09/2013 16:59, thomas.langer at lantiq.com wrote:
> Hello Stefano,
> 
> Stefano Babic wrote on 2013-09-02:
> 
>> Some phys have additional registers that are not covered
>> by standard. Access to this registers can be done via
>> specific sequence according to the phy datasheet.
>> The driver for Micrel phy contains some additional function,
>> that the board maintainer can call to tune the phy. However,
>> these registers cannot be accessed with "mmdio" command.
>>
>> Add calback to the phy API to allow to call the function
>> for reading / writing extended registers with the mmdio command.
>>
>>
> 
> The basic mechanism used for the access is not specific to Micrel, it is defined 
> in the IEEE standard [1], "Annex 22D: Clause 22 access to Clause 45 MMD registers"

Interesting - my changes were done according to the Micrel's KSZ9031
datasheet.

> 
> A presentation for this can be found when you ask google for it [2]
> 
> [1]: IEEE Std 802.3-2008 (or 2012): http://standards.ieee.org/about/get/802/802.3.html
> [2]: https://www.google.de/search?q=%22Clause+22+Access+to+Clause+45+Registers%22
> 
> So maybe it will be useful to have the access functions in the common phy lib?
> 

Maybe it is enough to move the extread / extwrite functions inside
phylib. However, if the behavior of the KSZ9031 matches the
documentation you have posted, the KSZ9021 seems to slightly deviate. Or
is the 9021 supporting another "clause" ?

> I assume that most current PHYs have these method implemented,
> as also some extended standard registers needs this.
> For example, the EEE (Energy Efficient Ethernet) registers are located in this extended
> register range.

This is also a nice to have feature.

> 
> Probably this can be extended in some follow-up patches, 

Let's wait for Joe's opinion.

> I just wanted to share my thoughts ;-)

Thanks, I was not aware of the standard. Learned something new...

Best regards,
Stefano

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================

      reply	other threads:[~2013-09-02 15:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 13:42 [U-Boot] [PATCH v1 0/5] Stefano Babic
2013-09-02 13:42 ` [U-Boot] [PATCH v1 1/5] phy: add missing constants for Micrel KSZ9031 Stefano Babic
2013-09-02 13:42 ` [U-Boot] [PATCH v1 2/5] net: fix mask for phy " Stefano Babic
2013-09-02 13:42 ` [U-Boot] [PATCH v1 3/5] net: add extended function to phy API Stefano Babic
2013-09-02 13:42 ` [U-Boot] [PATCH v1 4/5] net: add function to read/write extended registers in Micrel Phy Stefano Babic
2013-09-02 13:42 ` [U-Boot] [PATCH v1 5/5] net: add support for extended registers to mdio command Stefano Babic
2013-09-02 14:59 ` [U-Boot] [PATCH v1 0/5] thomas.langer at lantiq.com
2013-09-02 15:47   ` Stefano Babic [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=5224B306.2070007@denx.de \
    --to=sbabic@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