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 13:41:15 +0200 [thread overview]
Message-ID: <ZQWUWwi7pR7/negW@shikoro> (raw)
In-Reply-To: <TYBPR01MB5341A56291AFCB54E4918167D8F7A@TYBPR01MB5341.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
Hi Shimoda-san,
I had a look now with Kieran's Spider and could reproduce your findings.
It is not a problem, though, because the system behaves the same with
plain v6.6-rc1. The only difference with my branch is that DEBUG is
enabled for the I2C driver, so we see all the messages regarding
EPROBE_DEFER with DMA. If you add DEBUG to plain v6.6-rc1, then you see
the same messages. But still, the busses get probed and they also get
DMA channels after some time when the DMA driver is finally loaded. So,
this really has nothing to do with the patches themselves, only with the
additions for debugging. Phew!
Thank you for reporting and testing, still!
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-09-16 11:42 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
2023-09-16 11:41 ` Wolfram Sang [this message]
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=ZQWUWwi7pR7/negW@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox