From: Anjelique Melendez <anjelique.melendez@oss.qualcomm.com>
To: 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: [PATCH 0/3] soc: qcom: pmic_glink: Add support for battery management running on SOCCP
Date: Thu, 16 Oct 2025 17:30:30 -0700 [thread overview]
Message-ID: <20251017003033.268567-1-anjelique.melendez@oss.qualcomm.com> (raw)
System On Chip Control Processor (SOCCP) is a subsystem that can have
battery management firmware running on it to support Type-C/PD and
battery charging. Add support for devices, such as Kaanpali and Glymur,
which are running battery management on SOCCP.
** PATCH 2/3 - was picked up in this series and prior conversation can be found:
https://lore.kernel.org/all/20250919175025.2988948-1-anjelique.melendez@oss.qualcomm.com/
Anjelique Melendez (3):
dt-bindings: soc: qcom: qcom,pmic-glink: Add Kaanapali and Glymur
compatibles
soc: qcom: pmic_glink: Add support for SOCCP remoteproc channels
soc: qcom: pmic_glink: Add PDR service path and service name to client
data
.../bindings/soc/qcom/qcom,pmic-glink.yaml | 7 ++
drivers/soc/qcom/pmic_glink.c | 74 ++++++++++++-------
2 files changed, 56 insertions(+), 25 deletions(-)
--
2.34.1
next reply other threads:[~2025-10-17 0:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 0:30 Anjelique Melendez [this message]
2025-10-17 0:30 ` [PATCH 1/3] dt-bindings: soc: qcom: qcom,pmic-glink: Add Kaanapali and Glymur compatibles Anjelique Melendez
2025-10-17 4:53 ` Krzysztof Kozlowski
2025-10-17 0:30 ` [PATCH 2/3] soc: qcom: pmic_glink: Add support for SOCCP remoteproc channels Anjelique Melendez
2025-10-17 0:30 ` [PATCH 3/3] soc: qcom: pmic_glink: Add PDR service path and service name to client data Anjelique Melendez
2025-10-19 12:10 ` Dmitry Baryshkov
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=20251017003033.268567-1-anjelique.melendez@oss.qualcomm.com \
--to=anjelique.melendez@oss.qualcomm.com \
--cc=andersson@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).