From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Vinod Koul <vinod.koul@intel.com>,
dmaengine@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Nadav Haklai <nadavh@marvell.com>,
Lior Amsalem <alior@marvell.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Romain Perier <romain.perier@free-electrons.com>,
Omri Itach <omrii@marvell.com>, Marcin Wojtas <mw@semihalf.com>
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 [thread overview]
Message-ID: <874mb51yti.fsf@free-electrons.com> (raw)
In-Reply-To: <20160412183536.GJ27057@io.lakedaemon.net> (Jason Cooper's message of "Tue, 12 Apr 2016 18:35:36 +0000")
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
next prev parent reply other threads:[~2016-04-13 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 18:19 [PATCH v2 0/5] Add XOR engine support to Armada 3700 SoC (ARM64) Gregory CLEMENT
2016-04-12 18:19 ` [PATCH v2 1/5] dmaengine: mv_xor: make the code 64 bits compliant Gregory CLEMENT
2016-04-12 18:19 ` [PATCH v2 2/5] dmaengine: mv_xor: use SoC type instead of directly the operation mode Gregory CLEMENT
2016-04-12 18:19 ` [PATCH v2 3/5] dmaengine: mv_xor: add support for Armada 3700 SoC Gregory CLEMENT
2016-04-12 18:19 ` [PATCH v2 4/5] dmaengine: mv_xor: Allow selecting mv_xor for mvebu only compatible SoC Gregory CLEMENT
2016-04-12 18:35 ` Jason Cooper
2016-04-13 12:24 ` Gregory CLEMENT [this message]
2016-04-12 18:19 ` [PATCH v2 5/5] arm64: dts: marvell: add XOR node for Armada 3700 SoC Gregory CLEMENT
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=874mb51yti.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=omrii@marvell.com \
--cc=robh+dt@kernel.org \
--cc=romain.perier@free-electrons.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=vinod.koul@intel.com \
/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