From: Richard Cochran <richardcochran@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Dipen Patel <dipenp@nvidia.com>, Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@linaro.org>,
Kent Gibson <warthog618@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-tegra <linux-tegra@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Networking <netdev@vger.kernel.org>
Subject: Re: GTE - The hardware timestamping engine
Date: Tue, 23 Mar 2021 05:51:34 -0700 [thread overview]
Message-ID: <20210323125134.GA29209@hoboy.vegasvil.org> (raw)
In-Reply-To: <YFmu1pptAFQLABe3@orome.fritz.box>
On Tue, Mar 23, 2021 at 10:03:18AM +0100, Thierry Reding wrote:
> I agree. My understanding is the the TSC is basically an SoC-wide clock
> that can be (and is) used by several hardware blocks. There's an
> interface for software to read out the value, but it's part of a block
> called TKE (time-keeping engine, if I recall correctly) that implements
> various clock sources and watchdog functionality.
...
> Anyway, I think given that the GTE doesn't provide that clock itself but
> rather just a means of taking a snapshot of that clock and stamping
> certain events with that, it makes more sense to provide that clock from
> the TKE driver.
It sounds like TKE + GTE together act like a PHC, and GTE doesn't
need/want its own SW interface.
Thanks,
Richard
next prev parent reply other threads:[~2021-03-23 12:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 22:33 GTE - The hardware timestamping engine Dipen Patel
2021-03-20 11:56 ` Linus Walleij
2021-03-20 12:44 ` Arnd Bergmann
2021-03-20 15:38 ` Richard Cochran
2021-03-22 20:33 ` Dipen Patel
2021-03-23 9:03 ` Thierry Reding
2021-03-23 12:51 ` Richard Cochran [this message]
2021-03-22 6:00 ` Kent Gibson
2021-03-22 20:21 ` Dipen Patel
2021-03-23 0:32 ` Kent Gibson
2021-03-23 1:53 ` Dipen Patel
2021-03-23 2:59 ` Kent Gibson
2021-03-23 4:09 ` Dipen Patel
2021-03-23 5:22 ` Kent Gibson
2021-03-23 9:08 ` Linus Walleij
2021-03-23 10:06 ` Thierry Reding
2021-03-23 18:21 ` Marc Zyngier
2021-03-23 18:25 ` Dipen Patel
2021-03-23 21:19 ` Dipen Patel
2021-03-23 18:01 ` Dipen Patel
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=20210323125134.GA29209@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=arnd@arndb.de \
--cc=bgolaszewski@baylibre.com \
--cc=dipenp@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=warthog618@gmail.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).