public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Frank.Li@nxp.com, ping.bai@nxp.com, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Subject: Re: [PATCH V4] Input: bbnsm_pwrkey - add remove hook
Date: Mon, 16 Dec 2024 09:33:40 -0800	[thread overview]
Message-ID: <Z2BkdFHZnj-pDOoN@google.com> (raw)
In-Reply-To: <20241212030322.3110017-1-peng.fan@oss.nxp.com>

On Thu, Dec 12, 2024 at 11:03:22AM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
> 
> Without remove hook to clear wake irq, there will be kernel dump when
> doing module test.
> "bbnsm_pwrkey 44440000.bbnsm:pwrkey: wake irq already initialized"
> 
> Add remove hook to clear wake irq and set wakeup to false.
> 
> Fixes: 40e40fdfec3f ("Input: bbnsm_pwrkey - add bbnsm power key support")
> Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> 
> V4:
>  Fix build warning
> 
> V3:
>  I tried to dev_pm_clear_wake_irq in common code, but Greg rejected:
>  https://lore.kernel.org/all/2024111213-eradicate-puma-3592@gregkh/
>  So post v3 with input_unregister_device dropped

Greg did not reject the patch, he asked for a better justification.
Please answer his questions (we clear a lot of resources in remove() to
reduce boilerplate in the drivers), in the meantime I will apply this
patch to fix the pressing issue.

Thanks.

-- 
Dmitry

      reply	other threads:[~2024-12-16 17:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12  3:03 [PATCH V4] Input: bbnsm_pwrkey - add remove hook Peng Fan (OSS)
2024-12-16 17:33 ` Dmitry Torokhov [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=Z2BkdFHZnj-pDOoN@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=Frank.Li@nxp.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=ping.bai@nxp.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