[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <TYBPR01MB5341132B818922E7C01A915FD8FAA@TYBPR01MB5341.jpnprd01.prod.outlook.com>
Date: Tue, 19 Sep 2023 12:23:32 +0000
From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>
CC: "linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-renesas-soc@...r.kernel.org"
<linux-renesas-soc@...r.kernel.org>
Subject: RE: [PATCH 0/2] i2c: rcar: add support for Gen4 devices
Hi Wolfram-san,
> From: Wolfram Sang, Sent: Saturday, September 16, 2023 8:41 PM
>
> 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 the investigation! I also confirmed that reverting the "DEBUG"
commit resolved the issue about the EPROBE_DEFER.
> Thank you for reporting and testing, still!
You're welcome!
Best regards,
Yoshihiro Shimoda
> Wolfram
Powered by blists - more mailing lists