public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Antoine Tenart <antoine.tenart@free-electrons.com>
To: stable@vger.kernel.org
Cc: Antoine Tenart <antoine.tenart@free-electrons.com>,
	gregory.clement@free-electrons.com,
	thomas.petazzoni@free-electrons.com,
	miquel.raynal@free-electrons.com
Subject: Re: [PATCH] arm64: dts: marvell: mark the cp110 crypto engine as dma coherent
Date: Mon, 13 Nov 2017 16:55:53 +0100	[thread overview]
Message-ID: <20171113155553.GA25491@kwain> (raw)
In-Reply-To: <20171113155122.12710-1-antoine.tenart@free-electrons.com>

Hi,

On Mon, Nov 13, 2017 at 04:51:22PM +0100, Antoine Tenart wrote:
> commit ec0aef9881d18aa781268ec9cba8eba5b202f5b4 upstream.
> 
> The crypto engines found on the cp110 master and slave are dma coherent.
> This patch adds the relevant property to their dt nodes.
> 
> Cc: stable@vger.kernel.org # v4.12+
> Fixes: 973020fd9498 ("arm64: marvell: dts: add crypto engine description for 7k/8k")
> Signed-off-by: Antoine Tenart <antoine.tenart@free-electrons.com>
> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
> Signed-off-by: Antoine Tenart <antoine.tenart@free-electrons.com>

There is a duplicate signature. Can you remove it when applying or do
you guys want a new patch?

Antoine

> ---
> 
> Hi,
> 
> This patch did not apply to the 4.12-stable tree. Since the original
> patch made it to Linus tree, this is a version which applies nicely
> to the 4.12-stable tree.
> 
> Thanks,
> Antoine
> 
>  arch/arm64/boot/dts/marvell/armada-cp110-master.dtsi | 1 +
>  arch/arm64/boot/dts/marvell/armada-cp110-slave.dtsi  | 1 +
>  2 files changed, 2 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/marvell/armada-cp110-master.dtsi b/arch/arm64/boot/dts/marvell/armada-cp110-master.dtsi
> index b4bc42ece754..4e81130ae84a 100644
> --- a/arch/arm64/boot/dts/marvell/armada-cp110-master.dtsi
> +++ b/arch/arm64/boot/dts/marvell/armada-cp110-master.dtsi
> @@ -240,6 +240,7 @@
>  				interrupt-names = "mem", "ring0", "ring1",
>  				"ring2", "ring3", "eip";
>  				clocks = <&cpm_syscon0 1 26>;
> +				dma-coherent;
>  				status = "disabled";
>  			};
>  		};
> diff --git a/arch/arm64/boot/dts/marvell/armada-cp110-slave.dtsi b/arch/arm64/boot/dts/marvell/armada-cp110-slave.dtsi
> index 6e2058847ddc..b987565107f3 100644
> --- a/arch/arm64/boot/dts/marvell/armada-cp110-slave.dtsi
> +++ b/arch/arm64/boot/dts/marvell/armada-cp110-slave.dtsi
> @@ -230,6 +230,7 @@
>  				interrupt-names = "mem", "ring0", "ring1",
>  						  "ring2", "ring3", "eip";
>  				clocks = <&cps_syscon0 1 26>;
> +				dma-coherent;
>  				status = "disabled";
>  			};
>  		};
> -- 
> 2.14.3
> 

-- 
Antoine T�nart, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-11-13 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13 15:51 [PATCH] arm64: dts: marvell: mark the cp110 crypto engine as dma coherent Antoine Tenart
2017-11-13 15:55 ` Antoine Tenart [this message]
2017-11-13 16:12 ` Greg KH
2017-11-13 16:41   ` Antoine Tenart

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=20171113155553.GA25491@kwain \
    --to=antoine.tenart@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=miquel.raynal@free-electrons.com \
    --cc=stable@vger.kernel.org \
    --cc=thomas.petazzoni@free-electrons.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