From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Johan Hovold <johan@kernel.org>, Robert Foss <rfoss@kernel.org>,
Todor Tomov <todor.too@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Failure to stop CAMSS stream (sc8280xp)
Date: Wed, 3 Jul 2024 15:30:09 +0100 [thread overview]
Message-ID: <49b2504f-e5ab-4ea9-aefb-bc9c7f71f5fc@linaro.org> (raw)
In-Reply-To: <ZoVNHOTI0PKMNt4_@hovoldconsulting.com>
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, I also want to root cause intermittent sensor
startup failure, before switching on the sensor upstream for more common
use.
> I'm using the following (squashed) devicetree patch from Bryan to enable
> the camera (everything else is upstream):
>
> https://github.com/jhovold/linux/commit/85b41b8d0efd418509df548592f95b43b9663409
>
> 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.
> 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.
---
bod
next prev parent reply other threads:[~2024-07-03 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 13:07 Johan Hovold
2024-07-03 14:30 ` Bryan O'Donoghue [this message]
2024-07-03 15:12 ` Johan Hovold
2024-07-03 15:46 ` Bryan O'Donoghue
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=49b2504f-e5ab-4ea9-aefb-bc9c7f71f5fc@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=johan@kernel.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=todor.too@gmail.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®