From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: heiko@sntech.de, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, bugs@lists.linux.dev
Subject: Re: RK3328
Date: Fri, 05 Jul 2024 04:30:24 +0000 [thread overview]
Message-ID: <20240705-b217334c13-13d1a8cd7c07@bugzilla.kernel.org> (raw)
In-Reply-To: <20230419-b217334c0-3101f9f4b426@bugzilla.kernel.org>
antwain.schneider writes via Kernel.org Bugzilla:
thank you Huang-Huang Bao for addressing this problem better than i with commits
commit e8448a6c817c2aa6c6af785b1d45678bd5977e8d
commit 5ef6914e0bf578357b4c906ffe6b26e7eedb8ccf
commit 01b4b1d1cec48ef4c26616c2fc4600b2c9fec05a
GRF_GPIO2BL_IOMUX: 00000600
2b0 | 2b1 | 2b2 | 2b3 | 2b4 | 2b5 | 2b6 | res
00 01|02 03|04 05|06 07|08 09|10 11|12 13|14 15
0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0
GRF_GPIO2BH_IOMUX: 00000000
2b7 | reserved.............................
00 01 02|03 04 05 06 07 08 09 10 11 12 13 14 15
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
View: https://bugzilla.kernel.org/show_bug.cgi?id=217334#c13
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
WARNING: multiple messages have this Message-ID (diff)
From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: heiko@sntech.de, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, bugs@lists.linux.dev
Subject: Re: RK3328
Date: Fri, 05 Jul 2024 04:30:24 +0000 [thread overview]
Message-ID: <20240705-b217334c13-13d1a8cd7c07@bugzilla.kernel.org> (raw)
In-Reply-To: <20230419-b217334c0-3101f9f4b426@bugzilla.kernel.org>
antwain.schneider writes via Kernel.org Bugzilla:
thank you Huang-Huang Bao for addressing this problem better than i with commits
commit e8448a6c817c2aa6c6af785b1d45678bd5977e8d
commit 5ef6914e0bf578357b4c906ffe6b26e7eedb8ccf
commit 01b4b1d1cec48ef4c26616c2fc4600b2c9fec05a
GRF_GPIO2BL_IOMUX: 00000600
2b0 | 2b1 | 2b2 | 2b3 | 2b4 | 2b5 | 2b6 | res
00 01|02 03|04 05|06 07|08 09|10 11|12 13|14 15
0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0
GRF_GPIO2BH_IOMUX: 00000000
2b7 | reserved.............................
00 01 02|03 04 05 06 07 08 09 10 11 12 13 14 15
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
View: https://bugzilla.kernel.org/show_bug.cgi?id=217334#c13
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-07-05 4:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
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-19 16:12 ` 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 ` Kernel.org Bugbot [this message]
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=20240705-b217334c13-13d1a8cd7c07@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=bugs@lists.linux.dev \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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 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.