From: Esteban Urrutia <esteuwu@proton.me>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
phone-devel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: soc: qcom: qcom,pmic-glink: Add compatible string for SM8475
Date: Fri, 31 Jul 2026 14:44:30 +0000 [thread overview]
Message-ID: <9718d7b8-7303-47a2-9d75-58bbde6385e9@proton.me> (raw)
In-Reply-To: <20260731-savvy-piquant-chowchow-f516f2@quoll>
On 7/31/26 5:58 AM, Krzysztof Kozlowski wrote:
> On Fri, Jul 31, 2026 at 01:00:08AM -0400, Esteban Urrutia wrote:
>> Due to a different process design, SM8475 (4 nm) SoC takes things from both
>> SM8450 (4 LPX) and SM8550 (4 nm) SoCs.
>
> What things? This is just unspecific and not useful. And I doubt that it
> is even "different process design", because how one would know that?
The process design is specified on the corresponding datasheets for
these SoCs, which are flying somewhere around the internet.
Also [1].
>> Add a separate compatible string for this SoC to avoid possible confusions.
>
> No, explain the hardware compatibility.
>
> Add foo bar, which is not compatible with baz because it uses bam bam in
> different setup (difference in registers, e.g. XYZ and ABC),
How does this commit message based on what was said in [1] sound to you?
SM8475 is a respin of SM8450 on a different process node, which probably
forced some electrical changes.
Document the SM8475 compatible used to describe the PMIC GLINK on this
platform.
Regards,
Esteban
[1] https://lore.kernel.org/linux-arm-msm/afcbb668-ab9e-4f97-9014-ecbd5170ab92@linaro.org/
next prev parent reply other threads:[~2026-07-31 14:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 5:00 [PATCH v2 0/2] Support for pmic-glink in SM8475 Esteban Urrutia via B4 Relay
2026-07-31 5:00 ` [PATCH v2 1/2] dt-bindings: soc: qcom: qcom,pmic-glink: Add compatible string for SM8475 Esteban Urrutia via B4 Relay
2026-07-31 9:58 ` Krzysztof Kozlowski
2026-07-31 14:44 ` Esteban Urrutia [this message]
2026-07-31 15:30 ` Konrad Dybcio
2026-07-31 15:54 ` Esteban Urrutia
2026-07-31 16:28 ` Konrad Dybcio
2026-07-31 16:40 ` Esteban Urrutia
2026-07-31 16:42 ` Konrad Dybcio
2026-07-31 16:56 ` Esteban Urrutia
2026-07-31 5:00 ` [PATCH v2 2/2] usb: typec: ucsi: ucsi_glink: " Esteban Urrutia via B4 Relay
2026-07-31 5:40 ` Esteban Urrutia
2026-07-31 9:59 ` Krzysztof Kozlowski
2026-07-31 14:48 ` Esteban Urrutia
2026-07-31 10:00 ` [PATCH v2 0/2] Support for pmic-glink in SM8475 Krzysztof Kozlowski
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=9718d7b8-7303-47a2-9d75-58bbde6385e9@proton.me \
--to=esteuwu@proton.me \
--cc=andersson@kernel.org \
--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=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=phone-devel@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
all inboxes | Powered by JetHome®