From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Caleb Connolly <caleb.connolly@linaro.org>,
Alexey Klimov <alexey.klimov@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 0/2] arm64: dts: qcom: switch RB1 and RB2 platforms to i2c2-gpio
Date: Wed, 5 Jun 2024 22:20:30 -0500 [thread overview]
Message-ID: <171764403327.730206.16478168003566814778.b4-ty@kernel.org> (raw)
In-Reply-To: <20240605-rb12-i2c2g-pio-v2-0-946f5d6b6948@linaro.org>
On Wed, 05 Jun 2024 11:55:55 +0300, Dmitry Baryshkov wrote:
> On the Qualcomm RB1 and RB2 platforms the I2C bus connected to the
> LT9611UXC bridge under some circumstances can go into a state when all
> transfers timeout. This causes both issues with fetching of EDID and
> with updating of the bridge's firmware.
>
> While we are debugging the issue, switch corresponding I2C bus to use
> i2c-gpio driver. While using i2c-gpio no communication issues are
> observed.
>
> [...]
Applied, thanks!
[1/2] arm64: dts: qcom: qrb2210-rb1: switch I2C2 to i2c-gpio
commit: b7b545ccc08873e107aa24c461b1fdb123dd3761
[2/2] arm64: dts: qcom: qrb4210-rb2: switch I2C2 to i2c-gpio
commit: f77e7bd40c3c2d79685e9cc80de874b69a976f55
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-06-06 3:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 8:55 Dmitry Baryshkov
2024-06-05 8:55 ` [PATCH v2 1/2] arm64: dts: qcom: qrb2210-rb1: switch I2C2 to i2c-gpio Dmitry Baryshkov
2024-06-05 11:45 ` Caleb Connolly
2024-06-05 8:55 ` [PATCH v2 2/2] arm64: dts: qcom: qrb4210-rb2: " Dmitry Baryshkov
2024-06-05 11:44 ` Caleb Connolly
2024-06-06 3:20 ` Bjorn Andersson [this message]
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=171764403327.730206.16478168003566814778.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=alexey.klimov@linaro.org \
--cc=caleb.connolly@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®