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>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH v2 0/2] gpio: i.MX: make _get_value() able to read output pin state
Date: Sat, 18 Oct 2025 11:59:46 +0200 [thread overview]
Message-ID: <20251018-imx_gpio-v2-0-22e4fc090de6@hotmail.com> (raw)
Make _get_value() read back the dr register instead of the psr register
when the direction is set to output. Now _get_value() can actually read
the state of an output gpio instead of being always low.
Also add a note in the migration guide file.
Signed-off-by: Maud Spierings <maud_spierings@hotmail.com>
---
Changes in v2:
- Move the extra commit comment into the commit [1/2]
- Actually add a note to the migration file [2/2]
- Link to v1: https://lore.kernel.org/r/20251015-imx_gpio-v1-0-e57925f906bb@hotmail.com
---
Maud Spierings (2):
gpio: i.MX: make _get_value() able to read output pin state
Documentation: migration-2025.11.0: add note about new gpio behaviour
.../migration-guides/migration-2025.11.0.rst | 7 +++++++
drivers/gpio/gpio-imx.c | 19 +++++++++++--------
2 files changed, 18 insertions(+), 8 deletions(-)
---
base-commit: 8defba1d0ab1aef9dd5d57710e18d0d02e2c48e2
change-id: 20251015-imx_gpio-46efe1e7abd3
Best regards,
--
Maud Spierings <maud_spierings@hotmail.com>
next 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 Maud Spierings via B4 Relay [this message]
2025-10-18 9:59 ` [PATCH v2 1/2] " Maud Spierings via B4 Relay
2025-10-18 9:59 ` [PATCH v2 2/2] Documentation: migration-2025.11.0: add note about new gpio behaviour Maud Spierings via B4 Relay
2025-10-20 8:21 ` [PATCH v2 0/2] gpio: i.MX: make _get_value() able to read output pin state 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-0-22e4fc090de6@hotmail.com \
--to=devnull+maud_spierings.hotmail.com@kernel.org \
--cc=a.fatoum@pengutronix.de \
--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