From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linhua Xu <Linhua.xu@unisoc.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Orson Zhai <orsonzhai@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
lh xu <xulh0829@gmail.com>,
Xiongpeng Wu <xiongpeng.wu@unisoc.com>
Subject: Re: [PATCH 4/6] pinctrl: sprd: Add pinctrl support for UMS512
Date: Fri, 25 Aug 2023 13:17:38 +0300 [thread overview]
Message-ID: <ZOh/wpBKoO9wYYE4@smile.fi.intel.com> (raw)
In-Reply-To: <20230825031826.31599-5-Linhua.xu@unisoc.com>
On Fri, Aug 25, 2023 at 11:18:24AM +0800, Linhua Xu wrote:
> From: Linhua Xu <Linhua.Xu@unisoc.com>
>
> This patch adds the pin control driver for UNISOC UMS512 platform.
Read "Submitting Patches" documentation and find there what to do
with "This patch..."
...
> +config PINCTRL_SPRD_UMS512
> + tristate "Spreadtrum ums512 pinctrl driver"
> + depends on OF
Shouldn't you drop this from all drivers you have? I do not see this driver
being dependent on the OF.
> + depends on ARCH_SPRD || COMPILE_TEST
> + select PINCTRL_SPRD
...
kernel.h for ARRAY_SIZE()
> +#include <linux/module.h>
> +#include <linux/mod_devicetable.h>
> +#include <linux/platform_device.h>
...
> +#define PINCTRL_REG_OFFSET 0x34
0x0034
> +#define PINCTRL_REG_MISC_OFFSET 0x434
> +static int sprd_pinctrl_probe(struct platform_device *pdev)
> +{
> + return sprd_pinctrl_core_probe(pdev, sprd_ums512_pins_info,
> + ARRAY_SIZE(sprd_ums512_pins_info),
> + PINCTRL_REG_OFFSET,
> + PINCTRL_REG_MISC_OFFSET);
> +}
...
> +static const struct of_device_id sprd_pinctrl_of_match[] = {
> + {
> + .compatible = "sprd,ums512-pinctrl",
> + },
Can be one line.
> + { },
Drop trailing comma in the terminator entry.
> +};
...
> +static struct platform_driver sprd_pinctrl_driver = {
> + .driver = {
> + .name = "sprd-pinctrl",
> + .of_match_table = sprd_pinctrl_of_match,
> + },
> + .probe = sprd_pinctrl_probe,
> + .remove = sprd_pinctrl_remove,
> + .shutdown = sprd_pinctrl_shutdown,
> +};
> +
Redundant blank line.
> +module_platform_driver(sprd_pinctrl_driver);
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-08-25 10:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 3:18 [PATCH 0/6] pinctrl: sprd: Modification of UNIOC Platform pinctrl Driver Linhua Xu
2023-08-25 3:18 ` [PATCH 1/6] pinctrl: sprd: Modify the probe function parameters Linhua Xu
2023-08-25 5:25 ` kernel test robot
2023-08-25 10:08 ` Andy Shevchenko
2023-08-25 3:18 ` [PATCH 2/6] pinctrl: sprd: Fix the incorrect mask and shift definition Linhua Xu
2023-08-25 10:10 ` Andy Shevchenko
2023-08-25 3:18 ` [PATCH 3/6] pinctrl: sprd: Modify pull-up parameters Linhua Xu
2023-08-25 10:13 ` Andy Shevchenko
2023-08-25 3:18 ` [PATCH 4/6] pinctrl: sprd: Add pinctrl support for UMS512 Linhua Xu
2023-08-25 10:17 ` Andy Shevchenko [this message]
2023-08-25 3:18 ` [PATCH 5/6] pinctrl: sprd: Increase the range of register values Linhua Xu
2023-08-25 10:19 ` Andy Shevchenko
2023-08-25 3:18 ` [PATCH 6/6] pinctrl: sprd: Add pinctrl support for UMS9621 Linhua Xu
2023-08-25 10:20 ` Andy Shevchenko
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=ZOh/wpBKoO9wYYE4@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Linhua.xu@unisoc.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=xiongpeng.wu@unisoc.com \
--cc=xulh0829@gmail.com \
--cc=zhang.lyra@gmail.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