From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: maud_spierings@hotmail.com, Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH 2/2] Documentation: migration-2025.11.0: add new empty file
Date: Thu, 16 Oct 2025 14:58:02 +0200 [thread overview]
Message-ID: <ba046b46-3106-4ae5-bee4-2a55813d3de3@pengutronix.de> (raw)
In-Reply-To: <20251015-imx_gpio-v1-2-e57925f906bb@hotmail.com>
On 10/15/25 8:03 PM, Maud Spierings via B4 Relay wrote:
> From: Maud Spierings <maud_spierings@hotmail.com>
>
> Add an empty file to hold any future migration notes.
>
> Signed-off-by: Maud Spierings <maud_spierings@hotmail.com>
> ---
> Documentation/migration-guides/migration-2025.11.0.rst | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/migration-guides/migration-2025.11.0.rst b/Documentation/migration-guides/migration-2025.11.0.rst
Sorry, I should have been clearer; I am a bit wary of breaking scripts
or board code that do SION shenanigans, so my suggestion to add a note.
Something like:
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.
> new file mode 100644
> index 0000000000..e69de29bb2
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-10-16 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 18:03 [PATCH 0/2] gpio: i.MX: make _get_value() able to read output pin state Maud Spierings via B4 Relay
2025-10-15 18:03 ` [PATCH 1/2] " Maud Spierings via B4 Relay
2025-10-16 12:53 ` Ahmad Fatoum
2025-10-15 18:03 ` [PATCH 2/2] Documentation: migration-2025.11.0: add new empty file Maud Spierings via B4 Relay
2025-10-16 12:58 ` Ahmad Fatoum [this message]
2025-10-17 9:15 ` Maud Spierings
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=ba046b46-3106-4ae5-bee4-2a55813d3de3@pengutronix.de \
--to=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