From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: bugs@lists.linux.dev, linus.walleij@linaro.org,
linux-gpio@vger.kernel.org
Subject: rockchip rk3328 pinctrl unable to change gpio function of pins defined in rk3328_mux_recalced_data
Date: Wed, 19 Apr 2023 16:12:55 +0000 (UTC) [thread overview]
Message-ID: <20230419-b217334c0-3101f9f4b426@bugzilla.kernel.org> (raw)
antwain.schneider writes via Kernel.org Bugzilla:
rock64 exposes i2s1 on a secondary 22 pin header on the machine, this includes gpio2b7
since i don't care about i2s and those pins would be more valuable as gpios, i explicitly disabled i2s1 in the device tree
i set gpio2b7 as a cs-gpio but it wasn't working, eventually i got bold and actually started looking at the grf in memory
ma -k /dev/gpiomem dd 0x28 4
00000020 -------- -------- 00000001
no matter how many i2s1 things i disabled or removed from the dtb, GRF_GPIO2BH_IOMUX always read 00000001, meaning i2s1_mclk seems hardcoded
eventually i found the description in commit 3818e4a7678ea70508b6b6e72a4cbf445e1e7dfa and realized gpio2b4 also gives me trouble
i feel this is a bug, but probably not important for a 6 year old chip
View: https://bugzilla.kernel.org/show_bug.cgi?id=217334#c0
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
next reply other threads:[~2023-04-19 16:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 16:12 Kernel.org Bugbot [this message]
2023-04-19 16:12 ` rockchip rk3328 pinctrl unable to change gpio function of pins defined in rk3328_mux_recalced_data Kernel.org Bugbot
2023-04-21 10:32 ` Kernel.org Bugbot
2023-04-21 10:43 ` Kernel.org Bugbot
2023-04-22 21:08 ` rockchip rk3328 pinctrl overflow Kernel.org Bugbot
2023-04-22 21:08 ` Kernel.org Bugbot
2023-04-22 21:08 ` Kernel.org Bugbot
2023-05-04 11:01 ` [PATCH] pinctrl: rockchip: rk3328: rk3328_mux_recalced_data: fix bit alignment Kernel.org Bugbot
2023-05-04 11:01 ` Kernel.org Bugbot
2023-05-04 11:01 ` Kernel.org Bugbot
2023-05-19 7:10 ` Kernel.org Bugbot
2023-05-19 7:10 ` Kernel.org Bugbot
2023-05-19 7:10 ` Kernel.org Bugbot
2023-06-07 11:55 ` https://bugzilla.kernel.org/show_bug.cgi?id=217334 arm arm64 aarch64 pinctrl rockchip rk3328 rk3328_mux_recalced_data bits overflowing Kernel.org Bugbot
2023-06-07 11:55 ` Kernel.org Bugbot
2023-06-07 11:55 ` Kernel.org Bugbot
2023-06-28 9:20 ` rk3328_mux_recalced_data OVERFLOW noncontiguous CARRIED bits Kernel.org Bugbot
2023-06-28 9:20 ` Kernel.org Bugbot
2023-06-28 9:20 ` Kernel.org Bugbot
2023-08-27 14:52 ` linux rockchip gpio2b4 (gpio2b5) gpio2b7 broken GRF_GPIO2BL_IOMUX GRF_GPIO2BH_IOMUX 2bits 3bits pinctrl rk3328_mux_recalced_data (a fix exists, for a commiter brave enough to commit it) Kernel.org Bugbot
2023-08-27 14:52 ` Kernel.org Bugbot
2023-08-27 14:52 ` Kernel.org Bugbot
2024-01-29 14:15 ` Kernel.org Bugbot
2024-01-29 14:15 ` Kernel.org Bugbot
2024-01-29 14:15 ` Kernel.org Bugbot
2024-01-30 18:55 ` Kernel.org Bugbot
2024-01-30 18:55 ` Kernel.org Bugbot
2024-01-30 18:55 ` Kernel.org Bugbot
2024-01-31 21:05 ` inux ockchip pio2b4 (pio2b5) pio2b7 roken GRF_PIO2BL_IOMUX GRF_PIO2BH_IOMUX 2bits 3bits pinctrl rk332_mux_ecalced_data Kernel.org Bugbot
2024-07-05 4:30 ` RK3328 Kernel.org Bugbot
2024-07-05 4:30 ` RK3328 Kernel.org Bugbot
2025-01-18 16:45 ` RK3328 antwain.schneider via Bugspray Bot
2025-01-18 16:45 ` RK3328 antwain.schneider via Bugspray Bot
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=20230419-b217334c0-3101f9f4b426@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=bugs@lists.linux.dev \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.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 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.