From: Pengyu Luo <mitltlatltl@gmail.com>
To: Icenowy Zheng <zhengxingda@iscas.ac.cn>
Cc: Pengyu Luo <mitltlatltl@gmail.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>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] arm64: dts: qcom: sc8280xp: set GPI DMA channels according to DSDT
Date: Sat, 06 Jun 2026 17:22:10 +0800 [thread overview]
Message-ID: <178073773007.397244.9871455646149843167.b4-reply@b4> (raw)
In-Reply-To: <bc4644a6c1e30a99f1ed5d967c64ba7f5da77fbc.camel@iscas.ac.cn>
On 2026-06-02 21:21:27+08:00, Icenowy Zheng wrote:
> 在 2026-06-02二的 20:53 +0800,Pengyu Luo写道:
>
> > On Tue, 02 Jun 2026 16:14:45 +0800, Icenowy Zheng
> > <zhengxingda@iscas.ac.cn> wrote:
> >
> > I don't focus on the upstream for a while, was this problem still
> > here
> > recently? Could you attach the base commit, so I can reproduce it.
>
> I tested on v7.0.10 (with some extra patches, but not related to
> sc8280xp).
>
> It seems that raid456 module will lead to the hang because improper
> usage of GPI DMA, and without it loaded it seems to be working fine.
>
> Could you check whether you have any problems with CONFIG_MD_RAID456=y
> set?
>
The magnetic keyboard (USB HID) can't be connected somehow, others are
fine, such as the spi touchscreen (not upstream yet), which utilizes
DMA definitely. My config is here https://pastebin.com/SdjuyJYk
Which device are you testing? Please attach more information if
possible.
> Thanks,
> Icenowy
next prev parent reply other threads:[~2026-06-06 9:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 8:14 [PATCH 0/6] arm64: dts: qcom: sc8280xp: set GPI DMA channels according to DSDT Icenowy Zheng
2026-06-02 8:14 ` [PATCH 1/6] arm64: dts: qcom: sc8280xp-crd: set GPI DMA channels Icenowy Zheng
2026-06-02 8:14 ` [PATCH 2/6] arm64: dts: qcom: sc8280xp-huawei-gaokun3: " Icenowy Zheng
2026-06-02 8:14 ` [PATCH 3/6] arm64: dts: qcom: sc8280xp-lenovo-thinkpad-x13s: " Icenowy Zheng
2026-06-02 8:42 ` sashiko-bot
2026-06-02 8:14 ` [PATCH 4/6] arm64: dts: qcom: sc8280xp-microsoft-arcata: " Icenowy Zheng
2026-06-02 8:14 ` [PATCH 5/6] arm64: dts: qcom: sc8280xp-microsoft-blackrock: " Icenowy Zheng
2026-06-02 8:14 ` [PATCH 6/6] arm64: dts: qcom: sc8280xp: remove GPI DMA channel masks Icenowy Zheng
2026-06-02 9:01 ` sashiko-bot
2026-06-02 12:53 ` [PATCH 0/6] arm64: dts: qcom: sc8280xp: set GPI DMA channels according to DSDT Pengyu Luo
2026-06-02 13:21 ` Icenowy Zheng
2026-06-06 9:22 ` Pengyu Luo [this message]
2026-06-06 9:28 ` Icenowy Zheng
2026-06-06 9:46 ` Pengyu Luo
2026-06-06 13:21 ` Icenowy Zheng
2026-06-06 13:51 ` Pengyu Luo
2026-06-07 8:49 ` Icenowy Zheng
2026-06-09 12:23 ` Konrad Dybcio
2026-06-09 15:54 ` Icenowy Zheng
2026-06-18 9:04 ` Konrad Dybcio
2026-06-18 9:05 ` Konrad Dybcio
2026-06-18 10:34 ` Icenowy Zheng
2026-06-19 12:27 ` Konrad Dybcio
2026-06-19 12:50 ` Icenowy Zheng
2026-06-19 13:11 ` Konrad Dybcio
2026-06-11 5:55 ` Pengyu Luo
2026-06-14 8:06 ` Pengyu Luo
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=178073773007.397244.9871455646149843167.b4-reply@b4 \
--to=mitltlatltl@gmail.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=robh@kernel.org \
--cc=zhengxingda@iscas.ac.cn \
/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