archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <>
To: huangbibo <>
Subject: Re: [PATCH] i2c: designware: I2C unexpected interrupt handling will cause kernel panic
Date: Thu, 11 Nov 2021 18:13:42 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Nov 11, 2021 at 02:57:59PM +0800, huangbibo wrote:
> I2C interrupts may be triggered unexpectedly,

> such as programs that directly access I2C registers,

Wow! What programs you are talking about? How comes they are doing this
weirdness in parallel with the OS running?

Can you elaborate, please?

> bus conflicts caused by hardware design defects, etc.
> These can cause null pointer reference errors and kernel panic.

With Best Regards,
Andy Shevchenko

      parent reply	other threads:[~2021-11-11 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11  6:57 [PATCH] i2c: designware: I2C unexpected interrupt handling will cause kernel panic huangbibo
2021-11-11 14:05 ` Jarkko Nikula
     [not found]   ` <>
2021-11-12 10:26     ` andriy.shevchenko
2021-11-11 16:13 ` Andy Shevchenko [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).