[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2vpckcbl7biqaqtb2e22mhnorbiq3xqlsa4ys7x2grzrs67u6f@iixiq3xhfwzl>
Date: Mon, 15 Sep 2025 14:14:37 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
To: Xilin Wu <sophon@...xa.com>
Cc: Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/2] arm64: dts: qcom: qcs6490: Introduce Radxa Dragon
Q6A
On Mon, Sep 15, 2025 at 06:43:50PM +0800, Xilin Wu wrote:
> On 9/15/2025 6:10 PM, Dmitry Baryshkov wrote:
> > On Mon, Sep 15, 2025 at 09:31:44AM +0800, Xilin Wu wrote:
> > > Radxa Dragon Q6A is a single board computer, based on the Qualcomm
> > > QCS6490 platform.
> > >
> > > Features enabled and working:
> > >
> > > - Three USB-A 2.0 ports
> > > - RTL8111K Ethernet connected to PCIe0
> > > - eMMC module
> > > - SD card
> > > - M.2 M-Key 2230 PCIe 3.0 x2
> > > - 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
> > >
> > > Signed-off-by: Xilin Wu <sophon@...xa.com>
> > > ---
> > > arch/arm64/boot/dts/qcom/Makefile | 1 +
> > > .../boot/dts/qcom/qcs6490-radxa-dragon-q6a.dts | 961 +++++++++++++++++++++
> > > 2 files changed, 962 insertions(+)
> > >
> >
> > > +
> > > +&gpu_zap_shader {
> > > + firmware-name = "qcom/qcs6490/a660_zap.mbn";
> >
> > Is the device fused to reject standard qcs6490 firmware? If not, can we
> > point it to the existing files (maybe except the ADSP)? Anyway, could
> > you please submit the required set of files to the linux-firmware repo?
>
> No, the device is not fused. So it can use firmware from linux-firmware
> repo, except ADSP and Audioreach topology.
>
> Sure, I can submit the ADSP firmware and Audioreach topology file to
> linux-firmware.> >> +
Yes, please. Also please consider adding ADSP fastrpc shell and modules
to https://github.com/linux-msm/hexagon-dsp-binaries/
> > > +&usb_2 {
> > > + dr_mode = "host";
> >
> > As Konrad has asked, please describe the onboard hub and the USB ports.
> > This will ensure that corresponding ports are correctly marked as
> > hotplug in sysfs.
> >
>
> Sure, will describe them in v4.
>
> > > +
> > > + status = "okay";
> > > +};
> > > +
> > > +&usb_2_hsphy {
> > > + status = "okay";
> > > +
> > > + vdda-pll-supply = <&vreg_l10c_0p88>;
> > > + vdda33-supply = <&vreg_l2b_3p072>;
> > > + vdda18-supply = <&vreg_l1c_1p8>;
> > > +};
> > > +
> > > +&venus {
> > > + status = "okay";
> >
> > No separate firmware?
> >
>
> The one from linux-firmware works.>
Great!
>
>
> --
> Best regards,
> Xilin Wu <sophon@...xa.com>
>
--
With best wishes
Dmitry
Powered by blists - more mailing lists