Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp5664556rwr; Tue, 9 May 2023 04:56:16 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6R8X1z889TZKn4TDzi/4t7XUHOzCI6N3emde9wy3+AHf/yPJc8mdEc0NUjWcwwhWLO8zDh X-Received: by 2002:a05:6a00:181d:b0:645:b7fc:8311 with SMTP id y29-20020a056a00181d00b00645b7fc8311mr11269451pfa.4.1683633376468; Tue, 09 May 2023 04:56:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683633376; cv=none; d=google.com; s=arc-20160816; b=TYQ2l8+42JU3NuE3B6Zgs2W8V0XMAOBfePQPL19klWAgKPqeiEQudxKv2Y9LCkllH5 PWQMU3eWpf9K0azFosw7kJgLOrYOgp/ehFJJ9ClLQng3zOpleBfVQRVzifVJ/9eT9Usx AMVrxRa7BzT10X3J6xeq1o7BGNGxDn5o0tbnl1Pc7b3fN2PIuSRZpd3z2pfNW5RgRcRC IigPUnkj1ustqJzyfdsTW0NPMuLG8hD9D/c0m6WId+qr1sOZ/effAQQXaskWSAY4LVGU eCRV6Vuzx5dZ7ClmudH9ZKahVZ5Bfd+X3ykDOyAaWVAOXItz0pDDwiUq0bTtUyLDByHz 6d6w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=v7Pyw5nwHkNnu462qbwGos47j69OLpTlZbNxmPBS04M=; b=C5TPmsVKGFt3Fh+aaCtJQlORUjBCVIgyhogmUejrzIX2QkTJ1h5tkIx5PH7/fEhr2S OF8IwMIvIKR2uS9ZIE2twEYaqb1mISmc8gmTwVjNJfwxrkvYCC2S8M1fndfGIxbfl1/K szlcwr9YJB7cTEvYyoudf5c/Ohsv69mUoKgNTKFyp5D8U4/n+ROlC/MYjKjKrlYiLP8E GoLp9hjHrhflYf6fEZj4hSjHK7Q0W62fyblgtU3bUNLtr7RLGg5DzZtYNvhbPvsXQoV6 Q+4D+UssU0vWETvnEA9LWdgQJ2MeFQoOHjE96Qg4+pKYwBkWomppl7R8MBq5oxftm8cH ejtg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=KrIh5Hk1; 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 b123-20020a62cf81000000b00643b9afbb97si2262279pfg.56.2023.05.09.04.56.01; Tue, 09 May 2023 04:56:16 -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=KrIh5Hk1; 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 S234828AbjEILgY (ORCPT + 99 others); Tue, 9 May 2023 07:36:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50916 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235233AbjEILgW (ORCPT ); Tue, 9 May 2023 07:36:22 -0400 Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BE84B30F5 for ; Tue, 9 May 2023 04:35:52 -0700 (PDT) Received: by mail-yb1-xb2a.google.com with SMTP id 3f1490d57ef6-ba5f2522304so621792276.0 for ; Tue, 09 May 2023 04:35:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1683632151; x=1686224151; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=v7Pyw5nwHkNnu462qbwGos47j69OLpTlZbNxmPBS04M=; b=KrIh5Hk1NDf7N1L5Q/kIXQoVM/rJOfSZtn5DhWzorecfs4Y86UWthqOKU3cz6NRWfN 14DVPJxjxqLySDfnikRT3EB6uvhGfTR5rhRxgLfsH6BhL5yVg7OwrN3BNb2UhX7kT8FJ F8F8R09NEzrb4KCxRzGNoXMichNsn24s57JCZW1stf9BC+WQCFJkYqhvK00rUb24ZdM1 F8QZDG44dpCzaR/q7jKIUg1P3TzGnqK2D37Evjd7quQ00ZoUvKV727+L92lCAJM9KIZf SMawUtOh6bY3Qxhjg08P7crImuwFBKfX2Rp4OnYV0s8f1TSygKW4dL7idsm8i3CRWzUM uLEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683632151; x=1686224151; 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=v7Pyw5nwHkNnu462qbwGos47j69OLpTlZbNxmPBS04M=; b=JsbTCLIMWQua6chi+M1Gmm2sb+rCDp0d24Oj3uggKeTsSHpfbW02J+CoNbtjmgTvKS 7FMftyW6LMosWkROMcaTQz1lJgHiM/DKc3JbZX74m62R6O17u+szeulKmKdBCK0nmFxQ jecGBJsvVdrLkuEoW/6qNDp2m5Gsh6KZ6soud+1eP6AVeO3/Q/QHd1yKIj5tvsXTRmgZ 94zezn42yIcmWRgfRGevm57I1RQGXJZgwVUerrUY5bIlbWj0OFp/SjnshqZx3ST7+Unb Wvylm3RZ0gHT8+YqhJTfwM0fHda/UEZmg6bVjQcP/CqgsDLW+/DEdGti2rrP40rpnkmT YlNw== X-Gm-Message-State: AC+VfDxb6mjNAcxpHPBPjKBTVidSqkROzavZRqOlOxOAHzAN5V7eAqF3 VohTUFRbenouHP1GjuOyKY1kcgAhkOE/kgX1ZRCAPw== X-Received: by 2002:a25:5d6:0:b0:b95:2bd5:8f86 with SMTP id 205-20020a2505d6000000b00b952bd58f86mr14675399ybf.26.1683632150830; Tue, 09 May 2023 04:35:50 -0700 (PDT) MIME-Version: 1.0 References: <343182748e12b6a4ac57d336405c50e36fc5520c.1683628357.git.quic_schowdhu@quicinc.com> In-Reply-To: <343182748e12b6a4ac57d336405c50e36fc5520c.1683628357.git.quic_schowdhu@quicinc.com> From: Dmitry Baryshkov Date: Tue, 9 May 2023 14:35:39 +0300 Message-ID: Subject: Re: [PATCH V6 1/3] dt-bindings: sram: qcom,imem: Add Boot Stat region within IMEM To: Souradeep Chowdhury Cc: Andy Gross , Konrad Dybcio , Krzysztof Kozlowski , Bjorn Andersson , Rob Herring , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, Sibi Sankar , Rajendra Nayak Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,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 Tue, 9 May 2023 at 13:53, Souradeep Chowdhury wrote: > > All Qualcomm bootloaders log useful timestamp information related > to bootloader stats in the IMEM region. Add the child node within > IMEM for the boot stat region containing register address and > compatible string. I might have a minor vote here. Is there any reason why you have to instantiate the device from DT? It looks like a software interface. Ideally software should not be described in DT (e.g. this can be instantiated from imem driver-to-be). Or we can follow the RPM master-stats approach, where the device is a top-level device, having handle pointers to the sram regions. > > Signed-off-by: Souradeep Chowdhury > Reviewed-by: Krzysztof Kozlowski > --- > .../devicetree/bindings/sram/qcom,imem.yaml | 22 +++++++++++++++++++ > 1 file changed, 22 insertions(+) > > diff --git a/Documentation/devicetree/bindings/sram/qcom,imem.yaml b/Documentation/devicetree/bindings/sram/qcom,imem.yaml > index 0548e8e0d30b..bb884c5c8952 100644 > --- a/Documentation/devicetree/bindings/sram/qcom,imem.yaml > +++ b/Documentation/devicetree/bindings/sram/qcom,imem.yaml > @@ -50,6 +50,28 @@ patternProperties: > $ref: /schemas/remoteproc/qcom,pil-info.yaml# > description: Peripheral image loader relocation region > > + "^stats@[0-9a-f]+$": > + type: object > + description: > + Imem region dedicated for storing timestamps related > + information regarding bootstats. > + > + additionalProperties: false > + > + properties: > + compatible: > + items: > + - enum: > + - qcom,sm8450-bootstats > + - const: qcom,imem-bootstats > + > + reg: > + maxItems: 1 > + > + required: > + - compatible > + - reg > + > required: > - compatible > - reg > -- > 2.17.1 > -- With best wishes Dmitry