From: Jianqun Xu <jay.xu@rock-chips.com>
To: linus.walleij@linaro.org, robh+dt@kernel.org,
mark.rutland@arm.com, heiko@sntech.de,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Jianqun Xu <jay.xu@rock-chips.com>
Subject: [PATCH v2 0/2] pinctrl: rockchip: support rk3308 SoC
Date: Mon, 14 Oct 2019 08:25:21 +0800 [thread overview]
Message-ID: <20191014002523.4540-1-jay.xu@rock-chips.com> (raw)
In-Reply-To: <20191012061528.27821-1-jay.xu@rock-chips.com>
Add support for rk3308 SoC from rockchip.
Jianqun Xu (2):
dt-bindings: pinctrl: rockchip: add rk3308 SoC support
pinctrl: rockchip: add rk3308 SoC support
.../bindings/pinctrl/rockchip,pinctrl.txt | 1 +
drivers/pinctrl/pinctrl-rockchip.c | 377 ++++++++++++++++++
2 files changed, 378 insertions(+)
--
changes since v1:
- add Reviewed-by: Heiko Stuebner <heiko@sntech.de>, thanks Heiko
2.17.1
next prev parent reply other threads:[~2019-10-14 0:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 6:15 [PATCH 0/2] pinctrl: rockchip: support rk3308 SoC Jianqun Xu
2019-10-12 6:15 ` [PATCH 1/2] dt-bindings: pinctrl: rockchip: add rk3308 SoC support Jianqun Xu
2019-10-12 6:15 ` [PATCH 2/2] " Jianqun Xu
2019-10-12 8:58 ` [PATCH 0/2] pinctrl: rockchip: support rk3308 SoC Heiko Stübner
2019-10-14 0:25 ` Jianqun Xu [this message]
2019-10-14 0:25 ` [PATCH v2 1/2] dt-bindings: pinctrl: rockchip: add rk3308 SoC support Jianqun Xu
2019-10-14 0:25 ` [PATCH v2 2/2] " Jianqun Xu
2019-10-14 3:03 ` [PATCH v2 0/2] pinctrl: rockchip: support rk3308 SoC Jianqun Xu
2019-10-14 3:03 ` [PATCH v2 1/2] dt-bindings: pinctrl: rockchip: add rk3308 SoC support Jianqun Xu
2019-10-14 18:15 ` Rob Herring
2019-10-14 3:04 ` [PATCH v2 2/2] " Jianqun Xu
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=20191014002523.4540-1-jay.xu@rock-chips.com \
--to=jay.xu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--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-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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 NNTP newsgroup(s).