From: Vinod <vkoul@kernel.org>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Cc: swboyd@chromium.org, wsa+renesas@sang-engineering.com,
linux-i2c@vger.kernel.org, bjorn.andersson@linaro.org,
linux-arm-msm@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Todor Tomov <todor.tomov@linaro.org>
Subject: Re: [PATCH v4 2/2] i2c: Add Qualcomm CCI I2C driver
Date: Fri, 21 Sep 2018 08:36:01 -0700 [thread overview]
Message-ID: <20180921153601.GF2350@vkoul-mobl> (raw)
In-Reply-To: <CAPybu_0Patmox+1rd19mD03qfSbhNzR+6gmaJwsmhu650s36fA@mail.gmail.com>
Hi Ricardo,
On 20-09-18, 21:39, Ricardo Ribalda Delgado wrote:
> Sorry to enter the discussion this late.
>
> I have been using this driver with release/qcomlt-4.14 on a db820c and
> if I try to use the i2c bus before camss is running I get a Timeout
> error and the bus is unusable after that. I have sent a patch that
> fixes this issue, in case you want to merge it/add it before this
> driver goes upstream.
Thanks for this, I will test and port the fix to upstream and send it
along.
> Is there a way to use the i2c bus without using the camera?
This is Camera specific bus but it is an i2c bus, so theoretically it
should be possible to do so, Todor do you know if that is doable/done?
--
~Vinod
next prev parent reply other threads:[~2018-09-21 15:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 6:39 [PATCH v4 0/2] i2c: Add support for Qcom CCI I2C controller Vinod Koul
2018-08-20 6:39 ` [PATCH v4 1/2] dt-bindings: i2c: Add binding for Qualcomm " Vinod Koul
2018-08-20 18:18 ` Rob Herring
2018-08-21 9:28 ` Vinod
2018-08-21 13:11 ` Rob Herring
2018-08-21 13:12 ` Rob Herring
2018-08-21 16:00 ` Vinod
2018-08-20 6:39 ` [PATCH v4 2/2] i2c: Add Qualcomm CCI I2C driver Vinod Koul
2018-08-24 7:30 ` Stephen Boyd
2018-08-24 10:16 ` Vinod
2018-08-27 19:19 ` Stephen Boyd
2018-08-28 3:38 ` Vinod
2018-09-20 19:39 ` Ricardo Ribalda Delgado
2018-09-21 15:36 ` Vinod [this message]
2018-09-21 15:43 ` Todor Tomov
2018-09-22 22:02 ` Ricardo Ribalda Delgado
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=20180921153601.GF2350@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=ricardo.ribalda@gmail.com \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.org \
--cc=todor.tomov@linaro.org \
--cc=wsa+renesas@sang-engineering.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