netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v4 net-next] net: phy: Add Edge-rate driver for Microsemi PHYs.
Date: Wed, 28 Sep 2016 18:16:53 +0200	[thread overview]
Message-ID: <20160928161653.GA25553@lunn.ch> (raw)
In-Reply-To: <1475062449-22168-1-git-send-email-Raju.Lakkaraju@microsemi.com>

> +Optional properties:
> +- vsc8531,vddmac	: The vddmac in mV.
> +- vsc8531,edge-slowdown	: % the edge should be slowed down relative to
> +			  the fastest possible edge time. Native sign
> +			  need not enter.
> +			  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.  The goal of this setting is to help
> +			  reduce electrical emission (EMI) by being able
> +			  to reprogram drive strength and in effect slow
> +			  down the edge rate if desired.  Table 5 shows the

Hi Raju

There is no table five here? Is that a reference to a data sheet
table?

> +Example:
> +
> +        vsc8531_0: ethernet-phy@0 {
> +                compatible = "ethernet-phy-id0007.0570";
> +                vsc8531,vddmac		= /bits/ 16 <MSCC_VDDMAC_3300>;
> +                vsc8531,edge-slowdown	= /bits/ 8  <17>;

No, real values please:

                vsc8531,vddmac		= <2000>;
                vsc8531,edge-slowdown	= <21>;

The driver should then do the maths to figure out the nearest magic
value to write to the register, or complain the settings are out of
range with an -EINVAL.

FYI: No floating point maths are allowed in the kernel.

   Andrew

  reply	other threads:[~2016-09-28 16:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28 11:34 [PATCH v4 net-next] net: phy: Add Edge-rate driver for Microsemi PHYs Raju Lakkaraju
2016-09-28 16:16 ` Andrew Lunn [this message]
     [not found]   ` <20160928161653.GA25553-g2DYL2Zd6BY@public.gmane.org>
2016-10-03  7:20     ` Raju Lakkaraju
2016-10-03  7:56       ` Andrew Lunn
     [not found]         ` <20161003075656.GC18219-g2DYL2Zd6BY@public.gmane.org>
2016-10-03  9:23           ` Raju Lakkaraju

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=20160928161653.GA25553@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).