Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Val Packett <val@packett.cool>,
	cros-qcom-dts-watchers@chromium.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] arm64: dts: qcom: Add support for ECS LIVA QC710
Date: Tue, 13 Jan 2026 09:30:39 +0100	[thread overview]
Message-ID: <fcc6544f-b0dd-4f23-ade7-4d6f8b6a612f@oss.qualcomm.com> (raw)
In-Reply-To: <e7j3hctjlly44pjwe3jvjtpjuj33bdvpyo6pzc6o3q5tjjlyib@7evgyweq2deg>

On 1/13/26 2:31 AM, Dmitry Baryshkov wrote:
> On Mon, Jan 12, 2026 at 11:50:25AM +0100, Konrad Dybcio wrote:
>> On 1/12/26 1:31 AM, Val Packett wrote:
>>> [resent for the lists as plaintext, oops]
>>>
>>> On 1/11/26 1:50 PM, Dmitry Baryshkov wrote:
>>>
>>>> On Sun, Jan 11, 2026 at 05:35:12AM -0300, Val Packett wrote:
>>>>> Add a device tree for the ECS LIVA QC710 (Snapdragon 7c) mini PC/devkit.
>>>>> [..]
>>>>> +&dpu_intf1_out {
>>>>> +    /delete-property/ remote-endpoint;
>>>> Why? It should not be necessary.
>>>
>>> It seemed to be implicated in annoying EPROBE_DEFER issues.. But you're right, it wasn't this after all.
>>>
>>>>> +
>>>>> +&pm6150_pon {
>>>>> +    status = "disabled";
>>>> Do you know, how is Power-On routed?
>>> I think it's handled by the EC. Keeping this enabled doesn't make power-off work, and doesn't make the power button deliver events either.
>>>>> +};
>>
>> FYI I don't think a modern QC SoC can turn on without PON
>>
>> What do you mean by "doesn't make power-off work"?
> 
> It is basically a laptop SoM in the embedded case, so it has EC and PoN
> generated via the EC.

I got that part, but this doesn't answer my question. Val mentioned that
separately from the power button not generating keypress events.

Konrad

  reply	other threads:[~2026-01-13  8:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-11  8:35 [PATCH 0/5] Add support for ECS LIVA QC710 mini PC/devkit Val Packett
2026-01-11  8:35 ` [PATCH 1/5] dt-bindings: arm: qcom: Add ECS LIVA QC710 Val Packett
2026-01-12 10:39   ` Konrad Dybcio
2026-01-11  8:35 ` [PATCH 4/5] arm64: dts: qcom: Add support for " Val Packett
2026-01-11 16:50   ` Dmitry Baryshkov
2026-01-12  0:31     ` Val Packett
2026-01-12  0:55       ` Dmitry Baryshkov
2026-01-12 10:50       ` Konrad Dybcio
2026-01-13  1:31         ` Dmitry Baryshkov
2026-01-13  8:30           ` Konrad Dybcio [this message]
2026-01-13  9:30             ` Nikita Travkin
2026-01-13 10:17               ` Konrad Dybcio
2026-01-11 19:47   ` Dmitry Baryshkov
2026-01-12 10:53   ` Konrad Dybcio
2026-01-13  9:01   ` Neil Armstrong
2026-01-19  1:52     ` Val Packett
2026-01-11  8:35 ` [PATCH 5/5] firmware: qcom: scm: Allow QSEECOM on " Val Packett
2026-01-11 17:05   ` Dmitry Baryshkov
2026-01-21  9:57 ` (subset) [PATCH 0/5] Add support for ECS LIVA QC710 mini PC/devkit 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=fcc6544f-b0dd-4f23-ade7-4d6f8b6a612f@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=cros-qcom-dts-watchers@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=val@packett.cool \
    /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