From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxime Ripard Subject: Re: [PATCH 1/3] dt-bindings: dma: Add YAML schemas for the generic DMA bindings Date: Sat, 20 Jul 2019 11:24:21 +0200 Message-ID: <20190720092421.bqbsyrk3atejqgsf@flea> References: <20190720064123.15411-1-maxime.ripard@bootlin.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2476322633009275244==" Return-path: In-Reply-To: <20190720064123.15411-1-maxime.ripard@bootlin.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Mark Rutland , Rob Herring , Frank Rowand , Vinod Koul Cc: dmaengine@vger.kernel.org, devicetree@vger.kernel.org, Chen-Yu Tsai , linux-arm-kernel@lists.infradead.org, Peter Ujfalusi List-Id: devicetree@vger.kernel.org --===============2476322633009275244== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="s3wrpdsnzbasx2vv" Content-Disposition: inline --s3wrpdsnzbasx2vv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Jul 20, 2019 at 08:41:21AM +0200, Maxime Ripard wrote: > The DMA controllers and consumers have a bunch of generic properties that > are needed in a device tree. Add a YAML schemas for those. > > Signed-off-by: Maxime Ripard > > --- > > Changes from v1: > - Dropped the dma consumer schemas > - Fixed the node name of the examples > - Enhanced a bit the description for dma-requests in case of a router > - Split the bindings in two to handle the router and controller case > separately > - Made #dma-cells required > --- > .../devicetree/bindings/dma/dma-common.yaml | 43 +++++++ > .../bindings/dma/dma-controller.yaml | 35 ++++++ > .../devicetree/bindings/dma/dma-router.yaml | 50 ++++++++ > Documentation/devicetree/bindings/dma/dma.txt | 114 +----------------- > 4 files changed, 129 insertions(+), 113 deletions(-) > create mode 100644 Documentation/devicetree/bindings/dma/dma-common.yaml > create mode 100644 Documentation/devicetree/bindings/dma/dma-controller.yaml > create mode 100644 Documentation/devicetree/bindings/dma/dma-router.yaml > > diff --git a/Documentation/devicetree/bindings/dma/dma-common.yaml b/Documentation/devicetree/bindings/dma/dma-common.yaml > new file mode 100644 > index 000000000000..422fd6c8b0ce > --- /dev/null > +++ b/Documentation/devicetree/bindings/dma/dma-common.yaml > @@ -0,0 +1,43 @@ > +# SPDX-License-Identifier: GPL-2.0 > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/dma/dma-common.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: DMA Engine Generic Binding > + > +maintainers: > + - Vinod Koul > + > +description: > + Generic binding to provide a way for a driver using DMA Engine to > + retrieve the DMA request or channel information that goes from a > + hardware device to a DMA controller. > + > +properties: > + "#dma-cells": > + minimum: 1 > + # Should be enough > + maximum: 255 > + description: > + Used to provide DMA controller specific information. We need a select statement here, otherwise it will try to validate every node and report dma-cells as missing. I'll send a v3. Maxime -- Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com --s3wrpdsnzbasx2vv Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCXTLdvgAKCRDj7w1vZxhR xdEIAP9SpwDUkxDQ+DapyYxUkorj6+UJDJBYRlJBNOXYMiAgfQEAxr4NNseBz5i8 bXSG0DZSuo0iCBaU3l1PDEiGg26h2Qo= =aOju -----END PGP SIGNATURE----- --s3wrpdsnzbasx2vv-- --===============2476322633009275244== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel --===============2476322633009275244==--