From: Neil Armstrong <narmstrong@baylibre.com>
To: khilman@baylibre.com, devicetree@vger.kernel.org
Cc: linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Neil Armstrong <narmstrong@baylibre.com>
Subject: [PATCH 1/5] dt-bindings: sram: Add Amlogic SCP SRAM compatibles
Date: Thu, 26 Mar 2020 17:59:54 +0100 [thread overview]
Message-ID: <20200326165958.19274-2-narmstrong@baylibre.com> (raw)
In-Reply-To: <20200326165958.19274-1-narmstrong@baylibre.com>
Add compatibles for the Amlogic SCP SRAM memory zones.
Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
---
Documentation/devicetree/bindings/sram/sram.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/sram/sram.yaml b/Documentation/devicetree/bindings/sram/sram.yaml
index 7b83cc6c9bfa..0aea3d239a48 100644
--- a/Documentation/devicetree/bindings/sram/sram.yaml
+++ b/Documentation/devicetree/bindings/sram/sram.yaml
@@ -73,6 +73,8 @@ patternProperties:
- allwinner,sun50i-a64-sram-c
- amlogic,meson8-smp-sram
- amlogic,meson8b-smp-sram
+ - amlogic,meson-gxbb-scp-shmem
+ - amlogic,meson-axg-scp-shmem
- renesas,smp-sram
- rockchip,rk3066-smp-sram
- samsung,exynos4210-sysram
--
2.22.0
next prev parent reply other threads:[~2020-03-26 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 16:59 [PATCH 0/5] arm64: dts: meson: dtbs_checks fixups Neil Armstrong
2020-03-26 16:59 ` Neil Armstrong [this message]
2020-04-10 16:37 ` [PATCH 1/5] dt-bindings: sram: Add Amlogic SCP SRAM compatibles Rob Herring
2020-03-26 16:59 ` [PATCH 2/5] arm64: dts: meson: fixup SCP sram nodes Neil Armstrong
2020-03-26 16:59 ` [PATCH 3/5] arm64: dts: meson-g12b-ugoos-am6: fix board compatible Neil Armstrong
2020-03-26 16:59 ` [PATCH 4/5] arm64: dts: meson-gxbb-kii-pro: " Neil Armstrong
2020-03-26 16:59 ` [PATCH 5/5] arm64: dts: meson: fix leds subnodes name Neil Armstrong
2020-04-29 18:25 ` [PATCH 0/5] arm64: dts: meson: dtbs_checks fixups Kevin Hilman
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=20200326165958.19274-2-narmstrong@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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