From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
imx@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-rtc@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: [PATCH 0/4] rtc/scmi: Support multiple RTCs
Date: Mon, 20 Jan 2025 10:25:32 +0800 [thread overview]
Message-ID: <20250120-rtc-v1-0-08c50830bac9@nxp.com> (raw)
i.MX95 System Manager(SM) BBM protocol exports two RTCs for EVK board.
one RTC is SoC internal RTC, the other is board RTC.
The current driver only use the 1st RTC. With this patchset, both RTCs
could be used in Linux. To achieve this:
1. Support more event sources for BBM protocol
2. Add bbm_info hook to let users could query the number of RTCs
3. Introduce devm_rtc_allocate_device_priv to support setting rtc device
private information
4. Update rtc-imx-sm-bbm.c to register both RTCs
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
Peng Fan (4):
firmware: arm_scmi: imx: Support more event sources
firmware: arm_scmi: imx: Introduce bbm_info hook
rtc: Introduce devm_rtc_allocate_device_priv
rtc: imx-sm-bbm: Support multiple RTCs
drivers/firmware/arm_scmi/vendors/imx/imx-sm-bbm.c | 33 ++++++++++-
drivers/rtc/class.c | 9 ++-
drivers/rtc/dev.c | 8 ++-
drivers/rtc/interface.c | 16 ++---
drivers/rtc/proc.c | 2 +-
drivers/rtc/rtc-imx-sm-bbm.c | 69 ++++++++++++++--------
include/linux/rtc.h | 2 +
include/linux/scmi_imx_protocol.h | 2 +
8 files changed, 100 insertions(+), 41 deletions(-)
---
base-commit: e7bb221a638962d487231ac45a6699fb9bb8f9fa
change-id: 20250116-rtc-3834e01786a8
Best regards,
--
Peng Fan <peng.fan@nxp.com>
next reply other threads:[~2025-01-20 2:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 2:25 Peng Fan (OSS) [this message]
2025-01-20 2:25 ` [PATCH 1/4] firmware: arm_scmi: imx: Support more event sources Peng Fan (OSS)
2025-01-20 2:25 ` [PATCH 2/4] firmware: arm_scmi: imx: Introduce bbm_info hook Peng Fan (OSS)
2025-01-20 2:25 ` [PATCH 3/4] rtc: Introduce devm_rtc_allocate_device_priv Peng Fan (OSS)
2025-01-20 10:57 ` Dan Carpenter
2025-01-21 14:35 ` Peng Fan
2025-01-21 15:15 ` Dan Carpenter
2025-01-20 2:25 ` [PATCH 4/4] rtc: imx-sm-bbm: Support multiple RTCs Peng Fan (OSS)
2025-02-11 17:01 ` Sudeep Holla
2025-02-12 6:41 ` Peng Fan
2025-02-12 10:44 ` Sudeep Holla
2025-01-20 10:21 ` [PATCH 0/4] rtc/scmi: " Alexandre Belloni
2025-01-21 14:31 ` Peng Fan
2025-02-03 11:50 ` Peng Fan
2025-02-11 16:59 ` Sudeep Holla
2025-02-12 6:35 ` Peng Fan
2025-02-12 10:43 ` Sudeep Holla
2025-02-12 17:01 ` Alexandre Belloni
2025-02-13 3:30 ` Peng Fan
2025-02-13 8:20 ` Alexandre Belloni
2025-02-13 10:52 ` Peng Fan
2025-02-13 11:26 ` Alexandre Belloni
2025-02-13 13:35 ` Peng Fan
2025-02-13 12:54 ` Alexandre Belloni
2025-02-14 3:55 ` Peng Fan
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=20250120-rtc-v1-0-08c50830bac9@nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=sudeep.holla@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox