public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo2@yeah.net>
To: Mark Brown <broonie@kernel.org>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
	linux-kernel@vger.kernel.org, Shawn Guo <shawnguo@kernel.org>,
	stable@vger.kernel.org
Subject: Re: [PATCH] regmap: irq: Correct documentation of wake_invert flag
Date: Sat, 25 Oct 2025 14:55:25 +0800	[thread overview]
Message-ID: <aPx0XQTbFcD0kk9X@dragon> (raw)
In-Reply-To: <aPt6_lzhFYy5w0l0@finisterre.sirena.org.uk>

On Fri, Oct 24, 2025 at 02:11:26PM +0100, Mark Brown wrote:
> On Fri, Oct 24, 2025 at 04:23:44PM +0800, Shawn Guo wrote:
> 
> > Per commit 9442490a0286 ("regmap: irq: Support wake IRQ mask inversion")
> > the wake_invert flag is to support enable register, so cleared bits are
> > wake disabled.
> 
> > - * @wake_invert: Inverted wake register: cleared bits are wake enabled.
> > + * @wake_invert: Inverted wake register: cleared bits are wake disabled.
> 
> That sounds like what I'd expect for a normal polarity wake register?
> I'd expect to set the bit to enable, so inverting that means that
> instead we clear the bit which is what the original text says.

Hmm, am I misreading the wake disable code in regmap_add_irq_chip()?

	/* Wake is disabled by default */
	if (d->wake_buf) {
			...

			if (chip->wake_invert)
				ret = regmap_update_bits(d->map, reg,
							 d->mask_buf_def[i],
							 0);
			else
				ret = regmap_update_bits(d->map, reg,
							 d->mask_buf_def[i],
							 d->wake_buf[i]);
			...
	}

Isn't it clearing bits to disable wake for wake_invert flag?

Shawn


  reply	other threads:[~2025-10-25  6:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24  8:23 [PATCH] regmap: irq: Correct documentation of wake_invert flag Shawn Guo
2025-10-24 13:11 ` Mark Brown
2025-10-25  6:55   ` Shawn Guo [this message]
2025-10-28 17:25 ` Mark Brown

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=aPx0XQTbFcD0kk9X@dragon \
    --to=shawnguo2@yeah.net \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=stable@vger.kernel.org \
    /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