public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	linux-crypto@vger.kernel.org
Cc: ch@denx.de, "Herbert Xu" <herbert@gondor.apana.org.au>,
	"Horia Geantă" <horia.geanta@nxp.com>,
	"Iuliana Prodan" <iuliana.prodan@nxp.com>
Subject: Re: [RFC][PATCH] crypto: caam - Add missing MODULE_ALIAS
Date: Thu, 16 Sep 2021 16:06:52 +0200	[thread overview]
Message-ID: <08afb147-07c7-9fbb-4a0c-8a79717b06b7@denx.de> (raw)
In-Reply-To: <441a7e2e-7ac8-5000-72e0-3793ae7e58d5@canonical.com>

On 9/16/21 3:59 PM, Krzysztof Kozlowski wrote:
> On 16/09/2021 15:41, Marek Vasut wrote:
>> Add MODULE_ALIAS for caam and caam_jr modules, so they can be auto-loaded.
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
>> Cc: Herbert Xu <herbert@gondor.apana.org.au>
>> Cc: Horia Geantă <horia.geanta@nxp.com>
>> Cc: Iuliana Prodan <iuliana.prodan@nxp.com>
>> Cc: Krzysztof Kozlowski <krzk@kernel.org>
>> ---
>>   drivers/crypto/caam/ctrl.c | 1 +
>>   drivers/crypto/caam/jr.c   | 1 +
>>   2 files changed, 2 insertions(+)
>>
> 
> Since you marked it as RFC, let me share a comment - would be nice to
> see here explanation why do you need module alias.
> 
> Drivers usually do not need module alias to be auto-loaded, unless the
> subsystem/bus reports different alias than one used for binding. Since
> the CAAM can bind only via OF, I wonder what is really missing here. Is
> it a MFD child (it's one of cases this can happen)?

I noticed the CAAM is not being auto-loaded on boot, and then I noticed 
the MODULE_ALIAS fixes cropping up in the kernel log, but I couldn't 
find a good documentation for that MODULE_ALIAS. So I was hoping to get 
a feedback on it.

  reply	other threads:[~2021-09-16 14:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16 13:41 [RFC][PATCH] crypto: caam - Add missing MODULE_ALIAS Marek Vasut
2021-09-16 13:59 ` Krzysztof Kozlowski
2021-09-16 14:06   ` Marek Vasut [this message]
2021-09-16 14:22     ` Krzysztof Kozlowski
2021-09-17  9:51     ` Horia Geantă
2021-09-17 10:33       ` Krzysztof Kozlowski
2021-09-17 14:44         ` Horia Geantă
2021-09-17 16:21           ` Krzysztof Kozlowski
2021-09-17 17:30             ` Krzysztof Kozlowski
2021-09-20 13:43               ` Marek Vasut
2021-09-20 16:09                 ` Claudius Heine
2021-09-20 16:16                   ` Krzysztof Kozlowski
2021-09-21 11:08                   ` Fabio Estevam
2021-09-21 11:19                     ` Claudius Heine

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=08afb147-07c7-9fbb-4a0c-8a79717b06b7@denx.de \
    --to=marex@denx.de \
    --cc=ch@denx.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=horia.geanta@nxp.com \
    --cc=iuliana.prodan@nxp.com \
    --cc=krzysztof.kozlowski@canonical.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