From: Francesco Dolcini <francesco@dolcini.it>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: Francesco Dolcini <francesco.dolcini@toradex.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] ARM: dts: imx: enable SPI on Apalis iMX6 and Colibri iMX7
Date: Thu, 1 Oct 2026 17:53:57 +0200 [thread overview]
Message-ID: <20261001155401.2584935-1-francesco@dolcini.it> (raw)
From: Francesco Dolcini <francesco.dolcini@toradex.com>
The SPI controllers of the Apalis iMX6 and Colibri iMX6ULL modules are
disabled in the module device tree and no carrier board enabled them.
A device can be instantiated from user space through the spi_master
new_device sysfs interface, so enable the controllers on the carrier
boards where the signals reach a user accessible connector.
The Colibri iMX6 and iMX7 carrier boards and the Apalis iMX8 ones
already do this.
Francesco Dolcini (2):
ARM: dts: imx6q-apalis: enable SPI1 and SPI2
ARM: dts: imx6ull-colibri-iris: enable SPI
arch/arm/boot/dts/nxp/imx/imx6q-apalis-eval.dtsi | 10 ++++++++++
arch/arm/boot/dts/nxp/imx/imx6q-apalis-ixora-v1.2.dts | 10 ++++++++++
arch/arm/boot/dts/nxp/imx/imx6q-apalis-ixora.dts | 10 ++++++++++
arch/arm/boot/dts/nxp/imx/imx6ull-colibri-iris.dtsi | 5 +++++
4 files changed, 35 insertions(+)
--
2.47.3
next reply other threads:[~2026-10-01 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 15:53 Francesco Dolcini [this message]
2026-10-01 15:53 ` [PATCH v1 1/2] ARM: dts: imx6q-apalis: enable SPI1 and SPI2 Francesco Dolcini
2026-10-02 7:12 ` Daniel Baluta
2026-10-01 15:53 ` [PATCH v1 2/2] ARM: dts: imx6ull-colibri-iris: enable SPI Francesco Dolcini
2026-10-02 7:11 ` Daniel Baluta
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=20261001155401.2584935-1-francesco@dolcini.it \
--to=francesco@dolcini.it \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--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