Received: by 2002:a05:6358:a55:b0:ec:fcf4:3ecf with SMTP id 21csp1100829rwb; Thu, 19 Jan 2023 06:41:18 -0800 (PST) X-Google-Smtp-Source: AMrXdXvXZW545jxAEd8D845LL6ujUpN94NtGR+PRC+9s4Qa44G2vrvtBk9dzUGXrhMeotEu69fz1 X-Received: by 2002:a17:906:6b03:b0:86e:26d8:52ff with SMTP id q3-20020a1709066b0300b0086e26d852ffmr14029003ejr.2.1674139278423; Thu, 19 Jan 2023 06:41:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1674139278; cv=none; d=google.com; s=arc-20160816; b=X7IO+oBzWFYux8j0FHUy81x+Ii8Lb8fja/d3wMAcdHwdLg6HAekUV+PPlmicr+kVVz P7BEXoxDTnRVZ40Ei04y74bfDoRMkNU2riMWPUQ3OIqTV49FFMcpaiThQX6l8a9da9hk G7mEDWCZsvlI3cMyvEOTB6N1IHpVrmct3r8OuWgKIIEaKxEvDkpBM2ne+9GW9DuE19pd IK/Pm5qQd7i+uX5eQsMbnt9y/eHg16eSC8WI5ghT1SALe0VpY09LP9pmgZMknTmxhCsN PCojSTB96n8pUK0VUjG0Itia5DAQt3TqLIwmEDZafPFn2SbWxGN7iZUuzUNCD78LK8AR r7Lw== 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=E4Mx0B+gnlHiPQ5MYMwlb/qGt49i354n6i8Wn0CvMng=; b=Ef6SJT42jLF4VVDiM67jfmWauryq1+VL+JmlK1ajLSvUKrMSDtPNXCf4syQ3TzvMR4 WjV5mWy7tkiAOgGfo8EKhHN1SbGjKZgUak9F5b++fHRpVNbsI5JPX+9x+T16MegMt6Z0 cS4OBqa/bL0HalwL/ga+Hq4pCcltA9pEwJnsrJeEJiCfuPv5rSdGxAz1DJaWqpMDg8IW chi6CgKmhZmYtPoab2WiJpx0rmSwjh5HeZv2sFabiQ++CMVJ98ECH+8MR6CkYbiwQEgg Y+FONHc2/B8aU1q+DhwjqyvXqZMYY6fPZ0GnWw+6Nn63qHR/s0miAW3r86xr+6XHPlt/ FHIA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=KK2NJffV; 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 s5-20020a17090699c500b007c103219025si41547781ejn.825.2023.01.19.06.41.07; Thu, 19 Jan 2023 06:41:18 -0800 (PST) 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=KK2NJffV; 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 S230424AbjASOXz (ORCPT + 46 others); Thu, 19 Jan 2023 09:23:55 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46660 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229895AbjASOXw (ORCPT ); Thu, 19 Jan 2023 09:23:52 -0500 Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 736207AA0 for ; Thu, 19 Jan 2023 06:23:51 -0800 (PST) Received: by mail-lf1-x134.google.com with SMTP id j17so3488913lfr.3 for ; Thu, 19 Jan 2023 06:23:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.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=E4Mx0B+gnlHiPQ5MYMwlb/qGt49i354n6i8Wn0CvMng=; b=KK2NJffVpStog8GPaX5F22cqj3ZDzUpxyUabBu+ITeYbWCbB+bE86F/HAyB2R7nGpZ Uu8qabCrJGzTZMslT30QCxHXfNS4R6gjzvNXbNZuzqBozlkgA4N3Os6AzQIJHJp51U8T XC4cR46aFCys+gJpV42eO3mYXXfsNhlwhOAEaxAKaDMtpFsmnhC6iYpb0S+yVViqvJam NxndD7pfvMg86RKultFX9+JZHU4haKmEzfjdqUj9OzONfgrhzEgmsRMcOTKHRsO3qz24 +kUFB1CHO6QlsjK8iVClhBjI3yU4OUTzrhrg62IxQlX6tLlgHGpcOw/GUxiAJ8OxoGsR AfOQ== 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=E4Mx0B+gnlHiPQ5MYMwlb/qGt49i354n6i8Wn0CvMng=; b=rm0yoDbyS7gL5YB9gduBWWr7By+vVdOHhlF7Ls2jSIIBIaugUMMkpO9w29sVS/lEok nkfv69ZdLPth4Bo20rMsp3KGQ/MtLInr81z2ZNTFzWQZCBUlEzf1ZL/16Lb0dyLtf+BF DXg1matysp4fHWXgCNAE4kSMzFfqhHCbv4YGMUKWIGgJKxepVea8OXd1VLonPjBZ+bRN dFrONDQzY+qG/+YKL4w4TTxuIXWkb7oINT/fwml3fRdWyZlvhRNiNAJjYuCNzGMx1BdR XrHVBq0N6D7j5vouyO+X1ZFH2+fNQ4SGUWPBk73MYi+TYQL8Zf2WC+BYdjqng2oGPEgL boBw== X-Gm-Message-State: AFqh2koI48U0u+3MQxAEdX9DAyZknwsCK7hGT6kNGvsW5qYYEql4R50V 9g/llmfYb+x550/ny8IldUX9RZOqqieVdURPdSxlEw== X-Received: by 2002:a05:6512:409:b0:4cc:7876:9f35 with SMTP id u9-20020a056512040900b004cc78769f35mr612626lfk.125.1674138229728; Thu, 19 Jan 2023 06:23:49 -0800 (PST) MIME-Version: 1.0 References: <20221130104519.2266918-1-bhupesh.sharma@linaro.org> <0497ba61-7646-91bb-291c-0b437c18434f@linaro.org> In-Reply-To: <0497ba61-7646-91bb-291c-0b437c18434f@linaro.org> From: Bhupesh Sharma Date: Thu, 19 Jan 2023 19:53:37 +0530 Message-ID: Subject: Re: [PATCH] arm64: dts: qcom: sm6115: Add interconnect nodes To: Dmitry Baryshkov Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, agross@kernel.org, bhupesh.linux@gmail.com, linux-kernel@vger.kernel.org, robh+dt@kernel.org, krzysztof.kozlowski@linaro.org, konrad.dybcio@linaro.org, a39.skl@gmail.com, andersson@kernel.org 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 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 Hi Dmitry, On Thu, 19 Jan 2023 at 18:36, Dmitry Baryshkov wrote: > > On 30/11/2022 12:45, Bhupesh Sharma wrote: > > Add the interconnect nodes inside SM6115 dtsi. > > > > Cc: Bjorn Andersson > > Cc: Rob Herring > > Signed-off-by: Bhupesh Sharma > > --- > > - Based on linux-next/master > > - Depends on the SM6115 dt-binding and driver patchset, which can be > > seen here: https://lore.kernel.org/linux-arm-msm/20221130103841.2266464-1-bhupesh.sharma@linaro.org/ > > > > arch/arm64/boot/dts/qcom/sm6115.dtsi | 51 ++++++++++++++++++++++++++++ > > 1 file changed, 51 insertions(+) > > > > diff --git a/arch/arm64/boot/dts/qcom/sm6115.dtsi b/arch/arm64/boot/dts/qcom/sm6115.dtsi > > index e4a2440ce544..dad5ab3edf0e 100644 > > --- a/arch/arm64/boot/dts/qcom/sm6115.dtsi > > +++ b/arch/arm64/boot/dts/qcom/sm6115.dtsi > > @@ -485,6 +485,57 @@ usb_1_hsphy: phy@1613000 { > > status = "disabled"; > > }; > > > > + snoc: interconnect@1880000 { > > + compatible = "qcom,sm6115-snoc"; > > + reg = <0x01880000 0x60200>; > > + #interconnect-cells = <1>; > > Should we use 2 here as we do now for most of interconnect drivers? Right now, we are using the value present in upstream qcs404.dtsi which is the nearest in terms of similarity of the interconnect blocks present on this SoC. But let me try and make this change in v2. BTW the 'path tag' is optional, so I don't think that would be a mandatory change. Thanks, Bhupesh