From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: gregkh@linuxfoundation.org, arnd@arndb.de, mark.rutland@arm.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
bjorn.andersson@linaro.org, bkumar@qti.qualcomm.com,
linux-arm-msm@vger.kernel.org, thierry.escande@linaro.org
Subject: Re: [PATCH v3 1/5] misc: dt-bindings: Add Qualcomm Fastrpc bindings
Date: Wed, 16 Jan 2019 09:44:57 +0000 [thread overview]
Message-ID: <113dc31e-c17d-4df0-b275-9f2d09591037@linaro.org> (raw)
In-Reply-To: <20190115202206.GA4849@bogus>
Thanks for the review!
On 15/01/2019 20:22, Rob Herring wrote:
> On Mon, Jan 14, 2019 at 07:41:08PM +0000, Srinivas Kandagatla wrote:
>> The FastRPC driver implements an IPC (Inter-Processor Communication)
>> mechanism that allows for clients to transparently make remote method
>> invocations across DSP and APPS boundaries. This enables developers
>> to offload tasks to the DSP and free up the application processor for
>> other tasks.
>>
>> Co-developed-by: Thierry Escande <thierry.escande@linaro.org>
>> Signed-off-by: Thierry Escande <thierry.escande@linaro.org>
>> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
>> ---
>> .../devicetree/bindings/misc/qcom,fastrpc.txt | 84 +++++++++++++++++++
>> 1 file changed, 84 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/misc/qcom,fastrpc.txt
>>
>> diff --git a/Documentation/devicetree/bindings/misc/qcom,fastrpc.txt b/Documentation/devicetree/bindings/misc/qcom,fastrpc.txt
>> new file mode 100644
>> index 000000000000..004e636b4133
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/misc/qcom,fastrpc.txt
>> @@ -0,0 +1,84 @@
>> +Qualcomm Technologies, Inc. FastRPC Driver
>> +
>> +The FastRPC driver implements an IPC (Inter-Processor Communication)
>
> driver or this is a h/w block?
This is a software/firmware block in Hexagon DSP.
>
>> +mechanism that allows for clients to transparently make remote method
>> +invocations across DSP and APPS boundaries. This enables developers
>> +to offload tasks to the DSP and free up the application processor for
>> +other tasks.
>> +
>> +- compatible:
>> + Usage: required
>> + Value type: <stringlist>
>> + Definition: must be "qcom,fastrpc"
>> +
>> +- label
>> + Usage: required
>> + Value type: <string>
>> + Definition: should specify the dsp domain name this fastrpc
>> + corresponds to. must be one of this: "adsp", "mdsp", "sdsp", "cdsp"
>> +
>> +- #address-cells
>> + Usage: required
>> + Value type: <u32>
>> + Definition: Must be 1
>> +
>> +- #size-cells
>> + Usage: required
>> + Value type: <u32>
>> + Definition: Must be 0
>> +
>> += COMPUTE BANKS
>> +Each subnode of the Fastrpc node represents compute context banks available
>> +on the dsp. The name of the nodes are not important. The properties of these
>
> Please specify what the node names are.
Sure, these are compute context banks, will reword this accordingly.
>
>> +nodes are defined by the individual bindings for the specific service
>> +- All Compute context banks MUST contain the following property:
>> +
>> +- compatible:
>> + Usage: required
>> + Value type: <stringlist>
>> + Definition: must be "qcom,fastrpc-compute-cb"
>> +
>> +- reg
>> + Usage: required
>> + Value type: <u32>
>> + Definition: Context Bank ID.
>> +
>> +- secured:
>> + Usage: Optional
>> + Value type: <boolean>
>> + Defination: Indicating context bank is secured
>
> What does 'secured' mean here?
>
secured in TZ sense, this context requires secure buffers to work with.
>> +
>> +- nsessions:
>> + Usage: Optional
>> + Value type: <u32>
>> + Defination: A value indicating how many sessions can share this
>> + context bank. Defaults to 1 when this property
>> + is not specified.
>
> Needs a vendor prefix.
>
Sure, will do that in next version!
>> +
>> +Example:
>> +
>> +adsp-pil {
>> + compatible = "qcom,msm8996-adsp-pil";
>> + ...
>> + smd-edge {
>> + label = "lpass";
>> + fastrpc {
>> + compatible = "qcom,fastrpc";
>> + qcom,smd-channels = "fastrpcsmd-apps-dsp";
>> + lable = "adsp";
>
> typo.
Thanks for spotting this.. will fix this!
--srini
next prev parent reply other threads:[~2019-01-16 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 19:41 [PATCH v3 0/5] misc: Add support to Qualcomm FastRPC driver Srinivas Kandagatla
2019-01-14 19:41 ` [PATCH v3 1/5] misc: dt-bindings: Add Qualcomm Fastrpc bindings Srinivas Kandagatla
2019-01-15 20:22 ` Rob Herring
2019-01-16 9:44 ` Srinivas Kandagatla [this message]
2019-01-14 19:41 ` [PATCH v3 2/5] misc: fastrpc: Add Qualcomm fastrpc basic driver model Srinivas Kandagatla
2019-01-14 19:41 ` [PATCH v3 3/5] misc: fastrpc: Add support for context Invoke method Srinivas Kandagatla
2019-01-14 19:41 ` [PATCH v3 4/5] misc: fastrpc: Add support for create remote init process Srinivas Kandagatla
2019-01-14 19:41 ` [PATCH v3 5/5] misc: fastrpc: Add support for dmabuf exporter Srinivas Kandagatla
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=113dc31e-c17d-4df0-b275-9f2d09591037@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=bkumar@qti.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=thierry.escande@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).