From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 0/2] i2c: rcar: add support for Gen4 devices
Date: Sat, 16 Sep 2023 09:15:55 +0200 [thread overview]
Message-ID: <ZQVWK9Q2YtbehvjW@shikoro> (raw)
In-Reply-To: <TYBPR01MB5341A56291AFCB54E4918167D8F7A@TYBPR01MB5341.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
Hi Shimoda-san,
> I tested the branch on the Spider, and then the i2c cannot be probed with the following errors:
> -----
> # dmesg | grep i2c
> [ 1.528773] i2c_dev: i2c /dev entries driver
> [ 1.533572] i2c-rcar e6500000.i2c: clk 395647/400000(133333333), round 46, CDF: 6 SMD 20 SCL gran 27
These values look good and match the values from Falcon.
> [ 1.554646] i2c-rcar e6500000.i2c: request_channel failed for tx (-517)
> [ 1.561487] i2c-rcar e6500000.i2c: request_channel failed for tx (-517)
> [ 1.568133] i2c-rcar e6500000.i2c: request_channel failed for rx (-517)
-EPROBE_DEFER when requesting the DMA channel? This is weird, at first
glimpse this seems unrelated to my series. But you say v6.6-rc1 works
fine. Strange.
> I checked that the v6.6-rc1 (commit 0bb80ecc33a8) could worked correctly.
> JFYI, I pasted whole log at the end of this email. Should I do git bisect to find
> a bad commit on the branch?
Very kind of you but I think this is not needed. There is a Spider in
Kieran's lab and I will try to reproduce the issue there myself. If that
doesn't work, I'll come back to you.
Thank you for the report!
All the best,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-09-16 7:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 20:32 [PATCH 0/2] i2c: rcar: add support for Gen4 devices Wolfram Sang
2023-09-13 20:32 ` [PATCH 1/2] i2c: rcar: introduce " Wolfram Sang
2023-09-19 9:33 ` Geert Uytterhoeven
2023-09-19 14:24 ` Wolfram Sang
2023-09-13 20:32 ` [PATCH 2/2] i2c: rcar: add FastMode+ support for Gen4 Wolfram Sang
2023-09-19 9:51 ` Geert Uytterhoeven
2023-09-19 15:02 ` Wolfram Sang
2023-09-14 13:03 ` [PATCH 0/2] i2c: rcar: add support for Gen4 devices Yoshihiro Shimoda
2023-09-16 7:15 ` Wolfram Sang [this message]
2023-09-16 11:41 ` Wolfram Sang
2023-09-19 12:23 ` Yoshihiro Shimoda
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=ZQVWK9Q2YtbehvjW@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.