From: yfw <fengwei.yin@linaro.org>
To: Bjorn Andersson <bjorn.andersson@sonymobile.com>
Cc: Andy Gross <agross@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-soc@vger.kernel.org" <linux-soc@vger.kernel.org>
Subject: Re: [PATCH] soc: qcom: Introduce WCNSS_CTRL SMD client
Date: Fri, 23 Oct 2015 19:37:25 +0800 [thread overview]
Message-ID: <562A1BF5.2030900@linaro.org> (raw)
In-Reply-To: <20151022135056.GV24668@usrtlx11787.corpusers.net>
Hi Bjorn,
On 2015/10/22 21:50, Bjorn Andersson wrote:
> On Thu 22 Oct 03:25 PDT 2015, yfw wrote:
>
>> Hi Bjorn,
>>
>> On 2015/9/22 1:52, Bjorn Andersson wrote:
> [..]
>>
>> I have a question: Do you have plan to add the nob to trigger wcnss firmware
>> downloading which is also common for wifi and BT?
>>
>
> In caf the wcnss driver is actually two drivers intermingled;
> * a SMD client driver, responsible for pushing NV, something related to
> calibration, some power properties and so on
>
> * a platform_driver implementing the wcnss specifics of the PIL through
> some hooks and providing the knob to trigger the PIL.
>
> The first driver is related to the "OS" running on the wcnss, so that
> should follow the life cycle of the SMD channel "WCNSS_CTRL". This is
> what this patch provides - it loads the NV every time the wcnss core is
> booted.
>
>
> For the second part, I strongly believe that the PIL implementation
> should deal with the specifics (e.g. regulator handling and
> xo_calibration), rather than having a piece bolted on elsewhere - so
> that's in the remoteproc-wcnss driver.
>
Yes. I meant this remoteproc-wcnss driver. Will you try to upstream it?
>
> 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 do have the same thing in e.g. the Broadcom WiFi/BT solution and
> there seems to be discussions related to this.
>
>
> So for now, I punted and put a knob in the wcnss remoteproc driver.
>
> Regards,
> Bjorn
>
Regards
Yin, Fengwei
next prev parent reply other threads:[~2015-10-23 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 17:52 [PATCH] soc: qcom: Introduce WCNSS_CTRL SMD client Bjorn Andersson
2015-09-21 17:52 ` Bjorn Andersson
2015-09-22 18:03 ` yfw
2015-10-22 10:25 ` yfw
2015-10-22 13:50 ` Bjorn Andersson
2015-10-23 11:37 ` yfw [this message]
2015-10-23 13:41 ` Bjorn Andersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=562A1BF5.2030900@linaro.org \
--to=fengwei.yin@linaro.org \
--cc=agross@codeaurora.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.