From: "Pali Rohár" <pali@kernel.org>
To: Bramwel Barack <bramwelbarack89@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] tty: serial: mvebu-uart: use device_get_match_data()
Date: Thu, 5 Nov 2026 12:48:04 +0100 [thread overview]
Message-ID: <20261105114804.vqbs6ooleagwutal@pali> (raw)
In-Reply-To: <20261103201305.18963-1-bramwelbarack89@gmail.com>
On Tuesday 03 November 2026 23:13:05 Bramwel Barack wrote:
> Modernize the driver by replacing the legacy of_match_device() call
> with the modern device_get_match_data() helper API. This cleans up
> the boilerplate code by extracting the match driver data configuration
> directly.
>
> Consequently, drop the explicit inclusions of <linux/of_device.h> and
> <linux/of_platform.h> as they are no longer required by the driver.
> This allows us to also remove a now-redundant forward declaration and
> drop the problematic of_match_ptr() macro wrapper.
>
> Signed-off-by: Bramwel Barack <bramwelbarack89@gmail.com>
Looks good,
Acked-by: Pali Rohár <pali@kernel.org>
> ---
> Changes in v3:
> - Removed the redundant type cast from device_get_match_data() assignment as suggested by Jiri Slaby.
> - Marked the data pointer in struct mvebu_uart as const to match the return type of device_get_match_data() and prevent build errors.
>
> Changes in v2:
> - Dropped the redundant forward declaration of mvebu_uart_of_match.
> - Removed the of_match_ptr() macro wrapper from the platform driver structure
> to prevent build warnings when compiling with CONFIG_OF disabled.
> ---
> drivers/tty/serial/mvebu-uart.c | 11 +++--------
> 1 file changed, 3 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/tty/serial/mvebu-uart.c b/drivers/tty/serial/mvebu-uart.c
> index 33ea496c93b2..fcb8f3d52df8 100644
> --- a/drivers/tty/serial/mvebu-uart.c
> +++ b/drivers/tty/serial/mvebu-uart.c
> @@ -18,9 +18,7 @@
> #include <linux/math64.h>
> #include <linux/of.h>
> #include <linux/of_address.h>
> -#include <linux/of_device.h>
> #include <linux/of_irq.h>
> -#include <linux/of_platform.h>
> #include <linux/platform_device.h>
> #include <linux/serial.h>
> #include <linux/serial_core.h>
> @@ -154,7 +152,7 @@ struct mvebu_uart {
> struct uart_port *port;
> struct clk *clk;
> int irq[UART_IRQ_COUNT];
> - struct mvebu_uart_driver_data *data;
> + const struct mvebu_uart_driver_data *data;
> #if defined(CONFIG_PM)
> struct mvebu_uart_pm_regs pm_regs;
> #endif /* CONFIG_PM */
> @@ -859,15 +857,12 @@ static const struct dev_pm_ops mvebu_uart_pm_ops = {
> };
> #endif /* CONFIG_PM */
>
> -static const struct of_device_id mvebu_uart_of_match[];
>
> /* Counter to keep track of each UART port id when not using CONFIG_OF */
> static int uart_num_counter;
>
> static int mvebu_uart_probe(struct platform_device *pdev)
> {
> - const struct of_device_id *match = of_match_device(mvebu_uart_of_match,
> - &pdev->dev);
> struct uart_port *port;
> struct mvebu_uart *mvuart;
> struct resource *reg;
> @@ -919,7 +914,7 @@ static int mvebu_uart_probe(struct platform_device *pdev)
> return -ENOMEM;
>
> /* Get controller data depending on the compatible string */
> - mvuart->data = (struct mvebu_uart_driver_data *)match->data;
> + mvuart->data = device_get_match_data(&pdev->dev);
> mvuart->port = port;
>
> port->private_data = mvuart;
> @@ -1016,7 +1011,7 @@ static struct platform_driver mvebu_uart_platform_driver = {
> .probe = mvebu_uart_probe,
> .driver = {
> .name = "mvebu-uart",
> - .of_match_table = of_match_ptr(mvebu_uart_of_match),
> + .of_match_table = mvebu_uart_of_match,
> .suppress_bind_attrs = true,
> #if defined(CONFIG_PM)
> .pm = &mvebu_uart_pm_ops,
> --
> 2.56.0
>
prev parent reply other threads:[~2026-11-05 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 20:13 Bramwel Barack
2026-11-05 11:48 ` Pali Rohár [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=20261105114804.vqbs6ooleagwutal@pali \
--to=pali@kernel.org \
--cc=bramwelbarack89@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®