From: Xu Yang <xu.yang_2@nxp.com>
To: gregkh@linuxfoundation.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, peter.chen@kernel.org
Cc: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, jun.li@nxp.com
Subject: [PATCH v5 0/6] add USB2.0 support for i.MX95-19x19 EVK board
Date: Wed, 12 Mar 2025 16:26:54 +0800 [thread overview]
Message-ID: <20250312082700.260260-1-xu.yang_2@nxp.com> (raw)
The i.MX95-19x19 EVK board features a USB 2.0 Type-A port, with this
series primarily introducing USB 2.0 support. In the i.MX95 architecture,
the USB wake-up handling mechanism is integrated within the HSIO block
control module, utilizing a dedicated wake-up interrupt. Therefore, we
also implemented corresponding wake-up logic code to properly manage this
functionality.
For detailed changes can refer to patch commit log.
v5:
- add wakeup_irq valid checking
- add Ab tag
v4:
- add blkctl NULL checking
- warning if wakeup setting is missing for imx95
- add Tb tag
v3:
- fix possible build break
- remove usbmisc_imx95_init()
- add Rb tag in some patches
v2:
- apply some suggestions
- improve wakeup interrupt handling
- add Rb tag in some patches
Xu Yang (6):
dt-bindings: usb: chipidea: Add i.MX95 compatible string
'fsl,imx95-usb'
dt-bindings: usb: usbmisc-imx: add support for i.MX95 platform
usb: chipidea: imx: add wakeup interrupt handling
usb: chipidea: imx: add HSIO Block Control wakeup setting
arm64: dts: imx95: add USB2.0 nodes
arm64: dts: imx95-19x19-evk: enable USB2.0 node
.../bindings/usb/chipidea,usb2-common.yaml | 3 +
.../bindings/usb/chipidea,usb2-imx.yaml | 24 +++++-
.../devicetree/bindings/usb/fsl,usbmisc.yaml | 23 +++++-
.../boot/dts/freescale/imx95-19x19-evk.dts | 16 ++++
arch/arm64/boot/dts/freescale/imx95.dtsi | 30 ++++++++
drivers/usb/chipidea/ci_hdrc_imx.c | 37 +++++++++
drivers/usb/chipidea/usbmisc_imx.c | 77 +++++++++++++++++++
7 files changed, 208 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2025-03-12 8:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 8:26 Xu Yang [this message]
2025-03-12 8:26 ` [PATCH v5 1/6] dt-bindings: usb: chipidea: Add i.MX95 compatible string 'fsl,imx95-usb' Xu Yang
2025-03-12 8:26 ` [PATCH v5 2/6] dt-bindings: usb: usbmisc-imx: add support for i.MX95 platform Xu Yang
2025-03-12 8:26 ` [PATCH v5 3/6] usb: chipidea: imx: add wakeup interrupt handling Xu Yang
2025-03-17 3:26 ` Peter Chen (CIX)
2025-03-12 8:26 ` [PATCH v5 4/6] usb: chipidea: imx: add HSIO Block Control wakeup setting Xu Yang
2025-03-12 8:26 ` [PATCH v5 5/6] arm64: dts: imx95: add USB2.0 nodes Xu Yang
2025-03-12 8:27 ` [PATCH v5 6/6] arm64: dts: imx95-19x19-evk: enable USB2.0 node Xu Yang
2025-03-14 8:18 ` [PATCH v5 0/6] add USB2.0 support for i.MX95-19x19 EVK board Greg KH
2025-03-14 9:21 ` Xu Yang
2025-03-14 12:37 ` Greg KH
2025-03-18 7:24 ` Xu Yang
2025-03-18 13:12 ` Greg KH
2025-03-18 14:45 ` Xu Yang
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=20250312082700.260260-1-xu.yang_2@nxp.com \
--to=xu.yang_2@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@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