linux-kernel - Run-time dependencies for STE Modem remoteproc driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140721181507.5a6d3b2c@endymion.delvare>
Date:	Mon, 21 Jul 2014 18:15:07 +0200
From:	Jean Delvare <jdelvare@...e.de>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Dmitry Tarnyagin <dmitry.tarnyagin@...kless.no>,
	Ohad Ben-Cohen <ohad@...ery.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Sjur Brandeland <sjur.brandeland@...ricsson.com>
Subject: Run-time dependencies for STE Modem remoteproc driver

Hi all,

While other remoteproc drivers have proper platform dependencies set
(OMAP_REMOTEPROC depends on ARCH_OMAP4 || SOC_OMAP5, DA8XX_REMOTEPROC
depends on ARCH_DAVINCI_DA8XX), STE_MODEM_RPROC has no such
dependencies. So the driver is presented on all architectures and can
be enabled even on platforms where it makes no sense.

Could we please add run-time dependencies so that the driver can only
be selected where it makes sense? We can always add || COMPILE_TEST to
allow build-testing everywhere.

This brings the question: on which architectures / platforms is the STE
Modem remoteproc driver needed?

Thanks,
-- 
Jean Delvare
SUSE L3 Support
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/