public inbox for linux-remoteproc@vger.kernel.org
 help / color / mirror / Atom feed
From: Rohit Kumar <rohitkr@codeaurora.org>
To: Rob Herring <robh@kernel.org>
Cc: ohad@wizery.com, bjorn.andersson@linaro.org,
	mark.rutland@arm.com, linux-remoteproc@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	bgoswami@codeaurora.org, sbpata@codeaurora.org
Subject: Re: [PATCH v2] remoteproc: qcom: Introduce Non-PAS ADSP PIL driver
Date: Fri, 3 Aug 2018 16:53:05 +0530	[thread overview]
Message-ID: <be77dbce-49aa-862f-0192-f0264b5aa588@codeaurora.org> (raw)
In-Reply-To: <43dcb60b-720f-27ab-3696-dbf0fe0b65fc@codeaurora.org>

Hello Bjorn,


Can you please let us know the suggest the file name and review the patch.


On 7/9/2018 11:29 AM, Rohit Kumar wrote:
> Thanks Rob for reviewing.
>
>
> On 7/7/2018 2:02 AM, Rob Herring wrote:
>> On Fri, Jun 29, 2018 at 02:50:53PM +0530, Rohit kumar wrote:
>>> This adds APSS based ADSP PIL driver for QCOM SoCs.
>>> Added initial support for SDM845 with ADSP bootup and
>>> shutdown operation handled from Application Processor
>>> SubSystem(APSS).
>>>
>>> Signed-off-by: Rohit kumar <rohitkr@codeaurora.org>
>>> ---
>>> Changes since v1:
>>> - Used APIs from qcom_q6v5.c
>>> - Use clock, reset and regmap driver APIs instead of
>>>    directly writing into the LPASS registers.
>>> - Created new file for non PAS ADSP PIL instead of extending
>>>    existing ADSP PIL driver.
>>> - cleanups as suggested by Bjorn and Rob.
>>>
>>>   .../bindings/remoteproc/qcom,non-pas-adsp.txt      | 138 +++++
>> This should be a separate patch.
>
> Ok. Will separate it in next spin.
>>> drivers/remoteproc/Kconfig                         |  18 +
>>>   drivers/remoteproc/Makefile                        |   1 +
>>>   drivers/remoteproc/qcom_nonpas_adsp_pil.c          | 667 
>>> +++++++++++++++++++++
>>>   4 files changed, 824 insertions(+)
>>>   create mode 100644 
>>> Documentation/devicetree/bindings/remoteproc/qcom,non-pas-adsp.txt
>>>   create mode 100644 drivers/remoteproc/qcom_nonpas_adsp_pil.c
>>>
>>> diff --git 
>>> a/Documentation/devicetree/bindings/remoteproc/qcom,non-pas-adsp.txt 
>>> b/Documentation/devicetree/bindings/remoteproc/qcom,non-pas-adsp.txt
>>> new file mode 100644
>>> index 0000000..0581aaa
>>> --- /dev/null
>>> +++ 
>>> b/Documentation/devicetree/bindings/remoteproc/qcom,non-pas-adsp.txt
>>> @@ -0,0 +1,138 @@
>>> +Qualcomm Technology Inc. Non PAS ADSP Peripheral Image Loader
>>> +
>>> +This document defines the binding for a component that loads and 
>>> boots firmware
>>> +on the Qualcomm Technology Inc. ADSP Hexagon core.
>>> +
>>> +- compatible:
>>> +    Usage: required
>>> +    Value type: <string>
>>> +    Definition: must be one of:
>>> +            "qcom,sdm845-apss-adsp-pil"
>> Didn't Bjorn say to drop the 'apss' part?
>
> Yes, he had asked to rename compatible string for  existing PIL driver 
> as "qcom,platform-subsystem-pas"
> and non-pas pil driver as "qcom,platform-subsystem-pil". I wanted to 
> get confirmation from Bjorn whether
> we should rename the filename too.
> @Bjorn, can you please suggest filename and compatible strings for the 
> two drivers.
>>> +
>>> +- reg:
>>> +    Usage: required
>>> +    Value type: <prop-encoded-array>
>>> +    Definition: must specify the base address and size of the qdsp6ss
>>> +
>>> +- reg-names:
>>> +    Usage: required
>>> +    Value type: <stringlist>
>>> +    Definition: must be "qdsp6ss"
>>> +
>>>
>> -- 
>> To unsubscribe from this list: send the line "unsubscribe 
>> linux-remoteproc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> Thanks,
> Rohit
>

  reply	other threads:[~2018-08-03 11:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29  9:20 [PATCH v2] remoteproc: qcom: Introduce Non-PAS ADSP PIL driver Rohit kumar
2018-07-06 20:32 ` Rob Herring
2018-07-09  5:59   ` Rohit Kumar
2018-08-03 11:23     ` Rohit Kumar [this message]
2018-08-28  6:09 ` Bjorn Andersson
2018-08-30 14:16   ` Rohit Kumar

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=be77dbce-49aa-862f-0192-f0264b5aa588@codeaurora.org \
    --to=rohitkr@codeaurora.org \
    --cc=bgoswami@codeaurora.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=ohad@wizery.com \
    --cc=robh@kernel.org \
    --cc=sbpata@codeaurora.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