From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Lee Jones <lee@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 00/15] Convert Qualcomm RPM message RAM to a simple-mfd
Date: Sat, 11 Mar 2023 13:40:43 +0100 [thread overview]
Message-ID: <2b368fdc-8c81-8e87-68fc-866aef904413@linaro.org> (raw)
In-Reply-To: <CAA8EJpqm6F6pvBR81xA=ZFyTPXpz+e+Ja+X4qF4ZD-3W5T2jJA@mail.gmail.com>
On 11.03.2023 12:24, Dmitry Baryshkov wrote:
> On Sat, 11 Mar 2023 at 03:21, Konrad Dybcio <konrad.dybcio@linaro.org> wrote:
>>
>> The Qualcomm RPM message RAM is a part of the RPM low-power processor's
>> actual RAM that's exposed to the Application Processors as a MMIO-mapped
>> region. It contains a couple of things, most notably the RPM master stats,
>> detailing per-master (read: per-subsystem) sleep/wake statistics and an
>> interrupt controller that's crucial to achieving full SoC clock and/or
>> power collapse states (the MPM). This series tries to prepare the MSG
>> RAM node to be a host for such devices.
>>
>> Depends on https://lore.kernel.org/linux-arm-msm/20230308011705.291337-1-konrad.dybcio@linaro.org/
>>
>> to solve a warning in the example.
>>
>> The DTS commits don't add -cells or -ranges, as without children they're
>> not of very much use. They'll be introduced along with subnodes.
>>
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>> ---
>> Konrad Dybcio (15):
>> dt-bindings: mfd: Split out Qcom RPM MSG RAM
>> arm64: dts: qcom: msm8916: Add simple-mfd to rpm_msg_ram
>> arm64: dts: qcom: msm8953: Add simple-mfd to rpm_msg_ram
>> arm64: dts: qcom: msm8976: Add simple-mfd to rpm_msg_ram
>> arm64: dts: qcom: msm8994: Add simple-mfd to rpm_msg_ram
>> arm64: dts: qcom: msm8996: Add simple-mfd to rpm_msg_ram
>> arm64: dts: qcom: msm8998: Add simple-mfd to rpm_msg_ram
>> arm64: dts: qcom: qcs404: Add simple-mfd to rpm_msg_ram
>> arm64: dts: qcom: sdm630: Add simple-mfd to rpm_msg_ram
>> arm64: dts: qcom: sm6115: Add simple-mfd to rpm_msg_ram
>> arm64: dts: qcom: sm6125: Add simple-mfd to rpm_msg_ram
>> arm64: dts: qcom: sm6375: Add simple-mfd to rpm_msg_ram
>> ARM: dts: qcom-apq8084: Add simple-mfd to rpm_msg_ram
>> ARM: dts: qcom-msm8226: Add simple-mfd to rpm_msg_ram
>> ARM: dts: qcom-msm8974: Add simple-mfd to rpm_msg_ram
>
> These commits do not demonstrate the need for simple-mfd (other than
> qcom,mpm being mentioned in bindings). I'd suggest limiting the RFC to
> a single platform populated with rpm_msg_ram child devices. This way
> we can better understand the needs and the requirements for these
> patches.
Right.. I was debating whether to just send the bindings as a RFC, but
then I'd have to make simple-mfd optional just to retire it soon..
Konrad
>
>
prev parent reply other threads:[~2023-03-11 12:40 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
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 [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=2b368fdc-8c81-8e87-68fc-866aef904413@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@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 \
--cc=robh@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