From: Heiko Stuebner <heiko@sntech.de>
To: linux-gpio@vger.kernel.org, Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: Luca Ceresoli <luca.ceresoli@bootlin.com>,
Linus Walleij <linus.walleij@linaro.org>,
Jianqun Xu <jay.xu@rock-chips.com>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] pinctrl: rockchip: fix RK3308 pinmux bits
Date: Wed, 20 Apr 2022 17:04:23 +0200 [thread overview]
Message-ID: <5942762.lOV4Wx5bFT@phil> (raw)
In-Reply-To: <20220420142432.248565-1-luca.ceresoli@bootlin.com>
Am Mittwoch, 20. April 2022, 16:24:31 CEST schrieb Luca Ceresoli:
> Some of the pinmuxing bits described in rk3308_mux_recalced_data are wrong,
> pointing to non-existing registers.
>
> Fix the entire table.
>
> Also add a comment in front of each entry with the same string that appears
> in the datasheet to make the table easier to compare with the docs.
>
> This fix has been tested on real hardware for the gpio3b3_sel entry.
>
> Fixes: 7825aeb7b208 ("pinctrl: rockchip: add rk3308 SoC support")
> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Thanks for walking through the datasheet for the fixes :-)
> ---
> drivers/pinctrl/pinctrl-rockchip.c | 45 ++++++++++++++++++++----------
> 1 file changed, 30 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/pinctrl/pinctrl-rockchip.c b/drivers/pinctrl/pinctrl-rockchip.c
> index a1b598b86aa9..65fa305b5f59 100644
> --- a/drivers/pinctrl/pinctrl-rockchip.c
> +++ b/drivers/pinctrl/pinctrl-rockchip.c
> @@ -457,95 +457,110 @@ static struct rockchip_mux_recalced_data rk3128_mux_recalced_data[] = {
>
> static struct rockchip_mux_recalced_data rk3308_mux_recalced_data[] = {
> {
> + /* gpio1b6_sel */
> .num = 1,
> .pin = 14,
> .reg = 0x28,
> .bit = 12,
> .mask = 0xf
> }, {
> + /* gpio1b7_sel */
> .num = 1,
> .pin = 15,
> .reg = 0x2c,
> .bit = 0,
> .mask = 0x3
> }, {
> + /* gpio1c2_sel */
> .num = 1,
> .pin = 18,
> .reg = 0x30,
> .bit = 4,
> .mask = 0xf
> }, {
> + /* gpio1c3_sel */
> .num = 1,
> .pin = 19,
> .reg = 0x30,
> .bit = 8,
> .mask = 0xf
> }, {
> + /* gpio1c4_sel */
> .num = 1,
> .pin = 20,
> .reg = 0x30,
> .bit = 12,
> .mask = 0xf
> }, {
> + /* gpio1c5_sel */
> .num = 1,
> .pin = 21,
> .reg = 0x34,
> .bit = 0,
> .mask = 0xf
> }, {
> + /* gpio1c6_sel */
> .num = 1,
> .pin = 22,
> .reg = 0x34,
> .bit = 4,
> .mask = 0xf
> }, {
> + /* gpio1c7_sel */
> .num = 1,
> .pin = 23,
> .reg = 0x34,
> .bit = 8,
> .mask = 0xf
> }, {
> + /* gpio3b4_sel */
> .num = 3,
> .pin = 12,
> .reg = 0x68,
> .bit = 8,
> .mask = 0xf
> }, {
> + /* gpio3b5_sel */
> .num = 3,
> .pin = 13,
> .reg = 0x68,
> .bit = 12,
> .mask = 0xf
> }, {
> + /* gpio2a2_sel */
> .num = 2,
> .pin = 2,
> - .reg = 0x608,
> - .bit = 0,
> - .mask = 0x7
> + .reg = 0x40,
> + .bit = 4,
> + .mask = 0x3
> }, {
> + /* gpio2a3_sel */
> .num = 2,
> .pin = 3,
> - .reg = 0x608,
> - .bit = 4,
> - .mask = 0x7
> + .reg = 0x40,
> + .bit = 6,
> + .mask = 0x3
> }, {
> + /* gpio2c0_sel */
> .num = 2,
> .pin = 16,
> - .reg = 0x610,
> - .bit = 8,
> - .mask = 0x7
> + .reg = 0x50,
> + .bit = 0,
> + .mask = 0x3
> }, {
> + /* gpio3b2_sel */
> .num = 3,
> .pin = 10,
> - .reg = 0x610,
> - .bit = 0,
> - .mask = 0x7
> + .reg = 0x68,
> + .bit = 4,
> + .mask = 0x3
> }, {
> + /* gpio3b3_sel */
> .num = 3,
> .pin = 11,
> - .reg = 0x610,
> - .bit = 4,
> - .mask = 0x7
> + .reg = 0x68,
> + .bit = 6,
> + .mask = 0x3
> },
> };
>
>
next prev parent reply other threads:[~2022-04-20 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 14:24 [PATCH 1/2] pinctrl: rockchip: fix RK3308 pinmux bits Luca Ceresoli
2022-04-20 14:24 ` [PATCH 2/2] pinctrl: rockchip: sort the rk3308_mux_recalced_data entries Luca Ceresoli
2022-04-20 15:05 ` Heiko Stuebner
2022-04-20 15:04 ` Heiko Stuebner [this message]
2022-04-22 21:36 ` [PATCH 1/2] pinctrl: rockchip: fix RK3308 pinmux bits Linus Walleij
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=5942762.lOV4Wx5bFT@phil \
--to=heiko@sntech.de \
--cc=jay.xu@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 \
--cc=luca.ceresoli@bootlin.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).