Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 03923C433EF for ; Sat, 13 Nov 2021 20:02:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id DFC356058D for ; Sat, 13 Nov 2021 20:02:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236079AbhKMUFR (ORCPT ); Sat, 13 Nov 2021 15:05:17 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35738 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236057AbhKMUFN (ORCPT ); Sat, 13 Nov 2021 15:05:13 -0500 Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 640C1C061767 for ; Sat, 13 Nov 2021 12:02:20 -0800 (PST) Received: by mail-ot1-x335.google.com with SMTP id w6-20020a9d77c6000000b0055e804fa524so19703539otl.3 for ; Sat, 13 Nov 2021 12:02:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=y0rkE2eXHspUlHAthWH1b6o7jeh50VMqJ9wHRaI24M4=; b=aW9u9fGnts+Kui5gr1eOEqMyRfk/k5aY6qpEB/k9DiK9Ec191wxXRBV04evzKbA5tZ W21Mbviqpsbn6FP9XSQaRkHEInqMWxC3I/QHbIcooFKwG3+w0mqiBq3vNbaT+ItOUjGg aaaZyIVDLVaQ4gNU4KOa5Dsmwff/18yZLg7nROCBRt5Hw3+HHPD+lrczcuX+rRrnZ+DF fKUL29m8MOrtRf4Dwe23c2d3lX6txELLc4hrqWUt2vzFBRs2m9B3Ia1DTPR7cmye6W9S 13PqMdIDn3a32d17JwKLKyj8AbBOSfwF9mAegcmrn2FRfe5yDmTtT/Tqk32EUVrX+p7O OkQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=y0rkE2eXHspUlHAthWH1b6o7jeh50VMqJ9wHRaI24M4=; b=i0BCdgaFWB0f33i9Z3SeRckQIy5N6lV810m4C55igGwnTg7PMRq1GgGYWKO6cOORal C1NH0gqF/iAyrZNGIdTdU2UwgvmBFnK/WgAvLMHWkTpeirM68iW5cT78EuE8bYs3GMZ7 j/OEEMJXMTTzBxkEwk+AjtRscwH/DVhaD3c2FOj2qNT7o0Ju/Ll05pOnKfhxd36EYVpt jRizw9/BrxTMg2GiSDfmECDkehb0hVu5wZZEKlXm+N57t4JrwLHCYvUdQqazFlAj5VsV DcNDNZ0rg/zvg6SmaAVdOqROIGfBw6KCAwiSoIYJt75BSrDppzRNL+nuDqB+TJsn2awV /ncg== X-Gm-Message-State: AOAM530p+JlfzwfYzqo+0Tr815LWaCX6cUXvUS3d46bd1u9yT7cMvHbq 3RQe8xo+qLVOvuY6RYOVKcXXhA== X-Google-Smtp-Source: ABdhPJw/kvtWC5smOrH3f2SEC50UhtAALVArUdA8Hr+wIxdsYsdMw9Bg+kp/KqmSdjZ4B6wdAxw/EA== X-Received: by 2002:a9d:a64:: with SMTP id 91mr20346988otg.198.1636833739698; Sat, 13 Nov 2021 12:02:19 -0800 (PST) Received: from builder.lan (104-57-184-186.lightspeed.austtx.sbcglobal.net. [104.57.184.186]) by smtp.gmail.com with ESMTPSA id q12sm1935177otl.66.2021.11.13.12.02.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 13 Nov 2021 12:02:19 -0800 (PST) Date: Sat, 13 Nov 2021 14:02:14 -0600 From: Bjorn Andersson To: Bhupesh Sharma Cc: linux-arm-msm@vger.kernel.org, linux-crypto@vger.kernel.org, bhupesh.linux@gmail.com, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, robh+dt@kernel.org, agross@kernel.org, herbert@gondor.apana.org.au, davem@davemloft.net, stephan@gerhold.net, Thara Gopinath Subject: Re: [PATCH v5 09/22] dt-bindings: qcom-qce: Move 'clocks' to optional properties Message-ID: References: <20211110105922.217895-1-bhupesh.sharma@linaro.org> <20211110105922.217895-10-bhupesh.sharma@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211110105922.217895-10-bhupesh.sharma@linaro.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 10 Nov 04:59 CST 2021, Bhupesh Sharma wrote: > QCom QCE block on some SoCs like ipq6018 don't > require clock as the required property, so the properties > 'clocks' and 'clock-names' can be moved instead in the dt-bindings > to the 'optional' properties section. > > Otherwise, running 'make dtbs_check' leads to the following > errors: > > dma-controller@7984000: clock-names:0: 'bam_clk' was expected > arch/arm64/boot/dts/qcom/ipq6018-cp01-c1.dt.yaml > > dma-controller@7984000: clock-names: Additional items are not allowed ('bam_clk' was unexpected) > arch/arm64/boot/dts/qcom/ipq6018-cp01-c1.dt.yaml > > dma-controller@7984000: clock-names: ['iface_clk', 'bam_clk'] is too long > arch/arm64/boot/dts/qcom/ipq6018-cp01-c1.dt.yaml > > dma-controller@7984000: clocks: [[9, 138], [9, 137]] is too long > arch/arm64/boot/dts/qcom/ipq6018-cp01-c1.dt.yaml > > Cc: Thara Gopinath > Cc: Bjorn Andersson > Cc: Rob Herring > Signed-off-by: Bhupesh Sharma > --- > Documentation/devicetree/bindings/crypto/qcom-qce.yaml | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml > index 30deaa0fa93d..f35bdb9ee7a8 100644 > --- a/Documentation/devicetree/bindings/crypto/qcom-qce.yaml > +++ b/Documentation/devicetree/bindings/crypto/qcom-qce.yaml > @@ -53,8 +53,6 @@ properties: > required: > - compatible > - reg > - - clocks > - - clock-names I would prefer that we make this conditional on the compatible. That said, if this only applies to ipq6018 I think we should double check the fact that there's no clock there... For the sake of making progress on the series, I think you should omit this patch from the next version. Regards, Bjorn > - dmas > - dma-names > > -- > 2.31.1 >