From: Andrew Lunn <andrew@lunn.ch>
To: Raju Lakkaraju <Raju.Lakkaraju@microsemi.com>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
f.fainelli@gmail.com, Allan.Nielsen@microsemi.com
Subject: Re: [PATCH v3 net-next] net: phy: Add Edge-rate driver for Microsemi PHYs.
Date: Tue, 27 Sep 2016 16:16:33 +0200 [thread overview]
Message-ID: <20160927141633.GJ28432@lunn.ch> (raw)
In-Reply-To: <1474984075-12312-1-git-send-email-Raju.Lakkaraju@microsemi.com>
> index 0000000..7ba3855
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/mscc-phy-vsc8531.txt
> @@ -0,0 +1,61 @@
> +* Microsemi - vsc8531 Giga bit ethernet phy
> +
> +Required properties:
> +- compatible : Should contain phy id as "ethernet-phy-idAAAA.BBBB"
> + If the phy's identifier is known then the list may contain an entry
> + of the form: "ethernet-phy-idAAAA.BBBB" where
> + AAAA - The value of the 16 bit Phy Identifier 1 register as
> + 4 hex digits. This is the chip vendor OUI bits 3:18
> + BBBB - The value of the 16 bit Phy Identifier 2 register as
> + 4 hex digits. This is the chip vendor OUI bits 19:24,
> + followed by 10 bits of a vendor specific ID.
> +- reg : The ID number for the phy, usually a small integer
Please don't copy phy.txt. Just refer to it. Use text like:
The PHY device uses the binding described in
Documentation/devicetree/bindings/net/phy.txt
It may additionally have the following properties
> +Optional properties:
> +- vsc8531,edge-rate : Edge rate sets the drive strength of the MAC
> + interface output signals. Changing the drive
> + strength will affect the edge rate of the output
> + signal.
Are we specifying a rate or a strength? It is called edge-rate, so it
expect it to be a rate, mV/pS or something similar.
Andrew
next prev parent reply other threads:[~2016-09-27 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 13:47 [PATCH v3 net-next] net: phy: Add Edge-rate driver for Microsemi PHYs Raju Lakkaraju
2016-09-27 14:16 ` Andrew Lunn [this message]
2016-09-27 14:26 ` Allan W. Nielsen
[not found] ` <20160927142659.GC10776-dzo6w/eZyo2tG0bUXCXiUA@public.gmane.org>
2016-09-27 14:58 ` Andrew Lunn
2016-09-28 11:09 ` Raju Lakkaraju
-- strict thread matches above, loose matches on Subject: below --
2016-09-26 13:48 Raju Lakkaraju
[not found] ` <1474897705-30802-1-git-send-email-Raju.Lakkaraju-dzo6w/eZyo2tG0bUXCXiUA@public.gmane.org>
2016-09-26 15:12 ` 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=20160927141633.GJ28432@lunn.ch \
--to=andrew@lunn.ch \
--cc=Allan.Nielsen@microsemi.com \
--cc=Raju.Lakkaraju@microsemi.com \
--cc=devicetree@vger.kernel.org \
--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).