From: Maud Spierings via B4 Relay <devnull+maud_spierings.hotmail.com@kernel.org>
To: Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Cc: Maud Spierings <maud_spierings@hotmail.com>
Subject: [PATCH v2 2/2] Documentation: migration-2025.11.0: add note about new gpio behaviour
Date: Sat, 18 Oct 2025 11:59:48 +0200 [thread overview]
Message-ID: <20251018-imx_gpio-v2-2-22e4fc090de6@hotmail.com> (raw)
In-Reply-To: <20251018-imx_gpio-v2-0-22e4fc090de6@hotmail.com>
From: Maud Spierings <maud_spierings@hotmail.com>
The previous change, changes the behaviour of reading gpio values, make
a note of it in the migration guide.
Signed-off-by: Maud Spierings <maud_spierings@hotmail.com>
---
Documentation/migration-guides/migration-2025.11.0.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/migration-guides/migration-2025.11.0.rst b/Documentation/migration-guides/migration-2025.11.0.rst
new file mode 100644
index 0000000000..9cbc46acc3
--- /dev/null
+++ b/Documentation/migration-guides/migration-2025.11.0.rst
@@ -0,0 +1,7 @@
+i.MX GPIOs
+----------
+
+Reading output GPIOs now returns the configured output level instead
+of reading back the input register. This aligns us with what Linux
+is doing, but may falsify readings of single-ended GPIOs that have
+the SION bit configured.
--
2.51.1.dirty
next prev parent reply other threads:[~2025-10-18 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-18 9:59 [PATCH v2 0/2] gpio: i.MX: make _get_value() able to read output pin state Maud Spierings via B4 Relay
2025-10-18 9:59 ` [PATCH v2 1/2] " Maud Spierings via B4 Relay
2025-10-18 9:59 ` Maud Spierings via B4 Relay [this message]
2025-10-20 8:21 ` [PATCH v2 0/2] " Sascha Hauer
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=20251018-imx_gpio-v2-2-22e4fc090de6@hotmail.com \
--to=devnull+maud_spierings.hotmail.com@kernel.org \
--cc=barebox@lists.infradead.org \
--cc=maud_spierings@hotmail.com \
--cc=s.hauer@pengutronix.de \
/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