diff for duplicates of <20160915112029.GC6718@leverpostej> diff --git a/a/1.txt b/N1/1.txt index cac9e93..5351e5e 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -14,7 +14,7 @@ for the series. On Thu, Sep 15, 2016 at 11:35:56AM +0100, Bryan O'Donoghue wrote: > On Thu, 2016-09-15 at 11:13 +0100, Mark Rutland wrote: > > On Thu, Sep 15, 2016 at 10:35:33AM +0100, Bryan O'Donoghue wrote: -> > >? +> > > > > I don't think the history matters, > > Your comment seemed to indicate you thought we were reading a @@ -52,7 +52,7 @@ today on some platform, it is in no way *guaranteed*. > > > > * The "google,greybus-frame-time-counter" node is superfluous. It > > does -> > ? not describe a particular device, +> > not describe a particular device, > > It describes a timer running @ 19.2MHz, clocked by PMIC refclk. @@ -64,7 +64,7 @@ Given that, as far as I can tell, "google,greybus-frame-time-counter" describes a software construct that uses this, not an actual piece of hardware. -> > and duplicates information we have ? elsewhere. +> > and duplicates information we have elsewhere. > > Can you give an example ? @@ -75,9 +75,9 @@ Note that isn't guaranteed to match get_cycles() either. You need a better API to call. > > * The clock-frequency property isn't necessary. The architected timer -> > ? drivers know the frequency of the architected timers (MMIO or +> > drivers know the frequency of the architected timers (MMIO or > > sysreg), -> > ? and they should be queried as to the frequency. +> > and they should be queried as to the frequency. > > OK so if I'm understanding you. You think get_cycles() is fine but that > instead of encoding a "greybus-frame-time-counter" the platform code @@ -137,13 +137,13 @@ other devices within the SoC (e.g. anything other than the CPUs running this instance of Linux). > MSM8994 -- > USB -> ? ? ? ? ? ? ?APBridge (timer) -> UniPro bus -> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? -> Module with a UART -> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? -> Module with a GPIO -> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? -> Module with an etc, etc -> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? -> SPI bus -> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? -> SVC -> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?Owns FrameTime +> APBridge (timer) -> UniPro bus +> -> Module with a UART +> -> Module with a GPIO +> -> Module with an etc, etc +> -> SPI bus +> -> SVC +> Owns FrameTime > > So the SVC owns FrameTime and diseminates that to other entities in the > system by way of a GPIO and greybus. It's up to the MSM8994 to select a diff --git a/a/content_digest b/N1/content_digest index 5388576..9e6f68e 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,10 +5,27 @@ "ref\01473932133.10230.25.camel@nexus-software.ie\0" "ref\020160915101330.GB6718@leverpostej\0" "ref\01473935756.10230.42.camel@nexus-software.ie\0" - "From\0mark.rutland@arm.com (Mark Rutland)\0" - "Subject\0[GIT PULL] Greybus driver subsystem for 4.9-rc1\0" + "From\0Mark Rutland <mark.rutland@arm.com>\0" + "Subject\0Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1\0" "Date\0Thu, 15 Sep 2016 12:20:29 +0100\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Bryan O'Donoghue <pure.logic@nexus-software.ie>\0" + "Cc\0Greg KH <gregkh@linuxfoundation.org>" + Arnd Bergmann <arnd@arndb.de> + linux-kernel@vger.kernel.org + Johan Hovold <johan@hovoldconsulting.com> + Rui Miguel Silva <rmfrfs@gmail.com> + Laurent Pinchart <laurent.pinchart@ideasonboard.com> + Sandeep Patil <sspatil@google.com> + Matt Porter <mporter@kernel.crashing.org> + John Stultz <john.stultz@linaro.org> + Rob Herring <robh@kernel.org> + Viresh Kumar <viresh.kumar@linaro.org> + Alex Elder <elder@linaro.org> + David Lin <dtwlin@google.com> + Vaibhav Agarwal <vaibhav.agarwal@linaro.org> + Mark Greer <mgreer@animalcreek.com> + marc.zyngier@arm.com + " linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "Hi,\n" @@ -27,7 +44,7 @@ "On Thu, Sep 15, 2016 at 11:35:56AM +0100, Bryan O'Donoghue wrote:\n" "> On Thu, 2016-09-15 at 11:13 +0100, Mark Rutland wrote:\n" "> > On Thu, Sep 15, 2016 at 10:35:33AM +0100, Bryan O'Donoghue wrote:\n" - "> > >?\n" + "> > >\302\240\n" "> > I don't think the history matters, \n" "> \n" "> Your comment seemed to indicate you thought we were reading a\n" @@ -65,7 +82,7 @@ "> > \n" "> > * The \"google,greybus-frame-time-counter\" node is superfluous. It\n" "> > does\n" - "> > ? not describe a particular device,\n" + "> > \302\240 not describe a particular device,\n" "> \n" "> It describes a timer running @ 19.2MHz, clocked by PMIC refclk.\n" "\n" @@ -77,7 +94,7 @@ "describes a software construct that uses this, not an actual piece of\n" "hardware.\n" "\n" - "> > and duplicates information we have ? elsewhere.\n" + "> > and duplicates information we have \302\240 elsewhere.\n" "> \n" "> Can you give an example ?\n" "\n" @@ -88,9 +105,9 @@ "better API to call.\n" "\n" "> > * The clock-frequency property isn't necessary. The architected timer\n" - "> > ? drivers know the frequency of the architected timers (MMIO or\n" + "> > \302\240 drivers know the frequency of the architected timers (MMIO or\n" "> > sysreg),\n" - "> > ? and they should be queried as to the frequency.\n" + "> > \302\240 and they should be queried as to the frequency.\n" "> \n" "> OK so if I'm understanding you. You think get_cycles() is fine but that\n" "> instead of encoding a \"greybus-frame-time-counter\" the platform code\n" @@ -150,13 +167,13 @@ "this instance of Linux).\n" "\n" "> MSM8994 -- > USB\n" - "> ? ? ? ? ? ? ?APBridge (timer) -> UniPro bus\n" - "> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? -> Module with a UART\n" - "> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? -> Module with a GPIO\n" - "> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? -> Module with an etc, etc\n" - "> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? -> SPI bus\n" - "> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? -> SVC\n" - "> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?Owns FrameTime\n" + "> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240APBridge (timer) -> UniPro bus\n" + "> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 -> Module with a UART\n" + "> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 -> Module with a GPIO\n" + "> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 -> Module with an etc, etc\n" + "> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 -> SPI bus\n" + "> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 -> SVC\n" + "> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240Owns FrameTime\n" "> \n" "> So the SVC owns FrameTime and diseminates that to other entities in the\n" "> system by way of a GPIO and greybus. It's up to the MSM8994 to select a\n" @@ -173,4 +190,4 @@ "Thanks,\n" Mark. -7583229edd4b56d65b1f57f591716afa3f1bc06b2f02a05a986f435920b8805c +a1abdcbc3f0e26cd541eac513569d37d45f058e2bb7db12c70804af0e44cd23e
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.