mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jie Gan <jie.gan@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	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>,
	Tingwei Zhang <tingwei.zhang@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: remove the disabled replicator
Date: Fri, 20 Mar 2026 18:46:45 +0800	[thread overview]
Message-ID: <f32ad04f-450d-49b7-8652-b8357accb6a1@oss.qualcomm.com> (raw)
In-Reply-To: <aaf4d504-432e-407a-8b6f-08401a25f680@kernel.org>



On 3/16/2026 6:15 PM, Krzysztof Kozlowski wrote:
> On 16/03/2026 10:33, Jie Gan wrote:
>>
>>
>> On 3/16/2026 3:14 PM, Krzysztof Kozlowski wrote:
>>> On 16/03/2026 06:31, Jie Gan wrote:
>>>> Remove the disabled device that blocks probing of the connected
>>>> replicator, as the replicator driver validates all connected
>>>> devices during probe.
>>>>
>>>> kernel log:
>>>> [   18.540971] platform 6046000.replicator: deferred probe pending: (reason unknown)
>>>
>>> No, that's not a reason to remove a device. The device is there, right?
>>> So fix Linux drivers if they cannot handle it properly.
>>
>> CoreSight devices build a path from source to sink and defer probing if
>> any device in the path is unavailable so the deferred‑probe behavior is
>> expected.
>>
>> We could add logic to fix it in driver but it's much easier to address
>> it in DT because we are knowing the device is disabled/Failed in DT.
> 
> Nope. You got comment already. DTS represents the hardware, not your
> current Linux driver status.
> 

Thanks for the patience to explain it, I have submitted a driver patch 
to address it.

Thanks,
Jie

>>
>> It's my fault I didnt remove this disabled replicator device in previous
>> fix.
>>
> 
> 
> 
> Best regards,
> Krzysztof


      reply	other threads:[~2026-03-20 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16  5:31 Jie Gan
2026-03-16  7:14 ` Krzysztof Kozlowski
2026-03-16  9:33   ` Jie Gan
2026-03-16 10:15     ` Krzysztof Kozlowski
2026-03-20 10:46       ` Jie Gan [this message]

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=f32ad04f-450d-49b7-8652-b8357accb6a1@oss.qualcomm.com \
    --to=jie.gan@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=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=tingwei.zhang@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

all inboxes | Powered by JetHome®