From: Rob Herring <robh@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>, Andy Gross <agross@kernel.org>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, Lee Jones <lee@kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH RFC 01/15] dt-bindings: mfd: Split out Qcom RPM MSG RAM
Date: Fri, 10 Mar 2023 21:01:27 -0600 [thread overview]
Message-ID: <167850338434.3256356.12674736316044440757.robh@kernel.org> (raw)
In-Reply-To: <20230311-topic-msg_ram-v1-1-e9c2094daf09@linaro.org>
On Sat, 11 Mar 2023 02:21:31 +0100, Konrad Dybcio wrote:
> The RPM Message RAM is a part of the RPM low-power core's RAM that's a
> MMIO-mapped region from the main ARM CPUs' POV. It contains sleep stats
> divided per "RPM master" (ARM cluster, *DSP, ...), an interrupt controller
> (MPM) that's vital in the low-power mode entry/exit sequence, as it
> signals the readiness to enter sleep, replays the interrupts after a total
> power collapse recovery and is able to receive external interrupts from
> other IPs (like the PMIC, TSENS and USB) on the SoC to initiate a wakeup
> sequence.
>
> On top of that, it contains some regions that are (ab)used by SMEM (by
> design!), but we're not completely sure what ranges are r/w to/from.
> This would probably need to be determined on a SoC-by-SoC - or even worse
> - firmware-by-firmware basis, but since this region is quite "wild west"
> by design (it may be accessed and altered in one form or another by all of
> the subsystems at the same time) this shouldn't really worry us..
>
> Split out the bindings and re-model it as a simple-mfd to allow for better
> representation of the partitions within and allow child devices (MPM,
> master sleep stats - coming soon).
>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> ---
> .../devicetree/bindings/mfd/qcom,rpm-msg-ram.yaml | 82 ++++++++++++++++++++++
> Documentation/devicetree/bindings/sram/sram.yaml | 2 -
> 2 files changed, 82 insertions(+), 2 deletions(-)
>
My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
on your patch (DT_CHECKER_FLAGS is new in v5.13):
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/soc/qcom/qcom,smem.example.dtb: sram@fc428000: compatible: ['qcom,rpm-msg-ram'] is too short
From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/mfd/qcom,rpm-msg-ram.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/mfd/qcom,rpm-msg-ram.example.dtb: sram@45f0000: interrupt-controller@1b8: 'oneOf' conditional failed, one must be fixed:
'#power-domain-cells' does not match any of the regexes: 'pinctrl-[0-9]+'
From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/mfd/qcom,rpm-msg-ram.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/mfd/qcom,rpm-msg-ram.example.dtb: interrupt-controller@1b8: '#power-domain-cells' does not match any of the regexes: 'pinctrl-[0-9]+'
From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/interrupt-controller/qcom,mpm.yaml
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20230311-topic-msg_ram-v1-1-e9c2094daf09@linaro.org
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
next prev parent reply other threads:[~2023-03-11 3:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 1:21 [PATCH RFC 00/15] Convert Qualcomm RPM message RAM to a simple-mfd Konrad Dybcio
2023-03-11 1:21 ` [PATCH RFC 01/15] dt-bindings: mfd: Split out Qcom RPM MSG RAM Konrad Dybcio
2023-03-11 3:01 ` Rob Herring [this message]
2023-03-11 1:21 ` [PATCH RFC 02/15] arm64: dts: qcom: msm8916: Add simple-mfd to rpm_msg_ram Konrad Dybcio
2023-03-11 1:21 ` [PATCH RFC 03/15] arm64: dts: qcom: msm8953: " Konrad Dybcio
2023-03-11 1:21 ` [PATCH RFC 04/15] arm64: dts: qcom: msm8976: " Konrad Dybcio
2023-03-11 1:21 ` [PATCH RFC 05/15] arm64: dts: qcom: msm8994: " Konrad Dybcio
2023-03-11 1:21 ` [PATCH RFC 06/15] arm64: dts: qcom: msm8996: " Konrad Dybcio
2023-03-11 1:21 ` [PATCH RFC 07/15] arm64: dts: qcom: msm8998: " Konrad Dybcio
2023-03-11 1:21 ` [PATCH RFC 08/15] arm64: dts: qcom: qcs404: " Konrad Dybcio
2023-03-11 1:21 ` [PATCH RFC 09/15] arm64: dts: qcom: sdm630: " Konrad Dybcio
2023-03-11 1:21 ` [PATCH RFC 10/15] arm64: dts: qcom: sm6115: " Konrad Dybcio
2023-03-11 1:21 ` [PATCH RFC 11/15] arm64: dts: qcom: sm6125: " Konrad Dybcio
2023-03-11 1:21 ` [PATCH RFC 12/15] arm64: dts: qcom: sm6375: " Konrad Dybcio
2023-03-11 1:21 ` [PATCH RFC 13/15] ARM: dts: qcom-apq8084: " Konrad Dybcio
2023-03-11 1:21 ` [PATCH RFC 14/15] ARM: dts: qcom-msm8226: " Konrad Dybcio
2023-03-11 1:21 ` [PATCH RFC 15/15] ARM: dts: qcom-msm8974: " Konrad Dybcio
2023-03-11 11:24 ` [PATCH RFC 00/15] Convert Qualcomm RPM message RAM to a simple-mfd Dmitry Baryshkov
2023-03-11 12:40 ` Konrad Dybcio
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=167850338434.3256356.12674736316044440757.robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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