From: Joerg Roedel <joro@8bytes.org>
To: Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: andy.gross@linaro.org, will.deacon@arm.com, robin.murphy@arm.com,
bjorn.andersson@linaro.org, iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org, david.brown@linaro.org,
tfiga@chromium.org, swboyd@chromium.org,
linux-kernel@vger.kernel.org, robdclark@gmail.com
Subject: Re: [PATCH v2 0/4] Qcom smmu-500 TLB invalidation errata for sdm845
Date: Tue, 25 Sep 2018 14:09:34 +0200 [thread overview]
Message-ID: <20180925120933.54xd72sv65d63tkl@8bytes.org> (raw)
In-Reply-To: <20180910062551.28175-1-vivek.gautam@codeaurora.org>
On Mon, Sep 10, 2018 at 11:55:47AM +0530, Vivek Gautam wrote:
> Vivek Gautam (4):
> firmware: qcom_scm-64: Add atomic version of qcom_scm_call
> firmware/qcom_scm: Add atomic version of io read/write APIs
> firmware/qcom_scm: Add scm call to handle smmu errata
> iommu/arm-smmu: Add support to handle Qcom's TLBI serialization errata
>
> drivers/firmware/qcom_scm-32.c | 17 ++++
> drivers/firmware/qcom_scm-64.c | 181 +++++++++++++++++++++++++++++++----------
> drivers/firmware/qcom_scm.c | 18 ++++
> drivers/firmware/qcom_scm.h | 9 ++
> drivers/iommu/arm-smmu-regs.h | 2 +
> drivers/iommu/arm-smmu.c | 133 +++++++++++++++++++++++++++++-
> include/linux/qcom_scm.h | 6 ++
> 7 files changed, 320 insertions(+), 46 deletions(-)
Should this go through the iommu-tree? In that case I need Acked-by's
for the firmware code changes.
Regards,
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] Qcom smmu-500 TLB invalidation errata for sdm845
Date: Tue, 25 Sep 2018 14:09:34 +0200 [thread overview]
Message-ID: <20180925120933.54xd72sv65d63tkl@8bytes.org> (raw)
In-Reply-To: <20180910062551.28175-1-vivek.gautam@codeaurora.org>
On Mon, Sep 10, 2018 at 11:55:47AM +0530, Vivek Gautam wrote:
> Vivek Gautam (4):
> firmware: qcom_scm-64: Add atomic version of qcom_scm_call
> firmware/qcom_scm: Add atomic version of io read/write APIs
> firmware/qcom_scm: Add scm call to handle smmu errata
> iommu/arm-smmu: Add support to handle Qcom's TLBI serialization errata
>
> drivers/firmware/qcom_scm-32.c | 17 ++++
> drivers/firmware/qcom_scm-64.c | 181 +++++++++++++++++++++++++++++++----------
> drivers/firmware/qcom_scm.c | 18 ++++
> drivers/firmware/qcom_scm.h | 9 ++
> drivers/iommu/arm-smmu-regs.h | 2 +
> drivers/iommu/arm-smmu.c | 133 +++++++++++++++++++++++++++++-
> include/linux/qcom_scm.h | 6 ++
> 7 files changed, 320 insertions(+), 46 deletions(-)
Should this go through the iommu-tree? In that case I need Acked-by's
for the firmware code changes.
Regards,
Joerg
next prev parent reply other threads:[~2018-09-25 12:09 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 6:25 [PATCH v2 0/4] Qcom smmu-500 TLB invalidation errata for sdm845 Vivek Gautam
2018-09-10 6:25 ` Vivek Gautam
[not found] ` <20180910062551.28175-1-vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-09-10 6:25 ` [PATCH v2 1/4] firmware: qcom_scm-64: Add atomic version of qcom_scm_call Vivek Gautam
2018-09-10 6:25 ` Vivek Gautam
2018-09-10 6:25 ` Vivek Gautam
[not found] ` <20180910062551.28175-2-vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2019-03-25 21:09 ` Bjorn Andersson
2019-03-25 21:09 ` Bjorn Andersson
2019-03-25 21:09 ` Bjorn Andersson
2019-03-26 8:02 ` Vivek Gautam
2019-03-26 8:02 ` Vivek Gautam
2019-03-26 8:02 ` Vivek Gautam
2018-09-10 6:25 ` [PATCH v2 2/4] firmware/qcom_scm: Add atomic version of io read/write APIs Vivek Gautam
2018-09-10 6:25 ` Vivek Gautam
2018-09-10 6:25 ` Vivek Gautam
2019-03-25 21:09 ` Bjorn Andersson
2019-03-25 21:09 ` Bjorn Andersson
2018-09-10 6:25 ` [PATCH v2 4/4] iommu/arm-smmu: Add support to handle Qcom's TLBI serialization errata Vivek Gautam
2018-09-10 6:25 ` Vivek Gautam
2018-09-10 6:25 ` Vivek Gautam
2018-09-25 12:31 ` Robin Murphy
2018-09-25 12:31 ` Robin Murphy
[not found] ` <29fd7e9e-708b-b884-4de1-ecc141f41692-5wv7dgnIgG8@public.gmane.org>
2018-10-23 7:45 ` Vivek Gautam
2018-10-23 7:45 ` Vivek Gautam
2018-10-23 7:45 ` Vivek Gautam
2019-03-25 21:16 ` Bjorn Andersson
2019-03-25 21:16 ` Bjorn Andersson
2018-09-10 10:38 ` [PATCH v2 0/4] Qcom smmu-500 TLB invalidation errata for sdm845 Vivek Gautam
2018-09-10 10:38 ` Vivek Gautam
2018-09-10 10:38 ` Vivek Gautam
2018-09-25 5:58 ` Vivek Gautam
2018-09-25 5:58 ` Vivek Gautam
2018-09-25 5:58 ` Vivek Gautam
2018-09-10 6:25 ` [PATCH v2 3/4] firmware/qcom_scm: Add scm call to handle smmu errata Vivek Gautam
2018-09-10 6:25 ` Vivek Gautam
[not found] ` <20180910062551.28175-4-vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2019-03-25 21:10 ` Bjorn Andersson
2019-03-25 21:10 ` Bjorn Andersson
2019-03-25 21:10 ` Bjorn Andersson
2018-09-25 12:09 ` Joerg Roedel [this message]
2018-09-25 12:09 ` [PATCH v2 0/4] Qcom smmu-500 TLB invalidation errata for sdm845 Joerg Roedel
2018-09-25 16:39 ` Will Deacon
2018-09-25 16:39 ` Will Deacon
2018-09-26 6:23 ` Vivek Gautam
2018-09-26 6:23 ` Vivek Gautam
2018-09-26 6:23 ` Vivek Gautam
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=20180925120933.54xd72sv65d63tkl@8bytes.org \
--to=joro@8bytes.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=robin.murphy@arm.com \
--cc=swboyd@chromium.org \
--cc=tfiga@chromium.org \
--cc=vivek.gautam@codeaurora.org \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.