From: Alexey Romanov <avromanov@sberdevices.ru>
To: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<neil.armstrong@linaro.org>, <khilman@baylibre.com>,
<jbrunet@baylibre.com>, <martin.blumenstingl@googlemail.com>,
<linus.walleij@linaro.org>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-amlogic@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <kernel@sberdevices.ru>,
Alexey Romanov <avromanov@sberdevices.ru>
Subject: [PATCH v1 2/3] firmware: meson: use CONFIG_MESON_SM with CONFIG_ARM
Date: Wed, 22 Feb 2023 14:50:19 +0300 [thread overview]
Message-ID: <20230222115020.55867-3-avromanov@sberdevices.ru> (raw)
In-Reply-To: <20230222115020.55867-1-avromanov@sberdevices.ru>
Meson SM driver has one strong disturbing requirement.
It's size of the memory page, it should be equal to 4K.
ARM 32-bit arch always uses 4K page and doesn't support
bigger sizes. So it's not a stop factor.
Anyway, meson sm driver was tested in the meson-a1 ARM
board and it works correctly.
Signed-off-by: Alexey Romanov <avromanov@sberdevices.ru>
---
drivers/firmware/meson/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/firmware/meson/Kconfig b/drivers/firmware/meson/Kconfig
index f2fdd3756648..20303b7394fb 100644
--- a/drivers/firmware/meson/Kconfig
+++ b/drivers/firmware/meson/Kconfig
@@ -6,6 +6,6 @@ config MESON_SM
tristate "Amlogic Secure Monitor driver"
depends on ARCH_MESON || COMPILE_TEST
default y
- depends on ARM64_4K_PAGES
+ depends on ARM || ARM64_4K_PAGES
help
Say y here to enable the Amlogic secure monitor driver
--
2.38.1
next prev parent reply other threads:[~2023-02-22 11:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 11:50 [PATCH v1 0/3] Meson A1 32-bit support Alexey Romanov
2023-02-22 11:50 ` [PATCH v1 1/3] meson: pinctrl: use CONFIG_PINCTRL_A1 with CONFIG_ARM Alexey Romanov
2023-03-06 13:45 ` Linus Walleij
2023-03-06 13:49 ` neil.armstrong
2023-03-06 13:52 ` Linus Walleij
2023-02-22 11:50 ` Alexey Romanov [this message]
2023-02-22 11:50 ` [PATCH v1 3/3] arch/arm: dts: introduce meson-a1 device tree Alexey Romanov
2023-02-23 9:08 ` Krzysztof Kozlowski
2023-02-23 9:09 ` Krzysztof Kozlowski
2023-02-27 14:39 ` Dmitry Rokosov
2023-02-27 14:41 ` Krzysztof Kozlowski
2023-02-27 8:15 ` [PATCH v1 0/3] Meson A1 32-bit support neil.armstrong
2023-02-27 14:28 ` Dmitry Rokosov
2023-02-27 14:46 ` neil.armstrong
2023-02-27 16:01 ` Dmitry Rokosov
2023-02-27 14:58 ` Arnd Bergmann
2023-02-27 15:51 ` Dmitry Rokosov
2023-02-27 16:15 ` Arnd Bergmann
2023-02-27 16:37 ` Dmitry Rokosov
2023-02-27 16:38 ` Neil Armstrong
2023-02-27 16:50 ` Dmitry Rokosov
2023-02-27 18:19 ` Arnd Bergmann
2023-02-28 8:49 ` Dmitry Rokosov
2023-03-09 21:52 ` Kevin Hilman
2023-03-10 15:20 ` Dmitry Rokosov
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=20230222115020.55867-3-avromanov@sberdevices.ru \
--to=avromanov@sberdevices.ru \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=kernel@sberdevices.ru \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).