All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kane Chen <kane.chen@intel.com>
To: stable@vger.kernel.org
Cc: kane.chen@intel.com
Subject: [PATCH v1] rtc: cmos: avoid UIP when writing/reading alarm time
Date: Wed,  7 Dec 2022 11:57:22 +0800	[thread overview]
Message-ID: <20221207035722.15749-1-kane.chen@intel.com> (raw)

While runnings s0ix cycling test based on rtc alarm wakeup on ADL-P devices,
We found the data from CMOS_READ is not reasonable and causes RTC wake up fail.

With the below changes, we don't see unreasonable data from cmos and issue is gone.

cd17420: rtc: cmos: avoid UIP when writing alarm time
cdedc45: rtc: cmos: avoid UIP when reading alarm time
ec5895c: rtc: mc146818-lib: extract mc146818_avoid_UIP
ea6fa49: rtc: mc146818-lib: fix RTC presence check
13be2ef: rtc: cmos: Disable irq around direct invocation of cmos_interrupt()
0dd8d6c: rtc: Check return value from mc146818_get_time()
e1aba37: rtc: cmos: remove stale REVISIT comments
6950d04: rtc: cmos: Replace spin_lock_irqsave with spin_lock in hard IRQ
d35786b: rtc: mc146818-lib: change return values of mc146818_get_time()
ebb22a0: rtc: mc146818: Dont test for bit 0-5 in Register D
211e5db: rtc: mc146818: Detect and handle broken RTCs
dcf257e: rtc: mc146818: Reduce spinlock section in mc146818_set_time()
05a0302: rtc: mc146818: Prevent reading garbage


All of the above patches are landed on 6.0.11 stable kernel
I'd like pick the above patches back to 5.10 longterm kernel
Thanks


-- 
2.17.1


             reply	other threads:[~2022-12-07  3:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07  3:57 Kane Chen [this message]
2022-12-07  5:13 ` [PATCH v1] rtc: cmos: avoid UIP when writing/reading alarm time Sasha Levin
2022-12-07  6:51   ` Chen, Kane
2022-12-08 21:47     ` Mateusz Jończyk
2022-12-09  0:37       ` Sasha Levin
2022-12-09 22:40         ` Mateusz Jończyk
2022-12-11  6:09           ` Sasha Levin
2022-12-11  8:31             ` Chen, Kane

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=20221207035722.15749-1-kane.chen@intel.com \
    --to=kane.chen@intel.com \
    --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 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.