From: Heiko Stuebner <heiko@sntech.de>
To: Linus Walleij <linus.walleij@linaro.org>,
Huang-Huang Bao <i@eh5.me>,
kever.yang@rock-chips.com
Cc: linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Huang-Huang Bao <i@eh5.me>
Subject: Re: [PATCH v2 2/4] pinctrl: rockchip: fix pinmux bits for RK3328 GPIO3-B pins
Date: Fri, 07 Jun 2024 14:32:22 +0200 [thread overview]
Message-ID: <4786379.ElGaqSPkdT@phil> (raw)
In-Reply-To: <20240606125755.53778-3-i@eh5.me>
Am Donnerstag, 6. Juni 2024, 14:57:53 CEST schrieb Huang-Huang Bao:
> The pinmux bits for GPIO3-B1 to GPIO3-B6 pins are not explicitly
> specified in RK3328 TRM, however we can get hint from pad name and its
> correspinding IOMUX setting for pins in interface descriptions. The
> correspinding IOMIX settings for these pins can be found in the same
> row next to occurrences of following pad names in RK3328 TRM.
>
> GPIO3-B1: IO_TSPd5m0_CIFdata5m0_GPIO3B1vccio6
> GPIO3-B2: IO_TSPd6m0_CIFdata6m0_GPIO3B2vccio6
> GPIO3-B3: IO_TSPd7m0_CIFdata7m0_GPIO3B3vccio6
> GPIO3-B4: IO_CARDclkm0_GPIO3B4vccio6
> GPIO3-B5: IO_CARDrstm0_GPIO3B5vccio6
> GPIO3-B6: IO_CARDdetm0_GPIO3B6vccio6
>
> Add pinmux data to rk3328_mux_recalced_data as mux register offset for
> these pins does not follow rockchip convention.
>
> Signed-off-by: Huang-Huang Bao <i@eh5.me>
This matches the information that I found in my TRM, thanks to your
detailed explanation.
Though I of course can't say if the TRM is just wrong or the hardware
changed after the pads-description was written.
Did you test the usage of these pins on your board?
Heiko
> ---
> drivers/pinctrl/pinctrl-rockchip.c | 51 ++++++++++++++++++++++++++++++
> 1 file changed, 51 insertions(+)
>
> diff --git a/drivers/pinctrl/pinctrl-rockchip.c b/drivers/pinctrl/pinctrl-rockchip.c
> index 78dcf4daccde..23531ea0d088 100644
> --- a/drivers/pinctrl/pinctrl-rockchip.c
> +++ b/drivers/pinctrl/pinctrl-rockchip.c
> @@ -634,17 +634,68 @@ static struct rockchip_mux_recalced_data rk3308_mux_recalced_data[] = {
>
> static struct rockchip_mux_recalced_data rk3328_mux_recalced_data[] = {
> {
> + /* gpio2_b7_sel */
> .num = 2,
> .pin = 15,
> .reg = 0x28,
> .bit = 0,
> .mask = 0x7
> }, {
> + /* gpio2_c7_sel */
> .num = 2,
> .pin = 23,
> .reg = 0x30,
> .bit = 14,
> .mask = 0x3
> + }, {
> + /* gpio3_b1_sel */
> + .num = 3,
> + .pin = 9,
> + .reg = 0x44,
> + .bit = 2,
> + .mask = 0x3
> + }, {
> + /* gpio3_b2_sel */
> + .num = 3,
> + .pin = 10,
> + .reg = 0x44,
> + .bit = 4,
> + .mask = 0x3
> + }, {
> + /* gpio3_b3_sel */
> + .num = 3,
> + .pin = 11,
> + .reg = 0x44,
> + .bit = 6,
> + .mask = 0x3
> + }, {
> + /* gpio3_b4_sel */
> + .num = 3,
> + .pin = 12,
> + .reg = 0x44,
> + .bit = 8,
> + .mask = 0x3
> + }, {
> + /* gpio3_b5_sel */
> + .num = 3,
> + .pin = 13,
> + .reg = 0x44,
> + .bit = 10,
> + .mask = 0x3
> + }, {
> + /* gpio3_b6_sel */
> + .num = 3,
> + .pin = 14,
> + .reg = 0x44,
> + .bit = 12,
> + .mask = 0x3
> + }, {
> + /* gpio3_b7_sel */
> + .num = 3,
> + .pin = 15,
> + .reg = 0x44,
> + .bit = 14,
> + .mask = 0x3
> },
> };
>
>
next prev parent reply other threads:[~2024-06-07 12:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 12:57 [PATCH v2 0/4] pinctrl: rockchip: fix RK3328 pinmux bits Huang-Huang Bao
2024-06-06 12:57 ` [PATCH v2 1/4] pinctrl: rockchip: fix pinmux bits for RK3328 GPIO2-B pins Huang-Huang Bao
2024-06-07 12:23 ` Heiko Stuebner
2024-06-17 8:37 ` Linus Walleij
2024-06-06 12:57 ` [PATCH v2 2/4] pinctrl: rockchip: fix pinmux bits for RK3328 GPIO3-B pins Huang-Huang Bao
2024-06-07 12:32 ` Heiko Stuebner [this message]
2024-06-07 14:46 ` Huang-Huang Bao
2024-06-08 14:21 ` Heiko Stuebner
2024-06-08 14:21 ` Heiko Stuebner
2024-06-11 15:05 ` Huang-Huang Bao
2024-06-06 12:57 ` [PATCH v2 3/4] pinctrl: rockchip: use dedicated pinctrl type for RK3328 Huang-Huang Bao
2024-06-06 12:57 ` [PATCH v2 4/4] pinctrl: rockchip: fix pinmux reset in rockchip_pmx_set Huang-Huang Bao
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=4786379.ElGaqSPkdT@phil \
--to=heiko@sntech.de \
--cc=i@eh5.me \
--cc=kever.yang@rock-chips.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-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: 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).