From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Alex Elder <elder@linaro.org>
Cc: robh+dt@kernel.org, davem@davemloft.net, evgreen@chromium.org,
subashab@codeaurora.org, cpratapa@codeaurora.org,
agross@kernel.org, devicetree@vger.kernel.org,
netdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/4] dt-bindings: net: add IPA iommus property
Date: Mon, 4 May 2020 11:30:10 -0700 [thread overview]
Message-ID: <20200504183010.GD20625@builder.lan> (raw)
In-Reply-To: <20200504175859.22606-2-elder@linaro.org>
On Mon 04 May 10:58 PDT 2020, Alex Elder wrote:
> The IPA accesses "IMEM" and main system memory through an SMMU, so
> its DT node requires an iommus property to define range of stream IDs
> it uses.
>
> Signed-off-by: Alex Elder <elder@linaro.org>
> ---
> Documentation/devicetree/bindings/net/qcom,ipa.yaml | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/net/qcom,ipa.yaml b/Documentation/devicetree/bindings/net/qcom,ipa.yaml
> index 140f15245654..7b749fc04c32 100644
> --- a/Documentation/devicetree/bindings/net/qcom,ipa.yaml
> +++ b/Documentation/devicetree/bindings/net/qcom,ipa.yaml
> @@ -20,7 +20,10 @@ description:
> The GSI is an integral part of the IPA, but it is logically isolated
> and has a distinct interrupt and a separately-defined address space.
>
> - See also soc/qcom/qcom,smp2p.txt and interconnect/interconnect.txt.
> + See also soc/qcom/qcom,smp2p.txt and interconnect/interconnect.txt. See
> + iommu/iommu.txt and iommu/arm,smmu.yaml for more information about SMMU
> + bindings.
> +
>
> - |
> -------- ---------
> @@ -54,6 +57,9 @@ properties:
> - const: ipa-shared
> - const: gsi
>
> + iommus:
> + maxItems: 1
> +
> clocks:
> maxItems: 1
>
> @@ -126,6 +132,7 @@ properties:
>
> required:
> - compatible
> + - iommus
This technically "breaks" backwards compatibility, but the binding is
rather new and in limited use, so I think we should do this.
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Regards,
Bjorn
> - reg
> - clocks
> - interrupts
> @@ -164,6 +171,7 @@ examples:
> modem-init;
> modem-remoteproc = <&mss_pil>;
>
> + iommus = <&apps_smmu 0x720 0x3>;
> reg = <0 0x1e40000 0 0x7000>,
> <0 0x1e47000 0 0x2000>,
> <0 0x1e04000 0 0x2c000>;
> --
> 2.20.1
>
next prev parent reply other threads:[~2020-05-04 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 17:58 [PATCH net-next v2 0/4] net: ipa: I/O map SMEM and IMEM Alex Elder
2020-05-04 17:58 ` [PATCH net-next v2 1/4] dt-bindings: net: add IPA iommus property Alex Elder
2020-05-04 18:30 ` Bjorn Andersson [this message]
2020-05-04 18:52 ` Rob Herring
2020-05-04 17:58 ` [PATCH net-next v2 2/4] net: ipa: redefine struct ipa_mem_data Alex Elder
2020-05-04 18:31 ` Bjorn Andersson
2020-05-04 17:58 ` [PATCH net-next v2 3/4] net: ipa: define IMEM memory region for IPA Alex Elder
2020-05-04 18:28 ` Bjorn Andersson
2020-05-04 17:58 ` [PATCH net-next v2 4/4] net: ipa: define SMEM " Alex Elder
2020-05-04 18:27 ` [PATCH net-next v2 0/4] net: ipa: I/O map SMEM and IMEM David Miller
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=20200504183010.GD20625@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=elder@linaro.org \
--cc=evgreen@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=subashab@codeaurora.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;
as well as URLs for NNTP newsgroup(s).