linux-kernel - Re: [PATCH] arm64: dts: ti: k3-pinctrl: Enable Schmitt Trigger by default

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <175205731408.919009.13331484172952220730.b4-ty@ti.com>
Date: Wed, 9 Jul 2025 16:05:54 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <devicetree@...r.kernel.org>,
        Alexander Sverdlin
	<alexander.sverdlin@...il.com>
CC: Vignesh Raghavendra <vigneshr@...com>, Nishanth Menon <nm@...com>,
        Tero
 Kristo <kristo@...nel.org>, Rob Herring <robh@...nel.org>,
        Krzysztof
 Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley <conor+dt@...nel.org>,
        <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-pinctrl: Enable Schmitt Trigger by default

Hi A. Sverdlin,

On Tue, 01 Jul 2025 12:54:35 +0200, A. Sverdlin wrote:
> Switch Schmitt Trigger functions for PIN_INPUT* macros by default. This is
> HW PoR configuration, the slew rate requirements without ST enabled are
> pretty tough for these devices. We've noticed spurious GPIO interrupts even
> with noise-free edges but not meeting slew rate requirements (3.3E+6 V/s
> for 3.3v LVCMOS).
> 
> It's not obvious why one might want to disable the PoR-enabled ST on any
> pin. Just enable it by default. As it's not possible to provide OR-able
> macros to disable the ST, shall anyone require it, provide a set of
> new macros with _NOST suffix.
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/1] arm64: dts: ti: k3-pinctrl: Enable Schmitt Trigger by default
      commit: 5b272127884bded21576a6ddceca13725a351c63

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh