mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bibek Kumar Patro <quic_bibekkum@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
	Rob Clark <robdclark@gmail.com>
Cc: <will@kernel.org>, <robin.murphy@arm.com>, <joro@8bytes.org>,
	<jgg@ziepe.ca>, <jsnitsel@redhat.com>, <robh@kernel.org>,
	<krzysztof.kozlowski@linaro.org>, <quic_c_gdjako@quicinc.com>,
	<dmitry.baryshkov@linaro.org>, <iommu@lists.linux.dev>,
	<linux-arm-msm@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	Rob Clark <robdclark@chromium.org>
Subject: Re: [PATCH v13 6/6] iommu/arm-smmu: add support for PRR bit setup
Date: Mon, 15 Jul 2024 16:31:28 +0530	[thread overview]
Message-ID: <bc2d6a8e-4446-4311-8745-4a4fdb8bca3f@quicinc.com> (raw)
In-Reply-To: <f4994451-9dc4-4d25-b544-49531709e76d@linaro.org>



On 7/11/2024 3:31 AM, Konrad Dybcio wrote:
> On 10.07.2024 7:01 PM, Rob Clark wrote:
>> On Tue, Jul 9, 2024 at 12:43 PM Bibek Kumar Patro
>> <quic_bibekkum@quicinc.com> wrote:
> 
> [...]
> 
>> If there is a clean break, such as all smmu-500 have PRR and all
>> smmu-v2 do not, then it would be reasonable to use the compat strings.
>> If not, I think we need a different way.
> 
> if (a reserved-memory region is passed in dt) {
> 	init_prr()
> }
> 

This would have been a straight forward way to pass as a check for PRR
support, but as I mentioned in the above thread reserved-memory region 
is not required if gfx/drm allocates the page.
So I think compatible string would be more approachable way?

Thanks & regards,
Bibek

> Konrad

  reply	other threads:[~2024-07-15 11:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28 14:04 [PATCH v13 0/6] iommu/arm-smmu: introduction of ACTLR implementation for Qualcomm SoCs Bibek Kumar Patro
2024-06-28 14:04 ` [PATCH v13 1/6] iommu/arm-smmu: re-enable context caching in smmu reset operation Bibek Kumar Patro
2024-06-28 14:04 ` [PATCH v13 2/6] iommu/arm-smmu: refactor qcom_smmu structure to include single pointer Bibek Kumar Patro
2024-06-28 14:04 ` [PATCH v13 3/6] iommu/arm-smmu: introduction of ACTLR for custom prefetcher settings Bibek Kumar Patro
2024-06-28 14:04 ` [PATCH v13 4/6] iommu/arm-smmu: add ACTLR data and support for SM8550 Bibek Kumar Patro
2024-07-01 18:34   ` Dmitry Baryshkov
2024-07-03 12:15     ` Bibek Kumar Patro
2024-07-03 13:02       ` Will Deacon
2024-07-04  9:12         ` Bibek Kumar Patro
2024-07-04 11:26           ` Dmitry Baryshkov
2024-07-04 11:23       ` Dmitry Baryshkov
2024-07-10 17:44         ` Bibek Kumar Patro
2024-06-28 14:04 ` [PATCH v13 5/6] iommu/arm-smmu: add ACTLR data and support for SC7280 Bibek Kumar Patro
2024-06-28 14:04 ` [PATCH v13 6/6] iommu/arm-smmu: add support for PRR bit setup Bibek Kumar Patro
2024-06-28 14:17   ` Rob Clark
2024-06-28 15:09     ` Bibek Kumar Patro
2024-06-28 15:44       ` Rob Clark
2024-07-01 11:00         ` Bibek Kumar Patro
2024-07-01 20:31           ` Rob Clark
2024-07-03 11:38             ` Bibek Kumar Patro
2024-07-04 14:46               ` Rob Clark
2024-07-04 15:58                 ` Rob Clark
2024-07-09 19:42                   ` Bibek Kumar Patro
2024-07-10 17:01                     ` Rob Clark
2024-07-10 22:01                       ` Konrad Dybcio
2024-07-15 11:01                         ` Bibek Kumar Patro [this message]
2024-07-15 10:59                       ` Bibek Kumar Patro
2024-07-15 20:07                         ` Rob Clark
2024-07-16 12:14                           ` Konrad Dybcio
2024-07-19 12:59                             ` Bibek Kumar Patro
2024-07-17 10:27                           ` Bibek Kumar Patro
2024-07-17 15:00                             ` Rob Clark
2024-07-19 12:38                               ` Bibek Kumar Patro

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=bc2d6a8e-4446-4311-8745-4a4fdb8bca3f@quicinc.com \
    --to=quic_bibekkum@quicinc.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=joro@8bytes.org \
    --cc=jsnitsel@redhat.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski@linaro.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=robdclark@chromium.org \
    --cc=robdclark@gmail.com \
    --cc=robh@kernel.org \
    --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
all inboxes | Powered by JetHome®