From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Mateusz Jończyk" <mat.jonczyk@o2.pl>
Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>,
Huacai Chen <chenhuacai@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-mips@vger.kernel.org, linux-rtc@vger.kernel.org
Subject: Re: [PATCH 0/4] mips: CMOS RTC refactoring
Date: Wed, 16 Jul 2025 20:07:00 +0200 [thread overview]
Message-ID: <aHfqRH7vwcjmamMd@alpha.franken.de> (raw)
In-Reply-To: <20250713100434.699843-1-mat.jonczyk@o2.pl>
On Sun, Jul 13, 2025 at 12:04:30PM +0200, Mateusz Jończyk wrote:
> Hello,
>
> A while ago I wrote some patches that refactor a bit the RTC CMOS support on the
> MIPS architecture. These were in response to a bug report about locking
> problems during suspend / resume:
>
> Link: https://lore.kernel.org/all/CAP-bSRZ0CWyZZsMtx046YV8L28LhY0fson2g4EqcwRAVN1Jk+Q@mail.gmail.com/
>
> Back then, I was trying to convert the rtc_lock to a raw spinlock. This proved
> to be unnecessary and harmful, but in the process I removed some dead and
> duplicated code that touches the MC146818 (the chip of the CMOS RTC) for
> the MIPS architecture.
>
> These patches were tested only in an emulator, as I don't have the hardware.
> They are roughly in the order of increasing risk.
>
> Greetings,
> Mateusz
>
> Mateusz Jończyk (4):
> mips: remove unused function mc146818_set_rtc_mmss
> mips/mach-rm: remove custom mc146818rtc.h file
> mips: remove redundant macro mc146818_decode_year
> mips/malta,loongson2ef: use generic mc146818_get_time function
>
> arch/mips/Kconfig | 2 +
> .../include/asm/mach-generic/mc146818rtc.h | 4 -
> arch/mips/include/asm/mach-jazz/mc146818rtc.h | 2 -
> .../mips/include/asm/mach-malta/mc146818rtc.h | 2 -
> arch/mips/include/asm/mach-rm/mc146818rtc.h | 21 ----
> arch/mips/include/asm/mc146818-time.h | 105 ++----------------
> 6 files changed, 9 insertions(+), 127 deletions(-)
> delete mode 100644 arch/mips/include/asm/mach-rm/mc146818rtc.h
>
>
> base-commit: d7b8f8e20813f0179d8ef519541a3527e7661d3a
> --
> 2.25.1
series applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2025-07-16 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-13 10:04 [PATCH 0/4] mips: CMOS RTC refactoring Mateusz Jończyk
2025-07-13 10:04 ` [PATCH 1/4] mips: remove unused function mc146818_set_rtc_mmss Mateusz Jończyk
2025-07-13 10:04 ` [PATCH 2/4] mips/mach-rm: remove custom mc146818rtc.h file Mateusz Jończyk
2025-07-13 10:04 ` [PATCH 3/4] mips: remove redundant macro mc146818_decode_year Mateusz Jończyk
2025-07-13 10:04 ` [PATCH 4/4] mips/malta,loongson2ef: use generic mc146818_get_time function Mateusz Jończyk
2025-07-16 18:07 ` Thomas Bogendoerfer [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=aHfqRH7vwcjmamMd@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=alexandre.belloni@bootlin.com \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-mips@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mat.jonczyk@o2.pl \
/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.