From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-rtc@vger.kernel.org, linux-efi@vger.kernel.org
Subject: Re: [PATCH 4/9] rtc: efi: Transition to the faux device interface
Date: Mon, 17 Mar 2025 14:07:00 +0100 [thread overview]
Message-ID: <2025031755-simile-landside-e719@gregkh> (raw)
In-Reply-To: <20250317-plat2faux_dev-v1-4-5fe67c085ad5@arm.com>
On Mon, Mar 17, 2025 at 10:13:16AM +0000, Sudeep Holla wrote:
> The EFI RTC driver does not require the creation of a platform device.
> Originally, this approach was chosen for simplicity when the driver was
> first implemented.
>
> With the introduction of the lightweight faux device interface, we now
> have a more appropriate alternative. Migrate the driver to utilize the
> faux bus, given that the platform device it previously created was not
> a real one anyway. This will simplify the code, reducing its footprint
> while maintaining functionality.
>
> Cc: Ard Biesheuvel <ardb@kernel.org>
> Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>
> Cc: linux-rtc@vger.kernel.org
> Cc: linux-efi@vger.kernel.org
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
> drivers/firmware/efi/efi.c | 3 ---
> drivers/rtc/rtc-efi.c | 31 ++++++++++++++++++++++---------
> 2 files changed, 22 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c
> index eec173cb1f398d3b4f28b42c917e50e1728dc277..18deb2d212ce6944927f5e3a9a40bb6754e7ffa9 100644
> --- a/drivers/firmware/efi/efi.c
> +++ b/drivers/firmware/efi/efi.c
> @@ -427,9 +427,6 @@ static int __init efisubsys_init(void)
> }
> }
>
> - if (efi_rt_services_supported(EFI_RT_SUPPORTED_TIME_SERVICES))
> - platform_device_register_simple("rtc-efi", 0, NULL, 0);
> -
> /* We register the efi directory at /sys/firmware/efi */
> efi_kobj = kobject_create_and_add("efi", firmware_kobj);
> if (!efi_kobj) {
> diff --git a/drivers/rtc/rtc-efi.c b/drivers/rtc/rtc-efi.c
> index fa8bf82df9488e7d1c23c058b4a3032dde74bc6e..3d21a470e8ff9777c5eeb991f3aa9170f6351930 100644
> --- a/drivers/rtc/rtc-efi.c
> +++ b/drivers/rtc/rtc-efi.c
> @@ -14,7 +14,7 @@
> #include <linux/module.h>
> #include <linux/stringify.h>
> #include <linux/time.h>
> -#include <linux/platform_device.h>
> +#include <linux/device/faux.h>
> #include <linux/rtc.h>
> #include <linux/efi.h>
>
> @@ -254,7 +254,7 @@ static const struct rtc_class_ops efi_rtc_ops = {
> .proc = efi_procfs,
> };
>
> -static int __init efi_rtc_probe(struct platform_device *dev)
> +static int __init efi_rtc_probe(struct faux_device *dev)
> {
> struct rtc_device *rtc;
> efi_time_t eft;
> @@ -268,7 +268,7 @@ static int __init efi_rtc_probe(struct platform_device *dev)
> if (IS_ERR(rtc))
> return PTR_ERR(rtc);
>
> - platform_set_drvdata(dev, rtc);
> + faux_device_set_drvdata(dev, rtc);
>
> rtc->ops = &efi_rtc_ops;
> clear_bit(RTC_FEATURE_UPDATE_INTERRUPT, rtc->features);
> @@ -282,15 +282,28 @@ static int __init efi_rtc_probe(struct platform_device *dev)
> return devm_rtc_register_device(rtc);
> }
>
> -static struct platform_driver efi_rtc_driver = {
> - .driver = {
> - .name = "rtc-efi",
> - },
> +static struct faux_device_ops efi_rtc_fdev_ops = {
> + .probe = efi_rtc_probe,
> };
>
> -module_platform_driver_probe(efi_rtc_driver, efi_rtc_probe);
> +static int __init rtc_efi_init(void)
> +{
> + struct faux_device *fdev;
> +
> + if (!efi_rt_services_supported(EFI_RT_SUPPORTED_TIME_SERVICES))
> + return 0;
> +
> + fdev = faux_device_create("rtc-efi", NULL, &efi_rtc_fdev_ops);
> + if (!fdev) {
> + pr_err("rtc-efi: could not create the device\n");
> + return -ENODEV;
> + }
> +
> + return 0;
> +}
> +device_initcall(rtc_efi_init);
>
> MODULE_AUTHOR("dann frazier <dannf@dannf.org>");
> MODULE_LICENSE("GPL");
> MODULE_DESCRIPTION("EFI RTC driver");
> -MODULE_ALIAS("platform:rtc-efi");
> +MODULE_ALIAS("faux:rtc-efi");
No alias please.
next prev parent reply other threads:[~2025-03-17 13:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 10:13 [PATCH 0/9] drivers: Transition to the faux device interface Sudeep Holla
2025-03-17 10:13 ` [PATCH 1/9] cpuidle: psci: " Sudeep Holla
2025-04-09 18:03 ` Rafael J. Wysocki
2025-04-09 19:17 ` Sudeep Holla
2025-04-09 19:28 ` Rafael J. Wysocki
2025-03-17 10:13 ` [PATCH 2/9] hwrng: arm-smccc-trng - transition " Sudeep Holla
2025-03-17 13:04 ` Greg Kroah-Hartman
2025-03-17 14:22 ` Sudeep Holla
2025-03-17 14:30 ` Greg Kroah-Hartman
2025-03-17 14:43 ` Sudeep Holla
2025-03-17 16:46 ` Greg Kroah-Hartman
2025-03-17 16:53 ` Sudeep Holla
2025-03-17 10:13 ` [PATCH 3/9] efi: Remove redundant creation of the "efivars" platform device Sudeep Holla
2025-03-17 17:06 ` Ard Biesheuvel
2025-03-17 17:19 ` Sudeep Holla
2025-03-17 10:13 ` [PATCH 4/9] rtc: efi: Transition to the faux device interface Sudeep Holla
2025-03-17 13:07 ` Greg Kroah-Hartman [this message]
2025-03-17 14:04 ` Sudeep Holla
2025-03-17 10:13 ` [PATCH 5/9] virt: efi_secret: " Sudeep Holla
2025-03-17 13:06 ` Greg Kroah-Hartman
2025-03-17 10:13 ` [PATCH 6/9] ASoC: soc-utils: " Sudeep Holla
2025-03-17 10:13 ` [PATCH 7/9] net: phy: fixed_phy: transition " Sudeep Holla
2025-03-17 12:29 ` Andrew Lunn
2025-03-17 13:00 ` Greg Kroah-Hartman
2025-03-17 14:17 ` Sudeep Holla
2025-03-17 10:13 ` [PATCH 8/9] ACPI: APEI: EINJ: Transition " Sudeep Holla
2025-06-06 3:35 ` Dan Williams
2025-03-17 10:13 ` [PATCH 9/9] regulator: dummy: convert to use " Sudeep Holla
2025-03-17 10:24 ` Mark Brown
2025-03-17 10:34 ` Sudeep Holla
2025-03-17 13:00 ` Greg Kroah-Hartman
2025-03-17 14:13 ` Sudeep Holla
2025-03-17 14:26 ` Greg Kroah-Hartman
2025-03-17 14:30 ` Sudeep Holla
2025-03-17 13:01 ` [PATCH 0/9] drivers: Transition to " Greg Kroah-Hartman
2025-03-17 14:28 ` Sudeep Holla
2025-03-17 14:20 ` Mark Brown
2025-03-17 18:10 ` (subset) " Mark Brown
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=2025031755-simile-landside-e719@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexandre.belloni@bootlin.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.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 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.