From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "jay.xu@rock-chips.com" <jay.xu@rock-chips.com>
Cc: "Heiko Stübner" <heiko@sntech.de>,
"linus.walleij" <linus.walleij@linaro.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>
Subject: Re: [PATCH] pinctrl/rockchip: re-fix RK3308 pinmux bits
Date: Sat, 1 Oct 2022 15:10:59 +0200 [thread overview]
Message-ID: <20221001151059.7ddd4f7d@melee> (raw)
In-Reply-To: <2022100108422538502750@rock-chips.com>
Hello Jianqun,
Il giorno Sat, 1 Oct 2022 08:42:25 +0800
"jay.xu@rock-chips.com" <jay.xu@rock-chips.com> ha scritto:
> Hi Luca:
>
> BR
> --------------
> jay.xu@rock-chips.com
> >Hello Jianqun Xu,
> >
> >On Fri, 30 Sep 2022 18:26:20 +0800
> >Jianqun Xu <jay.xu@rock-chips.com> wrote:
> >
> >> Part of pins from RK3308 SoCs have two registers to do pinmux, one is
> >> the origin register with 2bits named by gpioxx_sel, and another with
> >> 3bits and named by gpioxx_sel_plus.
> >
> >Are the "plus" registers documented anywhere?
>
> At RK3308 TRM CH5 GRF,
>
> GRF_SOC_CON13
>
> 3 RW 0x0 gpio2a2_sel_src_ctrl
> IOMUX control source selection.
> 1'b0: use basic GPIO2A_IOMUX[gpio2a2_sel]
> 1'b1: use gpio2a2_sel_plus instead of GPIO2A_IOMUX[gpio2a2_sel]
>
> 2:0 RW 0x0 gpio2a2_sel_plus
> 3'b000: GPIO2_A2
> 3'b001: UART0_CTSN
> 3'b010: SPI0_CLK
> 3'b011: I2C2_SDA
> 3'b100: Reserved
> 3'b101: OWIRE_M2
>
> Sorry I don't know about the trm you got from our company, if you cannot find this part,
> may require a new version ?
First of all: is a complete TRM available for public download?
I searched again, but didn't find any.
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2022-10-01 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 10:26 [PATCH] pinctrl/rockchip: re-fix RK3308 pinmux bits Jianqun Xu
2022-09-30 16:23 ` Luca Ceresoli
2022-10-01 0:42 ` jay.xu
2022-10-01 13:10 ` Luca Ceresoli [this message]
2022-10-02 1:44 ` jay.xu
2022-10-10 14:04 ` Luca Ceresoli
2022-10-17 13:51 ` Luca Ceresoli
2022-10-18 3:10 ` jay.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=20221001151059.7ddd4f7d@melee \
--to=luca.ceresoli@bootlin.com \
--cc=heiko@sntech.de \
--cc=jay.xu@rock-chips.com \
--cc=linus.walleij@linaro.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).