From: "Danilo Krummrich" <dakr@kernel.org>
To: "Ioana Ciornei" <ioana.ciornei@nxp.com>
Cc: <gregkh@linuxfoundation.org>, <rafael@kernel.org>,
<broonie@kernel.org>, <will@kernel.org>, <robin.murphy@arm.com>,
<joro@8bytes.org>, <robin.clark@oss.qualcomm.com>,
<hanguidong02@gmail.com>, <quic_c_gdjako@quicinc.com>,
<dmitry.baryshkov@oss.qualcomm.com>,
<driver-core@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
<linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] iommu/arm-smmu-qcom: do not register driver in probe()
Date: Thu, 22 Jan 2026 12:52:46 +0100 [thread overview]
Message-ID: <DFV3I3D5UIZP.38TNCAJWQGI3O@kernel.org> (raw)
In-Reply-To: <6oogrqe3n5sxtpdydjqo4ucwp7n3ipqoupxtekvzbnqd7dae3s@q22wc7fpbtya>
On Thu Jan 22, 2026 at 10:21 AM CET, Ioana Ciornei wrote:
> The boot lockup was visible also on the NXP LX2160ARDB. This patch fixes
> it.
Interesting, this means that qcom_smmu_impl_init() must be called on this
machine, is this expected?
> Tested-by: Ioana Ciornei <ioana.ciornei@nxp.com> #LX2160ARDB
Thanks for testing!
next prev parent reply other threads:[~2026-01-22 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 14:12 [PATCH] iommu/arm-smmu-qcom: do not register driver in probe() Danilo Krummrich
2026-01-21 14:46 ` Greg KH
2026-01-21 15:11 ` Robin Murphy
2026-01-21 15:54 ` Bjorn Andersson
2026-01-21 16:02 ` Konrad Dybcio
2026-01-21 16:05 ` Mark Brown
2026-01-22 3:03 ` Wang Jiayue
2026-01-22 8:18 ` Jörg Rödel
2026-01-22 8:37 ` Danilo Krummrich
2026-01-22 9:21 ` Ioana Ciornei
2026-01-22 11:52 ` Danilo Krummrich [this message]
2026-01-22 12:12 ` Robin Murphy
2026-01-22 14:41 ` Danilo Krummrich
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=DFV3I3D5UIZP.38TNCAJWQGI3O@kernel.org \
--to=dakr@kernel.org \
--cc=broonie@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=hanguidong02@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_c_gdjako@quicinc.com \
--cc=rafael@kernel.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/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