Hi Ohad, On 05/09/2015 03:42 AM, Ohad Ben-Cohen wrote: > Hi Dave, > > On Wed, Apr 1, 2015 at 10:37 PM, Dave Gerlach <d-gerlach@xxxxxx> wrote: >> Add a remoteproc driver to load the firmware and boot a small >> Wakeup M3 processor present on TI AM33xx and AM43xx SoCs. This >> Wakeup M3 remote processor 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 peripherals. > > From a remoteproc point of view this looks generally ok. > > The only non-standard remoteproc aspect here is the handling of the > internal memories. Can you please generally describe how are these > memories being used in the context of remoteproc? The WkupM3 executes its code entirely from this internal RAM. how does the > resource table of your firmware look like - do you also have carveouts > or other resources? We don't have any carveouts or usage of any external DDR, as this processor is used during Power Management, like cpuidle or suspend path, and is used to control the MPU and DDR states. The resource table is very simple and straight-forward [1]. We used to have RSC_INTMEM as part of the resource table in the previous version, but we removed them since that approach was NACKed. regards Suman [1] https://git.ti.com/ti-cm3-pm-firmware/amx3-cm3/blobs/next-upstream/src/sys_exec/rsc_table.h -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
