From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 72E7A202972 for ; Tue, 4 Mar 2025 13:29:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.67.36.65 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741094945; cv=none; b=R2dPfWY2Y1rvVyXvDIXX/cJ93Y/mJ2+9RrbnxokC3cPVm8/TegYEgL7r7+jMy5U09WvZcFXF5OzbxrNwMrrukzraFNqy6NSA9gLErTQwRkGjfroT703oFPFS+60eB8ASSIRiH1usLCbnLuMIzzN/ZKjbtmSRM2U5m4MBRgIA7Tc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741094945; c=relaxed/simple; bh=GPsFfWzJ45kkPKaIC8bUVtCSlM7aVHTBZr1/4Ads9no=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=f9x0jZzz+7LpXKzjsapEqOLqFIM8cKtwyaekmMy5/W5ymdTOluVIAnhOCFFEhLVc2nuHBeQjvR6YMam+tlreD4v8/H2XdOJKbRfyb56f8xBFdJC5Gw/miVMEvQ7cZdwekt8ulChYFET6/LTTEn9qoqzWU4BJHfX02p27vvQLqGM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=posteo.net; spf=pass smtp.mailfrom=posteo.net; dkim=pass (2048-bit key) header.d=posteo.net header.i=@posteo.net header.b=d0s+Fhdb; arc=none smtp.client-ip=185.67.36.65 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=posteo.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=posteo.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=posteo.net header.i=@posteo.net header.b="d0s+Fhdb" Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id C341A240027 for ; Tue, 4 Mar 2025 14:28:54 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1741094934; bh=GPsFfWzJ45kkPKaIC8bUVtCSlM7aVHTBZr1/4Ads9no=; h=Date:From:To:Cc:Subject:Message-ID:MIME-Version:Content-Type: Content-Disposition:Content-Transfer-Encoding:From; b=d0s+FhdbcuLFwkfFcRwE0nqixpJG3lUz+6op8v5ee+kPQxW4c8DAimFo+uWWN14Xr 6h5PVkvfRVxBNEIVhA+s+hJKMA/5wnlT+WFT2Up2p1IolpujhW9j1jLTkXSooiTpYe C97Aa+YPXYlNBWDX+brECSJR1tPv3+XREPbQEHWLyBkMGMgzRIgiLzlqaZQaHhdrM2 hdj2o7yUiXQq2dW3uONLrMbZopjqpAXb3etXMJYl0KFQk9xjZ8qA3wD2R2agnB+//b Ab29dpSekP4Z585SMPTIcPR10qytyg0LgSyTjncWnnYKbcqVEwBNtoBWHqd6ejWE1I WN6cw/6Pyp6rA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Z6c2r19WLz9rxF; Tue, 4 Mar 2025 14:28:52 +0100 (CET) Date: Tue, 4 Mar 2025 13:28:51 +0000 From: =?utf-8?Q?J=2E_Neusch=C3=A4fer?= To: Rob Herring Cc: =?utf-8?Q?J=2E_Neusch=C3=A4fer?= , Conor Dooley , Michael Ellerman , Madhavan Srinivasan , Christophe Leroy , dmaengine@vger.kernel.org, Crystal Wood , linuxppc-dev@lists.ozlabs.org, Nicholas Piggin , Vinod Koul , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Krzysztof Kozlowski , Naveen N Rao Subject: Re: [PATCH v3] dt-bindings: dma: Convert fsl,elo*-dma to YAML Message-ID: References: <20250226-ppcyaml-dma-v3-1-79ce3133569f@posteo.net> <174059099427.2999773.4836262903761680275.robh@kernel.org> <20250303134200.GA1710704-robh@kernel.org> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20250303134200.GA1710704-robh@kernel.org> On Mon, Mar 03, 2025 at 07:42:00AM -0600, Rob Herring wrote: > On Wed, Feb 26, 2025 at 11:29:54AM -0600, Rob Herring (Arm) wrote: > > > > On Wed, 26 Feb 2025 16:57:17 +0100, J. Neuschäfer wrote: > > > The devicetree bindings for Freescale DMA engines have so far existed as > > > a text file. This patch converts them to YAML, and specifies all the > > > compatible strings currently in use in arch/powerpc/boot/dts. > > > > > > Signed-off-by: J. Neuschäfer > > > --- [...] > > dtschema/dtc warnings/errors: > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/dma/fsl,elo-dma.example.dtb: dma-controller@82a8: '#dma-cells' is a required property > > from schema $id: http://devicetree.org/schemas/dma/dma-controller.yaml# > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/dma/fsl,eloplus-dma.example.dtb: dma-controller@21300: '#dma-cells' is a required property > > from schema $id: http://devicetree.org/schemas/dma/dma-controller.yaml# > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/dma/fsl,elo3-dma.example.dtb: dma-controller@100300: '#dma-cells' is a required property > > from schema $id: http://devicetree.org/schemas/dma/dma-controller.yaml# > > Just stick with 'dma' for node name as that's what .dts files are using > and 'dma-controller' is reserved for users of DMA provider binding. > > Rob Ok, makes sense. Thanks, J. Neuschäfer