mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH v2 8/8] miitool: Add code to register a PHY
Date: Tue, 2 Feb 2016 16:41:46 -0800	[thread overview]
Message-ID: <CAHQ1cqGxkLm8axj4TGH4=NnyLjj-HupmD_5Df-tpMgAFsMN9Ug@mail.gmail.com> (raw)
In-Reply-To: <20160201093519.GP13058@pengutronix.de>

On Mon, Feb 1, 2016 at 1:35 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> Hi Andrey,
>
> On Sun, Jan 31, 2016 at 07:10:13PM -0800, Andrey Smirnov wrote:
>> This commit changes the behaviour of the 'miitool'. Now in order to show
>> PHY's link information 'miitool' should be invoked as such:
>>
>> miitool -s [PHY]
>>
>> Also, implment code to allow to register a dummy PHY device in order to
>> be able to perform raw MDIO bus access.
>
> These are not necessarily dummy phy devices, in fact if they were you
> wouldn't be interested in them ;)

Poor choice of words, perhaps :-). Now that I think of it I think
"driver-less" would be a better description.

>
> Do we need a way to register an individual phy? Wouldn't it be enough to
> add a -f(orce) option to register all phys on all busses even if there's
> nothing detected on them?

If we go with "-f" we would still overwhelm the /dev with a lot of
devices (in my use-case 96 of them), it's just we won't do that on the
first run on "miitool".

Andrey

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2016-02-03  0:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01  3:10 [PATCH v2 0/8] Bitbang MDIO, miitool changes Andrey Smirnov
2016-02-01  3:10 ` [PATCH v2 1/8] include/linux/phy.h: Add MII_ADDR_C45 Andrey Smirnov
2016-02-01  3:10 ` [PATCH v2 2/8] net: Port bitbanged MDIO code from Linux kernel Andrey Smirnov
2016-02-01  3:10 ` [PATCH v2 3/8] miitool: Fix PHY argument handling Andrey Smirnov
2016-02-01  3:10 ` [PATCH v2 4/8] mdio_bus: Change dev_info to dev_dbg Andrey Smirnov
2016-02-01  3:10 ` [PATCH v2 5/8] mdio_bus: Add mdiobus_get_bus() function Andrey Smirnov
2016-02-01  3:10 ` [PATCH v2 6/8] miitool: Don't print negative parent IDs Andrey Smirnov
2016-02-01  3:10 ` [PATCH v2 7/8] mdio_bus: Change PHY's naming scheme Andrey Smirnov
2016-02-03  7:36   ` Sascha Hauer
2016-02-03 19:23     ` Andrey Smirnov
2016-02-04  7:47       ` Sascha Hauer
2016-02-01  3:10 ` [PATCH v2 8/8] miitool: Add code to register a PHY Andrey Smirnov
2016-02-01  9:35   ` Sascha Hauer
2016-02-03  0:41     ` Andrey Smirnov [this message]
2016-02-03  7:34       ` Sascha Hauer
2016-02-03 19:20         ` Andrey Smirnov

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='CAHQ1cqGxkLm8axj4TGH4=NnyLjj-HupmD_5Df-tpMgAFsMN9Ug@mail.gmail.com' \
    --to=andrew.smirnov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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