netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harini Katakam <harinikatakamlinux@gmail.com>
To: Andrei Pistirica <andrei.pistirica@microchip.com>
Cc: Rafal Ozieblo <rafalo@cadence.com>,
	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: Re: [RFC PATCH 2/2] net: macb: Add 64 bit addressing support for GEM
Date: Fri, 18 Nov 2016 16:02:03 +0530	[thread overview]
Message-ID: <CAFcVEC+ft7FG2VYo21ifjv4ms+k2_BA98NAtP+Ppudx_8HUYeQ@mail.gmail.com> (raw)
In-Reply-To: <27516aeb-b8f9-dc38-4d01-d2a5c5cf44dd@microchip.com>

tHi Andrei,

>> Yes, Andre's version of Cadence does not ability to report have RX
>> timestamp.
>> The version I worked with did. This is the old series I sent:
>> https://lkml.org/lkml/2015/9/11/92
>> But right now, i'm working on building on top of Andre's changes.
>
>
> I'm addressing maintainer's feedback on both patches:
> https://patchwork.kernel.org/patch/9310989/
> https://patchwork.kernel.org/patch/9310991/
>
> I've done all suggested updates, except the numerous 64bit divisions in the
> frequency adjustment callback. I've implemented a different algorithm which
> uses 2 64bit division, but I couldn't find a way to use only 1.
>
> Also, I have a version with timecounter/cyclecounter which shows a much
> better accuracy (less than 100ns level). In my opinion this could be a
> better implementation. What is you opinion about this? Did you try it?
>

I did not try timecounter on Cadence IP versions later than r1p06.
Because with sub ns precision in HW timestamp, that works better
than SW cyclecounter.
On older Zynq version, yes timecounter is used and is better.

Regards,
Harini

  reply	other threads:[~2016-11-18 10:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 11:50 [RFC PATCH 2/2] net: macb: Add 64 bit addressing support for GEM Rafal Ozieblo
2016-11-17 12:21 ` Harini Katakam
2016-11-17 12:57   ` Rafal Ozieblo
2016-11-17 13:28   ` Nicolas Ferre
2016-11-17 13:35     ` Rafal Ozieblo
2016-11-18  4:29       ` Harini Katakam
2016-11-18  8:59         ` Rafal Ozieblo
2016-11-18  9:10           ` Nicolas Ferre
2016-11-18  9:30             ` Rafal Ozieblo
2016-11-18  9:43               ` Harini Katakam
2016-11-18  9:59                 ` Rafal Ozieblo
2016-11-18 10:03                   ` Harini Katakam
2016-11-18 10:14                   ` Nicolas Ferre
2016-11-18 10:07                 ` Andrei Pistirica
2016-11-18 10:32                   ` Harini Katakam [this message]
2016-11-18  9:58           ` Harini Katakam
2016-11-18 11:28             ` Rafal Ozieblo
  -- strict thread matches above, loose matches on Subject: below --
2016-08-01  7:20 [RFC PATCH 1/2] net: macb: Correct CAPS mask Harini Katakam
2016-08-01  7:20 ` [RFC PATCH 2/2] net: macb: Add 64 bit addressing support for GEM Harini Katakam

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=CAFcVEC+ft7FG2VYo21ifjv4ms+k2_BA98NAtP+Ppudx_8HUYeQ@mail.gmail.com \
    --to=harinikatakamlinux@gmail.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 \
    --cc=rafalo@cadence.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).