From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Zhipeng Wang <zhipeng.wang_1@nxp.com>
Cc: "daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"tglx@kernel.org" <tglx@kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"chun-hung.wu@mediatek.com" <chun-hung.wu@mediatek.com>,
"walter.chang@mediatek.com" <walter.chang@mediatek.com>,
"jstultz@google.com" <jstultz@google.com>,
"amergnat@baylibre.com" <amergnat@baylibre.com>,
Aisheng Dong <aisheng.dong@nxp.com>,
Jindong Yue <jindong.yue@nxp.com>,
Xuegang Liu <xuegang.liu@nxp.com>,
Greg Kroah-Hartman <gregkh@google.com>
Subject: Re: [EXT] Re: [PATCH v4 3/4] clocksource/drivers/timer-mediatek: Convert timer-mediatek to a loadable module
Date: Sun, 8 Mar 2026 20:51:06 +0100 [thread overview]
Message-ID: <6255aa0f-529c-41cb-be32-e5d54a839125@oss.qualcomm.com> (raw)
In-Reply-To: <AS8PR04MB84206CF559371D3966653F8EEB7AA@AS8PR04MB8420.eurprd04.prod.outlook.com>
On 3/6/26 06:46, Zhipeng Wang wrote:
> Hi Daniel,
>
> Thank you for sharing your RFC patch. I think the approach is very
> interesting and addresses a real problem in the timer subsystem.
>
> For the MediaTek and IMX timer driver, I see a few considerations:
>
> 1. Current approach: My current patch uses the existing pattern
> (similar to renesas-ostm.c) with #ifdef MODULE. It's simple and
> works, but I agree it's not ideal.
> 2. Your approach: Your TIMER_OF_DECLARE_PDEV approach would be
> cleaner and allow us to use devm_ functions, which would be a
> nice improvement.
> 3. MediaTek and IMX timer specifics: The IMX timer doesn't require
> early initialization on modern platforms (we have arch timers on
> ARM64), so it would fit well with your TIMER_OF_DECLARE_PLATFORM_DRIVER
> macro (if you go with the two-macro approach).
>
> I'm very interested in your approach. May I ask what timeline you're
> considering for your patch series?
> The reason I ask is that we're working towards GKI support and I want
> to make sure I choose the right approach.
Well, if you are willing to collaborate, we can start right now to think
about it and propose an unified solution
next prev parent reply other threads:[~2026-03-08 19:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 8:12 [PATCH v4 0/4] clocksource: Add module support for timer drivers Zhipeng Wang
2026-03-04 8:12 ` [PATCH v4 1/4] clocksource/drivers/mmio: Export clocksource_mmio_init() Zhipeng Wang
2026-03-04 8:12 ` [PATCH v4 2/4] clocksource/drivers/timer-of: Remove __init markings Zhipeng Wang
2026-03-04 8:12 ` [PATCH v4 3/4] clocksource/drivers/timer-mediatek: Convert timer-mediatek to a loadable module Zhipeng Wang
2026-03-04 19:02 ` Daniel Lezcano
2026-03-06 5:46 ` [EXT] " Zhipeng Wang
2026-03-08 19:51 ` Daniel Lezcano [this message]
2026-03-09 5:31 ` Zhipeng Wang
2026-03-09 6:14 ` Trilok Soni
2026-03-09 9:38 ` Daniel Lezcano
2026-03-10 8:41 ` Zhipeng Wang
2026-03-25 14:42 ` Daniel Lezcano
2026-03-26 10:34 ` Zhipeng Wang
2026-03-04 8:12 ` [PATCH v4 4/4] clocksource/drivers/imx-tpm: Support building imx-tpm driver as module Zhipeng Wang
2026-03-05 13:44 ` kernel test robot
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=6255aa0f-529c-41cb-be32-e5d54a839125@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=aisheng.dong@nxp.com \
--cc=amergnat@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chun-hung.wu@mediatek.com \
--cc=daniel.lezcano@linaro.org \
--cc=festevam@gmail.com \
--cc=gregkh@google.com \
--cc=imx@lists.linux.dev \
--cc=jindong.yue@nxp.com \
--cc=jstultz@google.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tglx@kernel.org \
--cc=walter.chang@mediatek.com \
--cc=xuegang.liu@nxp.com \
--cc=zhipeng.wang_1@nxp.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