From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Anjelique Melendez <anjelique.melendez@oss.qualcomm.com>,
andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] soc: qcom: pmic_glink: Add charger PDR service path and service name to client data
Date: Tue, 28 Oct 2025 10:22:34 +0100 [thread overview]
Message-ID: <a9da8c31-fb88-4350-96a4-de61d68fd756@oss.qualcomm.com> (raw)
In-Reply-To: <20251027212250.3847537-3-anjelique.melendez@oss.qualcomm.com>
On 10/27/25 10:22 PM, Anjelique Melendez wrote:
> Currently, the charger PD service path and service name are hard coded
> however these paths are not guaranteed to be the same between PMICs. For
> example, on Kaanapali and Glymur, Charger FW runs on SOCCP(another subsystem)
> which does not have any specific charger PDs defined.
>
> Define charger PDR service path and service name as client data so that
> each PMIC generation can properly define these paths.
>
> While at it, add the qcom,kaanapali-pmic-glink and
> qcom,glymur-pmic-glink compatible strings.
>
> Signed-off-by: Anjelique Melendez <anjelique.melendez@oss.qualcomm.com>
> ---
I think this change disqualifies Glymur from having a fallback to 8550,
since it couldn't have worked without ignoring the PDR
Konrad
next prev parent reply other threads:[~2025-10-28 9:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 21:22 [PATCH v2 0/2] soc: qcom: pmic_glink: Add support for battery management running on SOCCP Anjelique Melendez
2025-10-27 21:22 ` [PATCH v2 1/2] dt-bindings: soc: qcom: qcom,pmic-glink: Add Kaanapali and Glymur compatibles Anjelique Melendez
2025-10-28 3:58 ` Bjorn Andersson
2025-10-28 8:29 ` Krzysztof Kozlowski
2025-10-28 8:36 ` Krzysztof Kozlowski
2025-10-28 9:04 ` Konrad Dybcio
2025-10-28 9:16 ` Krzysztof Kozlowski
2025-10-28 9:19 ` Konrad Dybcio
2025-10-28 9:21 ` Krzysztof Kozlowski
2025-10-28 9:30 ` Krzysztof Kozlowski
2025-10-28 22:55 ` Anjelique Melendez
2025-10-29 5:26 ` Krzysztof Kozlowski
2025-10-28 14:14 ` Bjorn Andersson
2025-11-05 13:07 ` Kamal Wadhwa
2025-10-27 21:22 ` [PATCH v2 2/2] soc: qcom: pmic_glink: Add charger PDR service path and service name to client data Anjelique Melendez
2025-10-28 9:22 ` Konrad Dybcio [this message]
2025-10-28 17:20 ` Abel Vesa
2025-10-28 23:30 ` Anjelique Melendez
2025-10-29 8:41 ` Abel Vesa
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=a9da8c31-fb88-4350-96a4-de61d68fd756@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=anjelique.melendez@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.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