From: "周琰杰 (Zhou Yanjie)" <zhouyanjie@wanyeetech.com>
To: linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, robh+dt@kernel.org,
paul.burton@mips.com, paulburton@kernel.org,
paul@crapouillou.net, mark.rutland@arm.com,
sernia.zhou@foxmail.com, zhenwenjin@gmail.com,
linus.walleij@linaro.org
Subject: [PATCH v8 0/5] Fix bugs in X1000/X1500 and add X1830 pinctrl driver v8
Date: Mon, 16 Dec 2019 00:20:59 +0800 [thread overview]
Message-ID: <1576426864-35348-2-git-send-email-zhouyanjie@wanyeetech.com> (raw)
In-Reply-To: <1576426864-35348-1-git-send-email-zhouyanjie@wanyeetech.com>
v7->v8:
Separate the part of introduce reg_offset in [4/4] in v7 into [3/5] in v8.
周琰杰 (Zhou Yanjie) (5):
pinctrl: Ingenic: Fix bugs in X1000 and X1500.
pinctrl: Ingenic: Add missing parts for X1000 and X1500.
pinctrl: Ingenic: Introduce reg_offset and use it instead hard code.
dt-bindings: pinctrl: Add bindings for Ingenic X1830.
pinctrl: Ingenic: Add pinctrl driver for X1830.
.../bindings/pinctrl/ingenic,pinctrl.txt | 8 +-
drivers/pinctrl/pinctrl-ingenic.c | 456 ++++++++++++++++++---
2 files changed, 395 insertions(+), 69 deletions(-)
--
2.7.4
next prev parent reply other threads:[~2019-12-15 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 16:20 Fix bugs in X1000/X1500 and add X1830 pinctrl driver v8 周琰杰 (Zhou Yanjie)
2019-12-15 16:20 ` 周琰杰 (Zhou Yanjie) [this message]
2020-01-06 22:46 ` [PATCH v8 0/5] " Linus Walleij
2019-12-15 16:21 ` [PATCH v8 1/5] pinctrl: Ingenic: Fix bugs in X1000 and X1500 周琰杰 (Zhou Yanjie)
2019-12-15 16:21 ` [PATCH v8 2/5] pinctrl: Ingenic: Add missing parts for " 周琰杰 (Zhou Yanjie)
2019-12-15 16:21 ` [PATCH v8 3/5] pinctrl: Ingenic: Introduce reg_offset and use it instead hard code 周琰杰 (Zhou Yanjie)
2019-12-15 16:21 ` [PATCH v8 4/5] dt-bindings: pinctrl: Add bindings for Ingenic X1830 周琰杰 (Zhou Yanjie)
2019-12-15 16:21 ` [PATCH v8 5/5] pinctrl: Ingenic: Add pinctrl driver for X1830 周琰杰 (Zhou Yanjie)
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=1576426864-35348-2-git-send-email-zhouyanjie@wanyeetech.com \
--to=zhouyanjie@wanyeetech.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=paul.burton@mips.com \
--cc=paul@crapouillou.net \
--cc=paulburton@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sernia.zhou@foxmail.com \
--cc=zhenwenjin@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;
as well as URLs for NNTP newsgroup(s).