From: carlos.song@nxp.com
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, haibo.chen@nxp.com,
frank.li@nxp.com
Subject: [PATCH 0/5] arm64: dts: imx: Add LPSPI alias for I.MX8ULP/8QXP/8QM/8DXL/93
Date: Fri, 18 Oct 2024 11:45:27 +0800 [thread overview]
Message-ID: <20241018034532.2552325-1-carlos.song@nxp.com> (raw)
From: Carlos Song <carlos.song@nxp.com>
Now there is no alias for LPSPI on I.MX8ULP/8QXP/8QM/8DXL/93.
So spidevB.C index B will be automatically allocated by kernel
incrementally from zero according to the order of registering
spi controller. In this case, it is hard to determine spidevB.C
is spi interface of device C on which LPSPI bus. It will cause
confusion when operate spi devices in userspace.
For example, in I.MX93, When LPSPI3 and LPSPI5 are enabled
without alais:
:~# ls /dev/spidev*
/dev/spidev0.0 /dev/spidev1.0
After LPSPI alais is applied, fixedly B is the LPSPI index and
C is the spi device index in spidevB.C. They are the pleasant
spidev names. Directly spidev2.0 is the device0 at LPSPI3 bus
and spidev4.0 is the device0 at LPSPI5 bus:
:~# ls /dev/spidev*
/dev/spidev2.0 /dev/spidev4.0
Signed-off-by: Carlos Song <carlos.song@nxp.com>
Signed-off-by: Haibo Chen <haibo.chen@nxp.com>
Carlos Song (5):
arm64: dts: imx8qxp: Add LPSPI alias
arm64: dts: imx8qm: Add LPSPI alias
arm64: dts: imx8dxl: Add LPSPI alias
arm64: dts: imx8ulp: Add LPSPI alias
arm64: dts: imx93: Add LPSPI alias
arch/arm64/boot/dts/freescale/imx8dxl.dtsi | 4 ++++
arch/arm64/boot/dts/freescale/imx8qm.dtsi | 4 ++++
arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 4 ++++
arch/arm64/boot/dts/freescale/imx8ulp.dtsi | 2 ++
arch/arm64/boot/dts/freescale/imx93.dtsi | 8 ++++++++
5 files changed, 22 insertions(+)
--
2.34.1
next reply other threads:[~2024-10-18 3:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 3:45 carlos.song [this message]
2024-10-18 3:45 ` [PATCH 1/5] arm64: dts: imx8qxp: Add LPSPI alias carlos.song
2024-10-18 3:45 ` [PATCH 2/5] arm64: dts: imx8qm: " carlos.song
2024-10-18 3:45 ` [PATCH 3/5] arm64: dts: imx8dxl: " carlos.song
2024-10-18 3:45 ` [PATCH 4/5] arm64: dts: imx8ulp: " carlos.song
2024-10-18 3:45 ` [PATCH 5/5] arm64: dts: imx93: " carlos.song
2024-11-01 8:15 ` [PATCH 0/5] arm64: dts: imx: Add LPSPI alias for I.MX8ULP/8QXP/8QM/8DXL/93 Shawn Guo
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=20241018034532.2552325-1-carlos.song@nxp.com \
--to=carlos.song@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=haibo.chen@nxp.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 \
--cc=shawnguo@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