From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Biju Das <biju.das.jz@bp.renesas.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>
Subject: RE: [PATCH] usb: renesas_usbhs: Remove renesas_usbhs_get_info() wrapper
Date: Wed, 17 Apr 2024 07:36:20 +0000 [thread overview]
Message-ID: <TYWPR01MB11030828622DFCFD2517FB6D5D80F2@TYWPR01MB11030.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <fa296af4452dfe394a58b75fd44c3bb9591936eb.1713282736.git.geert+renesas@glider.be>
Hi Geert-san,
> From: Geert Uytterhoeven, Sent: Wednesday, April 17, 2024 12:54 AM
>
> The renesas_usbhs_get_info() wrapper was useful for legacy board code.
> Since commit 1fa59bda21c7fa36 ("ARM: shmobile: Remove legacy board code
> for Armadillo-800 EVA") in v4.3, it is no longer used outside the USBHS
> driver, and provides no added value over dev_get_platdata(), while
> obfuscating the real operation.
>
> Drop it, and replace it by dev_get_platdata() in its sole user.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Thank you for the patch!
Reviewed-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Best regards,
Yoshihiro Shimoda
> ---
> drivers/usb/renesas_usbhs/common.c | 2 +-
> include/linux/usb/renesas_usbhs.h | 5 -----
> 2 files changed, 1 insertion(+), 6 deletions(-)
>
> diff --git a/drivers/usb/renesas_usbhs/common.c b/drivers/usb/renesas_usbhs/common.c
> index b6bef9081bf275f0..edc43f169d493c65 100644
> --- a/drivers/usb/renesas_usbhs/common.c
> +++ b/drivers/usb/renesas_usbhs/common.c
> @@ -613,7 +613,7 @@ static int usbhs_probe(struct platform_device *pdev)
>
> info = of_device_get_match_data(dev);
> if (!info) {
> - info = renesas_usbhs_get_info(pdev);
> + info = dev_get_platdata(dev);
> if (!info)
> return dev_err_probe(dev, -EINVAL, "no platform info\n");
> }
> diff --git a/include/linux/usb/renesas_usbhs.h b/include/linux/usb/renesas_usbhs.h
> index 372898d9eeb00bbc..67bfcda6c7d2779e 100644
> --- a/include/linux/usb/renesas_usbhs.h
> +++ b/include/linux/usb/renesas_usbhs.h
> @@ -194,9 +194,4 @@ struct renesas_usbhs_platform_info {
> struct renesas_usbhs_driver_param driver_param;
> };
>
> -/*
> - * macro for platform
> - */
> -#define renesas_usbhs_get_info(pdev)\
> - ((struct renesas_usbhs_platform_info *)(pdev)->dev.platform_data)
> #endif /* RENESAS_USB_H */
> --
> 2.34.1
prev parent reply other threads:[~2024-04-17 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 15:53 [PATCH] usb: renesas_usbhs: Remove renesas_usbhs_get_info() wrapper Geert Uytterhoeven
2024-04-16 15:57 ` Biju Das
2024-04-17 7:36 ` Yoshihiro Shimoda [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=TYWPR01MB11030828622DFCFD2517FB6D5D80F2@TYWPR01MB11030.jpnprd01.prod.outlook.com \
--to=yoshihiro.shimoda.uh@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-usb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).