From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Will Deacon <will@kernel.org>
Cc: agross@kernel.org, Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org,
Stephen Boyd <swboyd@chromium.org>,
Vivek Gautam <vivek.gautam@codeaurora.org>,
bjorn.andersson@linaro.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Rajendra Nayak <rnayak@codeaurora.org>,
linux-arm-msm-owner@vger.kernel.org
Subject: Re: [PATCHv7 0/3] QCOM smmu-500 wait-for-safe handling for sdm845
Date: Fri, 01 Nov 2019 22:49:00 +0530 [thread overview]
Message-ID: <af7e9a14ae7512665f0cae32e08c8b06@codeaurora.org> (raw)
In-Reply-To: <20191101163136.GC3603@willie-the-truck>
On 2019-11-01 22:01, Will Deacon wrote:
> On Fri, Sep 20, 2019 at 01:34:26PM +0530, Sai Prakash Ranjan wrote:
>> Previous version of the patches are at [1]:
>>
>> QCOM's implementation of smmu-500 on sdm845 adds a hardware logic
>> called
>> wait-for-safe. This logic helps in meeting the invalidation
>> requirements
>> from 'real-time clients', such as display and camera. This
>> wait-for-safe
>> logic ensures that the invalidations happen after getting an ack from
>> these
>> devices.
>> In this patch-series we are disabling this wait-for-safe logic from
>> the
>> arm-smmu driver's probe as with this enabled the hardware tries to
>> throttle invalidations from 'non-real-time clients', such as USB and
>> UFS.
>>
>> For detailed information please refer to patch [3/4] in this series.
>> I have included the device tree patch too in this series for someone
>> who
>> would like to test out this. Here's a branch [2] that gets display on
>> MTP
>> SDM845 device.
>>
>> This patch series is inspired from downstream work to handle
>> under-performance
>> issues on real-time clients on sdm845. In downstream we add separate
>> page table
>> ops to handle TLB maintenance and toggle wait-for-safe in tlb_sync
>> call so that
>> achieve required performance for display and camera [3, 4].
>
> What's the plan for getting this merged? I'm not happy taking the
> firmware
> bits without Andy's ack, but I also think the SMMU changes should go
> via
> the IOMMU tree to avoid conflicts.
>
> Andy?
>
Bjorn maintains QCOM stuff now if I am not wrong and he has already
reviewed the firmware bits. So I'm hoping you could take all these
through IOMMU tree.
-Sai
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member
of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2019-11-01 17:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 8:04 [PATCHv7 0/3] QCOM smmu-500 wait-for-safe handling for sdm845 Sai Prakash Ranjan
2019-09-20 8:04 ` [PATCHv7 1/3] firmware: qcom_scm-64: Add atomic version of qcom_scm_call Sai Prakash Ranjan
2019-11-04 5:16 ` Andy Gross
2019-09-20 8:04 ` [PATCHv7 2/3] firmware/qcom_scm: Add scm call to handle smmu errata Sai Prakash Ranjan
2019-11-04 5:15 ` Andy Gross
2019-09-20 8:04 ` [PATCHv7 3/3] iommu: arm-smmu-impl: Add sdm845 implementation hook Sai Prakash Ranjan
2019-09-20 21:07 ` Stephen Boyd
2019-10-05 5:03 ` Bjorn Andersson
2019-11-01 16:31 ` [PATCHv7 0/3] QCOM smmu-500 wait-for-safe handling for sdm845 Will Deacon
2019-11-01 17:19 ` Sai Prakash Ranjan [this message]
2019-11-01 17:25 ` Will Deacon
2019-11-01 17:31 ` Sai Prakash Ranjan
2019-11-04 5:19 ` Andy Gross
2019-11-04 5:32 ` Sai Prakash Ranjan
2019-11-04 15:15 ` Will Deacon
2019-11-04 16:23 ` Will Deacon
2019-11-04 17:41 ` Bjorn Andersson
2019-11-05 2:29 ` Sai Prakash Ranjan
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=af7e9a14ae7512665f0cae32e08c8b06@codeaurora.org \
--to=saiprakash.ranjan@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-msm-owner@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rnayak@codeaurora.org \
--cc=robin.murphy@arm.com \
--cc=swboyd@chromium.org \
--cc=vivek.gautam@codeaurora.org \
--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