* Felipe Balbi ba...@ti.com [150105 12:23]:
On Mon, Jan 05, 2015 at 02:10:14PM -0600, Dave Gerlach wrote:
+static int wkup_m3_rpm_suspend(struct device *dev)
+{
+return -EBUSY;
+}
looks like this is just coping with omap_device bogosity, no ?
Yes, without this
Felipe,
On 01/02/2015 02:04 PM, Felipe Balbi wrote:
On Fri, Jan 02, 2015 at 01:51:59PM -0600, Dave Gerlach wrote:
Add a remoteproc driver to load the firmware for and boot the wkup_m3
present on am33xx. The wkup_m3 is an integrated Cortex M3 that allows
the SoC to enter the lowest possible
Hi,
On Mon, Jan 05, 2015 at 02:10:14PM -0600, Dave Gerlach wrote:
Add a remoteproc driver to load the firmware for and boot the wkup_m3
present on am33xx. The wkup_m3 is an integrated Cortex M3 that allows
the SoC to enter the lowest possible power state by taking control from
the MPU
Add a remoteproc driver to load the firmware for and boot the wkup_m3
present on am33xx. The wkup_m3 is an integrated Cortex M3 that allows
the SoC to enter the lowest possible power state by taking control from
the MPU after it has gone into its own low power state and shutting off
any additional
On Fri, Jan 02, 2015 at 01:51:59PM -0600, Dave Gerlach wrote:
Add a remoteproc driver to load the firmware for and boot the wkup_m3
present on am33xx. The wkup_m3 is an integrated Cortex M3 that allows
the SoC to enter the lowest possible power state by taking control from
the MPU after it has
Add a remoteproc driver to load the firmware for and boot the wkup_m3
present on am33xx. The wkup_m3 is an integrated Cortex M3 that allows
the SoC to enter the lowest possible power state by taking control from
the MPU after it has gone into its own low power state and shutting off
any additional
