Devicetree
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Jason Pettit <jason.pettit@oss.qualcomm.com>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Akhil P Oommen <akhilpo@oss.qualcomm.com>,
	Mahadevan P <mahadevan.p@oss.qualcomm.com>,
	Sibi Sankar <sibi.sankar@oss.qualcomm.com>,
	Jingyi Wang <jingyi.wang@oss.qualcomm.com>,
	Ananthu C V <ananthu.cv@oss.qualcomm.com>
Subject: Re: [PATCH v2 2/3] arm64: dts: qcom: Add HP EliteBook X G2q 14 AI
Date: Tue, 30 Jun 2026 13:04:06 +0200	[thread overview]
Message-ID: <28bd19ae-14b0-44ed-93f5-e066d7d695a0@oss.qualcomm.com> (raw)
In-Reply-To: <20260629070903.1341-1-jason.pettit@oss.qualcomm.com>

On 6/29/26 4:19 PM, Jason Pettit wrote:
> On Mon, 29 Jun 2026 11:47:52 +0200, Konrad Dybcio wrote:
>> At a glance, this seems to be different vs the reference data, could
>> you give it a spin?
>> [...]
>> -	QMP_PHY_INIT_CFG(QSERDES_V8_USB43_COM_SYSCLK_EN_SEL, 0x04),
>> +	QMP_PHY_INIT_CFG(QSERDES_V8_USB43_COM_SYSCLK_EN_SEL, 0x3b),
> 
> The prerequisite this v2 lists (the Glymur DP PLL change,
> 20260419-glymur_dp-v1-1-ad1067a8e8ae) already includes that 0x04 -> 0x3b
> change, so it is applied in my build. Just to be sure, I retested with
> &usb_2 and &usb_2_hsphy removed, and the same result is observed.
> 
> I can leave my v2 as-is and wait to submit v3 if there are other
> patch series pending that I should wait for.

The merge windows just closed, so we can pick up patches again.
Let's see how the (many) dependencies that we have shape up.

Konrad

  reply	other threads:[~2026-06-30 11:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26  5:47 [PATCH v2 0/3] X2 Elite HP EliteBook X G2q support Jason Pettit
2026-06-26  5:47 ` [PATCH v2 1/3] dt-bindings: arm: qcom: Add HP EliteBook X G2q 14 AI Jason Pettit
2026-06-26 10:20   ` Krzysztof Kozlowski
2026-06-26  5:47 ` [PATCH v2 2/3] arm64: dts: " Jason Pettit
2026-06-26  6:00   ` sashiko-bot
2026-06-26 11:26   ` Konrad Dybcio
2026-06-27 18:55     ` t
2026-06-27 19:06     ` Jason Pettit
2026-06-29  9:27       ` Konrad Dybcio
2026-06-26 11:27   ` Konrad Dybcio
2026-06-27 18:55     ` t
2026-06-27 19:06     ` Jason Pettit
2026-06-28 13:02       ` Dmitry Baryshkov
2026-06-28 16:29         ` Jason Pettit
2026-06-29  9:47           ` Konrad Dybcio
2026-06-29 14:19             ` Jason Pettit
2026-06-30 11:04               ` Konrad Dybcio [this message]
2026-06-26  5:47 ` [PATCH v2 3/3] firmware: qcom: scm: Allow QSEECOM on " Jason Pettit
2026-06-28 13:02   ` 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=28bd19ae-14b0-44ed-93f5-e066d7d695a0@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=akhilpo@oss.qualcomm.com \
    --cc=ananthu.cv@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=jason.pettit@oss.qualcomm.com \
    --cc=jingyi.wang@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mahadevan.p@oss.qualcomm.com \
    --cc=robh@kernel.org \
    --cc=sibi.sankar@oss.qualcomm.com \
    /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