From: Guenter Roeck <linux@roeck-us.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org,
Gerd Hoffmann <kraxel@redhat.com>,
Guenter Roeck <linux@roeck-us.net>,
Jean-Christophe Dubois <jcd@tribudubois.net>
Subject: [PATCH v3 0/5] Wire up USB controllers in i.MX6 emulations
Date: Thu, 12 Mar 2020 18:45:46 -0700 [thread overview]
Message-ID: <20200313014551.12554-1-linux@roeck-us.net> (raw)
This patch series wires up the USB controllers on fsl-imx6 and fsl-imx6ul
emulations.
The first patch provides a basic implementation of the USB PHY controller
used in i.MX28 and later chips. Only reset bit handling in the control
register is actually implemented. Basic USB PHY support is needed to make
the USB ports operational in Linux.
The second patch fixes USB and USB PHY interrupt numbers for i.MX6UL.
The third patch instantiates unimplemented pwm and can devices. This patch
is necessary to avoid crashes in Linux when it tries to access those
devices. The crashes are observed when trying to boot Linux v4.21 or later.
The final two patches instantiate the USB controllers for i.mMX6 and
i.MX6UL.
v3:
- Minor cleanup in patch 1/5 (see details in patch)
- Added patch to fix USB and USB PHY interrupt numbers for fsl-imx6ul.
- Added patch to instantiate unimplemented pwm and CAN devices.
- Instantiate USB and USB PHY separately. They are logically different,
and the number of instances is not always the same.
v2:
- Implement and instantiate basic USB PHY implementation
instead of emulating a single USB PHY register
----------------------------------------------------------------
Guenter Roeck (5):
hw/usb: Add basic i.MX USB Phy support
hw/arm/fsl-imx6ul: Fix USB interrupt numbers
hw/arm/fsl-imx6ul: Instantiate unimplemented pwm and can devices
hw/arm/fsl-imx6ul: Wire up USB controllers
hw/arm/fsl-imx6: Wire up USB controllers
MAINTAINERS | 2 +
hw/arm/Kconfig | 1 +
hw/arm/fsl-imx6.c | 36 +++++++
hw/arm/fsl-imx6ul.c | 49 ++++++++++
hw/usb/Kconfig | 5 +
hw/usb/Makefile.objs | 2 +
hw/usb/imx-usb-phy.c | 225 +++++++++++++++++++++++++++++++++++++++++++
include/hw/arm/fsl-imx6.h | 6 ++
include/hw/arm/fsl-imx6ul.h | 16 ++-
include/hw/usb/imx-usb-phy.h | 53 ++++++++++
10 files changed, 392 insertions(+), 3 deletions(-)
create mode 100644 hw/usb/imx-usb-phy.c
create mode 100644 include/hw/usb/imx-usb-phy.h
next reply other threads:[~2020-03-13 1:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 1:45 Guenter Roeck [this message]
2020-03-13 1:45 ` [PATCH v3 1/5] hw/usb: Add basic i.MX USB Phy support Guenter Roeck
2021-05-19 19:00 ` Philippe Mathieu-Daudé
2023-03-16 13:41 ` Peter Maydell
2023-03-16 14:12 ` Guenter Roeck
2023-03-16 14:51 ` Peter Maydell
2023-03-16 17:07 ` Guenter Roeck
2020-03-13 1:45 ` [PATCH v3 2/5] hw/arm/fsl-imx6ul: Fix USB interrupt numbers Guenter Roeck
2020-03-13 1:45 ` [PATCH v3 3/5] hw/arm/fsl-imx6ul: Instantiate unimplemented pwm and can devices Guenter Roeck
2020-03-13 1:45 ` [PATCH v3 4/5] hw/arm/fsl-imx6ul: Wire up USB controllers Guenter Roeck
2020-03-13 1:45 ` [PATCH v3 5/5] hw/arm/fsl-imx6: " Guenter Roeck
2020-03-13 11:25 ` [PATCH v3 0/5] Wire up USB controllers in i.MX6 emulations Peter Maydell
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=20200313014551.12554-1-linux@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jcd@tribudubois.net \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).