All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@kernel.org>
To: Markus Elfring <Markus.Elfring@web.de>,
	 Peter Korsgaard <peter@korsgaard.com>,
	Andrew Lunn <andrew@lunn.ch>,
	 Thomas Gleixner <tglx@linutronix.de>,
	linux-i2c@vger.kernel.org,  linux-kernel@vger.kernel.org,
	Grygorii Tertychnyi <grembeter@gmail.com>
Cc: Grygorii Tertychnyi <grygorii.tertychnyi@leica-geosystems.com>,
	 bsp-development.geo@leica-geosystems.com,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] i2c: ocores: set IACK bit after core is enabled
Date: Fri, 21 Jun 2024 01:19:46 +0200	[thread overview]
Message-ID: <171892558671.2178094.6404949110171049934.b4-ty@kernel.org> (raw)
In-Reply-To: <20240520153932.116731-1-grygorii.tertychnyi@leica-geosystems.com>

Hi

On Mon, 20 May 2024 17:39:32 +0200, Grygorii Tertychnyi wrote:
> Setting IACK bit when core is disabled does not clear the "Interrupt Flag"
> bit in the status register, and the interrupt remains pending.
> 
> Sometimes it causes failure for the very first message transfer, that is
> usually a device probe.
> 
> Hence, set IACK bit after core is enabled to clear pending interrupt.
> 
> [...]

Applied to i2c/i2c-host-next on

git://git.kernel.org/pub/scm/linux/kernel/git/local tree

Thank you,
Andi

Patches applied
===============
[1/1] i2c: ocores: set IACK bit after core is enabled
      commit: 5a72477273066b5b357801ab2d315ef14949d402


      parent reply	other threads:[~2024-06-21  2:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-20 15:39 [PATCH v2] i2c: ocores: set IACK bit after core is enabled Grygorii Tertychnyi
2024-05-20 17:00 ` Markus Elfring
2024-05-20 18:20   ` Greg KH
2024-06-02 13:07 ` grygorii tertychnyi
2024-06-17 17:22 ` grygorii tertychnyi
2024-06-20 23:19 ` Andi Shyti [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:
  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=171892558671.2178094.6404949110171049934.b4-ty@kernel.org \
    --to=andi.shyti@kernel.org \
    --cc=Markus.Elfring@web.de \
    --cc=andrew@lunn.ch \
    --cc=bsp-development.geo@leica-geosystems.com \
    --cc=grembeter@gmail.com \
    --cc=grygorii.tertychnyi@leica-geosystems.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@korsgaard.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.