From: Richard Acayan <mailingradian@gmail.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Loic Poulain <loic.poulain@linaro.org>,
Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-media@vger.kernel.org,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Subject: Re: [PATCH v4 0/7] Add SDM670 camera subsystem
Date: Thu, 5 Sep 2024 22:36:28 -0400 [thread overview]
Message-ID: <ZtpqrANbJurWNOzV@radian> (raw)
In-Reply-To: <tthbaop6bkyvebpibiyvyct4khrd5o4apdbipqdthnidxmu2cx@m726xv4ocblg>
On Thu, Sep 05, 2024 at 10:09:34PM +0200, Andi Shyti wrote:
> Hi Richard,
>
> On Tue, Sep 03, 2024 at 10:04:49PM GMT, Richard Acayan wrote:
> > This adds support for the camera subsystem on the Snapdragon 670.
> >
> > As of next-20240902, camss seems to be a bit broken, but the same series
> > works on stable (although it is much less reliable now that the CCI clock
> > frequency is not being assigned).
>
> I am not understanding this bit: is this series making it better
> or not? Can you please clarify what is broken, what is less
> reliable and what works?
When applying this camss series and some camera sensor patches on
linux-next, the Pixel 3a seems to hang when camera capture starts.
When applying the same patches on stable, the camera does not cause the
Pixel 3a to hang.
When these device tree properties from the previous series were removed:
assigned-clocks = <&camcc CAM_CC_CCI_CLK>;
assigned-clock-rates = <37500000>;
the CCI would sometimes fail to probe with the error:
[ 51.572732] i2c-qcom-cci ac4a000.cci: deferred probe timeout, ignoring dependency
[ 51.572769] i2c-qcom-cci ac4a000.cci: probe with driver i2c-qcom-cci failed with error -110
On further testing, the rate can be set to 19.2 MHz, and there would be
no failure (or rather, it wouldn't happen often enough for me to witness
it).
> Besides, I'm reading that this series has not been tested and it
> makes it difficult for me to take this in, considering that you
> are adding a new support.
Of course. This revision of the series wasn't submitted to rush into
v6.12-rc1. It can wait until everything is resolved.
When device tree maintainers comment "not tested" on the documentation,
it usually means that `make dt_bindings_check DT_SCHEMA_FILES=...` gives
errors or warnings (even though the device tree and driver may work on
the hardware). It's a separate test and one of the things I haven't
scripted into my workflow, although it's still a responsibility.
next prev parent reply other threads:[~2024-09-06 2:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 2:04 [PATCH v4 0/7] Add SDM670 camera subsystem Richard Acayan
2024-09-04 2:04 ` [PATCH v4 1/7] dt-bindings: clock: qcom,sdm845-camcc: add sdm670 compatible Richard Acayan
2024-09-04 6:11 ` Krzysztof Kozlowski
2024-09-04 2:04 ` [PATCH v4 2/7] dt-bindings: i2c: qcom-cci: Document SDM670 compatible Richard Acayan
2024-09-04 6:12 ` Krzysztof Kozlowski
2024-09-04 2:04 ` [PATCH v4 3/7] i2c: qcom-cci: Stop complaining about DT set clock rate Richard Acayan
2024-09-05 13:57 ` Konrad Dybcio
2024-09-05 14:18 ` Vladimir Zapolskiy
2024-09-05 15:18 ` Konrad Dybcio
2024-09-05 16:05 ` Bryan O'Donoghue
2024-09-04 2:04 ` [PATCH v4 4/7] dt-bindings: media: camss: Add qcom,sdm670-camss Richard Acayan
2024-09-04 3:35 ` Rob Herring (Arm)
2024-09-04 5:57 ` Krzysztof Kozlowski
2024-09-05 14:54 ` Vladimir Zapolskiy
2024-09-04 2:04 ` [PATCH v4 5/7] media: qcom: camss: add support for SDM670 camss Richard Acayan
2024-09-04 2:04 ` [PATCH v4 6/7] arm64: dts: qcom: sdm670: add camcc Richard Acayan
2024-09-04 2:04 ` [PATCH v4 7/7] arm64: dts: qcom: sdm670: add camss and cci Richard Acayan
2024-09-05 20:09 ` [PATCH v4 0/7] Add SDM670 camera subsystem Andi Shyti
2024-09-05 20:27 ` Bryan O'Donoghue
2024-09-06 2:36 ` Richard Acayan [this message]
2024-09-06 7:21 ` Andi Shyti
2024-09-06 12:19 ` Bryan O'Donoghue
2024-09-06 13:00 ` Vladimir Zapolskiy
2024-09-27 22:23 ` Richard Acayan
2024-09-28 10:46 ` Vladimir Zapolskiy
2024-09-05 20:53 ` Vladimir Zapolskiy
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=ZtpqrANbJurWNOzV@radian \
--to=mailingradian@gmail.com \
--cc=andersson@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=mchehab@kernel.org \
--cc=mturquette@baylibre.com \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=todor.too@gmail.com \
--cc=vladimir.zapolskiy@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).