All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: alexandre.belloni@bootlin.com, linux-rtc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtc: bd70528: properly enable wakeup
Date: Thu, 10 Sep 2026 16:23:04 +0200	[thread overview]
Message-ID: <20260910162304.25333671@kemnade.info> (raw)
In-Reply-To: <af4854a4-d626-4896-af62-312b49b94f71@gmail.com>

On Thu, 10 Sep 2026 13:28:23 +0300
Matti Vaittinen <mazziesaccount@gmail.com> wrote:

> On 10/09/2026 12:25, Andreas Kemnade wrote:
> > Wakeup on RTC alarm now only accidentially works when wakeup for the power
> > button connected to the same PMIC is also enabled. Fix that by properly
> > specifying the wakeup irq.
> > 
> > Signed-off-by: Andreas Kemnade <andreas@kemnade.info>  
> 
> Reviewed-by: Matti Vaittinen <mazziesaccount@gmail.com>
> 
> Thanks!
> 
> By the way, I am not 100% sure all of the PMICs using this driver even 
> have a power button input. I suspect some doesn't (maybe bd71815). I 
> wouldn't be against Fixes -tag :)
> 
looking at mfd driver:

                 * BD71815 data-sheet does not list the power-button IRQ so we
                 * don't use it.
                 */
                button_irq = 0;
....

 if (button_irq) {
                ret = rohm_register_pwrbutton(&i2c->dev, button_irq,
                                              "bd71828-pwrkey", true, irq_domain);
                if (ret)
                        return ret;
        }
....
so you are right about the power button.
Sashiko wants some error-checking there, so I'll send a
v2 with a fixes-tag and error checking.

Regards,
Andreas

      reply	other threads:[~2026-09-10 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10  9:25 [PATCH] rtc: bd70528: properly enable wakeup Andreas Kemnade
2026-09-10  9:35 ` sashiko-bot
2026-09-10 10:28 ` Matti Vaittinen
2026-09-10 14:23   ` Andreas Kemnade [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=20260910162304.25333671@kemnade.info \
    --to=andreas@kemnade.info \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=mazziesaccount@gmail.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 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.