On Fri, Jul 24, 2015 at 08:14:31PM +0300, Horia Geantă wrote:
>
> Even more, not all SOC_IMX6 variants have a CAAM block.
> 
> Not sure what's better:
> -try to exactly indicate the HW that has the IP
> -only name the arch / SoC (provided compilation passes), and then depend
> on defconfig and/or device tree (and possibly boot loader dynamically
> fixing the DT)
> 
> For e.g. Sahara crypto driver also depends on ARCH_MXC and it's not
> available on all i.MX SoCs.

Kconfig entry dependencies do not have to guarantee the existence
of the device.  It only has to guarantee the ability to compile the
code.

Cheers,
-- 
Email: Herbert Xu <herb...@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to