Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp1345721rwd; Wed, 31 May 2023 12:33:20 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4oJbW8vaWKvRHhgswN4w/xHPQMrakz9Fye6md/WJTbkj4vh3IjP49LUw7TWqREtSs044k9 X-Received: by 2002:a05:6a20:158a:b0:104:ffd0:232a with SMTP id h10-20020a056a20158a00b00104ffd0232amr16651617pzj.8.1685561600559; Wed, 31 May 2023 12:33:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685561600; cv=none; d=google.com; s=arc-20160816; b=TI9HMj8C5vdLETPM+Li1uuihXxhUqjoBweBXfD1sE+bk2JUuM++i/WOClWClYOWoMI EI3XEr+S6XHZ2K/p5W8wMnGmVallZXvKRE+sJWdQfFFuxJTgbejIDN68+4uJrsa2tVOS DGKA9Why0ouKTyh9Ts/W95kFanOord3f+5hq6x80543KKPp7Nc8d+3zkYb/eHr+RGadI XCobwJe78yYRIE3SlTbM9wDzNoX3laGW9zlI5TY2dnqorFIia/KF/1W0YyT1Z7mTBO0O w2mfSEXYtPvmxebURplipD1pxCn6dJK8XwnVnRvDsuJucglS6+VBXD1PqyJ8gl77WIzR FqzA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=Lz1nG2B3q0llv6deAIMIjSEMvsrQuQ3uKlNlDgfU5wU=; b=fQodhRv8OL4+5c4mn0SrbEbJDMqCiGnQ4NJ3JdAroqtAFZMbHDWy3BfNTOw+9qQdfw gJFpbxqd9j6YSxZ3fqt24DxpqimdDyUxhA78UoSDkj5fh1pfH+g8B9pFNN1K9A4Ksi9C GQYUPFN7TxJ/cp75y457C+ukyuSxtud5b2n9wzwqFUTYeA1CvaBtI0SgpVkzI3qMji51 fDUpl/AXhY+PyzFi+V06sq7rYZ8xvTyHWC2qh4Q2v1uCk1V1AQElhi75SWIAy71+HikU 98vY3E/HD2P0GxMCSzbNE/mGJFWiaWjEF3Ru751TwxCjjtT26j80zhYG7GXqlBwIqaHK WImw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=DvSDgeuR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z19-20020a63b913000000b0053eedcc5049si1476962pge.105.2023.05.31.12.33.05; Wed, 31 May 2023 12:33:20 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=DvSDgeuR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229833AbjEaTVH (ORCPT + 99 others); Wed, 31 May 2023 15:21:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52524 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229761AbjEaTVF (ORCPT ); Wed, 31 May 2023 15:21:05 -0400 Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6A130124 for ; Wed, 31 May 2023 12:21:04 -0700 (PDT) Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-514924ca903so185684a12.2 for ; Wed, 31 May 2023 12:21:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1685560863; x=1688152863; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=Lz1nG2B3q0llv6deAIMIjSEMvsrQuQ3uKlNlDgfU5wU=; b=DvSDgeuRNVRc8TL9mrIG3iWEzc8MrZLyaNSP/JQxFELc38pYKUWja2yVsCJ/cLylkK vEC47lS9oNgkqcKMZs/FZgHJowNhBLhNvkHJ40isYf3g0WyhF+DUNnCLXo3+6gjHTa0w oLm8Xa69uEAyeRhU395izpWOeLSeQhhkgxOVsh0S9N4+kvu5SAyf2AnTBKzcm6uqw+D4 7hHVZ8ysTESRDxZPDIX3Z25qomuOQBysCWfrJnNPkCwW5+sEI4ZGgiGoIeRfbiem7gZX qIaCtoUxYF/Gxd4zaa5YZV0QRImRI9Ki4dp12nSYjIIYDW2AtyYsZa+J+buibw/NRRXc mbjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685560863; x=1688152863; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Lz1nG2B3q0llv6deAIMIjSEMvsrQuQ3uKlNlDgfU5wU=; b=WVRGQ0Aqv/GgEOhApIpX4Rkdcs82oYUf+1+n/9lTJq0L2b/A1GiVcdRXHTtaeCL6Mx oZ4BREadglzIoJbmnAc64TNcw7ico7GYSDl1Xrm3oM0LmI4fpD0ULd64b2tXV4V8p/2B f7LIeUXKa8nLVSU7Jix+u44sRgr2p0Zan9bAXOKlDBA+qEgrMFfeNpGGVJ2YnxtYyyah UKwDJX6Rog87njcirvHkP8UvI+bN/y8Lsgw2uH6z8vw0sLppt5tVYZbRAKQW0HPzvaj+ QdVyW695b8BkiSkPZ9ZI8mdgxAQIMYZmG4/7WAYzObCtU5ACqw888/WPXFPiJ473a/bO 2XyA== X-Gm-Message-State: AC+VfDy44GU0B3VlEy5qLt3ZfFXNANdALTI85VvH3/e4NBUrP2vV9LTv mFbt2fTufpPWHVMFydsNqYXS8tf7IevOM8cfLZs= X-Received: by 2002:a17:907:26ca:b0:969:f433:9b54 with SMTP id bp10-20020a17090726ca00b00969f4339b54mr6317786ejc.39.1685560862913; Wed, 31 May 2023 12:21:02 -0700 (PDT) Received: from [192.168.1.20] ([178.197.199.204]) by smtp.gmail.com with ESMTPSA id s7-20020a170906c30700b0094f410225c7sm9397440ejz.169.2023.05.31.12.21.00 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 31 May 2023 12:21:02 -0700 (PDT) Message-ID: <0cb1d679-9e5b-8030-368e-69c3fc54511f@linaro.org> Date: Wed, 31 May 2023 21:20:59 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [PATCH V2 1/6] dt-bindings: clock: qcom: Add SM8550 camera clock controller Content-Language: en-US To: Bryan O'Donoghue , Jagadeesh Kona , Andy Gross , Michael Turquette , Stephen Boyd , Rob Herring , Krzysztof Kozlowski , Conor Dooley Cc: Bjorn Andersson , Konrad Dybcio , Vladimir Zapolskiy , Vinod Koul , linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Taniya Das , Satya Priya Kakitapalli , Imran Shaik , Ajit Pandey References: <20230525172142.9039-1-quic_jkona@quicinc.com> <20230525172142.9039-2-quic_jkona@quicinc.com> <546876ba-970d-5cd5-648e-723698ca74fd@linaro.org> From: Krzysztof Kozlowski In-Reply-To: <546876ba-970d-5cd5-648e-723698ca74fd@linaro.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 26/05/2023 14:29, Bryan O'Donoghue wrote: > On 25/05/2023 18:21, Jagadeesh Kona wrote: >> Add device tree bindings for the camera clock controller on >> Qualcomm SM8550 platform. >> >> Signed-off-by: Taniya Das >> Signed-off-by: Jagadeesh Kona >> --- >> Changes since V1: >> - Removed new YAML file and reused SM8450 CAMCC YAML file for SM8550 >> >> .../bindings/clock/qcom,sm8450-camcc.yaml | 8 +- >> include/dt-bindings/clock/qcom,sm8550-camcc.h | 187 ++++++++++++++++++ >> 2 files changed, 193 insertions(+), 2 deletions(-) >> create mode 100644 include/dt-bindings/clock/qcom,sm8550-camcc.h >> >> diff --git a/Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml b/Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml >> index 87ae74166807..8dbc9004202f 100644 >> --- a/Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml >> +++ b/Documentation/devicetree/bindings/clock/qcom,sm8450-camcc.yaml >> @@ -13,11 +13,15 @@ description: | >> Qualcomm camera clock control module provides the clocks, resets and power >> domains on SM8450. >> >> - See also:: include/dt-bindings/clock/qcom,sm8450-camcc.h >> + See also:: >> + include/dt-bindings/clock/qcom,sm8450-camcc.h >> + include/dt-bindings/clock/qcom,sm8550-camcc.h >> >> properties: >> compatible: >> - const: qcom,sm8450-camcc >> + enum: >> + - qcom,sm8450-camcc >> + - qcom,sm8550-camcc > > Hmm, > > So looking at Documentation/devicetree/bindings/clock/*camcc*.yaml we > seem to be repeating yaml over and over again with no substantial > difference between one description and another. > > You've picked at the thread here by adding sm8550 into sm8450. > > I think sm8250, sm8450, sm8550, sc7280 and ... probably sm6350 should > live in the one yaml description > Documentation/devicetree/bindings/clock/qcom,camcc.yaml > > sm6350 looks a bit sparse/incomplete to me so perhaps leave that out. > The others sc7280, sm8250, sm8450 and sm8550 can/should all be moved > into the same yaml file with a list of compatibles. Clocks are different. The ones with same clocks should be together, but in other cases better to have separate schemas. It gets trickier to read with multiple if:then: Best regards, Krzysztof