From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: linux-rtc@vger.kernel.org
Subject: Re: [PATCH] rtc: mxc: Remove unused .id_table support
Date: Mon, 16 Nov 2020 18:26:53 +0100 [thread overview]
Message-ID: <20201116172653.GU4556@piout.net> (raw)
In-Reply-To: <20201116154303.15055-1-festevam@gmail.com>
Hello,
On 16/11/2020 12:43:03-0300, Fabio Estevam wrote:
> Since 5.10-rc1 i.MX is a devicetree-only platform and the existing
> .id_table support in this driver was only useful for old non-devicetree
> platforms.
>
> Get rid of the .id_table since it is no longer used.
>
> Signed-off-by: Fabio Estevam <festevam@gmail.com>
> ---
> drivers/rtc/rtc-mxc.c | 14 --------------
> 1 file changed, 14 deletions(-)
>
> diff --git a/drivers/rtc/rtc-mxc.c b/drivers/rtc/rtc-mxc.c
> index a8cfbde048f4..78d7fba00895 100644
> --- a/drivers/rtc/rtc-mxc.c
> +++ b/drivers/rtc/rtc-mxc.c
> @@ -70,19 +70,6 @@ struct rtc_plat_data {
> enum imx_rtc_type devtype;
> };
>
> -static const struct platform_device_id imx_rtc_devtype[] = {
> - {
> - .name = "imx1-rtc",
> - .driver_data = IMX1_RTC,
> - }, {
> - .name = "imx21-rtc",
> - .driver_data = IMX21_RTC,
> - }, {
> - /* sentinel */
> - }
> -};
> -MODULE_DEVICE_TABLE(platform, imx_rtc_devtype);
> -
> #ifdef CONFIG_OF
Is this #ifdef still necessary?
> static const struct of_device_id imx_rtc_dt_ids[] = {
> { .compatible = "fsl,imx1-rtc", .data = (const void *)IMX1_RTC },
> @@ -438,7 +425,6 @@ static struct platform_driver mxc_rtc_driver = {
> .name = "mxc_rtc",
> .of_match_table = of_match_ptr(imx_rtc_dt_ids),
> },
> - .id_table = imx_rtc_devtype,
> .probe = mxc_rtc_probe,
> };
>
> --
> 2.17.1
>
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-11-16 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 15:43 [PATCH] rtc: mxc: Remove unused .id_table support Fabio Estevam
2020-11-16 17:26 ` Alexandre Belloni [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=20201116172653.GU4556@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=festevam@gmail.com \
--cc=linux-rtc@vger.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.