From: "Horia Geantă" <horia.geanta@nxp.com>
To: Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Matt Mackall <mpm@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: devicetree@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Iuliana Prodan <iuliana.prodan@nxp.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Marco Felsch <m.felsch@pengutronix.de>,
linux-kernel@vger.kernel.org,
Franck Lenormand <franck.lenormand@nxp.com>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Martin Kaiser <martin@kaiser.cx>,
Silvano Di Ninno <silvano.dininno@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org
Subject: [PATCH v4 5/5] hwrng: imx-rngc: enable driver for i.MX6
Date: Wed, 15 Jul 2020 18:26:04 +0300 [thread overview]
Message-ID: <20200715152604.10407-6-horia.geanta@nxp.com> (raw)
In-Reply-To: <20200715152604.10407-1-horia.geanta@nxp.com>
i.MX6 SL, SLL, ULL, ULZ SoCs have an RNGB block.
Since imx-rngc driver supports also rngb,
let's enable it for these SoCs too.
Signed-off-by: Horia Geantă <horia.geanta@nxp.com>
Reviewed-by: Martin Kaiser <martin@kaiser.cx>
Reviewed-by: Marco Felsch <m.felsch@pengutronix.de>
---
drivers/char/hw_random/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/char/hw_random/Kconfig b/drivers/char/hw_random/Kconfig
index 8478eb757f3c..98f95a09ce55 100644
--- a/drivers/char/hw_random/Kconfig
+++ b/drivers/char/hw_random/Kconfig
@@ -255,7 +255,7 @@ config HW_RANDOM_MXC_RNGA
config HW_RANDOM_IMX_RNGC
tristate "Freescale i.MX RNGC Random Number Generator"
depends on HAS_IOMEM && HAVE_CLK
- depends on SOC_IMX25 || COMPILE_TEST
+ depends on SOC_IMX25 || SOC_IMX6SL || SOC_IMX6SLL || SOC_IMX6UL || COMPILE_TEST
default HW_RANDOM
help
This driver provides kernel-side support for the Random Number
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-15 15:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 15:25 [PATCH v4 0/5] hwrng: add support for i.MX6 rngb Horia Geantă
2020-07-15 15:26 ` [PATCH v4 1/5] dt-bindings: rng: add RNGB compatibles for i.MX6 SoCs Horia Geantă
2020-07-15 15:26 ` [PATCH v4 2/5] ARM: dts: imx6sl: fix rng node Horia Geantă
2020-07-15 15:26 ` [PATCH v4 3/5] ARM: dts: imx6sll: add rng Horia Geantă
2020-07-15 15:26 ` [PATCH v4 4/5] ARM: dts: imx6ull: " Horia Geantă
2021-08-17 15:39 ` Frieder Schrempf
2021-08-17 17:38 ` Frieder Schrempf
2020-07-15 15:26 ` Horia Geantă [this message]
2020-07-23 7:57 ` [PATCH v4 0/5] hwrng: add support for i.MX6 rngb Herbert Xu
2020-08-17 8:07 ` Shawn Guo
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=20200715152604.10407-6-horia.geanta@nxp.com \
--to=horia.geanta@nxp.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=franck.lenormand@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=iuliana.prodan@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=martin@kaiser.cx \
--cc=mpm@selenic.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=silvano.dininno@nxp.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).