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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2984DC61DA7 for ; Fri, 27 Jan 2023 00:21:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232387AbjA0AVC (ORCPT ); Thu, 26 Jan 2023 19:21:02 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57090 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231986AbjA0AU5 (ORCPT ); Thu, 26 Jan 2023 19:20:57 -0500 Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com [IPv6:2607:f8b0:4864:20::f29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 518BE2685 for ; Thu, 26 Jan 2023 16:20:29 -0800 (PST) Received: by mail-qv1-xf29.google.com with SMTP id d13so2771626qvj.8 for ; Thu, 26 Jan 2023 16:20:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=zpmDswi/wSigvewXIn7qeq2QNhLH9j+uFliOJerl3lI=; b=OsZ8dXBoYhzZZ+SDvz0bZZkdfFSs1vHlgrFlAn8uyjA2zFJyTwHyDBRRywqSGIvvVy +Ul/d89CbpIla0hrjNvJ0A55rDuffKixQywKL37Wylwihl91tTVpfsoO2Vuoiu2Odhkx uaeGVL62yT1cNxnk9T0AomAe8JrddORL1eRtw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=zpmDswi/wSigvewXIn7qeq2QNhLH9j+uFliOJerl3lI=; b=7kP18WhyW12bF9VMLrM6P9Rc0/i/pp2BdZ0X7eNnF+hkjnOAwle5hC5FAQgc/wyfoc 1kEU3N2+25PU7sVuvgtCHS7/+YSCZ9kWU91f90lFE5RIKgRZiyAb/OTCVCgM/A9SOoUT X4F6cW7hn64UziQdO6t+pRhu4ctQomlIoQsZ28LLlJvT+OA0BGtroG+bqa9zHt7KBnkp HKrLh2aiuGOtGoZs0ZTAmN3FnqlJ8fAoMOWDI9mpcAW+ZCEffeP7z2Fenx8wIJ3UicUI LiZ32z1fX3xug9j0Lr6fLApFzIrBkKjWsFztqSH8oOmRvRONF/Pp1w7Dwdul+xDWwsf+ wXmQ== X-Gm-Message-State: AO0yUKUa63EqMLZHq5orsXF1+0Aqtg4cIjImLmlEFTHg20WhLlIxWzNV 7amG2eXo7l74IzR7yQufkatW4NqhrYja0FIzN6A= X-Google-Smtp-Source: AK7set9GgD+I+ipm9NEapjWvgejGxQgGFLa8BBDsgmGyGT9DCnwK2MCH/lkbVyfALQChf+ZZNKhamw== X-Received: by 2002:a05:6214:3109:b0:537:7402:e781 with SMTP id ks9-20020a056214310900b005377402e781mr10960823qvb.50.1674778828009; Thu, 26 Jan 2023 16:20:28 -0800 (PST) Received: from mail-yb1-f174.google.com (mail-yb1-f174.google.com. [209.85.219.174]) by smtp.gmail.com with ESMTPSA id d184-20020a3768c1000000b006eee3a09ff3sm1865574qkc.69.2023.01.26.16.20.24 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 26 Jan 2023 16:20:24 -0800 (PST) Received: by mail-yb1-f174.google.com with SMTP id e15so4123550ybn.10 for ; Thu, 26 Jan 2023 16:20:24 -0800 (PST) X-Received: by 2002:a25:4b41:0:b0:803:e799:d7b9 with SMTP id y62-20020a254b41000000b00803e799d7b9mr2481898yba.16.1674778823633; Thu, 26 Jan 2023 16:20:23 -0800 (PST) MIME-Version: 1.0 References: <20221216112918.1243-1-quic_rjendra@quicinc.com> <9f6bd192-2a42-0a23-0032-df8b01921bdc@linaro.org> <18c2bd9a-0216-c4fc-773e-601aea030b48@quicinc.com> In-Reply-To: <18c2bd9a-0216-c4fc-773e-601aea030b48@quicinc.com> From: Doug Anderson Date: Thu, 26 Jan 2023 16:20:10 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v4 1/2] dt-bindings: arm: qcom: Document the sc7280 CRD Pro boards To: Rajendra Nayak Cc: Dmitry Baryshkov , andersson@kernel.org, Matthias Kaehlcke , agross@kernel.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, konrad.dybcio@linaro.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Mon, Jan 9, 2023 at 8:21 PM Rajendra Nayak wrote: > > > On 1/10/2023 3:12 AM, Doug Anderson wrote: > > Hi, > > > > On Mon, Jan 9, 2023 at 1:36 PM Dmitry Baryshkov > > wrote: > >> > >> On 09/01/2023 23:00, Doug Anderson wrote: > >>> Hi, > >>> > >>> On Tue, Dec 20, 2022 at 9:12 AM Dmitry Baryshkov > >>> wrote: > >>>> > >>>> On 20/12/2022 18:20, Rajendra Nayak wrote: > >>>>> > >>>>> > >>>>> On 12/20/2022 8:00 PM, Matthias Kaehlcke wrote: > >>>>>> On Tue, Dec 20, 2022 at 10:30:32AM +0530, Rajendra Nayak wrote: > >>>>>>> > >>>>>>> On 12/16/2022 7:49 PM, Matthias Kaehlcke wrote: > >>>>>>>> On Fri, Dec 16, 2022 at 04:59:17PM +0530, Rajendra Nayak wrote: > >>>>>>>>> Add compatibles for the Pro SKU of the sc7280 CRD boards > >>>>>>>>> which come with a Pro variant of the qcard. > >>>>>>>>> The Pro qcard variant has smps9 from pm8350c ganged up with > >>>>>>>>> smps7 and smps8. > >>>>>>>>> > >>>>>>>>> Signed-off-by: Rajendra Nayak > >>>>>>>>> Acked-by: Krzysztof Kozlowski > >>>>>>>>> Reviewed-by: Matthias Kaehlcke > >>>>>>>>> --- > >>>>>>>>> v4 changes: > >>>>>>>>> Added the zoglin-sku1536 compatible along with hoglin-sku1536. > >>>>>>>>> Zoglin is same as the Hoglin variant, with the SPI Flash reduced > >>>>>>>>> from 64MB to 8MB > >>>>>>>>> > >>>>>>>>> Documentation/devicetree/bindings/arm/qcom.yaml | 6 ++++++ > >>>>>>>>> 1 file changed, 6 insertions(+) > >>>>>>>>> > >>>>>>>>> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml > >>>>>>>>> b/Documentation/devicetree/bindings/arm/qcom.yaml > >>>>>>>>> index 1b5ac6b02bc5..07771d4c91bd 100644 > >>>>>>>>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml > >>>>>>>>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml > >>>>>>>>> @@ -558,6 +558,12 @@ properties: > >>>>>>>>> - const: google,hoglin > >>>>>>>>> - const: qcom,sc7280 > >>>>>>>>> + - description: Qualcomm Technologies, Inc. sc7280 CRD Pro > >>>>>>>>> platform (newest rev) > >>>>>>>>> + items: > >>>>>>>>> + - const: google,zoglin-sku1536 > >>>>>>>>> + - const: google,hoglin-sku1536 > >>>>>>>> > >>>>>>>> Is there actually such a thing as a 'hoglin-sku1536', i.e. the Pro > >>>>>>>> qcard > >>>>>>>> with 64MB of SPI flash, or do they all have 8MB of flash? > >>>>>>> > >>>>>>> The SPI flash is on the CRD mother-board and not on the qcards, so if > >>>>>>> you replace > >>>>>>> the qcards on the CRDs with 64MB flash you would need the > >>>>>>> hoglin-sku1536 to > >>>>>>> boot on those. > >>>>>> > >>>>>> With such a configuration how does the bootloader know it should pass > >>>>>> the kernel > >>>>>> the device tree for 'hoglin-sku1536' (pro) and not the non-pro > >>>>>> variant? IIUC the > >>>>>> device tree is selected based on pin strappings on the mother-board, > >>>>>> not the > >>>>>> qcard. > >>>>> > >>>>> The device tree is selected based on the pin strappings _and_ additional > >>>>> logic > >>>>> to dynamically identify modem/non-modem(wifi) as well as pro/non-pro > >>>>> SKUs which > >>>>> was added in the bootloaders. > >>>> > >>>> Just to clarify things, when you mention pro SKU, is it a separate SoC > >>>> revision (like sc7280-pro vs bare sc7280), or is it a CRD revision (CRD > >>>> Pro vs bare CRD)? > >>> > >>> I guess Rajendra never responded, but since I know the answer: it's a > > Thanks Doug for the clarifications, I seem to have missed responding to this > once I was back from vacation, > > >>> different SoC revision. ...but the SoC in this case is on a daughter > >>> card, so you could remove the daughter card containing the SoC and put > >>> a new daughtercard on. That would have the effect of making an old CRD > >>> revision have the new Pro SKU SoC. > >> > >> So, this is a new SoC. Is it 100% compatible with the sc7280? In other > >> words: does it require any additional customizations (in OPP tables, in > >> frequences, speed bins, etc)? > > Yes, the OPP differences are taken care of with no changes needed in kernel. > We describe a superset of *all* OPPs supported by a SoC family in DT and the > cpufreq driver then queries the firmware for supported OPPs on a given > SoC variant and ends up disabling the rest. I saw that Bjorn just send out a pull request but it didn't include this patch. Bjorn: are you expecting anything from Rajendra here, or did it just get missed? I think Rajendra responded to all of Dmitry's comments, but I could be mistaken. -Doug