From: Bjorn Andersson <andersson@kernel.org>
To: linux-arm-msm@vger.kernel.org, konrad.dybcio@linaro.org,
agross@kernel.org, krzysztof.kozlowski@linaro.org
Cc: marijn.suijten@somainline.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
robh+dt@kernel.org
Subject: Re: (subset) [PATCH v4 1/3] dt-bindings: reserved-memory: rmtfs: Make qcom,vmid an array
Date: Tue, 10 Jan 2023 23:09:24 -0600 [thread overview]
Message-ID: <167341377741.2246479.8259536119397257522.b4-ty@kernel.org> (raw)
In-Reply-To: <20230109130523.298971-1-konrad.dybcio@linaro.org>
On Mon, 9 Jan 2023 14:05:21 +0100, Konrad Dybcio wrote:
> Some SoCs mandate that the RMTFS is also assigned to the NAV VM, while
> others really don't want that. Since it has to be conditional, turn
> qcom,vmid into an u32 array so that we can handle the NAV case, as
> well as other similar ones if they pop up in the future.
>
>
Applied, thanks!
[1/3] dt-bindings: reserved-memory: rmtfs: Make qcom,vmid an array
commit: da0d37e42f93f7bd6351e7ef67a52ea9a272c761
[2/3] soc: qcom: rmtfs: Optionally map RMTFS to more VMs
commit: e656cd0bcf3d2ba2eceac82b44714bf355428ec4
[3/3] dt-bindings: firmware: qcom: scm: Separate VMIDs from header to bindings
commit: 45ca30eb9dfe622b00ce352cf28ee141d243254b
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-01-11 5:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 13:05 Konrad Dybcio
2023-01-09 13:05 ` [PATCH v4 2/3] soc: qcom: rmtfs: Optionally map RMTFS to more VMs Konrad Dybcio
2023-01-09 13:05 ` [PATCH v4 3/3] dt-bindings: firmware: qcom: scm: Separate VMIDs from header to bindings Konrad Dybcio
2023-01-10 10:11 ` Krzysztof Kozlowski
2023-01-10 10:11 ` [PATCH v4 1/3] dt-bindings: reserved-memory: rmtfs: Make qcom,vmid an array Krzysztof Kozlowski
2023-01-11 5:09 ` Bjorn Andersson [this message]
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=167341377741.2246479.8259536119397257522.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--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
all inboxes | Powered by JetHome®