From: Vitor Soares <ivitro@gmail.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Vitor Soares <vitor.soares@toradex.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, ivitro@gmail.com
Subject: [PATCH v1 0/2] arm64: dts: ti: k3-am69-aquila: fix SPI hardware CS issue
Date: Mon, 12 Jan 2026 17:53:45 +0000 [thread overview]
Message-ID: <20260112175350.79270-1-ivitro@gmail.com> (raw)
From: Vitor Soares <vitor.soares@toradex.com>
Hardware chip select does not work correctly on main_spi0 and main_spi2
controllers on the Aquila AM69 module. Testing revealed main_spi2 loses
CS state during runtime PM suspend, while main_spi0 cannot drive CS HIGH
when bus is idle. This series switches both controllers to use GPIO-based
chip select instead.
Vitor Soares (2):
arm64: dts: ti: k3-am69-aquila: change main_spi0/2 CS to GPIO mode
arm64: dts: ti: k3-am69-aquila-clover: change main_spi2 CS0 to GPIO
mode
arch/arm64/boot/dts/ti/k3-am69-aquila-clover.dts | 3 ++-
arch/arm64/boot/dts/ti/k3-am69-aquila.dtsi | 6 ++++--
2 files changed, 6 insertions(+), 3 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-12 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 17:53 Vitor Soares [this message]
2026-01-12 17:53 ` [PATCH v1 1/2] arm64: dts: ti: k3-am69-aquila: change main_spi0/2 CS to GPIO mode Vitor Soares
2026-01-12 17:53 ` [PATCH v1 2/2] arm64: dts: ti: k3-am69-aquila-clover: change main_spi2 CS0 " Vitor Soares
2026-01-13 6:35 ` [PATCH v1 0/2] arm64: dts: ti: k3-am69-aquila: fix SPI hardware CS issue Francesco Dolcini
2026-01-14 17:11 ` Nishanth Menon
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=20260112175350.79270-1-ivitro@gmail.com \
--to=ivitro@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
--cc=vitor.soares@toradex.com \
/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