From: Wolfram Sang <wsa@kernel.org>
To: Kristian Evensen <kristian.evensen@gmail.com>,
Qii Wang <qii.wang@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: mt7621 i2c fails with upstream driver
Date: Thu, 6 Jan 2022 14:23:53 +0100 [thread overview]
Message-ID: <YdbtaYzG9MX0pwMd@ninjato> (raw)
In-Reply-To: <CAKfDRXgUvN19PUd_ebRJs-k_ytrGwgA=e6d3QJ9cwJogUGpoyw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
Adding maintainers for this driver/platform to CC...
On Wed, Jan 05, 2022 at 10:51:38AM +0100, Kristian Evensen wrote:
> Hello,
>
> I am in the process of bringing kernel 5.10 up on an mt7621-based
> board. The board is equipped with a temperature sensor that is
> connected to the i2c bus. Reading the temperature worked fine with my
> previous kernel (OpenWRT 4.14/downstream i2c driver), but fails when I
> use the upstream driver.
>
> With the 5.10 i2c-mt7621-driver, i2cdetect is no longer able to detect
> the sensor and i2cget fails with "Error: Read failed". An strace of
> i2cget reveals the cause to be the final ioctl call failing with
> ETIMEDOUT.
>
> Replacing the new with the old driver makes i2c work again, but I
> would like to try to avoid that. My knowledge of i2c is very limited,
> so I wondered if anyone knows what could be wrong or have any
> suggestions on things I can try to for example change in the driver?
>
> Thanks in advance for any help,
> Kristian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-01-06 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 9:51 mt7621 i2c fails with upstream driver Kristian Evensen
2022-01-05 11:45 ` Kristian Evensen
2022-01-06 13:23 ` Wolfram Sang [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=YdbtaYzG9MX0pwMd@ninjato \
--to=wsa@kernel.org \
--cc=kristian.evensen@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=qii.wang@mediatek.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