From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Jon Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] dt-bindings: memory: Add Tegra210 memory controller bindings
Date: Sat, 18 Dec 2021 11:59:26 +0100 [thread overview]
Message-ID: <d64330da-3ced-b37e-4bc9-ba7556822f7d@canonical.com> (raw)
In-Reply-To: <20211217165919.2700920-2-thierry.reding@gmail.com>
On 17/12/2021 17:59, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Document the bindings for the memory controller found on Tegra210 SoCs.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../nvidia,tegra210-mc.yaml | 77 +++++++++++++++++++
> 1 file changed, 77 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra210-mc.yaml
>
> diff --git a/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra210-mc.yaml b/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra210-mc.yaml
> new file mode 100644
> index 000000000000..ef21c11052e3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra210-mc.yaml
> @@ -0,0 +1,77 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/memory-controllers/nvidia,tegra210-mc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NVIDIA Tegra210 SoC Memory Controller
> +
> +maintainers:
> + - Thierry Reding <thierry.reding@gmail.com>
> + - Jon Hunter <jonathanh@nvidia.com>
> +
> +description: |
> + The NVIDIA Tegra210 SoC features a 64 bit memory controller that is split into two 32 bit
> + channels to support LPDDR3 and LPDDR4 with x16 subpartitions. The MC handles memory requests for
> + 34-bit virtual addresses from internal clients and arbitrates among them to allocate memory
> + bandwidth.
> +
> + Up to 8 GiB of physical memory can be supported. Security features such as encryption of traffic
> + to and from DRAM via general security apertures are available for video and other secure
> + applications.
> +
> +properties:
> + $nodename:
> + pattern: "^memory-controller@[0-9a-f]+$"
> +
> + compatible:
> + items:
> + - enum:
> + - nvidia,tegra210-mc
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + items:
> + - description: module clock
> +
> + clock-names:
> + items:
> + - const: mc
> +
> + "#iommu-cells":
> + const: 1
> +
> + "#reset-cells":
> + const: 1
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> + - clock-names
> + - "#iommu-cells"
> + - "#reset-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/tegra210-car.h>
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> + mc: memory-controller@70019000 {
If there is going to be resubmit, please skip the alias. It just adds
noise. Without resubmit, I can fix it when applying.
Best regards,
Krzysztof
next prev parent reply other threads:[~2021-12-18 10:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 16:59 [PATCH 1/5] dt-bindings: memory: Document Tegra210 EMC table Thierry Reding
2021-12-17 16:59 ` [PATCH 2/5] dt-bindings: memory: Add Tegra210 memory controller bindings Thierry Reding
2021-12-18 10:59 ` Krzysztof Kozlowski [this message]
2021-12-17 16:59 ` [PATCH 3/5] dt-bindings: memory: Add Tegra114 " Thierry Reding
2021-12-18 11:02 ` Krzysztof Kozlowski
2021-12-18 18:08 ` Rob Herring
2021-12-17 16:59 ` [PATCH 4/5] dt-bindings: memory: tegra: Fix Tegra132 compatible string Thierry Reding
2021-12-18 18:08 ` Rob Herring
2022-01-04 19:13 ` Rob Herring
2021-12-17 16:59 ` [PATCH 5/5] dt-bindings: memory: tegra210: Mark EMC as cooling device Thierry Reding
2021-12-22 17:20 ` Rob Herring
2022-01-04 19:13 ` [PATCH 1/5] dt-bindings: memory: Document Tegra210 EMC table Rob Herring
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=d64330da-3ced-b37e-4bc9-ba7556822f7d@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.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 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).