From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
robert.foss@linaro.org, todor.too@gmail.com, agross@kernel.org,
bjorn.andersson@linaro.org
Cc: mchehab@kernel.org, robh+dt@kernel.org, krzk+dt@kernel.org,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, mmitkov@quicinc.com,
jgrahsl@snap.com, hfink@snap.com
Subject: Re: [PATCH 1/1] arm64: dts: qcom: qrb5165-rb5: Enable the IMX577 on cam1
Date: Sun, 22 May 2022 18:10:31 +0100 [thread overview]
Message-ID: <19c92f9d-fa1c-fbe8-50ef-324da3e00695@linaro.org> (raw)
In-Reply-To: <33abcc93-13f1-d6f5-36a3-6ab796f124f9@linaro.org>
On 18/05/2022 20:09, Vladimir Zapolskiy wrote:
>
> I run on you branch on top of linux-next, but switch build options from
> modules to built-in
>
> CONFIG_I2C_QCOM_CCI=y
> CONFIG_VIDEO_QCOM_CAMSS=y
>
> I didn't get the sensor initialized and hence there is no /dev/media0 node:
>
> [ 0.620205] i2c-qcom-cci ac50000.cci: Found 19200000 cci clk rate
> while 37500000 was expected
> [ 0.620551] i2c 20-001a: Fixing up cyclic dependency with ac6a000.camss
> [ 0.620754] imx412 20-001a: Looking up dovdd-supply from device tree
> [ 0.620797] imx412 20-001a: Looking up avdd-supply from device tree
> [ 0.620860] imx412 20-001a: Looking up dvdd-supply from device tree
> [ 0.620876] duplicated lane 1 in clock-lanes, using defaults
> [ 0.622789] imx412 20-001a: failed to find sensor: -5
> [ 0.622880] imx412: probe of 20-001a failed with error -5
>
> I believe the problem could be related to CCI, please remind me, are
> there I2C bus pull-ups?
Hmm.
Just trying to replicate this on linux-next
https://git.linaro.org/people/bryan.odonoghue/kernel.git/log/?h=linux-next-22-05-22%2bimx577-rb5
root@linaro-gnome:~# zcat /proc/config.gz | grep -e CONFIG_I2C_QCOM_CCI
-e CONFIG_VIDEO_QCOM_CAMSS
CONFIG_I2C_QCOM_CCI=y
CONFIG_VIDEO_QCOM_CAMSS=y
root@linaro-gnome:~# uname -a
Linux linaro-gnome 5.18.0-rc7-next-20220518-00006-g3beef4d1d353-dirty
#40 SMP PREEMPT Sun May 22 17:53:29 IST 2022 aarch64 GNU/Linux
root@linaro-gnome:~# cam -l
Available cameras:
1: 'imx412' (/base/soc@0/cci@ac50000/i2c-bus@0/camera@1a)
are you compiling everything in ?
---
bod
next prev parent reply other threads:[~2022-05-22 17:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 13:30 [PATCH 0/1] Switch on IMX577 on RB5 Bryan O'Donoghue
2022-05-18 13:30 ` [PATCH 1/1] arm64: dts: qcom: qrb5165-rb5: Enable the IMX577 on cam1 Bryan O'Donoghue
2022-05-18 13:55 ` Konrad Dybcio
2022-05-18 14:04 ` Vladimir Zapolskiy
2022-05-18 15:35 ` Bryan O'Donoghue
2022-05-18 19:09 ` Vladimir Zapolskiy
2022-05-22 17:10 ` Bryan O'Donoghue [this message]
2022-05-23 13:50 ` Vladimir Zapolskiy
2022-05-23 15:30 ` Bryan O'Donoghue
2022-05-21 4:50 ` kernel test robot
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=19c92f9d-fa1c-fbe8-50ef-324da3e00695@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hfink@snap.com \
--cc=jgrahsl@snap.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mmitkov@quicinc.com \
--cc=robert.foss@linaro.org \
--cc=robh+dt@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).