From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>, agross@kernel.org
Cc: andersson@kernel.org, konrad.dybcio@linaro.org, joro@8bytes.org,
will@kernel.org, robin.murphy@arm.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, robdclark@gmail.com,
linux-arm-msm@vger.kernel.org, iommu@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
marijn.suijten@somainline.org, kernel@collabora.com,
luca@z3ntu.xyz, a39.skl@gmail.com, phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH 1/7] dt-bindings: iommu: qcom,iommu: Document qcom,ctx-num property
Date: Mon, 14 Nov 2022 11:54:38 +0100 [thread overview]
Message-ID: <b01091e0-993e-5dbb-ad69-c80d253fef76@collabora.com> (raw)
In-Reply-To: <c0dca253-77a0-2a0a-8a03-2a727512eedb@linaro.org>
Il 14/11/22 09:23, Krzysztof Kozlowski ha scritto:
> On 11/11/2022 14:55, AngeloGioacchino Del Regno wrote:
>> Add a new "qcom,ctx-num" property to force an ASID number on IOMMU
>> contexts where required.
>>
>> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>> ---
>> Documentation/devicetree/bindings/iommu/qcom,iommu.txt | 1 +
>
> This is already a v2:
> https://lore.kernel.org/all/20220527212901.29268-1-konrad.dybcio@somainline.org/
>
> and your v2 was a v3...
>
I honestly didn't remember that this got sent again 5 months ago... besides,
I have to send a new version anyway because of a code fix, should I name it v3?
Regards,
Angelo
next prev parent reply other threads:[~2022-11-14 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 13:55 [PATCH 0/7] Add support for Qualcomm's legacy IOMMU v2 AngeloGioacchino Del Regno
2022-11-11 13:55 ` [PATCH 1/7] dt-bindings: iommu: qcom,iommu: Document qcom,ctx-num property AngeloGioacchino Del Regno
2022-11-14 8:23 ` Krzysztof Kozlowski
2022-11-14 10:54 ` AngeloGioacchino Del Regno [this message]
2022-11-11 13:55 ` [PATCH 2/7] iommu/qcom: Use the asid read from device-tree if specified AngeloGioacchino Del Regno
2022-11-11 13:55 ` [PATCH 3/7] iommu/qcom: Properly reset the IOMMU context AngeloGioacchino Del Regno
2022-11-11 13:55 ` [PATCH 4/7] iommu/qcom: Index contexts by asid number to allow asid 0 AngeloGioacchino Del Regno
2022-11-11 13:55 ` [PATCH 5/7] dt-bindings: iommu: qcom,iommu: Document QSMMU v2 compatibles AngeloGioacchino Del Regno
2022-11-11 13:55 ` [PATCH 6/7] iommu/qcom: Add support for QSMMUv2 and QSMMU-500 secured contexts AngeloGioacchino Del Regno
2022-11-11 13:55 ` [PATCH 7/7] dt-bindings: iommu: qcom,iommu: Document MSM8976 compatible AngeloGioacchino Del Regno
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=b01091e0-993e-5dbb-ad69-c80d253fef76@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=a39.skl@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kernel@collabora.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@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=luca@z3ntu.xyz \
--cc=marijn.suijten@somainline.org \
--cc=phone-devel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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