From: Stephen Boyd <sboyd@kernel.org>
To: Lina Iyer <ilina@codeaurora.org>,
andy.gross@linaro.org, david.brown@linaro.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org
Cc: rnayak@codeaurora.org, bjorn.andersson@linaro.org,
linux-kernel@vger.kernel.org, Lina Iyer <ilina@codeaurora.org>,
devicetree@vger.kernel.org,
Mahesh Sivasubramanian <msivasub@codeaurora.org>
Subject: Re: [PATCH v4 2/2] dt-bindings: introduce Command DB for QCOM SoCs
Date: Mon, 05 Mar 2018 16:21:13 -0800 [thread overview]
Message-ID: <152029567344.218381.8756848686590091138@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20180226175802.20052-3-ilina@codeaurora.org>
Quoting Lina Iyer (2018-02-26 09:58:02)
> diff --git a/Documentation/devicetree/bindings/arm/msm/cmd-db.txt b/Documentation/devicetree/bindings/arm/msm/cmd-db.txt
> new file mode 100644
> index 000000000000..5737ed2ac6e8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/msm/cmd-db.txt
> @@ -0,0 +1,38 @@
> +Command DB
> +---------
> +
> +Command DB is a database that provides a mapping between resource key and the
s/between/between the/
> +resource address for a system resource managed by a remote processor. The data
> +is stored in a shared memory region and is loaded by the remote processor.
> +
> +Some of the Qualcomm Technologies Inc SoC's have hardware accelerators for
s/SoC's/SoCs/
> +controlling shared resources. Depending on the board configuration the shared
> +resource properties may change. These properties are dynamically probed by the
> +remote processor and made available in the shared memory.
> +
> +The bindings for Command DB is specified in the reserved-memory section in
s/bindings/node/
maybe?
> +devicetree. The devicetree representation of the command DB driver should be:
Maybe drop this last sentence entirely.
> +
> +Properties:
> +- compatible:
> + Usage: required
> + Value type: <string>
> + Definition: Should be "qcom,cmd-db"
> +
> +- reg:
> + Usage: required
> + Value type: <prop encoded array>
> + Definition: The register address that points to the location of the
> + Command DB in memory. Additionally, specify the address
> + and size of the actual lacation in memory.
s/lacation/location/
> +
> +Example:
> +
> + reserved-memory {
> + [...]
> + qcom,cmd-db@c3f000c {
> + reg = <0x0 0xc3f000c 0x0 0x8>,
> + <0x0 0x85fe0000 0x0 0x20000>;
> + compatible = "qcom,cmd-db";
> + };
> + };
next prev parent reply other threads:[~2018-03-06 0:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 17:58 [PATCH v4 0/2] drivers/qcom: add Command DB support Lina Iyer
2018-02-26 17:58 ` [PATCH v4 1/2] drivers: qcom: add command DB driver Lina Iyer
2018-03-05 18:42 ` Stephen Boyd
2018-03-06 16:21 ` Lina Iyer
2018-03-06 16:56 ` Lina Iyer
2018-03-06 22:08 ` Stephen Boyd
2018-03-06 22:08 ` Stephen Boyd
2018-02-26 17:58 ` [PATCH v4 2/2] dt-bindings: introduce Command DB for QCOM SoCs Lina Iyer
2018-03-05 21:10 ` Rob Herring
2018-03-05 23:14 ` Bjorn Andersson
2018-03-06 15:57 ` Lina Iyer
2018-03-07 19:02 ` Bjorn Andersson
2018-03-16 18:26 ` Stephen Boyd
2018-03-16 19:55 ` Bjorn Andersson
2018-03-06 0:21 ` Stephen Boyd [this message]
2018-03-06 15:57 ` Lina Iyer
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=152029567344.218381.8756848686590091138@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=ilina@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=msivasub@codeaurora.org \
--cc=rnayak@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;
as well as URLs for NNTP newsgroup(s).