netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Amr Bekhit <amrbekhit@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>, netdev@vger.kernel.org
Subject: Re: Davicom DM9162 PHY supported in the kernel?
Date: Tue, 24 May 2016 18:30:47 +0200	[thread overview]
Message-ID: <20160524163047.GF8897@lunn.ch> (raw)
In-Reply-To: <CAOLz05o5SELBH6LovChQrFXQWXOZANhrYrTNcuktM_nKnp10VQ@mail.gmail.com>

On Tue, May 24, 2016 at 05:09:35PM +0100, Amr Bekhit wrote:
> Hi Andrew,
> 
> > How about adding a printk() in genphy_read_status().
> 
> Would you be able to point me to some more information about these
> status bits, please?

You can get the datasheet from here:

http://www.davicom.com.tw/userfile/24247/DM9162_DM9162I-12-MCO-DS-F01_08062014.pdf

I would start by looking at the BMCR register. The
genphy_read_status() function should get called about once per second,
so that is an O.K. place to add debug prints, and there is example
code for reading MII_BMCR.

     Andrew

  reply	other threads:[~2016-05-24 16:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOLz05qgn2-9Qxm1cR7mXa67GAwD2SGbMnbeeEBrYeSPsBexuw@mail.gmail.com>
2016-04-20 15:25 ` Fwd: Davicom DM9162 PHY supported in the kernel? Amr Bekhit
2016-04-20 18:03 ` Florian Fainelli
2016-05-03 14:38   ` Amr Bekhit
2016-05-03 15:36     ` Andrew Lunn
2016-05-09 10:01       ` Amr Bekhit
2016-05-09 12:06         ` Andrew Lunn
2016-05-24 16:09           ` Amr Bekhit
2016-05-24 16:30             ` Andrew Lunn [this message]
2016-05-25 10:28               ` Amr Bekhit
2016-05-25 12:39                 ` Andrew Lunn
2016-05-25 13:20                   ` Amr Bekhit
2016-05-25 14:00                     ` Amr Bekhit
2016-05-25 14:03                     ` Andrew Lunn

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=20160524163047.GF8897@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=amrbekhit@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).