linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rafal Ozieblo <rafalo@cadence.com>
To: "andrei.pistirica@microchip.com" <andrei.pistirica@microchip.com>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
	"harini.katakam@xilinx.com" <harini.katakam@xilinx.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [RFC PATCH 1/2] macb: Add 1588 support in Cadence GEM.
Date: Fri, 18 Nov 2016 12:05:53 +0000	[thread overview]
Message-ID: <BN3PR07MB2516576760AA9CDF8647973DC9B00@BN3PR07MB2516.namprd07.prod.outlook.com> (raw)

Hello Andrei,

>+static struct ptp_clock_info macb_ptp_caps = {
>+       .owner          = THIS_MODULE,
>+       .name           = GMAC_TIMER_NAME,
>+       .max_adj        = 250000000,
>+       .n_alarm        = 0,
>+       .n_ext_ts       = 0,
>+       .n_per_out      = 0,
>+       .n_pins         = 0,
>+       .pps            = 0,
>+       .adjfreq        = macb_ptp_adjfreq,
>+       .adjtime        = macb_ptp_adjtime,
>+       .gettime64      = macb_ptp_gettime,
>+       .settime64      = macb_ptp_settime,
>+       .enable         = macb_ptp_enable,
>+};

I'm wondering, how did you count max_adj ?

Best regards,

Rafal Ozieblo   |   Firmware System Engineer, 
phone nbr.: +48 32 5085469 


www.cadence.com


 

             reply	other threads:[~2016-11-18 12:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 12:05 Rafal Ozieblo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-02 12:53 [RFC PATCH 1/2] macb: Add 1588 support in Cadence GEM Andrei Pistirica
2016-09-06  7:36 ` Harini Katakam
2016-09-06 15:48 ` Richard Cochran
2016-09-08  4:52   ` Harini Katakam
2016-09-08  7:44     ` Richard Cochran
2016-09-08 19:06     ` Richard Cochran
2016-09-09 13:51   ` Andrei Pistirica

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=BN3PR07MB2516576760AA9CDF8647973DC9B00@BN3PR07MB2516.namprd07.prod.outlook.com \
    --to=rafalo@cadence.com \
    --cc=andrei.pistirica@microchip.com \
    --cc=harini.katakam@xilinx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.ferre@atmel.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 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).