From: Rob Herring <robh@kernel.org>
To: Sibi Sankar <sibis@codeaurora.org>
Cc: bjorn.andersson@linaro.org, david.brown@linaro.org,
robh+dt@kernel.org, mark.rutland@arm.com, andy.gross@linaro.org,
briannorris@chromium.org, akdwived@codeaurora.org,
clew@codeaurora.org, linux-kernel@vger.kernel.org,
linux-arm-msm-owner@vger.kernel.org, ohad@wizery.com,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: remoteproc: qcom: Add firmware bindings for Q6V5
Date: Fri, 28 Dec 2018 16:17:06 -0600 [thread overview]
Message-ID: <20181228221706.GA22610@bogus> (raw)
In-Reply-To: <20181228044819.5697-2-sibis@codeaurora.org>
On Fri, 28 Dec 2018 10:18:18 +0530, Sibi Sankar wrote:
> Add optional "firmware-name" bindings for Q6V5 MSS and PAS based
> remoteprocs. For Q6V5 MSS/PAS the two/one relative firmware
> paths/path are to be listed respectively. Fallback to the default
> images for mba/modem for Q6V5 MSS or the default Hexagon image
> for Q6V5 PAS if the "firmware-name" binding is not present.
>
> Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
> ---
> Documentation/devicetree/bindings/remoteproc/qcom,adsp.txt | 6 ++++++
> Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 7 +++++++
> 2 files changed, 13 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
Cc: bjorn.andersson@linaro.org, david.brown@linaro.org,
robh+dt@kernel.org, mark.rutland@arm.com, andy.gross@linaro.org,
briannorris@chromium.org, akdwived@codeaurora.org,
clew@codeaurora.org, linux-kernel@vger.kernel.org,
linux-arm-msm-owner@vger.kernel.org, ohad@wizery.com,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
Sibi Sankar <sibis@codeaurora.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: remoteproc: qcom: Add firmware bindings for Q6V5
Date: Fri, 28 Dec 2018 16:17:06 -0600 [thread overview]
Message-ID: <20181228221706.GA22610@bogus> (raw)
In-Reply-To: <20181228044819.5697-2-sibis@codeaurora.org>
On Fri, 28 Dec 2018 10:18:18 +0530, Sibi Sankar wrote:
> Add optional "firmware-name" bindings for Q6V5 MSS and PAS based
> remoteprocs. For Q6V5 MSS/PAS the two/one relative firmware
> paths/path are to be listed respectively. Fallback to the default
> images for mba/modem for Q6V5 MSS or the default Hexagon image
> for Q6V5 PAS if the "firmware-name" binding is not present.
>
> Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
> ---
> Documentation/devicetree/bindings/remoteproc/qcom,adsp.txt | 6 ++++++
> Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 7 +++++++
> 2 files changed, 13 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Sibi Sankar <sibis@codeaurora.org>
Cc: bjorn.andersson@linaro.org, david.brown@linaro.org,
robh+dt@kernel.org, mark.rutland@arm.com, andy.gross@linaro.org,
briannorris@chromium.org, akdwived@codeaurora.org,
clew@codeaurora.org, linux-kernel@vger.kernel.org,
linux-arm-msm-owner@vger.kernel.org, ohad@wizery.com,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
Sibi Sankar <sibis@codeaurora.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: remoteproc: qcom: Add firmware bindings for Q6V5
Date: Fri, 28 Dec 2018 16:17:06 -0600 [thread overview]
Message-ID: <20181228221706.GA22610@bogus> (raw)
In-Reply-To: <20181228044819.5697-2-sibis@codeaurora.org>
On Fri, 28 Dec 2018 10:18:18 +0530, Sibi Sankar wrote:
> Add optional "firmware-name" bindings for Q6V5 MSS and PAS based
> remoteprocs. For Q6V5 MSS/PAS the two/one relative firmware
> paths/path are to be listed respectively. Fallback to the default
> images for mba/modem for Q6V5 MSS or the default Hexagon image
> for Q6V5 PAS if the "firmware-name" binding is not present.
>
> Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
> ---
> Documentation/devicetree/bindings/remoteproc/qcom,adsp.txt | 6 ++++++
> Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 7 +++++++
> 2 files changed, 13 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-12-28 22:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 4:48 [PATCH v2 0/2] Add firmware bindings for Q6V5 MSS/PAS Sibi Sankar
2018-12-28 4:48 ` [PATCH v2 1/2] dt-bindings: remoteproc: qcom: Add firmware bindings for Q6V5 Sibi Sankar
2018-12-28 22:17 ` Rob Herring [this message]
2018-12-28 22:17 ` Rob Herring
2018-12-28 22:17 ` Rob Herring
2019-01-03 23:30 ` Brian Norris
2019-01-03 23:50 ` Brian Norris
2019-01-04 0:01 ` Bjorn Andersson
2019-01-04 0:11 ` Brian Norris
2019-01-05 1:54 ` Brian Norris
2019-01-08 10:50 ` Sibi Sankar
2019-01-08 15:22 ` Rob Herring
2019-01-09 21:55 ` Brian Norris
2019-01-10 14:56 ` Rob Herring
2018-12-28 4:48 ` [PATCH v2 2/2] remoteproc: qcom: Add support for parsing fw dt bindings Sibi Sankar
2019-01-03 23:09 ` Bjorn Andersson
2019-01-03 23:44 ` Brian Norris
2019-01-08 10:32 ` Sibi Sankar
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=20181228221706.GA22610@bogus \
--to=robh@kernel.org \
--cc=akdwived@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=briannorris@chromium.org \
--cc=clew@codeaurora.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm-owner@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+dt@kernel.org \
--cc=sibis@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 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.