Messages in this thread | | | From | Gregory CLEMENT <> | Subject | Re: [PATCH v2 4/5] dmaengine: mv_xor: Allow selecting mv_xor for mvebu only compatible SoC | Date | Wed, 13 Apr 2016 14:24:25 +0200 |
| |
Hi Jason,
On mar., avril 12 2016, Jason Cooper <jason@lakedaemon.net> wrote:
> On Tue, Apr 12, 2016 at 08:19:17PM +0200, Gregory CLEMENT wrote: >> Armada 3700 SoC uses the mv_xor driver but don't select anymore the >> PLAT_ORION symbol. This commit extends the dependency of the mv_xor >> driver to the more modern SoCs only compatible with ARCH_MVEBU, which >> allows using it with the Armada 3700 SoC. >> >> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com> >> --- >> drivers/dma/Kconfig | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig >> index d96d87c56f2e..cdc50c2c172f 100644 >> --- a/drivers/dma/Kconfig >> +++ b/drivers/dma/Kconfig >> @@ -332,7 +332,7 @@ config MPC512X_DMA >> >> config MV_XOR >> bool "Marvell XOR engine support" >> - depends on PLAT_ORION >> + depends on PLAT_ORION || ARCH_MVEBU > > || COMPILE_TEST ?
OK and I've just test that it can be compiled on x86 without error or warning. I am going to send a v3 with this modification.
Thanks,
Gregory
> > thx, > > Jason.
-- Gregory Clement, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
| |