From: Neil Armstrong <neil.armstrong@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: regulator: qcom,rpmh-regulator: allow i and j as RPMh resource name suffix
Date: Tue, 22 Aug 2023 11:52:39 +0200 [thread overview]
Message-ID: <35f3aac5-7b8b-4cc7-9572-adf3d93e7a67@linaro.org> (raw)
In-Reply-To: <af07578e-2d31-4b26-931d-aeb0833db267@linaro.org>
Hi,
On 22/08/2023 11:42, Konrad Dybcio wrote:
> On 22.08.2023 11:29, Konrad Dybcio wrote:
>> On 22.08.2023 11:28, Konrad Dybcio wrote:
>>> On 22.08.2023 11:27, Neil Armstrong wrote:
>>>> Add "i" and "j" to the allowed subffix list as they can be used as RPMh
>>>> resource name suffixes on new platforms.
>>>>
>>>> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
>>>> ---
>>> Also 'n' and 'm' for 8550
>> Correction, the PMICs are indexed 'n' and 'm' but looks
>> like there are no RPMh-managed regulators on there
> Correction of the correction ;) there are some
Indeed, you're right, let's for for i, j, n & m then !
Neil
>
> Konrad
prev parent reply other threads:[~2023-08-22 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 9:27 [PATCH] dt-bindings: regulator: qcom,rpmh-regulator: allow i and j as RPMh resource name suffix Neil Armstrong
2023-08-22 9:28 ` Konrad Dybcio
2023-08-22 9:29 ` Konrad Dybcio
2023-08-22 9:42 ` Konrad Dybcio
2023-08-22 9:52 ` Neil Armstrong [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=35f3aac5-7b8b-4cc7-9572-adf3d93e7a67@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).