From: Chester Lin <clin@suse.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Chester Lin" <clin@suse.com>, "NXP S32 Linux Team" <s32@nxp.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Ghennadi Procopciuc" <Ghennadi.Procopciuc@oss.nxp.com>,
"Andrei Stefanescu" <andrei.stefanescu@nxp.com>,
"Radu Pirea" <radu-nicolae.pirea@nxp.com>,
"Andreas Färber" <afaerber@suse.de>,
"Matthias Brugger" <mbrugger@suse.com>
Subject: [PATCH v3 1/6] pinctrl: s32g2: use of_device_get_match_data() to get device data
Date: Thu, 23 Mar 2023 22:48:28 +0800 [thread overview]
Message-ID: <20230323144833.28562-2-clin@suse.com> (raw)
In-Reply-To: <20230323144833.28562-1-clin@suse.com>
Choose of_device_get_match_data() instead of indirect reference via
of_match_device() so that the implementation can be more concise.
Suggested-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Signed-off-by: Chester Lin <clin@suse.com>
---
Changes in v3:
- Declare the struct var 'info' as const and remove unnecessary type casting.
drivers/pinctrl/nxp/pinctrl-s32g2.c | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/pinctrl/nxp/pinctrl-s32g2.c b/drivers/pinctrl/nxp/pinctrl-s32g2.c
index 5028f4adc389..0e2d93681769 100644
--- a/drivers/pinctrl/nxp/pinctrl-s32g2.c
+++ b/drivers/pinctrl/nxp/pinctrl-s32g2.c
@@ -740,14 +740,11 @@ MODULE_DEVICE_TABLE(of, s32_pinctrl_of_match);
static int s32g_pinctrl_probe(struct platform_device *pdev)
{
- const struct of_device_id *of_id =
- of_match_device(s32_pinctrl_of_match, &pdev->dev);
+ const struct s32_pinctrl_soc_info *info;
- if (!of_id)
- return -ENODEV;
+ info = of_device_get_match_data(&pdev->dev);
- return s32_pinctrl_probe
- (pdev, (struct s32_pinctrl_soc_info *) of_id->data);
+ return s32_pinctrl_probe(pdev, info);
}
static const struct dev_pm_ops s32g_pinctrl_pm_ops = {
--
2.37.3
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-03-23 14:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 14:48 [PATCH v3 0/6] pinctrl: s32: driver improvements and generic struct use Chester Lin
2023-03-23 14:48 ` Chester Lin [this message]
2023-03-23 17:11 ` [PATCH v3 1/6] pinctrl: s32g2: use of_device_get_match_data() to get device data kernel test robot
2023-03-23 17:42 ` Chester Lin
2023-03-23 14:48 ` [PATCH v3 2/6] pinctrl: s32: refine error/return/config checks and simplify driver codes Chester Lin
2023-03-23 14:48 ` [PATCH v3 3/6] pinctrl: s32cc: refactor pin config parsing Chester Lin
2023-03-23 18:44 ` Andy Shevchenko
2023-03-23 14:48 ` [PATCH v3 4/6] pinctrl: s32cc: embed generic struct pingroup Chester Lin
2023-03-23 14:48 ` [PATCH v3 5/6] pinctrl: s32cc: Use generic struct data to describe pin function Chester Lin
2023-03-23 18:49 ` Andy Shevchenko
2023-03-23 14:48 ` [PATCH v3 6/6] pinctrl: s32: separate const device data from struct s32_pinctrl_soc_info Chester Lin
2023-03-23 18:50 ` Andy Shevchenko
2023-03-24 7:45 ` Chester Lin
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=20230323144833.28562-2-clin@suse.com \
--to=clin@suse.com \
--cc=Ghennadi.Procopciuc@oss.nxp.com \
--cc=afaerber@suse.de \
--cc=andrei.stefanescu@nxp.com \
--cc=andy.shevchenko@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=radu-nicolae.pirea@nxp.com \
--cc=s32@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;
as well as URLs for NNTP newsgroup(s).