From: Sasha Levin <sashal@kernel.org>
To: Kane Chen <kane.chen@intel.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v1] rtc: cmos: avoid UIP when writing/reading alarm time
Date: Wed, 7 Dec 2022 00:13:13 -0500 [thread overview]
Message-ID: <Y5Ag6YhxcPPbs4Jr@sashalap> (raw)
In-Reply-To: <20221207035722.15749-1-kane.chen@intel.com>
On Wed, Dec 07, 2022 at 11:57:22AM +0800, Kane Chen wrote:
>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.
Thanks for the analysis, I can queue most of these up. There are two
which won't go in:
>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
This one fixes a commit which isn't in the 5.10 tree.
>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()
This one looks like an optimization.
--
Thanks,
Sasha
next prev parent reply other threads:[~2022-12-07 5:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 3:57 [PATCH v1] rtc: cmos: avoid UIP when writing/reading alarm time Kane Chen
2022-12-07 5:13 ` Sasha Levin [this message]
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=Y5Ag6YhxcPPbs4Jr@sashalap \
--to=sashal@kernel.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox