[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1473936433.10230.46.camel@nexus-software.ie>
Date: Thu, 15 Sep 2016 11:47:13 +0100
From: Bryan O'Donoghue <pure.logic@...us-software.ie>
To: Mark Rutland <mark.rutland@....com>
Cc: Greg KH <gregkh@...uxfoundation.org>,
Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
Johan Hovold <johan@...oldconsulting.com>,
Rui Miguel Silva <rmfrfs@...il.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Sandeep Patil <sspatil@...gle.com>,
Matt Porter <mporter@...nel.crashing.org>,
John Stultz <john.stultz@...aro.org>,
Rob Herring <robh@...nel.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
Alex Elder <elder@...aro.org>, David Lin <dtwlin@...gle.com>,
Vaibhav Agarwal <vaibhav.agarwal@...aro.org>,
Mark Greer <mgreer@...malcreek.com>, marc.zyngier@....com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1
On Thu, 2016-09-15 at 11:35 +0100, Bryan O'Donoghue wrote:
>
Here's a slightly better diagram.
PMIC -> refclk provided to each (timer) element below.
MSM8994(timer) -- > USB
WD8a
APBridgeA (timer) -> UniPro bus
WD8a
-> Module(timer) with UART
WD1
-> Module(timer) with GPIO
WD2
-> Module(timer) with blah
WD3
-> SPI bus
-> SVC(timer)
Owns FrameTime
GPIO {WD0...WDn}
So yes, each processor has it's own timer. We aren't trying to read the
MSM's FrameTime.
---
bod
Powered by blists - more mailing lists