From: Xing Zheng <zhengxing@rock-chips.com> To: heiko@sntech.de Cc: linux-rockchip@lists.infradead.org, Xing Zheng <zhengxing@rock-chips.com>, Linus Walleij <linus.walleij@linaro.org>, linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH v1 2/3] pinctrl: rockchip: add support for the rk3036 Date: Fri, 28 Aug 2015 13:46:47 +0800 [thread overview] Message-ID: <1440740808-15004-3-git-send-email-zhengxing@rock-chips.com> (raw) In-Reply-To: <1440740808-15004-1-git-send-email-zhengxing@rock-chips.com> Many parts of pinctrl rk3036 are similar to rk2928's. Signed-off-by: Xing Zheng <zhengxing@rock-chips.com> --- Changes in v1: None drivers/pinctrl/pinctrl-rockchip.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/drivers/pinctrl/pinctrl-rockchip.c b/drivers/pinctrl/pinctrl-rockchip.c index cc2843a..d06631d 100644 --- a/drivers/pinctrl/pinctrl-rockchip.c +++ b/drivers/pinctrl/pinctrl-rockchip.c @@ -2042,6 +2042,21 @@ static struct rockchip_pin_ctrl rk2928_pin_ctrl = { .pull_calc_reg = rk2928_calc_pull_reg_and_bit, }; +static struct rockchip_pin_bank rk3036_pin_banks[] = { + PIN_BANK(0, 32, "gpio0"), + PIN_BANK(1, 32, "gpio1"), + PIN_BANK(2, 32, "gpio2"), +}; + +static struct rockchip_pin_ctrl rk3036_pin_ctrl = { + .pin_banks = rk3036_pin_banks, + .nr_banks = ARRAY_SIZE(rk3036_pin_banks), + .label = "RK3036-GPIO", + .type = RK2928, + .grf_mux_offset = 0xa8, + .pull_calc_reg = rk2928_calc_pull_reg_and_bit, +}; + static struct rockchip_pin_bank rk3066a_pin_banks[] = { PIN_BANK(0, 32, "gpio0"), PIN_BANK(1, 32, "gpio1"), @@ -2160,6 +2175,8 @@ static struct rockchip_pin_ctrl rk3368_pin_ctrl = { static const struct of_device_id rockchip_pinctrl_dt_match[] = { { .compatible = "rockchip,rk2928-pinctrl", .data = (void *)&rk2928_pin_ctrl }, + { .compatible = "rockchip,rk3036-pinctrl", + .data = (void *)&rk3036_pin_ctrl }, { .compatible = "rockchip,rk3066a-pinctrl", .data = (void *)&rk3066a_pin_ctrl }, { .compatible = "rockchip,rk3066b-pinctrl", -- 1.7.9.5
WARNING: multiple messages have this Message-ID (diff)
From: zhengxing@rock-chips.com (Xing Zheng) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v1 2/3] pinctrl: rockchip: add support for the rk3036 Date: Fri, 28 Aug 2015 13:46:47 +0800 [thread overview] Message-ID: <1440740808-15004-3-git-send-email-zhengxing@rock-chips.com> (raw) In-Reply-To: <1440740808-15004-1-git-send-email-zhengxing@rock-chips.com> Many parts of pinctrl rk3036 are similar to rk2928's. Signed-off-by: Xing Zheng <zhengxing@rock-chips.com> --- Changes in v1: None drivers/pinctrl/pinctrl-rockchip.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/drivers/pinctrl/pinctrl-rockchip.c b/drivers/pinctrl/pinctrl-rockchip.c index cc2843a..d06631d 100644 --- a/drivers/pinctrl/pinctrl-rockchip.c +++ b/drivers/pinctrl/pinctrl-rockchip.c @@ -2042,6 +2042,21 @@ static struct rockchip_pin_ctrl rk2928_pin_ctrl = { .pull_calc_reg = rk2928_calc_pull_reg_and_bit, }; +static struct rockchip_pin_bank rk3036_pin_banks[] = { + PIN_BANK(0, 32, "gpio0"), + PIN_BANK(1, 32, "gpio1"), + PIN_BANK(2, 32, "gpio2"), +}; + +static struct rockchip_pin_ctrl rk3036_pin_ctrl = { + .pin_banks = rk3036_pin_banks, + .nr_banks = ARRAY_SIZE(rk3036_pin_banks), + .label = "RK3036-GPIO", + .type = RK2928, + .grf_mux_offset = 0xa8, + .pull_calc_reg = rk2928_calc_pull_reg_and_bit, +}; + static struct rockchip_pin_bank rk3066a_pin_banks[] = { PIN_BANK(0, 32, "gpio0"), PIN_BANK(1, 32, "gpio1"), @@ -2160,6 +2175,8 @@ static struct rockchip_pin_ctrl rk3368_pin_ctrl = { static const struct of_device_id rockchip_pinctrl_dt_match[] = { { .compatible = "rockchip,rk2928-pinctrl", .data = (void *)&rk2928_pin_ctrl }, + { .compatible = "rockchip,rk3036-pinctrl", + .data = (void *)&rk3036_pin_ctrl }, { .compatible = "rockchip,rk3066a-pinctrl", .data = (void *)&rk3066a_pin_ctrl }, { .compatible = "rockchip,rk3066b-pinctrl", -- 1.7.9.5
next prev parent reply other threads:[~2015-08-28 5:46 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-28 5:46 [PATCH v1 0/3] Port and support rk3036 SoC platform Xing Zheng 2015-08-28 5:46 ` Xing Zheng 2015-08-28 5:46 ` [PATCH v1 1/3] ARM: dts: rockchip: add core rk3036 dts Xing Zheng 2015-08-28 5:46 ` Xing Zheng 2015-08-28 5:46 ` Xing Zheng 2015-08-28 8:11 ` Eddie Cai 2015-08-28 8:36 ` Eddie Cai 2015-08-28 8:36 ` Eddie Cai 2015-08-28 8:36 ` Eddie Cai 2015-08-28 8:59 ` Heiko Stuebner 2015-08-28 8:59 ` Heiko Stuebner 2015-09-17 8:51 ` Xing Zheng 2015-09-17 8:51 ` Xing Zheng 2015-08-28 5:46 ` Xing Zheng [this message] 2015-08-28 5:46 ` [PATCH v1 2/3] pinctrl: rockchip: add support for the rk3036 Xing Zheng 2015-08-28 7:53 ` Heiko Stuebner 2015-08-28 7:53 ` Heiko Stuebner 2015-09-25 16:25 ` Linus Walleij 2015-09-25 16:25 ` Linus Walleij 2015-08-28 5:46 ` [PATCH v1 3/3] clk: rockchip: add clock controller for rk3036 Xing Zheng 2015-08-28 5:46 ` Xing Zheng 2015-08-28 9:54 ` Heiko Stuebner 2015-08-28 9:54 ` Heiko Stuebner 2015-08-28 9:54 ` Heiko Stuebner 2015-09-17 8:50 ` Xing Zheng 2015-09-17 8:50 ` Xing Zheng 2015-08-28 9:59 ` [PATCH v1 0/3] Port and support rk3036 SoC platform Heiko Stuebner 2015-08-28 9:59 ` Heiko Stuebner 2015-08-28 10:07 ` Xing Zheng 2015-08-28 10:07 ` Xing Zheng
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=1440740808-15004-3-git-send-email-zhengxing@rock-chips.com \ --to=zhengxing@rock-chips.com \ --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 \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.