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: Mon, 23 May 2022 16:30:10 +0100 [thread overview]
Message-ID: <625094db-a1e7-b62c-9862-6e5b20420c97@linaro.org> (raw)
In-Reply-To: <e7bbe076-a1d1-a005-8110-5d35bc0d80de@linaro.org>
On 23/05/2022 14:50, Vladimir Zapolskiy wrote:
> it's some kind of a race related to probes of CAMSS, CCI and IMX412
> drivers.
>
> Since I'm able to reproduce it, I'll take the analysis on myself, and it
> does not
> interfere with your patch series.
Ah, I think I have it pretty much narrowed down now. Needed to switch
off modules entirely.
First probe fails, second probe succeeds.
Thanks anyway, I think I'm close to fix.
---
bod
next prev parent reply other threads:[~2022-05-23 15:30 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
2022-05-23 13:50 ` Vladimir Zapolskiy
2022-05-23 15:30 ` Bryan O'Donoghue [this message]
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=625094db-a1e7-b62c-9862-6e5b20420c97@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).