From: Stefan Wahren <stefan.wahren@i2se•com>
To: Horia Geanta <horia.geanta@nxp•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>, arm-soc <arm@kernel•org>,
Marc Gonzalez <marc.w.gonzalez@free•fr>,
LKML <linux-kernel@vger•kernel.org>,
linux-next@vger•kernel.org, Olof Johansson <olof@lixom•net>,
Linux ARM <linux-arm-kernel@lists•infradead.org>
Subject: Re: [PATCH v3 7/9] arm64: defconfig: Enable FSL_MC_BUS and FSL_MC_DPIO
Date: Tue, 18 Dec 2018 21:10:30 +0100 (CET) [thread overview]
Message-ID: <2071995319.127120.1545163830046@email.ionos.de> (raw)
In-Reply-To: <VI1PR0402MB3485A452549CF37694720A7B98BC0@VI1PR0402MB3485.eurprd04.prod.outlook.com>
Hi Horia,
> Horia Geanta <horia.geanta@nxp•com> hat am 17. Dezember 2018 um 16:33 geschrieben:
>
>
> On 12/15/2018 11:44 PM, Stefan Wahren wrote:
> > Hi,
> >
> >> Olof Johansson <olof@lixom•net> hat am 13. Dezember 2018 um 07:48 geschrieben:
> >>
> >>
> >> On Fri, Nov 09, 2018 at 06:05:24AM +0000, Horia Geanta wrote:
> >>> On 11/9/2018 3:11 AM, Marc Gonzalez wrote:
> >>>> Commit e8342cc7954e ("enable CAAM crypto engine on QorIQ DPAA2 SoCs")
> >>>> enabled CRYPTO_DEV_FSL_DPAA2_CAAM, which depends on FSL_MC_DPIO,
> >>>> which is not set. Enable FSL_MC_BUS, and build FSL_MC_DPIO and
> >>>> CRYPTO_DEV_FSL_DPAA2_CAAM as modules.
> >>>>
> >>>> Signed-off-by: Marc Gonzalez <marc.w.gonzalez@free•fr>
> >>> Reviewed-by: Horia Geantă <horia.geanta@nxp•com>
> >>
> >> I had to redo this one, and when I did I noticed that there's also an ethernet
> >> driver. Should that be enabled as well?
> >>
> >
> > this patch in next-20181214 breaks "make modules_install" for arm64/defconfig on my Ubuntu machine:
> >
> > DEPMOD 4.20.0-rc6-next-20181214
> > depmod: ERROR: Found 6 modules in dependency cycles!
> > depmod: ERROR: Cycle detected: caamalg_desc -> dpaa2_caam -> authenc
> > depmod: ERROR: Cycle detected: caamalg_desc -> dpaa2_caam -> fsl_mc_dpio
> > depmod: ERROR: Cycle detected: dpaa2_caam -> caamhash_desc -> dpaa2_caam
> > depmod: ERROR: Cycle detected: caamalg_desc -> dpaa2_caam -> caamhash_desc -> error
> > depmod: ERROR: Cycle detected: caamalg_desc -> dpaa2_caam -> caamhash_desc -> caamalg_desc
> >
> > After reverting of this patch the issue disappeared.
> >
> Seems there's a dependency cycle b/w dpaa2_caam and caam{alg,hash}_desc, as follows:
>
> A->B
> ---
> dpaa2_caam needs cnstr_* exported by caam{alg,hash}_desc
>
> B->A
> ---
> caam{alg,hash}_desc need caam_imx, caam_little_end:
> caam{hash,alg}_desc.c
> --> desc_constr.h (included for descriptors generation functions)
> --> regs.h (included for endianness helpers)
> --> extern bool caam_imx, caam_little_end
> caam_imx, caam_little_end are exported by dpaa2_caam - caamalg_qi2.c (when
> CONFIG_CRYPTO_DEV_FSL_CAAM=n)
>
> Could we drop this patch, until CAAM driver gets a proper fix (which is not
> straightforward)?
this issue still persists in 4.20.0-rc7-next-20181218. Could you please send a patch to revert this change?
Thanks Stefan
>
> Thanks,
> Horia
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists•infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
_______________________________________________
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:[~2018-12-18 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49a5d199-4eeb-a7c2-b539-13356162547f@free.fr>
[not found] ` <beb32683-fbd0-fc17-8e71-4f4f51163223@free.fr>
[not found] ` <VI1PR0402MB3485824A9FB3BC878E7B83D498C60@VI1PR0402MB3485.eurprd04.prod.outlook.com>
[not found] ` <20181213064803.kd7p7fzsegu6nhnl@localhost>
2018-12-15 21:44 ` [PATCH v3 7/9] arm64: defconfig: Enable FSL_MC_BUS and FSL_MC_DPIO Stefan Wahren
2018-12-17 15:33 ` Horia Geanta
2018-12-18 20:10 ` Stefan Wahren [this message]
2018-12-19 10:18 ` [PATCH] Revert "arm64: defconfig: Enable FSL_MC_BUS and FSL_MC_DPIO" Horia Geantă
2018-12-20 15:27 ` Arnd Bergmann
2018-12-20 20:43 ` Horia Geanta
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=2071995319.127120.1545163830046@email.ionos.de \
--to=stefan.wahren@i2se$(echo .)com \
--cc=arm@kernel$(echo .)org \
--cc=horia.geanta@nxp$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=marc.w.gonzalez@free$(echo .)fr \
--cc=olof@lixom$(echo .)net \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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