From: Will Deacon <will@kernel.org>
To: lkml <linux-kernel@vger.kernel.org>,
John Stultz <john.stultz@linaro.org>
Cc: Maulik Shah <mkshah@codeaurora.org>,
Marc Zyngier <maz@kernel.org>,
Saravana Kannan <saravanak@google.com>,
Will Deacon <will@kernel.org>,
catalin.marinas@arm.com, Robin Murphy <robin.murphy@arm.com>,
Lina Iyer <ilina@codeaurora.org>,
iommu@lists.linux-foundation.org, Andy Gross <agross@kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
kernel-team@android.com
Subject: Re: [PATCH 1/2] arm-smmu-qcom: Ensure the qcom_scm driver has finished probing
Date: Mon, 23 Nov 2020 15:46:59 +0000 [thread overview]
Message-ID: <160614327473.875458.14207739459234972190.b4-ty@kernel.org> (raw)
In-Reply-To: <20201112220520.48159-1-john.stultz@linaro.org>
On Thu, 12 Nov 2020 22:05:19 +0000, John Stultz wrote:
> Robin Murphy pointed out that if the arm-smmu driver probes before
> the qcom_scm driver, we may call qcom_scm_qsmmu500_wait_safe_toggle()
> before the __scm is initialized.
>
> Now, getting this to happen is a bit contrived, as in my efforts it
> required enabling asynchronous probing for both drivers, moving the
> firmware dts node to the end of the dtsi file, as well as forcing a
> long delay in the qcom_scm_probe function.
>
> [...]
Applied only the first patch to arm64 (for-next/iommu/fixes), thanks!
[1/2] arm-smmu-qcom: Ensure the qcom_scm driver has finished probing
https://git.kernel.org/arm64/c/72b55c96f3a5
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2020-11-23 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 22:05 [RESEND][PATCH 1/2] arm-smmu-qcom: Ensure the qcom_scm driver has finished probing John Stultz
2020-11-12 22:05 ` [RESEND][PATCH 2/2] iommu: Avoid crash if iommu_group is null John Stultz
2020-11-13 14:22 ` Robin Murphy
2020-11-13 13:05 ` [RESEND][PATCH 1/2] arm-smmu-qcom: Ensure the qcom_scm driver has finished probing Robin Murphy
2020-11-23 15:46 ` Will Deacon [this message]
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=160614327473.875458.14207739459234972190.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=agross@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=ilina@codeaurora.org \
--cc=iommu@lists.linux-foundation.org \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=mkshah@codeaurora.org \
--cc=robin.murphy@arm.com \
--cc=saravanak@google.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;
as well as URLs for NNTP newsgroup(s).