Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1483989
| From | Bryan O'Donoghue <pure.logic@nexus-software.ie> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 |
| Date | 2016-09-15 13:00 +0200 |
| Message-ID | <shCyC-5VC-9@gated-at.bofh.it> (permalink) |
| References | <shfsm-830-21@gated-at.bofh.it> <shmk9-3Lq-3@gated-at.bofh.it> <shmNd-4aI-47@gated-at.bofh.it> <shoFj-5qB-7@gated-at.bofh.it> <shBVV-5HB-57@gated-at.bofh.it> |
| Organization | Nexus Software |
On Thu, 2016-09-15 at 12:17 +0200, Greg KH wrote:
> This
> > is the first I've heard of timesync having a binding. I can't
> imagine
> > why it needs one.
>
> Ah, I'll let Bryan answer that one :)
It's possible we could drop the binding. It was needed to describe the
register location of the MMIO architectural register on MSM8994. I have
this binding ATM the describe fact that get_cycles() on MSM8994 returns
a free-running counter, clocked by refclk and that refclk is provided
to each processor that want to do FrameTime - i.e. the clock driving
get_cycles() comes from PMIC and drives the relevant PLLs on the
downstream processors clocking their respective TMR blocks.
static const struct of_device_id arch_timer_of_match[] = {
{ .compatible = "google,greybus-frame-time-counter", },
{},
};
I'm not aware of a corresponding kernel API that describes the
frequency get_cycles() operates at but if there is one then there's no
need for this binding.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Mark Rutland <mark.rutland@arm.com> - 2016-09-14 19:40 +0200
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Greg KH <gregkh@linuxfoundation.org> - 2016-09-14 20:10 +0200
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Joe Perches <joe@perches.com> - 2016-09-14 21:10 +0200
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Rob Herring <robh@kernel.org> - 2016-09-14 22:10 +0200
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Greg KH <gregkh@linuxfoundation.org> - 2016-09-15 12:20 +0200
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Bryan O'Donoghue <pure.logic@nexus-software.ie> - 2016-09-15 13:00 +0200
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Bryan O'Donoghue <pure.logic@nexus-software.ie> - 2016-09-15 11:40 +0200
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Mark Rutland <mark.rutland@arm.com> - 2016-09-15 12:20 +0200
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Bryan O'Donoghue <pure.logic@nexus-software.ie> - 2016-09-15 12:40 +0200
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Bryan O'Donoghue <pure.logic@nexus-software.ie> - 2016-09-15 12:50 +0200
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Mark Rutland <mark.rutland@arm.com> - 2016-09-15 13:30 +0200
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Bryan O'Donoghue <pure.logic@nexus-software.ie> - 2016-09-15 13:50 +0200
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Mark Rutland <mark.rutland@arm.com> - 2016-09-15 14:50 +0200
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Bryan O'Donoghue <pure.logic@nexus-software.ie> - 2016-09-15 17:40 +0200
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Mark Rutland <mark.rutland@arm.com> - 2016-09-15 17:50 +0200
Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1 Bryan O'Donoghue <pure.logic@nexus-software.ie> - 2016-09-15 18:10 +0200
csiph-web