From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Xilin Wu <sophon@radxa.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Neil Armstrong <neil.armstrong@linaro.org>,
Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>,
Ram Kumar Dwivedi <quic_rdwivedi@quicinc.com>
Subject: Re: [PATCH RFC 0/2] arm64: dts: qcom: qcs6490: Introduce Radxa Dragon Q6A
Date: Fri, 12 Sep 2025 11:15:06 +0200 [thread overview]
Message-ID: <cc8ba407-1d44-419d-9171-b6911f673772@oss.qualcomm.com> (raw)
In-Reply-To: <103424579111FE76+93c3daf1-4bce-440b-9048-74edb833031e@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
next prev parent reply other threads:[~2025-09-12 9:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 8:03 Xilin Wu
2025-09-12 8:03 ` [PATCH RFC 1/2] dt-bindings: arm: qcom: Add " Xilin Wu
2025-09-12 8:16 ` Krzysztof Kozlowski
2025-09-12 8:03 ` [PATCH RFC 2/2] arm64: dts: qcom: qcs6490: Introduce " Xilin Wu
2025-09-12 8:15 ` Krzysztof Kozlowski
2025-09-12 9:07 ` Konrad Dybcio
2025-09-12 8:12 ` [PATCH RFC 0/2] " Krzysztof Kozlowski
2025-09-12 8:25 ` Xilin Wu
2025-09-12 8:53 ` Krzysztof Kozlowski
2025-09-12 8:16 ` Krzysztof Kozlowski
2025-09-12 8:56 ` Konrad Dybcio
2025-09-12 9:04 ` Xilin Wu
2025-09-12 9:15 ` Konrad Dybcio [this message]
2026-04-07 10:16 ` Andriy Sharandakov
2026-04-07 15:22 ` Xilin Wu
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=cc8ba407-1d44-419d-9171-b6911f673772@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_rdwivedi@quicinc.com \
--cc=robh@kernel.org \
--cc=sophon@radxa.com \
--cc=viken.dadhaniya@oss.qualcomm.com \
/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
all inboxes | Powered by JetHome®