From: Leonard Crestez <leonard.crestez@nxp.com>
To: Fabio Estevam <fabio.estevam@nxp.com>, Shawn Guo <shawnguo@kernel.org>
Cc: Marek Vasut <marek.vasut@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Horia Geanta <horia.geanta@nxp.com>,
Franck Lenormand <franck.lenormand@nxp.com>,
Aymen Sghaier <aymen.sghaier@nxp.com>,
"David S . Miller " <davem@davemloft.net>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] Port mxs-dcp to 6ull and 6sll
Date: Tue, 2 Oct 2018 19:18:21 +0000 [thread overview]
Message-ID: <cover.1538507155.git.leonard.crestez@nxp.com> (raw)
The only important difference relative to 6sl is that explicit clock
enabling is required.
The driver currently doesn't even probe on 6sl, a separate series was
posted to deal with the crypto functionality, those might take a while:
https://lkml.org/lkml/2018/10/2/1355
Since the functionality issues are not SOC-specific it seems reasonable
to deal with porting separately.
Leonard Crestez (3):
dt-bindings: crypto: Mention clocks for mxs-dcp
crypto: mxs-dcp - Add support for dcp clk
ARM: dts: imx6ull: Add dcp node
.../devicetree/bindings/crypto/fsl-dcp.txt | 2 ++
arch/arm/boot/dts/imx6ull.dtsi | 10 ++++++++++
drivers/crypto/mxs-dcp.c | 18 ++++++++++++++++++
3 files changed, 30 insertions(+)
--
2.17.1
next reply other threads:[~2018-10-02 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 19:18 Leonard Crestez [this message]
2018-10-02 19:18 ` [PATCH 1/3] dt-bindings: crypto: Mention clocks for mxs-dcp Leonard Crestez
2018-10-08 0:36 ` Shawn Guo
2018-10-02 19:18 ` [PATCH 2/3] crypto: mxs-dcp - Add support for dcp clk Leonard Crestez
2018-10-02 19:18 ` [PATCH 3/3] ARM: dts: imx6ull: Add dcp node Leonard Crestez
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=cover.1538507155.git.leonard.crestez@nxp.com \
--to=leonard.crestez@nxp.com \
--cc=aymen.sghaier@nxp.com \
--cc=davem@davemloft.net \
--cc=fabio.estevam@nxp.com \
--cc=franck.lenormand@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=shawnguo@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).