From: Sean Wang <sean.wang@mediatek.com>
To: Zhiyong Tao <zhiyong.tao@mediatek.com>
Cc: <robh+dt@kernel.org>, <linus.walleij@linaro.org>,
<mark.rutland@arm.com>, <matthias.bgg@gmail.com>,
<devicetree@vger.kernel.org>, <hongkun.cao@mediatek.com>,
<srv_heupstream@mediatek.com>, <linux-gpio@vger.kernel.org>,
<biao.huang@mediatek.com>, <erin.lo@mediatek.com>,
<liguo.zhang@mediatek.com>, <linux-kernel@vger.kernel.org>,
<hongzhou.yang@mediatek.com>,
<linux-mediatek@lists.infradead.org>, <yingjoe.chen@mediatek.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 0/4] PINCTRL: Mediatek pinctrl driver for mt2712
Date: Thu, 8 Mar 2018 11:08:50 +0800 [thread overview]
Message-ID: <1520478530.4049.3.camel@mtkswgap22> (raw)
In-Reply-To: <1520249745-6757-1-git-send-email-zhiyong.tao@mediatek.com>
Hi, Zhiyong
you should checkpatch every patch before sending them out
because I saw tons of check messages like below result for scanning v3
3/4
CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#152: FILE: drivers/pinctrl/mediatek/pinctrl-mt2712.c:85:
+static int mt2712_spec_pull_set(struct regmap *regmap, unsigned int
pin,
+ unsigned char align, bool isup, unsigned int r1r0)
CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#353: FILE: drivers/pinctrl/mediatek/pinctrl-mt2712.c:286:
+static int mt2712_ies_smt_set(struct regmap *regmap, unsigned int pin,
+ unsigned char align, int value, enum pin_config_param
arg)
CHECK:LINE_SPACING: Please don't use multiple blank lines
#423: FILE: drivers/pinctrl/mediatek/pinctrl-mt2712.c:356:
+
+
CHECK:LINE_SPACING: Please don't use multiple blank lines
#473: FILE: drivers/pinctrl/mediatek/pinctrl-mt2712.c:406:
+
+
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#719: FILE: drivers/pinctrl/mediatek/pinctrl-mtk-mt2712.h:14:
+ MTK_PIN(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#731: FILE: drivers/pinctrl/mediatek/pinctrl-mtk-mt2712.h:26:
+ MTK_PIN(
CHECK:OPEN_ENDED_LINE: Lines should not end with a '('
#742: FILE: drivers/pinctrl/mediatek/pinctrl-mtk-mt2712.h:37:
+ MTK_PIN(
....
total: 0 errors, 1 warnings, 214 checks, 2619 lines checked
On Mon, 2018-03-05 at 19:35 +0800, Zhiyong Tao wrote:
> This series includes four patches:
> 1.Add mt2712 pintcrl head file.
> 2.Add mt2712 pinctrl device node.
> 3.Add mt2712 pinctrl driver.
> 4.Support bias-disable of generic and special pins simultaneously.
>
> Changes in patch v3:
> 1)Use SPDX identifiers for all new files.
> 2)Use right data for Copyright and Author.
> 3)Correct some spelling mistake.
> 4)Reusing original logic and change solution to support bias-disable of generic and special pins simultaneously.
> 5)Add some comments for the speical path of special pins bias-disable.
>
> Changes in patch v2:
> 1)Separate patch4 for supporting bias-disable of generic and special pins.
> 2)GPIO16~17 direction setting is changed as generic pins in mt2712 E2,
> So remove GPIO16~17 special direction setting and remove apmixedsys node in pinctrl device node.
> 3)Add pinmux define in "mt2712-pinfunc.h" and "pinctrl-mtk-mt2712.h" for mt2712 E2 design.
>
> Zhiyong Tao (4):
> arm64: dts: mt2712: add pintcrl file
> arm64: dts: mt2712: add pintcrl device node.
> pinctrl: add mt2712 pinctrl driver
> pintcrl: support bias-disable of generic and special pins
> simultaneously
>
> arch/arm64/boot/dts/mediatek/mt2712-pinfunc.h | 1123 ++++++++++++++
> arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 18 +
> drivers/pinctrl/mediatek/Kconfig | 7 +
> drivers/pinctrl/mediatek/Makefile | 1 +
> drivers/pinctrl/mediatek/pinctrl-mt2712.c | 632 ++++++++
> drivers/pinctrl/mediatek/pinctrl-mtk-common.c | 6 +
> drivers/pinctrl/mediatek/pinctrl-mtk-mt2712.h | 1967 +++++++++++++++++++++++++
> 7 files changed, 3754 insertions(+)
> create mode 100644 arch/arm64/boot/dts/mediatek/mt2712-pinfunc.h
> create mode 100644 drivers/pinctrl/mediatek/pinctrl-mt2712.c
> create mode 100644 drivers/pinctrl/mediatek/pinctrl-mtk-mt2712.h
>
> --
> 2.6.4
>
>
> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek
prev parent reply other threads:[~2018-03-08 3:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 11:35 [PATCH v3 0/4] PINCTRL: Mediatek pinctrl driver for mt2712 Zhiyong Tao
2018-03-05 11:35 ` [PATCH v3 1/4] arm64: dts: mt2712: add pintcrl file Zhiyong Tao
2018-03-07 22:28 ` Rob Herring
2018-03-05 11:35 ` [PATCH v3 2/4] arm64: dts: mt2712: add pintcrl device node Zhiyong Tao
2018-03-05 11:35 ` [PATCH v3 3/4] pinctrl: add mt2712 pinctrl driver Zhiyong Tao
2018-03-05 11:35 ` [PATCH v3 4/4] pintcrl: support bias-disable of generic and special pins simultaneously Zhiyong Tao
2018-03-08 3:08 ` Sean Wang [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=1520478530.4049.3.camel@mtkswgap22 \
--to=sean.wang@mediatek.com \
--cc=biao.huang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=erin.lo@mediatek.com \
--cc=hongkun.cao@mediatek.com \
--cc=hongzhou.yang@mediatek.com \
--cc=liguo.zhang@mediatek.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=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=yingjoe.chen@mediatek.com \
--cc=zhiyong.tao@mediatek.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).