RE: Remoteproc adaptations for ST-Ericsson modems
From: Sjur BRENDELAND
Date: Tue May 08 2012 - 09:28:07 EST
>> 2. Physical addressing:
>> Support for specifying physical memory locations in resource table.
>> We need some way to specify physical memory locations instead of using
>> carveouts. The physical address will be outside the allocatable Linux
> Can you please share more details about the use case ? is this a
> hardware limitation or a policy (i.e. by reserving memory using the
> boot argument mem=) ?
For the C2C memory we don't have a IOMMU between memory and modem.
(There is some black magic using a offset register etc, but this is
all setup in the Linux boot loader.) So seen from Linux kernel point
of view we're working with a fixed physical address for the shared
> Can you make this memory allocatable via the DMA API (e.g. via CMA or
> dma_declare_coherent_memory) ?
Yes, I might be able to do just that. I wasn't aware of this function.
Nice! This way I don't need any other tweaks for the memory allocation
in remoteproc either - Very nice!
>> Skip the dependency on a driver:
> Not sure I'm following. Care to elaborate ?
I was trying to point out that I might call remoteproc from a
module_init function and not from a device driver. But I'm starting
to realize that both firmware-loading and dma_declare_coherent_memory
requires to work on a device. So let's just forget about this point.
>> Skip load of firmware during early boot:
>> I probably missed something, but this feature doesn't make sense
>> to me.
> This mechanism registers the virito devices that are supported by the
> Relevant drivers (if any) will then get probed, and may then power up
> the remote processor (if needed).
> > Also it causes big warning from sysfs if I don't finish
> > the async loading before starting the blocking loading of firmware.
> Can you explain how you triggered this ? Are you using
> rproc_get_by_name() ?
No, I trigger this warning by calling rproc_register() and rproc_boot()
in sequence from a remoteproc client without using rpmsg. If you haven't
finished the asynchronous loading of firmware initiated by
rproc_register() and call rproc_boot() immediately after you will get
a warning when initiating synchronous firmware loading from rproc_boot().
This is caused by loading the firmware for the same device twice
> > And I fail to see the need for it.
> Without it, no virtio driver is going to be probed - we don't
> statically register virtio devices, because we don't know what kind of
> functionality the remote processor supports without loading the
> firmware first.
Ok, I see. You have a chicken and egg problem. And solve this by loading
the firmware twice. If I understand correctly you do something like this:
1. rproc-client does rproc_alloc() and rproc_register()
2. This trigger loading of firmware asynchronously.
3. Resource table is scanned for virtio device and virtio device
4. Registration cause probing of rpmsg virtio driver
5. rpmsg virtio driver calls rproc_boot() from probe function.
6. remote_proc loads downloads firmware, parses the resource table 2nd time.
7. rproc->ops->load() is called and DSP is loaded and started.
>> I think it would be nice to be able to turn this feature off.
> Care to explain why ? what exactly do you want to do that you can't
> today ?
The difference is that I am not planning to call rproc_boot()
from rpmsg, but trigger booting from user space using sysfs. In this
case I don't need to probe any virtio drivers in order to trigger
the call of rproc_boot(). Consequently I don't need to load firmware twice.
So I think I'd like to see the following sequence:
1. rproc-client calls rproc_alloc() and rproc_register()
2. User space initiates booting via sysfs, causing rproc_boot() to be
3. remoteproc initiates synchronous firmware loading.
4. resource table is scanned once, handling all resource entries
including virtio device registration.
5. rproc->ops->load() is called and DSP is loaded and started.
It would be good to know if this approach makes sense for you. And if
you agree, I'd like to get your view on how you think we could support
this in remoteproc. ie. do you approve of the feature bit I proposed,
or do you have something else in mind?
>> Below is a stab at supporting non-ELF binaries and disabling the
>> pre-loading of ELF.
> It's in the TODO list of remoteproc, but unfortunately not a high
> priority for me...
OK, good to know.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/