Skip to main content
The following table lists the device interface features in Dragonwing IQ-615. Table : Dragonwing IQ-615 device interfaces
3xQUP v3 serial engine
Serial engine instancesQUPV3_0QUPV3_1
Application processor QUP v3 serial engine44
LPI QUP v3 serial engine5–
2xUSB controller
Controller address0xa6000000xa800000
Max speedUSB 3.x SuperSpeedUSB 2.0 high speed
HS/SS PHY power rails
  • L4A: VDDD_QUSB_0_HS0_0P9
  • L11A: VDDA_QUSB_0_HS0_1P8
  • L17A: VDDA_QUSB_0_HS0_3P1
  • L4A: VDDD_QUSB_1_HS0_0P9
  • L11A: VDDA_QUSB_1_HS0_1P8
  • L17A: VDDA_QUSB_1_HS0_3P1
1xPCIe controller
Root complexRC0 (0x1c08000)–
SpeedGen2–
Configuration space0x40100000 (0x100000) 1 MB–
I/O space0x40200000 (0x100000) 1 MB–
Base address register space (BAR)0x40300000 (0x1fd00000) 509 MB–
Power rails
  • L12A (vreg-1p2-supply)
  • L5A (vreg-0p9-supply)
–
InterruptsMSI and PCI legacy interrupts–
Power managementASPM (L1/L1ss, L0s)–

QUP v3 mapping to protocols and GPIOs in Dragonwing IQ-615

Dragonwing IQ-615 has three QUP v3 serial engines: two application-processor QUPs and one LPI QUP. The following table lists the protocol and GPIO mappings.
SSC QUP ownershipThe SSC QUP serial engines—SPI, UART, and I2C—are dedicated to ADSP use cases and are not accessible from Linux user space. Although their associated interface pins can be configured as GPIOs, the pins remain under ADSP ownership and cannot be accessed or controlled from the APPS/Linux domain.
Table : Dragonwing IQ-615 QUP v3 serial engine protocol mapping
QUP v3 serial engineProtocolsQUP lane to GPIO mapping
UARTHS UARTI2C-MSPI-ML0L1L2L3L4L5L6
QUP_0SE0Yes–––1617–––––
SE1––Yes–45–––––
SE2Yes–YesYes0123–––
SE3––Yes–1819–––––
QUP_1SE0Yes–YesYes20212223–––
SE1––Yes–1415–––––
SE2Yes–YesYes6789–––
SE3YesYesYesYes10111213–––
LPI_QUPSE0––Yes–01–––––
SE1––YesYes234567–
SE2––YesYes891011–––
SE3Yes–Yes–1213–––––
SE4Yes–Yes–1415–––––