From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Bjorn Andersson <quic_bjorande@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: reserved-memory: rmtfs: Allow dynamic allocation
Date: Tue, 30 May 2023 21:37:46 +0200 [thread overview]
Message-ID: <c9c232a4-519a-108f-3651-5af6ba812dc8@linaro.org> (raw)
In-Reply-To: <20230530193436.3833889-2-quic_bjorande@quicinc.com>
On 30.05.2023 21:34, Bjorn Andersson wrote:
> Allow instances of the qcom,rmtfs-mem either be defined as a
> reserved-memory regoin, or just standalone given just a size.
>
> This relieve the DeviceTree source author the need to come up with a
> static memory region for the region.
>
> Signed-off-by: Bjorn Andersson <quic_bjorande@quicinc.com>
> ---
> .../reserved-memory/qcom,rmtfs-mem.yaml | 23 ++++++++++++++++---
> 1 file changed, 20 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml b/Documentation/devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml
> index bab982f00485..8b5de033f9ac 100644
> --- a/Documentation/devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml
> +++ b/Documentation/devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml
> @@ -14,13 +14,16 @@ description: |
> maintainers:
> - Bjorn Andersson <bjorn.andersson@linaro.org>
>
> -allOf:
> - - $ref: reserved-memory.yaml
> -
> properties:
> compatible:
> const: qcom,rmtfs-mem
>
> + qcom,alloc-size:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + Requested size of the rmtfs memory allocation, when not defined as a
> + reserved-memory region.
> +
> qcom,client-id:
> $ref: /schemas/types.yaml#/definitions/uint32
> description: >
> @@ -36,6 +39,11 @@ properties:
> required:
> - qcom,client-id
>
> +oneOf:
> + - $ref: reserved-memory.yaml
> + - required:
> + - qcom,alloc-size
> +
> unevaluatedProperties: false
>
> examples:
> @@ -53,3 +61,12 @@ examples:
> qcom,client-id = <1>;
> };
> };
> + - |
> + rmtfs {
> + compatible = "qcom,rmtfs-mem";
> +
> + qcom,alloc-size = <(2*1024*1024)>;
2 nitty nits:
- Most uses of DT arithmetic put spaces between the operands
- You could add a comment explaining what this example brings to
the table
Konrad
> + qcom,client-id = <1>;
> + qcom,vmid = <15>;
> + };
> +...
next prev parent reply other threads:[~2023-05-30 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 19:34 [PATCH 0/2] soc: qcom: rmtfs: Support dynamic allocation Bjorn Andersson
2023-05-30 19:34 ` [PATCH 1/2] dt-bindings: reserved-memory: rmtfs: Allow " Bjorn Andersson
2023-05-30 19:37 ` Konrad Dybcio [this message]
2023-05-31 8:05 ` Krzysztof Kozlowski
2023-05-31 17:44 ` Bjorn Andersson
2023-05-30 19:34 ` [PATCH 2/2] soc: qcom: rmtfs: Support dynamic placement of region Bjorn Andersson
2023-05-30 19:45 ` Konrad Dybcio
2023-05-30 21:31 ` Bjorn Andersson
2023-05-30 19:48 ` Stephan Gerhold
2023-05-30 21:39 ` 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=c9c232a4-519a-108f-3651-5af6ba812dc8@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_bjorande@quicinc.com \
--cc=robh+dt@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 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).