linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: qii.wang@mediatek.com
Cc: matthias.bgg@gmail.com, linux-i2c@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
	srv_heupstream@mediatek.com, leilk.liu@mediatek.com
Subject: Re: [v2] i2c: mediatek: Move suspend and resume handling to NOIRQ phase
Date: Wed, 2 Dec 2020 16:35:43 +0100	[thread overview]
Message-ID: <20201202153543.GG874@kunai> (raw)
In-Reply-To: <1605701861-30800-1-git-send-email-qii.wang@mediatek.com>

[-- Attachment #1: Type: text/plain, Size: 480 bytes --]

Hi,

> Some i2c device driver indirectly uses I2C driver when it is now
> being suspended. The i2c devices driver is suspended during the
> NOIRQ phase and this cannot be changed due to other dependencies.
> Therefore, we also need to move the suspend handling for the I2C
> controller driver to the NOIRQ phase as well.
> 
> Signed-off-by: Qii Wang <qii.wang@mediatek.com>

Is this a bugfix and should go into 5.10? Or can it wait for 5.11?

Thanks,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-12-02 15:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 12:17 [v2] i2c: mediatek: Move suspend and resume handling to NOIRQ phase qii.wang
2020-12-02 15:35 ` Wolfram Sang [this message]
2020-12-03  1:25   ` Qii Wang
2020-12-03  8:01     ` Grygorii Strashko
2020-12-07  7:33       ` Qii Wang
2020-12-07 16:35         ` Grygorii Strashko
2020-12-10  1:56           ` Qii Wang
2020-12-10 13:03             ` Grygorii Strashko
2020-12-14  8:48               ` Qii Wang
2020-12-14 20:08                 ` Grygorii Strashko
2020-12-15 13:08                   ` Qii Wang
2020-12-23  6:31                   ` Qii Wang

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=20201202153543.GG874@kunai \
    --to=wsa@the-dreams.de \
    --cc=leilk.liu@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=qii.wang@mediatek.com \
    --cc=srv_heupstream@mediatek.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;
as well as URLs for NNTP newsgroup(s).