Re: [PATCH] soc: qcom: Introduce WCNSS_CTRL SMD client

[Bjorn Andersson]

On Fri, Oct 23, 2015 at 4:37 AM, yfw <fengwei.yin@xxxxxxxxxx> wrote:
[..]
> Yes. I meant this remoteproc-wcnss driver. Will you try to upstream it?
>

https://lkml.org/lkml/2015/9/26/10

I thought I got you on the Cc on that series, sorry about that. I will
resend it once we have smsm/smp2p so that the kbuild robot doesn't
have a chance to shoot it down. (But no planned functional change so
far)

>>
>> Left is a mechanism to trigger the thing to boot and shutdown. One
>> potential solution would be to have the module_init/exit call
>> rproc_boot/shutdown from the WiFi & BT drivers. That way if one loads
>> the wcn36xx driver, the core is booted. This would also fit quite nicely
>> for other things - e.g. load the ALSA driver to trigger the ADSP
>> loading.
>>
>> The problem here is that we're then forced to either have a method of
>> deferring the rproc_boot() until the firmware is available or we always
>> must compile these drivers as kernel modules. This because the
>> file system isn't there during boot to provide the firmware.
>
> The firmware file could be put to initrd. That should allow wcn wifi driver
> builtin.
>

We have the same puzzle to solve for adsp, venus and the modem. And
the combined size of all these makes it practically infeasible to do
so.

Regards,
Bjorn
--
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/