linux-kernel - Re: Failure to stop CAMSS stream (sc8280xp)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <00676ba0-d2ba-48ce-8b8e-8c1d81a4c24f@nexus-software.ie>
Date: Wed, 3 Jul 2024 16:46:11 +0100
From: Bryan O'Donoghue <pure.logic@...us-software.ie>
To: Johan Hovold <johan@...nel.org>,
 Bryan O'Donoghue <bryan.odonoghue@...aro.org>
Cc: Robert Foss <rfoss@...nel.org>, Todor Tomov <todor.too@...il.com>,
 Mauro Carvalho Chehab <mchehab@...nel.org>,
 Kieran Bingham <kieran.bingham@...asonboard.com>,
 linux-media@...r.kernel.org, linux-arm-msm@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: Failure to stop CAMSS stream (sc8280xp)

On 03/07/2024 16:12, Johan Hovold wrote:
> On Wed, Jul 03, 2024 at 03:30:09PM +0100, Bryan O'Donoghue wrote:
>> On 03/07/2024 14:07, Johan Hovold wrote:
>>> Is this a known issue with CAMSS or is something missing in the sc8280xp
>>> integration?
>>
>> A known issue on my end,
> 
> Ok, good. Do you know already if this is a generic CAMSS issue or
> something with the sc8280xp integration? I believe I heard someone
> saying that they had seen something similar on other Qualcomm platforms.

It seems generic but, I only really started to see it on x13s, then 
again I use x13s as a semi-daily driver...

> 
>> I also want to root cause intermittent sensor
>> startup failure, before switching on the sensor upstream for more common
>> use.
> 
>>> The issue was there with 6.9 as well so it's not a (recent) regression.
>>>
>>> Probing the camera sometimes, but infrequently, also fails with:
>>>
>>> 	qcom-camss ac5a000.camss: Failed to power up pipeline: -13
>>
>> Yes this. If you recall on the pm8010 I had mentioned to you about a
>> wait-time to startup the regulator - thinking it was the regulator
>> causing this error.
>>
>> More likely the GPIO reset polarity or delay needs to be tweaked in the
>> sensor driver.
> 
> Ok. Seems to happen quite rarely here. I have also seen a probe deferral
> warning (which should be suppressed if it's legit) that may or may not
> be related:
> 
> 	ov5675 24-0010: failed to get HW configuration: -517

Hah odd, I haven't seen probe deferral myself - perhaps not in the intrd 
for my laptop.

> 
>>> and I'm seeing the following warning on every boot:
>>>
>>> 	i2c-qcom-cci ac4c000.cci: Found 19200000 cci clk rate while 37500000 was expected
>>
>> That's hanging around for quite a long time 19.2 MHz is a perfectly
>> valid clock, useless error message.
> 
> Ok, but please do something to get rid of this warning as well. With
> too much noise in the logs, people may fail to notice real issues.

ack

---
bod