From: Sudeep Holla <sudeep.holla@arm.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: 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>,
<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: Re: [PATCH 4/4] rtc: imx-sm-bbm: Support multiple RTCs
Date: Tue, 11 Feb 2025 17:01:12 +0000 [thread overview]
Message-ID: <Z6uCWK8jMTP7wInM@bogus> (raw)
In-Reply-To: <20250120-rtc-v1-4-08c50830bac9@nxp.com>
On Mon, Jan 20, 2025 at 10:25:36AM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> i.MX95 EVK has two RTCs exported by SCMI BBM protocol. Current driver
> only enables the 1st RTC inside BBNSM module, leaving the board RTC
> not used by Linux.
>
> To use the 2nd RTC, use 'bbm_info' to get the number of RTCs, register
> them all, and set 'bbnsm' as private info for rtc device to know which
> RTC it is when using rtc_class_ops to access rtc device.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> drivers/rtc/rtc-imx-sm-bbm.c | 69 +++++++++++++++++++++++++++-----------------
> 1 file changed, 43 insertions(+), 26 deletions(-)
>
> diff --git a/drivers/rtc/rtc-imx-sm-bbm.c b/drivers/rtc/rtc-imx-sm-bbm.c
> index daa472be7c80697aa3cd3432eccef0c877e4c378..a29b30555d0c0581ecaa8b79760209dc780d2f0e 100644
> --- a/drivers/rtc/rtc-imx-sm-bbm.c
> +++ b/drivers/rtc/rtc-imx-sm-bbm.c
> @@ -15,16 +15,18 @@ struct scmi_imx_bbm {
> struct rtc_device *rtc_dev;
> struct scmi_protocol_handle *ph;
> struct notifier_block nb;
> + u32 bbm_rtc_id;
Is it not same as rtc_dev->id ? Why do you need a copy in this wrapper/
container structure ?
--
Regards,
Sudeep
next prev parent reply other threads:[~2025-02-11 17:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 2:25 [PATCH 0/4] rtc/scmi: Support multiple RTCs Peng Fan (OSS)
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 [this message]
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=Z6uCWK8jMTP7wInM@bogus \
--to=sudeep.holla@arm.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=peng.fan@oss.nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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.