From: Krzysztof Kozlowski <krzk@kernel.org>
To: Anjelique Melendez <anjelique.melendez@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, sre@kernel.org,
heikki.krogerus@linux.intel.com, gregkh@linuxfoundation.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v5 1/5] dt-bindings: soc: qcom: qcom,pmic-glink: Add Glymur and Kaanapali compatibles
Date: Tue, 10 Feb 2026 10:17:18 +0100 [thread overview]
Message-ID: <20260210-whimsical-unyielding-owl-bb3bec@quoll> (raw)
In-Reply-To: <20260209204915.1983997-2-anjelique.melendez@oss.qualcomm.com>
On Mon, Feb 09, 2026 at 12:49:11PM -0800, Anjelique Melendez wrote:
> Glymur (a recent compute platform) and Kaanapali (a recent mobile
> platform) have the charger FW running on a new subsystem SOCCP (SOC
> Control Processor) instead of on ADSP like in previous platforms. Because
> of this, pmic_glink interface on Glymur and Kaanapali platforms are not
> compatible with previous platforms. Hence, add new compatible strings
> for Glymur and Kaanapali.
>
> Signed-off-by: Anjelique Melendez <anjelique.melendez@oss.qualcomm.com>
> ---
> Documentation/devicetree/bindings/soc/qcom/qcom,pmic-glink.yaml | 2 ++
> 1 file changed, 2 insertions(+)
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-10 9:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 20:49 [PATCH v5 0/5] soc: qcom: pmic_glink: Add support for battery management running on SOCCP Anjelique Melendez
2026-02-09 20:49 ` [PATCH v5 1/5] dt-bindings: soc: qcom: qcom,pmic-glink: Add Glymur and Kaanapali compatibles Anjelique Melendez
2026-02-10 9:17 ` Krzysztof Kozlowski [this message]
2026-02-09 20:49 ` [PATCH v5 2/5] soc: qcom: pmic_glink: Add charger PDR service information to client data Anjelique Melendez
2026-02-10 9:47 ` Konrad Dybcio
2026-02-10 12:26 ` Dmitry Baryshkov
2026-02-09 20:49 ` [PATCH v5 3/5] soc: qcom: pmic_glink: Add support for Glymur and Kaanapali Anjelique Melendez
2026-02-10 9:45 ` Konrad Dybcio
2026-02-10 12:27 ` Dmitry Baryshkov
2026-02-09 20:49 ` [PATCH v5 4/5] usb: typec: ucsi: ucsi_glink: " Anjelique Melendez
2026-02-10 9:49 ` Konrad Dybcio
2026-02-10 12:16 ` Heikki Krogerus
2026-02-10 12:27 ` Dmitry Baryshkov
2026-02-09 20:49 ` [PATCH v5 5/5] power: supply: qcom_battmgr: " Anjelique Melendez
2026-02-10 9:49 ` Konrad Dybcio
2026-02-10 12:28 ` Dmitry Baryshkov
2026-02-23 16:34 ` Bjorn Andersson
2026-02-23 19:56 ` (subset) [PATCH v5 0/5] soc: qcom: pmic_glink: Add support for battery management running on SOCCP Bjorn Andersson
2026-03-02 23:41 ` Sebastian Reichel
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=20260210-whimsical-unyielding-owl-bb3bec@quoll \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=anjelique.melendez@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sre@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