From: Chris Spencer <spencercw@gmail.com>
To: "Horia Geantă" <horia.geanta@nxp.com>,
"Aymen Sghaier" <aymen.sghaier@nxp.com>
Cc: linux-crypto@vger.kernel.org,
Chris Spencer <christopher.spencer@sea.co.uk>
Subject: Re: [RFC 1/4] crypto: caam - fix detection of i.MX8 SoC
Date: Mon, 25 Feb 2019 07:50:53 +0000 [thread overview]
Message-ID: <CAGUNXRSKXZdw_M-4RCyckVS_-MxfWe+H6Cw+kPU6=DorxZWmTg@mail.gmail.com> (raw)
In-Reply-To: <20190222100613.2290-2-christopher.spencer@sea.co.uk>
On Fri, 22 Feb 2019 at 10:07, <spencercw@gmail.com> wrote:
> From: Chris Spencer <christopher.spencer@sea.co.uk>
>
> The i.MX8 does not currently have an SoC driver so soc_device_match does
> not recognise it. Check the machine compatible instead.
>
> Signed-off-by: Chris Spencer <christopher.spencer@sea.co.uk>
Turns out there is already an outstanding patch to add the SoC driver
[1], so I will drop this one from the next version.
Chris
[1] https://lore.kernel.org/patchwork/patch/1038272/
next prev parent reply other threads:[~2019-02-25 7:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 10:06 [RFC 0/4] crypto: caam - Add i.MX8MQ support spencercw
2019-02-22 10:06 ` [RFC 1/4] crypto: caam - fix detection of i.MX8 SoC spencercw
2019-02-25 7:50 ` Chris Spencer [this message]
2019-02-22 10:06 ` [RFC 2/4] crypto: caam - do not initialise clocks on the i.MX8 spencercw
2019-02-22 10:06 ` [RFC 3/4] crypto: caam - correct DMA address size for " spencercw
2019-02-22 10:06 ` [RFC 4/4] crypto: caam - use job ring for RNG instantiation instead of DECO spencercw
2019-02-25 14:22 ` Horia Geanta
2019-02-25 14:36 ` Chris Spencer
2019-02-26 14:53 ` Horia Geanta
2019-02-26 16:24 ` Chris Spencer
2019-02-28 11:33 ` Chris Spencer
2019-03-04 18:13 ` Horia Geanta
2019-03-05 8:54 ` Chris Spencer
2019-02-25 14:03 ` [RFC 0/4] crypto: caam - Add i.MX8MQ support Horia Geanta
2019-02-25 14:17 ` Chris Spencer
2019-02-25 19:28 ` Chris Spencer
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='CAGUNXRSKXZdw_M-4RCyckVS_-MxfWe+H6Cw+kPU6=DorxZWmTg@mail.gmail.com' \
--to=spencercw@gmail.com \
--cc=aymen.sghaier@nxp.com \
--cc=christopher.spencer@sea.co.uk \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@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;
as well as URLs for NNTP newsgroup(s).