From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jesper Dangaard Brouer <hawk@kernel.org>
Cc: Luis Oliveira <lolivei@synopsys.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>, Andi Shyti <andi.shyti@kernel.org>,
linux-i2c@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
kernel-team <kernel-team@cloudflare.com>
Subject: Re: Hitting WARN_ON_ONCE in i2c-designware-common.c
Date: Wed, 16 Apr 2025 09:37:58 +0300 [thread overview]
Message-ID: <Z_9QRqk_8rTkQVpx@smile.fi.intel.com> (raw)
In-Reply-To: <36736a3d-9ba1-43d7-ac52-d0f2f8a36bec@kernel.org>
On Tue, Apr 15, 2025 at 02:30:10PM +0200, Jesper Dangaard Brouer wrote:
> On 15/04/2025 14.19, Andy Shevchenko wrote:
> > On Tue, Apr 15, 2025 at 03:17:37PM +0300, Andy Shevchenko wrote:
> > > On Tue, Apr 15, 2025 at 02:03:26PM +0200, Jesper Dangaard Brouer wrote:
> > > >
> > > > I'm hitting a WARN_ON_ONCE in drivers/i2c/busses/i2c-designware-common.c
> > > > when booting the kernel on our Gen12 hardware.
> > > >
> > > > I'm using devel kernel net-next at commit 1a9239bb425 (merge tag
> > > > 'net-next-6.15').
> > > >
> > > > I assume you want this report.
> > > >
> > > > Maybe it is not a critical error(?)
> > > > ... looking the comment in the function:
> > >
> > > Have you forgotten to compile in the drivers/acpi/acpi_apd.c?
>
> I have double checked that drivers/acpi/acpi_apd.o is compiled.
Hmm... But is the function that creates clock is compiled? And does it succeed
(see also my comment about missing error check which you probably want to
address independently on the affection on this issue).
> > Also that driver has the missing error check in acpi_apd_setup() for
> > clk_register_clkdev().
>
> Are you saying I'm missing a .config option?
I'm saying that please double check that the clock is provided and AFAICT it
has to be created by the above mentioned module.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-04-16 6:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 12:03 Hitting WARN_ON_ONCE in i2c-designware-common.c Jesper Dangaard Brouer
2025-04-15 12:17 ` Andy Shevchenko
2025-04-15 12:19 ` Andy Shevchenko
2025-04-15 12:30 ` Jesper Dangaard Brouer
2025-04-16 6:37 ` Andy Shevchenko [this message]
2025-04-15 12:28 ` Jarkko Nikula
2025-04-15 12:45 ` Jesper Dangaard Brouer
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=Z_9QRqk_8rTkQVpx@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=hawk@kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lolivei@synopsys.com \
--cc=mika.westerberg@linux.intel.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