From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>,
Benjamin Beckmeyer <beb@eks-engel.de>
Subject: Re: MII command to read and write specific registers
Date: Fri, 12 Jul 2019 00:13:11 -0700 [thread overview]
Message-ID: <CAHQ1cqGrOd4PEpXT4-s+1cAtjkU3gnbaUK0-BoC7f1stbYP_sA@mail.gmail.com> (raw)
In-Reply-To: <20190711203617.4014fbc3a8c357e2de2d422d@gmail.com>
On Thu, Jul 11, 2019 at 10:36 AM Antony Pavlov <antonynpavlov@gmail.com> wrote:
>
> On Thu, 11 Jul 2019 15:30:01 +0200
> Benjamin Beckmeyer <beb@eks-engel.de> wrote:
>
> > Hey all,
> > is there a possibility to read/write specific registers from/to different MII addresses?
> >
> > I know that there is miitool but it just can give me the first 16 registers of a PHY.
> > But I need write specific registers e.g. MII addr 2 register 0 and read MII addr 2
> > register 1. I know uboot is having the mii command(exactly what I would need), and I
> > have seen that there were parameters for address and register in miitool but they
> > were deleted lastly.
> >
>
> Hi Benjamin!
>
> You can use /dev/mdio* devices for reading/writing MII registers.
> E.g.
> md -s /dev/mdio0-phy00
> mw -d /dev/mdio0-phy00 -w 0 0x12345678
>
> Just after barebox boot there is no /dev/mdio* devices.
> After network interface initialization (e.g. after ifup command) or
> after miitool command the /dev/mdio* devices appear.
>
Adding to that, if you device doesn't have register layout detectable
by MII bus probe algorithm an arbitrary phydev can be forcefully
created using
miitool -r <busno>:<addr>
Comes really handy when dealing with something other than PHY devices
(e.g reading switch registers).
Thanks,
Andrey Smirnov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-07-12 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 13:30 Benjamin Beckmeyer
2019-07-11 17:36 ` Antony Pavlov
2019-07-12 6:40 ` Benjamin Beckmeyer
2019-07-12 7:13 ` Andrey Smirnov [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=CAHQ1cqGrOd4PEpXT4-s+1cAtjkU3gnbaUK0-BoC7f1stbYP_sA@mail.gmail.com \
--to=andrew.smirnov@gmail.com \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=beb@eks-engel.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