mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joshua Kinard <linux@kumba.dev>
To: Imre Kaloz <kaloz@kernel.org>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] rtc: ds1685: power-off fixes
Date: Mon, 26 Oct 2026 12:14:59 -0400	[thread overview]
Message-ID: <35a6296a-332a-4e7e-a199-26b99602caed@kumba.dev> (raw)
In-Reply-To: <20261013094930.574-1-kaloz@kernel.org>

On 10/13/2026 05:49, Imre Kaloz wrote:
> Two fixes for ds1685_rtc_poweroff(), on SGI O2 and Octane machines.
> 
> Patch 1 arms the wake-up alarm only if an alarm is set, so that stale
> alarm registers no longer power the machine back on.
> 
> Patch 2 repeats the PAB write, clearing the kickstart and wake-up
> flags with it, until power is removed.
> 
> Patch 1 was tested on an O2, patch 2 on an Octane.
> 
> Imre Kaloz (2):
>    rtc: ds1685: arm the wake-up alarm at power-off only if an alarm is
>      set
>    rtc: ds1685: keep setting PAB until power is removed
> 
>   drivers/rtc/rtc-ds1685.c | 38 +++++++++++++++++++++++++-------------
>   1 file changed, 25 insertions(+), 13 deletions(-)
> 
> 
> base-commit: 24a19b953e2a3d0ea5a8c4951a0ab8f32720c907

Both of these look good.  I am unable to test them right now, but it sounds 
like the second patch might fix the sporadic issue of an Octane sometimes 
not powering off.

Thanks!

Acked-by: Joshua Kinard <linux@kumba.dev>


      parent reply	other threads:[~2026-10-26 16:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13  9:49 Imre Kaloz
2026-10-13  9:49 ` [PATCH 1/2] rtc: ds1685: arm the wake-up alarm at power-off only if an alarm is set Imre Kaloz
2026-10-13  9:49 ` [PATCH 2/2] rtc: ds1685: keep setting PAB until power is removed Imre Kaloz
2026-10-26 16:14 ` Joshua Kinard [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=35a6296a-332a-4e7e-a199-26b99602caed@kumba.dev \
    --to=linux@kumba.dev \
    --cc=alexandre.belloni@bootlin.com \
    --cc=kaloz@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@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

all inboxes | Powered by JetHome®