From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.andi.de1.cc (mail.andi.de1.cc [178.238.236.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 67D7640FDA1; Mon, 2 Mar 2026 15:11:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=178.238.236.174 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772464317; cv=none; b=Z6c+hEvufVbkNQMsUWBeHocOAepNFC6KvSsJWn7SmRt1pc1QubKlGzq2HpVjXgjjLCAkrJ/jiO3aoY/FI2QP3l5zpti8HkVD0nkfiDjvcirEDZ9SI1DC4x8DK1CwSYRNFV0wSGr09cQdhX+YxIwYyqG19saKNCRMQKo8Jr9+gZc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772464317; c=relaxed/simple; bh=3iYO0kg6ueKYDxo+WUqxQW/1ohu/Io5iWqOcMOoZVaY=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=QssdM/O35g7ViXM5tIHHDoiMt1NW4MBvyMGz91fwp48riO+A3zao7k5PLnBPQD3GhjfrOZ8yZHeXlsLeK31H1FBes71YOktETSfoZwjxFR9bpPDONPY/61KlmS5rsmsHV8i1JvkNRh0+vaZlMA7+oXf7XU16/Yj6I8Pgzs0JurA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=kemnade.info; spf=pass smtp.mailfrom=kemnade.info; dkim=pass (2048-bit key) header.d=kemnade.info header.i=@kemnade.info header.b=noBkohPQ; arc=none smtp.client-ip=178.238.236.174 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=kemnade.info Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=kemnade.info Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kemnade.info header.i=@kemnade.info header.b="noBkohPQ" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kemnade.info; s=20220719; h=References:In-Reply-To:Cc:From:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID; bh=fOE00VOY5CO+udhbXmZXmQz9cKeY+YffWZiDPf2sZPk=; b=noBkohPQtvbuoZmsWo6lCfVC0v wnxzq1SQ5Lj/pBCMSx747FmzuCK3eO9Ch94CEp6EBHx2GpGzcEerfJlEq3n25yBTSh935UFK8DGD4 SzpfFNUZZdnGXXIg7FSlb6nQN0crQj1+1RVt0ZZrhPMu/VabG3RzgYsd+0pDI8YtVWoftgAogzXGG /Kt60pHaK6B/3iUjTMbmMNc/i8GCJHUQ93IX3MyLxeBxH+Y2VHs239W1HoqMHwAv+BQ0YU39VuaD6 rxdtCJn8AyOra+wikSbvm26LeV9ISHk9b2tds38fBYg7DDQIVOZYTRpNq1xyd648ZITveXnM4+DWx DsvP98lQ==; Date: Mon, 2 Mar 2026 16:09:23 +0100 From: Andreas Kemnade To: Kalle Niemi Cc: Bartosz Golaszewski , Wolfram Sang , Bartosz Golaszewski , Mukesh Kumar Savaliya , Viken Dadhaniya , Andi Shyti , Florian Fainelli , Ray Jui , Branden Scott , bcm-kernel-feedback-list@broadcom.com, Vignesh R , Aaro Koskinen , Janusz Krzysztofik , Tony Lindgren , Kevin Hilman , Roger Quadros , Geert Uytterhoeven , Magnus Damm , Patrice Chotard , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , Linus Walleij , Frank Li , linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-omap@vger.kernel.org, linux-renesas-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev, linux-rpi-kernel@lists.infradead.org, Matti Vaittinen Subject: Re: [PATCH v2 01/12] i2c: allow setting the parent device and OF node through the adapter struct Message-ID: <20260302160923.53abf2ea@kemnade.info> In-Reply-To: References: X-Mailer: Claws Mail 4.3.1 (GTK 3.24.49; aarch64-unknown-linux-gnu) Precedence: bulk X-Mailing-List: linux-omap@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, 2 Mar 2026 12:38:27 +0200 Kalle Niemi wrote: > =EF=BB=BFOn 3/2/26 10:55, Bartosz Golaszewski wrote: > > On Mon, Mar 2, 2026 at 8:47=E2=80=AFAM Kalle Niemi wrote: =20 > >> On 2/23/26 11:05, Bartosz Golaszewski wrote: =20 > >>> In order to stop i2c bus drivers from dereferencing the struct device > >>> embedded in struct i2c_adapter, let's allow configuring the parent > >>> device and OF-node of the adapter directly through dedicated fields. > >>> Signed-off-by: Bartosz Golaszewski > >>> --- =20 > >> Hello, > >> Automated driver test system bisected this commit to be the first bad > >> commit, linux-next next-20260227 was tested. Failed tests include driv= er > >> tests for ROHM PMIC and accelerometers, which are connected to > >> BeagleBone Black. > >> The failed driver tests all fail to first i2cget and the tests stop > >> there: "Could not open file '/dev/i2c-2' or 'dev/i2c/2': No such file = or > >> directory". =20 > > Wolfram: well, now it would actually be useful to know which commit > > exactly is the culprit so maybe splitting the changes is not a bad > > idea after all. > > Kalle: which i2c bus driver fails here? Any errors in kernel log? > > Bart =20 >=20 > Hello Bart, >=20 > i2c-1 and i2c-2 are failing. I am not seeing any i2c errors in kernel log= . I got two failures without the dmesg available (this is bugged test seque= nce, and not a kernel crash), but those got the same stdout message "Could = not open file ...." as all others. >=20 Probably I am using the same host driver tested on OMAP3 DM3730, result: i2c drivers get bound to their devices, no obvious trouble. But controllers are registered with high indexes. localhost:~# i2cdetect -l i2c-3 i2c OMAP I2C adapter I2C adapter i2c-4 i2c OMAP I2C adapter I2C adapter i2c-5 i2c OMAP I2C adapter I2C adapter localhost:~# uname -a Linux localhost 7.0.0-rc1-next-20260227 #27 SMP Mon Mar 2 11:56:27 CET 202= 6 armv7l Linux Regards, Andreas