All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-crypto@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"David S . Miller" <davem@davemloft.net>,
	Krzysztof Halasa <khalasa@piap.pl>,
	devicetree@vger.kernel.org, Imre Kaloz <kaloz@openwrt.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Corentin Labbe <clabbe@baylibre.com>
Subject: Re: [PATCH 2/3 v4] crypto: ixp4xx: Add DT bindings
Date: Wed, 2 Jun 2021 13:52:42 -0500	[thread overview]
Message-ID: <20210602185242.GA3768191@robh.at.kernel.org> (raw)
In-Reply-To: <20210525084846.1114575-1-linus.walleij@linaro.org>

On Tue, 25 May 2021 10:48:46 +0200, Linus Walleij wrote:
> This adds device tree bindings for the ixp4xx crypto engine.
> 
> Cc: Corentin Labbe <clabbe@baylibre.com>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v3->v4:
> - Revert back to the phandle to the NPE with the instance
>   in the cell as in v1. Use intel,npe-handle just like
>   the ethernet driver does.
> - Drop the other changes related to using an u32 or reg
>   and revert back to v1.
> - Keep the other useful stuff from v2 and v3.
> ChangeLog v2->v3:
> - Use the reg property to set the NPE instance number for
>   the crypto engine.
> - Add address-cells and size-cells to the NPE bindings
>   consequently.
> - Use a patternProperty to match the cryto engine child
>   "crypto@N".
> - Define as crypto@2 in the example.
> - Describe the usage of the queue instance cell for the
>   queue manager phandles.
> ChangeLog v1->v2:
> - Drop the phandle to self, just add an NPE instance number
>   instead.
> - Add the crypto node to the NPE binding.
> - Move the example over to the NPE binding where it appears
>   in context.
> ---
>  .../bindings/crypto/intel,ixp4xx-crypto.yaml  | 47 +++++++++++++++++++
>  ...ntel,ixp4xx-network-processing-engine.yaml | 22 +++++++--
>  2 files changed, 65 insertions(+), 4 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/crypto/intel,ixp4xx-crypto.yaml
> 

Reviewed-by: Rob Herring <robh@kernel.org>

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-crypto@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"David S . Miller" <davem@davemloft.net>,
	Krzysztof Halasa <khalasa@piap.pl>,
	devicetree@vger.kernel.org, Imre Kaloz <kaloz@openwrt.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Corentin Labbe <clabbe@baylibre.com>
Subject: Re: [PATCH 2/3 v4] crypto: ixp4xx: Add DT bindings
Date: Wed, 2 Jun 2021 13:52:42 -0500	[thread overview]
Message-ID: <20210602185242.GA3768191@robh.at.kernel.org> (raw)
In-Reply-To: <20210525084846.1114575-1-linus.walleij@linaro.org>

On Tue, 25 May 2021 10:48:46 +0200, Linus Walleij wrote:
> This adds device tree bindings for the ixp4xx crypto engine.
> 
> Cc: Corentin Labbe <clabbe@baylibre.com>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v3->v4:
> - Revert back to the phandle to the NPE with the instance
>   in the cell as in v1. Use intel,npe-handle just like
>   the ethernet driver does.
> - Drop the other changes related to using an u32 or reg
>   and revert back to v1.
> - Keep the other useful stuff from v2 and v3.
> ChangeLog v2->v3:
> - Use the reg property to set the NPE instance number for
>   the crypto engine.
> - Add address-cells and size-cells to the NPE bindings
>   consequently.
> - Use a patternProperty to match the cryto engine child
>   "crypto@N".
> - Define as crypto@2 in the example.
> - Describe the usage of the queue instance cell for the
>   queue manager phandles.
> ChangeLog v1->v2:
> - Drop the phandle to self, just add an NPE instance number
>   instead.
> - Add the crypto node to the NPE binding.
> - Move the example over to the NPE binding where it appears
>   in context.
> ---
>  .../bindings/crypto/intel,ixp4xx-crypto.yaml  | 47 +++++++++++++++++++
>  ...ntel,ixp4xx-network-processing-engine.yaml | 22 +++++++--
>  2 files changed, 65 insertions(+), 4 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/crypto/intel,ixp4xx-crypto.yaml
> 

Reviewed-by: Rob Herring <robh@kernel.org>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-06-02 18:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25  8:48 [PATCH 2/3 v4] crypto: ixp4xx: Add DT bindings Linus Walleij
2021-05-25  8:48 ` Linus Walleij
2021-06-02 18:52 ` Rob Herring [this message]
2021-06-02 18:52   ` Rob Herring

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=20210602185242.GA3768191@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=arnd@arndb.de \
    --cc=clabbe@baylibre.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kaloz@openwrt.org \
    --cc=khalasa@piap.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.