diff for duplicates of <1473935756.10230.42.camel@nexus-software.ie> diff --git a/a/1.txt b/N1/1.txt index fcb64f7..6d7fccd 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,6 +1,6 @@ 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 @@ -24,23 +24,23 @@ processor in the system. > > * 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. > and duplicates information we have -> ? elsewhere. +> elsewhere. Can you give an example ? > It does not explicitly define the relationship with the -> ? underlying clocksource. +> underlying clocksource. > * 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 @@ -79,13 +79,13 @@ No. The MMIO timers are useful only to the MSM. We don't have any type of parallel (or serial) bus that can access that on-chip resource. 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 942813e..47a837b 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,15 +4,32 @@ "ref\020160914182952.GA21615@kroah.com\0" "ref\01473932133.10230.25.camel@nexus-software.ie\0" "ref\020160915101330.GB6718@leverpostej\0" - "From\0pure.logic@nexus-software.ie (Bryan O'Donoghue)\0" - "Subject\0[GIT PULL] Greybus driver subsystem for 4.9-rc1\0" + "From\0Bryan O'Donoghue <pure.logic@nexus-software.ie>\0" + "Subject\0Re: [GIT PULL] Greybus driver subsystem for 4.9-rc1\0" "Date\0Thu, 15 Sep 2016 11:35:56 +0100\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Mark Rutland <mark.rutland@arm.com>\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" "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" @@ -36,23 +53,23 @@ "> \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" "> and duplicates information we have\n" - "> ? elsewhere.\n" + "> \302\240 elsewhere.\n" "\n" "Can you give an example ?\n" "\n" "> It does not explicitly define the relationship with the\n" - "> ? underlying clocksource.\n" + "> \302\240 underlying clocksource.\n" "\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" @@ -91,13 +108,13 @@ "of parallel (or serial) bus that can access that on-chip resource.\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" @@ -107,4 +124,4 @@ "---\n" bod -044722f94cccff15218e69a031dcc2289205b68bfdb5c112639c9db9bd2c33aa +debbab2aa3e52575dab89cc6eca97b24a5b9a620c3cbfe6564e2acce6462684b
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.