Ohad,
On 09/17/2014 08:37 AM, Ohad Ben-Cohen wrote: Hi Suman,
On Tue, Sep 16, 2014 at 7:14 PM, Suman Anna s-a...@ti.com wrote:
The current remoteproc infrastructure automatically calls rproc_boot only
as part of the rpmsg/virtio stack (in remoteproc_virtio.c), but since the
WkupM3 does not
Hi Suman,
On Tue, Sep 16, 2014 at 7:14 PM, Suman Anna s-a...@ti.com wrote:
The current remoteproc infrastructure automatically calls rproc_boot
only as part of the rpmsg/virtio stack (in remoteproc_virtio.c), but
since the WkupM3 does not use rpmsg, there is no automatic booting of
the WkupM3
On Wed, Sep 10, 2014 at 12:10 AM, Kevin Hilman khil...@kernel.org wrote:
What I think you need to do (and what I've recommended at least once in
earlier reviews) put all the (non-rproc) wkup_m3 IPC into into one
driver and create a well-described, well-documented API that the
platform PM code
Hi Ohad,
On 09/16/2014 10:08 AM, Ohad Ben-Cohen wrote:
On Wed, Sep 10, 2014 at 12:10 AM, Kevin Hilman khil...@kernel.org wrote:
What I think you need to do (and what I've recommended at least once in
earlier reviews) put all the (non-rproc) wkup_m3 IPC into into one
driver and create a
Kevin,
On 09/09/2014 04:10 PM, Kevin Hilman wrote:
Dave Gerlach d-gerl...@ti.com writes:
Kevin/Ohad,
On 09/09/2014 02:59 PM, Suman Anna wrote:
Hi Ohad,
On 09/09/2014 05:31 AM, Ohad Ben-Cohen wrote:
On Tue, Sep 9, 2014 at 1:30 AM, Kevin Hilman khil...@linaro.org wrote:
To me, it's not
On Tue, Sep 9, 2014 at 1:30 AM, Kevin Hilman khil...@linaro.org wrote:
To me, it's not terribly clear how you made the split between this PM
core code an the remoteproc code. In the changelog for the remoteproc
patch, it states it's to load the firmware for and boot the wkup_m3.
But, while
Hi Ohad,
On 09/09/2014 05:31 AM, Ohad Ben-Cohen wrote:
On Tue, Sep 9, 2014 at 1:30 AM, Kevin Hilman khil...@linaro.org wrote:
To me, it's not terribly clear how you made the split between this PM
core code an the remoteproc code. In the changelog for the remoteproc
patch, it states it's to
Kevin/Ohad,
On 09/09/2014 02:59 PM, Suman Anna wrote:
Hi Ohad,
On 09/09/2014 05:31 AM, Ohad Ben-Cohen wrote:
On Tue, Sep 9, 2014 at 1:30 AM, Kevin Hilman khil...@linaro.org wrote:
To me, it's not terribly clear how you made the split between this PM
core code an the remoteproc code. In the
Dave Gerlach d-gerl...@ti.com writes:
Kevin/Ohad,
On 09/09/2014 02:59 PM, Suman Anna wrote:
Hi Ohad,
On 09/09/2014 05:31 AM, Ohad Ben-Cohen wrote:
On Tue, Sep 9, 2014 at 1:30 AM, Kevin Hilman khil...@linaro.org wrote:
To me, it's not terribly clear how you made the split between this PM
+Ohad
Dave Gerlach d-gerl...@ti.com writes:
AM335x supports various low power modes as documented
in section 8.1.4.3 of the AM335x Technical Reference Manual.
DeepSleep0 mode offers the lowest power mode with limited
wakeup sources without a system reboot and is mapped as
the suspend state
AM335x supports various low power modes as documented
in section 8.1.4.3 of the AM335x Technical Reference Manual.
DeepSleep0 mode offers the lowest power mode with limited
wakeup sources without a system reboot and is mapped as
the suspend state in the kernel. In this state, MPU and
PER domains
11 matches
Mail list logo
