devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Vic Wu <vic.wu@mediatek.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
	Ryder Lee <ryder.lee@mediatek.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: mediatek - remove obsolete documentation
Date: Mon, 8 Mar 2021 13:07:46 -0700	[thread overview]
Message-ID: <20210308200746.GA2870408@robh.at.kernel.org> (raw)
In-Reply-To: <20210303093950.20309-1-vic.wu@mediatek.com>

On Wed, Mar 03, 2021 at 05:39:50PM +0800, Vic Wu wrote:
> The crypto mediatek driver has been replaced by the inside-secure driver now.
> Remove DT bindings documentation and update crypto engine nodes to the mt7623.dtsi files.

Wrap lines.

> 
> Signed-off-by: Vic Wu <vic.wu@mediatek.com>
> Acked-by: Ryder Lee <ryder.lee@mediatek.com>
> ---
>  Documentation/devicetree/bindings/crypto/mediatek-crypto.txt       | 25 -------------------
>  arch/arm/boot/dts/mt7623.dtsi                 |  8 +++---
>  2 files changed, 3 insertions(+), 30 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/crypto/mediatek-crypto.txt
> 
> diff --git a/Documentation/devicetree/bindings/crypto/mediatek-crypto.txt b/Documentation/devicetree/bindings/crypto/mediatek-crypto.txt
> deleted file mode 100644
> index 450da3661cad..000000000000
> --- a/Documentation/devicetree/bindings/crypto/mediatek-crypto.txt
> +++ /dev/null
> @@ -1,25 +0,0 @@
> -MediaTek cryptographic accelerators
> -
> -Required properties:
> -- compatible: Should be "mediatek,eip97-crypto"
> -- reg: Address and length of the register set for the device
> -- interrupts: Should contain the five crypto engines interrupts in numeric
> -	order. These are global system and four descriptor rings.
> -- clocks: the clock used by the core
> -- clock-names: Must contain "cryp".
> -- power-domains: Must contain a reference to the PM domain.
> -
> -
> -Example:
> -	crypto: crypto@1b240000 {
> -		compatible = "mediatek,eip97-crypto";
> -		reg = <0 0x1b240000 0 0x20000>;
> -		interrupts = <GIC_SPI 82 IRQ_TYPE_LEVEL_LOW>,
> -			     <GIC_SPI 83 IRQ_TYPE_LEVEL_LOW>,
> -			     <GIC_SPI 84 IRQ_TYPE_LEVEL_LOW>,
> -			     <GIC_SPI 91 IRQ_TYPE_LEVEL_LOW>,
> -			     <GIC_SPI 97 IRQ_TYPE_LEVEL_LOW>;
> -		clocks = <&ethsys CLK_ETHSYS_CRYPTO>;
> -		clock-names = "cryp";
> -		power-domains = <&scpsys MT2701_POWER_DOMAIN_ETH>;
> -	};
> diff --git a/arch/arm/boot/dts/mt7623.dtsi b/arch/arm/boot/dts/mt7623.dtsi
> index aea6809500d7..25e3f3b04123 100644
> --- a/arch/arm/boot/dts/mt7623.dtsi
> +++ b/arch/arm/boot/dts/mt7623.dtsi
> @@ -949,16 +949,14 @@
>  	};
>  
>  	crypto: crypto@1b240000 {
> -		compatible = "mediatek,eip97-crypto";
> +		compatible = "inside-secure,safexcel-eip97";

Please read what the new binding says about this compatible string.

>  		reg = <0 0x1b240000 0 0x20000>;
>  		interrupts = <GIC_SPI 82 IRQ_TYPE_LEVEL_LOW>,
>  			     <GIC_SPI 83 IRQ_TYPE_LEVEL_LOW>,
>  			     <GIC_SPI 84 IRQ_TYPE_LEVEL_LOW>,
> -			     <GIC_SPI 91 IRQ_TYPE_LEVEL_LOW>,
> -			     <GIC_SPI 97 IRQ_TYPE_LEVEL_LOW>;
> +			     <GIC_SPI 91 IRQ_TYPE_LEVEL_LOW>;

Where did the extra interrupt go?

> +		interrupt-names = "ring0", "ring1", "ring2", "ring3";
>  		clocks = <&ethsys CLK_ETHSYS_CRYPTO>;
> -		clock-names = "cryp";
> -		power-domains = <&scpsys MT2701_POWER_DOMAIN_ETH>;

Suddenly the h/w is not in a power domain?

Seems to me 'mediatek,eip97-crypto' should be added to the common driver 
without having a dts change.

Rob

      reply	other threads:[~2021-03-08 20:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03  9:39 [PATCH] crypto: mediatek - remove obsolete documentation Vic Wu
2021-03-08 20:07 ` Rob Herring [this message]

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=20210308200746.GA2870408@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=ryder.lee@mediatek.com \
    --cc=vic.wu@mediatek.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;
as well as URLs for NNTP newsgroup(s).