From: Bibek Kumar Patro <quic_bibekkum@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <will@kernel.org>, <robin.murphy@arm.com>, <joro@8bytes.org>,
<a39.skl@gmail.com>, <konrad.dybcio@linaro.org>,
<quic_saipraka@quicinc.com>, <quic_pkondeti@quicinc.com>,
<quic_molvera@quicinc.com>,
<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>,
<qipl.kernel.upstream@quicinc.com>
Subject: Re: [PATCH 0/3] iommu/arm-smmu: introduction of ACTLR implementation for Qualcomm SoCs
Date: Mon, 6 Nov 2023 12:09:26 +0530 [thread overview]
Message-ID: <6c4bd8fd-624a-4c2f-a9a8-dfdbd8281010@quicinc.com> (raw)
In-Reply-To: <CAA8EJpqtZXNSz2-VEdQL2XTxi6GnZBkLABLe1qSUcwCbfoEHVQ@mail.gmail.com>
On 11/4/2023 4:14 AM, Dmitry Baryshkov wrote:
> On Fri, 3 Nov 2023 at 23:53, Bibek Kumar Patro
> <quic_bibekkum@quicinc.com> wrote:
>>
>> This patch series consists of three parts and covers the following:
>>
>> 1. Introducing intital set of driver changes to implement ACTLR register
>> for custom prefetcher settings in Qualcomm SoCs.
>>
>> 2. Adding ACTLR data and implementation operations for SM8550.
>>
>> 3. Re-enabling context caching for Qualcomm SoCs to retain prefetcher
>> settings during reset and runtime suspend.
>>
>> Link to discussion on RFC posted on ACTLR implementation:
>> https://lore.kernel.org/all/a01e7e60-6ead-4a9e-ba90-22a8a6bbd03f@quicinc.com/
>
> First two patches in that thread were not archived for some reason.
>
> However, as there was a previous iteration, it is suggested to include
> the changelog between RFC and v1.
>
Right, in the initial RFC sent somehow only the replies were archived.
Although the RFC patch was a WIP patch in rough state, sent to take
upstream inputs.
Will try adding the changelog in v2.
To give a context, in the RFC patch, we we're initially proposing a dt
based approach to set the actlr property, where we would piggyback on
the iommus property to store actlr value and set the property during
smmu device probe.
>>
>> Bibek Kumar Patro (3):
>> iommu/arm-smmu: introduction of ACTLR for custom prefetcher settings
>> iommu/arm-smmu: add ACTLR data and support for sm8550
>> iommu/arm-smmu: re-enable context caching in smmu reset operation
>>
>> drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 143 ++++++++++++++++++++-
>> drivers/iommu/arm/arm-smmu/arm-smmu-qcom.h | 2 +
>
> Although it is not mentioned in the MAINTAINERS file, could you please
> CC linux-arm-msm when sending v2?
>
Sure Dmitry, will take care of this and CC linux-arm-msm while sending v2.
>> drivers/iommu/arm/arm-smmu/arm-smmu.c | 5 +-
>> drivers/iommu/arm/arm-smmu/arm-smmu.h | 5 +
>> 4 files changed, 146 insertions(+), 9 deletions(-)
>>
>> --
>> 2.17.1
>>
>
>
prev parent reply other threads:[~2023-11-06 6:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 21:51 Bibek Kumar Patro
2023-11-03 21:51 ` [PATCH 1/3] iommu/arm-smmu: introduction of ACTLR for custom prefetcher settings Bibek Kumar Patro
2023-11-03 22:03 ` Dmitry Baryshkov
2023-11-06 6:12 ` Bibek Kumar Patro
2023-11-14 10:20 ` Bibek Kumar Patro
2023-11-14 10:36 ` Dmitry Baryshkov
2023-11-03 21:51 ` [PATCH 2/3] iommu/arm-smmu: add ACTLR data and support for SM8550 Bibek Kumar Patro
2023-11-03 22:01 ` Dmitry Baryshkov
2023-11-03 22:38 ` Bibek Kumar Patro
2023-11-03 22:41 ` Dmitry Baryshkov
2023-11-06 6:09 ` Bibek Kumar Patro
2023-11-06 9:05 ` Dmitry Baryshkov
2023-11-06 12:09 ` Bibek Kumar Patro
2023-11-10 9:55 ` Pratyush Brahma
2023-11-04 11:29 ` Konrad Dybcio
2023-11-06 6:26 ` Bibek Kumar Patro
2023-11-04 15:29 ` kernel test robot
2023-11-03 21:51 ` [PATCH 3/3] iommu/arm-smmu: re-enable context caching in smmu reset operation Bibek Kumar Patro
2023-11-03 21:58 ` Dmitry Baryshkov
2023-11-03 22:06 ` Bibek Kumar Patro
2023-11-03 22:23 ` Dmitry Baryshkov
2023-11-03 22:42 ` Bibek Kumar Patro
2023-11-04 11:30 ` Konrad Dybcio
2023-11-06 6:28 ` Bibek Kumar Patro
2023-11-03 22:44 ` [PATCH 0/3] iommu/arm-smmu: introduction of ACTLR implementation for Qualcomm SoCs Dmitry Baryshkov
2023-11-06 6:39 ` Bibek Kumar Patro [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=6c4bd8fd-624a-4c2f-a9a8-dfdbd8281010@quicinc.com \
--to=quic_bibekkum@quicinc.com \
--cc=a39.skl@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qipl.kernel.upstream@quicinc.com \
--cc=quic_molvera@quicinc.com \
--cc=quic_pkondeti@quicinc.com \
--cc=quic_saipraka@quicinc.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
all inboxes | Powered by JetHome®