All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: "Stefan Sørensen" <stefan.sorensen@spectralink.com>,
	davem@davemloft.net, richardcochran@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/3] dp83640: Program pulsewidth2 values of perout triggers 0 and 1
Date: Wed, 25 Jun 2014 21:50:49 +0400	[thread overview]
Message-ID: <53AB0BF9.3060101@cogentembedded.com> (raw)
In-Reply-To: <1403699851-11178-3-git-send-email-stefan.sorensen@spectralink.com>

Hello.

On 06/25/2014 04:37 PM, Stefan Sørensen wrote:

> Periodic output triggers 0 and 1 of the dp83640 has a programmable
> duty-cycle which is controlled by the Pulsewidth2 field of the trigger
> data register.  This field is not documented in the datasheet, but it
> is described in the "PHYTER Software Development Guide" section
> 3.1.4.1. Failing to set the field can result in unstable/no trigger
> output.

> Add programming of the Pulsewidth2 field, setting it to the same value
> as the Pulsewidth field for a 50% duty cycle.

> Signed-off-by: Stefan Sørensen <stefan.sorensen@spectralink.com>
> ---
>   drivers/net/phy/dp83640.c | 5 +++++
>   1 file changed, 5 insertions(+)

> diff --git a/drivers/net/phy/dp83640.c b/drivers/net/phy/dp83640.c
> index 73fada9..0343b6c 100644
> --- a/drivers/net/phy/dp83640.c
> +++ b/drivers/net/phy/dp83640.c
> @@ -353,6 +353,11 @@ static int periodic_output(struct dp83640_clock *clock,
>   	ext_write(0, phydev, PAGE4, PTP_TDR, sec >> 16);       /* sec[31:16] */
>   	ext_write(0, phydev, PAGE4, PTP_TDR, pwidth & 0xffff); /* ns[15:0] */
>   	ext_write(0, phydev, PAGE4, PTP_TDR, pwidth >> 16);    /* ns[31:16] */
> +	/* Triggers 0 and 1 has programmable pulsewidth2 */
> +	if(trigger < 2) {

    Please run your patches thru scripts/checkpatch.pl -- space is needed 
after *if*.

WBR, Sergei

  reply	other threads:[~2014-06-25 17:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25 12:37 [PATCH net-next 0/3] dp83640: Increase support perout pins Stefan Sørensen
2014-06-25 12:37 ` [PATCH net-next 1/3] ptp: Allow reassigning calibration pin function Stefan Sørensen
2014-06-26  5:21   ` Richard Cochran
2014-06-26  6:14     ` Christian Riesch
2014-06-26  6:16       ` Christian Riesch
2014-06-26 14:57       ` Richard Cochran
2014-06-25 12:37 ` [PATCH net-next 2/3] dp83640: Program pulsewidth2 values of perout triggers 0 and 1 Stefan Sørensen
2014-06-25 17:50   ` Sergei Shtylyov [this message]
2014-06-25 12:37 ` [PATCH net-next 3/3] dp83640: Increase supported perout pins to 7 Stefan Sørensen

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=53AB0BF9.3060101@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=stefan.sorensen@spectralink.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.