Documentation/devicetree/bindings/arm/qcom.yaml | 1 + arch/arm64/boot/dts/qcom/Makefile | 1 + .../boot/dts/qcom/qcs6490-radxa-dragon-q6a.dts | 1208 ++++++++++++++++++++ 3 files changed, 1210 insertions(+)
Radxa Dragon Q6A (https://docs.radxa.com/en/dragon/q6a) is a single board
computer, based on the Qualcomm QCS6490 platform.
The board ships with a modified version of the Qualcomm Linux boot
firmware, which is stored on the onboard SPI NOR flash. This allows
booting standard EFI-based bootloaders from SD/eMMC/USB/UFS/NVMe. It
supports replaceable UFS 3.1/eMMC modules for easy user upgrades.
The board schematic is available at [1].
Features enabled and working:
- USB-A 3.0 port (depends on [2])
- Three USB-A 2.0 ports
- RTL8111K Ethernet connected to PCIe0
- UFS 3.1 module (depends on [3])
- eMMC module
- SD card
- M.2 M-Key 2230 PCIe 3.0 x2
- HDMI 2.0 port including audio (depends on [2])
- Configurable I2C/SPI/UART from 40-Pin GPIO (depends on [4])
- Headphone jack
- Onboard thermal sensors
- QSPI controller for updating boot firmware
- ADSP remoteproc (Type-C and charging features disabled in firmware)
- CDSP remoteproc (for AI applications using QNN)
- Venus video encode and decode accelerator
Features available with additional DT overlays:
- CSI cameras
- DSI display
ALSA UCM and Audioreach topology patches are available at [5] and [6].
This series is posted as an RFC because it depends on several other patch series.
[1]: https://docs.radxa.com/en/dragon/q6a/download
[2]: https://lore.kernel.org/all/20250908-topic-x1e80100-hdmi-v3-4-c53b0f2bc2fb@linaro.org/
[3]: https://lore.kernel.org/all/20250902164900.21685-1-quic_rdwivedi@quicinc.com/
[4]: https://lore.kernel.org/all/20250911043256.3523057-1-viken.dadhaniya@oss.qualcomm.com/
[5]: https://github.com/alsa-project/alsa-ucm-conf/pull/601
[6]: https://github.com/linux-msm/audioreach-topology/pull/24
Signed-off-by: Xilin Wu <sophon@radxa.com>
---
Xilin Wu (2):
dt-bindings: arm: qcom: Add Radxa Dragon Q6A
arm64: dts: qcom: qcs6490: Introduce Radxa Dragon Q6A
Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
arch/arm64/boot/dts/qcom/Makefile | 1 +
.../boot/dts/qcom/qcs6490-radxa-dragon-q6a.dts | 1208 ++++++++++++++++++++
3 files changed, 1210 insertions(+)
---
base-commit: 51095600e8c19d53729a7fbd273abc4435a25e9b
change-id: 20250912-radxa-dragon-q6a-eedcdeaf3e66
prerequisite-message-id: <20250902164900.21685-1-quic_rdwivedi@quicinc.com>
prerequisite-patch-id: 257564b609217fda19c9f3424fcd9f6e2ce3ef3c
prerequisite-patch-id: a8f21781f3bff140260100b74041752000c06000
prerequisite-patch-id: b46127e2433ede17cc5e1a012f58041c6ef97b13
prerequisite-patch-id: e8978c5a30373c3ff312b2c8720f586c389f18f8
prerequisite-message-id: <20250911043256.3523057-1-viken.dadhaniya@oss.qualcomm.com>
prerequisite-patch-id: c7a057030b78afbbb231280de3765294c006c6f8
prerequisite-patch-id: 56011305aa35e4c64fc7d63950764807cb81cc4d
prerequisite-patch-id: c3d3b313ac6abe4ec10fd820b6a9bbc63fdbdb82
prerequisite-patch-id: 63ee94d0ccd40f60a98b0004d627ad2e7b440d25
prerequisite-patch-id: 392e8f1902571e5035d5af72e40dc474b5f1b274
prerequisite-patch-id: e38fba722bdabc02ba09d2dc51df7010dbe28168
prerequisite-patch-id: a3ca5dba8def5769ffb4b95df2963da60a736f96
prerequisite-patch-id: 4c0fe8d677d73aaf1b5b842e072246d84729d1c4
Best regards,
--
Xilin Wu <sophon@radxa.com>
On 9/12/25 10:03 AM, Xilin Wu wrote: > Radxa Dragon Q6A (https://docs.radxa.com/en/dragon/q6a) is a single board > computer, based on the Qualcomm QCS6490 platform. > > The board ships with a modified version of the Qualcomm Linux boot > firmware, which is stored on the onboard SPI NOR flash. This allows > booting standard EFI-based bootloaders from SD/eMMC/USB/UFS/NVMe. It > supports replaceable UFS 3.1/eMMC modules for easy user upgrades. > > The board schematic is available at [1]. > > Features enabled and working: > > - USB-A 3.0 port (depends on [2]) > - Three USB-A 2.0 ports > - RTL8111K Ethernet connected to PCIe0 > - UFS 3.1 module (depends on [3]) > - eMMC module > - SD card > - M.2 M-Key 2230 PCIe 3.0 x2 > - HDMI 2.0 port including audio (depends on [2]) > - Configurable I2C/SPI/UART from 40-Pin GPIO (depends on [4]) > - Headphone jack > - Onboard thermal sensors > - QSPI controller for updating boot firmware > - ADSP remoteproc (Type-C and charging features disabled in firmware) > - CDSP remoteproc (for AI applications using QNN) > - Venus video encode and decode accelerator You have a number of features that depend on several other series, and as Krzysztof pointed out this is difficult to merge/review.. Could you please create a "linux-next/master-ready" version of this series and separate the changes for which the dependencies are unmet, putting them at the end? This way we can take at least some of your diff. If you still want review on them, you can also send them as [PATCH DNM] or so Konrad
On 2025/9/12 16:56:04, Konrad Dybcio wrote: > On 9/12/25 10:03 AM, Xilin Wu wrote: >> Radxa Dragon Q6A (https://docs.radxa.com/en/dragon/q6a) is a single board >> computer, based on the Qualcomm QCS6490 platform. >> >> The board ships with a modified version of the Qualcomm Linux boot >> firmware, which is stored on the onboard SPI NOR flash. This allows >> booting standard EFI-based bootloaders from SD/eMMC/USB/UFS/NVMe. It >> supports replaceable UFS 3.1/eMMC modules for easy user upgrades. >> >> The board schematic is available at [1]. >> >> Features enabled and working: >> >> - USB-A 3.0 port (depends on [2]) >> - Three USB-A 2.0 ports >> - RTL8111K Ethernet connected to PCIe0 >> - UFS 3.1 module (depends on [3]) >> - eMMC module >> - SD card >> - M.2 M-Key 2230 PCIe 3.0 x2 >> - HDMI 2.0 port including audio (depends on [2]) >> - Configurable I2C/SPI/UART from 40-Pin GPIO (depends on [4]) >> - Headphone jack >> - Onboard thermal sensors >> - QSPI controller for updating boot firmware >> - ADSP remoteproc (Type-C and charging features disabled in firmware) >> - CDSP remoteproc (for AI applications using QNN) >> - Venus video encode and decode accelerator > > You have a number of features that depend on several other series, and > as Krzysztof pointed out this is difficult to merge/review.. Could you > please create a "linux-next/master-ready" version of this series and > separate the changes for which the dependencies are unmet, putting them > at the end? This way we can take at least some of your diff. > > If you still want review on them, you can also send them as [PATCH DNM] > or so > > Konrad > Thanks for the suggestion. I think I can separate the changes that have unmet dependencies, and mark them as DNM. Can I send the new series now, or am I supposed to wait for a few days? -- Best regards, Xilin Wu <sophon@radxa.com>
On 9/12/25 11:04 AM, Xilin Wu wrote: > On 2025/9/12 16:56:04, Konrad Dybcio wrote: >> On 9/12/25 10:03 AM, Xilin Wu wrote: >>> Radxa Dragon Q6A (https://docs.radxa.com/en/dragon/q6a) is a single board >>> computer, based on the Qualcomm QCS6490 platform. >>> >>> The board ships with a modified version of the Qualcomm Linux boot >>> firmware, which is stored on the onboard SPI NOR flash. This allows >>> booting standard EFI-based bootloaders from SD/eMMC/USB/UFS/NVMe. It >>> supports replaceable UFS 3.1/eMMC modules for easy user upgrades. >>> >>> The board schematic is available at [1]. >>> >>> Features enabled and working: >>> >>> - USB-A 3.0 port (depends on [2]) >>> - Three USB-A 2.0 ports >>> - RTL8111K Ethernet connected to PCIe0 >>> - UFS 3.1 module (depends on [3]) >>> - eMMC module >>> - SD card >>> - M.2 M-Key 2230 PCIe 3.0 x2 >>> - HDMI 2.0 port including audio (depends on [2]) >>> - Configurable I2C/SPI/UART from 40-Pin GPIO (depends on [4]) >>> - Headphone jack >>> - Onboard thermal sensors >>> - QSPI controller for updating boot firmware >>> - ADSP remoteproc (Type-C and charging features disabled in firmware) >>> - CDSP remoteproc (for AI applications using QNN) >>> - Venus video encode and decode accelerator >> >> You have a number of features that depend on several other series, and >> as Krzysztof pointed out this is difficult to merge/review.. Could you >> please create a "linux-next/master-ready" version of this series and >> separate the changes for which the dependencies are unmet, putting them >> at the end? This way we can take at least some of your diff. >> >> If you still want review on them, you can also send them as [PATCH DNM] >> or so >> >> Konrad >> > > Thanks for the suggestion. I think I can separate the changes that have unmet dependencies, and mark them as DNM. Can I send the new series now, or am I supposed to wait for a few days? Since we can't do much with this one, please apply Krzysztof's review comments and tags and feel free to resend Konrad
On 12/09/2025 10:03, Xilin Wu wrote: > Radxa Dragon Q6A (https://docs.radxa.com/en/dragon/q6a) is a single board > computer, based on the Qualcomm QCS6490 platform. > > The board ships with a modified version of the Qualcomm Linux boot > firmware, which is stored on the onboard SPI NOR flash. This allows > booting standard EFI-based bootloaders from SD/eMMC/USB/UFS/NVMe. It > supports replaceable UFS 3.1/eMMC modules for easy user upgrades. > > The board schematic is available at [1]. > > Features enabled and working: > > - USB-A 3.0 port (depends on [2]) > - Three USB-A 2.0 ports > - RTL8111K Ethernet connected to PCIe0 > - UFS 3.1 module (depends on [3]) > - eMMC module > - SD card > - M.2 M-Key 2230 PCIe 3.0 x2 > - HDMI 2.0 port including audio (depends on [2]) > - Configurable I2C/SPI/UART from 40-Pin GPIO (depends on [4]) > - Headphone jack > - Onboard thermal sensors > - QSPI controller for updating boot firmware > - ADSP remoteproc (Type-C and charging features disabled in firmware) > - CDSP remoteproc (for AI applications using QNN) > - Venus video encode and decode accelerator > > Features available with additional DT overlays: > - CSI cameras > - DSI display > > ALSA UCM and Audioreach topology patches are available at [5] and [6]. > > This series is posted as an RFC because it depends on several other patch series. Ah, here it is. That's the most important information, so should be placed at the top. You do not put the most important information hidden somewhere in the mail. Question about dependencies stays, though... Best regards, Krzysztof
On 12/09/2025 10:03, Xilin Wu wrote: > base-commit: 51095600e8c19d53729a7fbd273abc4435a25e9b > change-id: 20250912-radxa-dragon-q6a-eedcdeaf3e66 > prerequisite-message-id: <20250902164900.21685-1-quic_rdwivedi@quicinc.com> > prerequisite-patch-id: 257564b609217fda19c9f3424fcd9f6e2ce3ef3c > prerequisite-patch-id: a8f21781f3bff140260100b74041752000c06000 > prerequisite-patch-id: b46127e2433ede17cc5e1a012f58041c6ef97b13 > prerequisite-patch-id: e8978c5a30373c3ff312b2c8720f586c389f18f8 > prerequisite-message-id: <20250911043256.3523057-1-viken.dadhaniya@oss.qualcomm.com> > prerequisite-patch-id: c7a057030b78afbbb231280de3765294c006c6f8 > prerequisite-patch-id: 56011305aa35e4c64fc7d63950764807cb81cc4d > prerequisite-patch-id: c3d3b313ac6abe4ec10fd820b6a9bbc63fdbdb82 > prerequisite-patch-id: 63ee94d0ccd40f60a98b0004d627ad2e7b440d25 > prerequisite-patch-id: 392e8f1902571e5035d5af72e40dc474b5f1b274 > prerequisite-patch-id: e38fba722bdabc02ba09d2dc51df7010dbe28168 > prerequisite-patch-id: a3ca5dba8def5769ffb4b95df2963da60a736f96 > prerequisite-patch-id: 4c0fe8d677d73aaf1b5b842e072246d84729d1c4 So the RFC is because it cannot be yet merged? Please always add such note in the cover letter. Also, are you sure these are real dependencies? Like REALLY real dependencies? Best regards, Krzysztof
On 2025/9/12 16:12:54, Krzysztof Kozlowski wrote: > On 12/09/2025 10:03, Xilin Wu wrote: >> base-commit: 51095600e8c19d53729a7fbd273abc4435a25e9b >> change-id: 20250912-radxa-dragon-q6a-eedcdeaf3e66 >> prerequisite-message-id: <20250902164900.21685-1-quic_rdwivedi@quicinc.com> >> prerequisite-patch-id: 257564b609217fda19c9f3424fcd9f6e2ce3ef3c >> prerequisite-patch-id: a8f21781f3bff140260100b74041752000c06000 >> prerequisite-patch-id: b46127e2433ede17cc5e1a012f58041c6ef97b13 >> prerequisite-patch-id: e8978c5a30373c3ff312b2c8720f586c389f18f8 >> prerequisite-message-id: <20250911043256.3523057-1-viken.dadhaniya@oss.qualcomm.com> >> prerequisite-patch-id: c7a057030b78afbbb231280de3765294c006c6f8 >> prerequisite-patch-id: 56011305aa35e4c64fc7d63950764807cb81cc4d >> prerequisite-patch-id: c3d3b313ac6abe4ec10fd820b6a9bbc63fdbdb82 >> prerequisite-patch-id: 63ee94d0ccd40f60a98b0004d627ad2e7b440d25 >> prerequisite-patch-id: 392e8f1902571e5035d5af72e40dc474b5f1b274 >> prerequisite-patch-id: e38fba722bdabc02ba09d2dc51df7010dbe28168 >> prerequisite-patch-id: a3ca5dba8def5769ffb4b95df2963da60a736f96 >> prerequisite-patch-id: 4c0fe8d677d73aaf1b5b842e072246d84729d1c4 > So the RFC is because it cannot be yet merged? Please always add such > note in the cover letter. > > Also, are you sure these are real dependencies? Like REALLY real > dependencies? Well, I think these are indeed dependencies. The dtb does build without them, but dtbs_check will fail. The board will also malfunction or simple crash on boot without the DT and driver changes. > > Best regards, > Krzysztof > -- Best regards, Xilin Wu <sophon@radxa.com>
On 12/09/2025 10:25, Xilin Wu wrote: > On 2025/9/12 16:12:54, Krzysztof Kozlowski wrote: >> On 12/09/2025 10:03, Xilin Wu wrote: >>> base-commit: 51095600e8c19d53729a7fbd273abc4435a25e9b >>> change-id: 20250912-radxa-dragon-q6a-eedcdeaf3e66 >>> prerequisite-message-id: <20250902164900.21685-1-quic_rdwivedi@quicinc.com> >>> prerequisite-patch-id: 257564b609217fda19c9f3424fcd9f6e2ce3ef3c >>> prerequisite-patch-id: a8f21781f3bff140260100b74041752000c06000 >>> prerequisite-patch-id: b46127e2433ede17cc5e1a012f58041c6ef97b13 >>> prerequisite-patch-id: e8978c5a30373c3ff312b2c8720f586c389f18f8 >>> prerequisite-message-id: <20250911043256.3523057-1-viken.dadhaniya@oss.qualcomm.com> >>> prerequisite-patch-id: c7a057030b78afbbb231280de3765294c006c6f8 >>> prerequisite-patch-id: 56011305aa35e4c64fc7d63950764807cb81cc4d >>> prerequisite-patch-id: c3d3b313ac6abe4ec10fd820b6a9bbc63fdbdb82 >>> prerequisite-patch-id: 63ee94d0ccd40f60a98b0004d627ad2e7b440d25 >>> prerequisite-patch-id: 392e8f1902571e5035d5af72e40dc474b5f1b274 >>> prerequisite-patch-id: e38fba722bdabc02ba09d2dc51df7010dbe28168 >>> prerequisite-patch-id: a3ca5dba8def5769ffb4b95df2963da60a736f96 >>> prerequisite-patch-id: 4c0fe8d677d73aaf1b5b842e072246d84729d1c4 >> So the RFC is because it cannot be yet merged? Please always add such >> note in the cover letter. >> >> Also, are you sure these are real dependencies? Like REALLY real >> dependencies? > > Well, I think these are indeed dependencies. The dtb does build without > them, but dtbs_check will fail. The board will also malfunction or That's not a dependency. > simple crash on boot without the DT and driver changes. Neither is this. > > Best regards, Krzysztof
© 2016 - 2025 Red Hat, Inc.