From: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
To: linusw@kernel.org, brgl@kernel.org, thierry.reding@kernel.org,
jonathanh@nvidia.com,
Samasth Norway Ananda <samasth.norway.ananda@oracle.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
linux-gpio@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: tegra: fix irq_release_resources calling enable instead of disable
Date: Thu, 9 Apr 2026 10:36:23 +0200 [thread overview]
Message-ID: <177572378022.62056.4431173020007463184.b4-ty@oss.qualcomm.com> (raw)
In-Reply-To: <20260407210247.1737938-1-samasth.norway.ananda@oracle.com>
On Tue, 07 Apr 2026 14:02:47 -0700, Samasth Norway Ananda wrote:
> tegra_gpio_irq_release_resources() erroneously calls tegra_gpio_enable()
> instead of tegra_gpio_disable(). When IRQ resources are released, the
> GPIO configuration bit (CNF) should be cleared to deconfigure the pin as
> a GPIO. Leaving it enabled wastes power and can cause unexpected behavior
> if the pin is later reused for an alternate function via pinctrl.
>
>
> [...]
Applied, thanks!
[1/1] gpio: tegra: fix irq_release_resources calling enable instead of disable
https://git.kernel.org/brgl/c/1561d96f5f55c1bca9ff047ace5813f4f244eea6
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
prev parent reply other threads:[~2026-04-09 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 21:02 [PATCH] gpio: tegra: fix irq_release_resources calling enable instead of disable Samasth Norway Ananda
2026-04-09 8:36 ` Bartosz Golaszewski [this message]
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=177572378022.62056.4431173020007463184.b4-ty@oss.qualcomm.com \
--to=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=samasth.norway.ananda@oracle.com \
--cc=thierry.reding@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).