Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp1808754iog; Tue, 14 Jun 2022 14:00:46 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tPm9ECQcxemA+KnVhI7Z9x+T7ZZ10U4jj49MBUhDNAhS/PMNy8L0TGfOCA9yJJmhaaBvKM X-Received: by 2002:a17:902:c7d1:b0:163:bb03:d5f0 with SMTP id r17-20020a170902c7d100b00163bb03d5f0mr5908680pla.167.1655240445876; Tue, 14 Jun 2022 14:00:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655240445; cv=none; d=google.com; s=arc-20160816; b=Cw/l/Fiu5MpQOmSqso9+HCrIm2lwLc06wHB5Rnphg7OM0awgreCpFT87kiCkZPaKCg LTB9Tq8df2OfjZb+fxvVowBc+IO5wc8PENybK5lq/FlxcOARR+Jp9olqvtQ0Yj981IUn wz+numbGrQlduE7QSlKSUvcEnsHMiDNOTnnHslZopYABuE2d7k9E1dGeYw/W62JNBCk9 sNoXrFc7Ur5KPXcdfQyC0uUZAn7orEMJjgUlqAs7Yavpv78OnFpxnVS711LGRUQ3A0oI WaqCSnMjp3UIiB9PXW4mj2oDC3sAKowD/gT3veqR3jWnE8YYAdzX4mGMMYoQgyEC2st1 BLMw== 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:user-agent:from :references:in-reply-to:mime-version:dkim-signature; bh=R9se4fkQIATOHeiM0V5pTwXbBCtBLskjJDXmy+aUXOg=; b=ljWnGerMfLEDANOHjPyP2P1ylXC1MPMM60JJwpBDmTg+cf4XxId0nm9e6NcGToLqOz F5iW0Xwt/a1LPvWPN6DbHPTvfZKO4UibaCu+RHJjewEwyvhKQ9VnTvvhmVE+cm4aclue /b2o/GaQZbRIb71CvoO3vQB4zq5muMSQbzwhtxCI/Z2vrzT2Fi6s9m7xTN0WIii5gaUI ijh80l5liNiI/4eqdQtxg74hnl78d9qko9/k17aVf5VGg5hOvXSoj71NjaXANL6NF9qD a7PBuYOZBLvvpPxFaiAzIoZOcA8/UMQp5LVDOePZRnqBQD1OmgbQJAorWHfa5JlQplem oXQQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=JyDOPWyT; 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=chromium.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d131-20020a636889000000b0040512c17f1asi14337530pgc.819.2022.06.14.14.00.33; Tue, 14 Jun 2022 14:00:45 -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=@chromium.org header.s=google header.b=JyDOPWyT; 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=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238917AbiFNUiq (ORCPT + 99 others); Tue, 14 Jun 2022 16:38:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57272 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238684AbiFNUip (ORCPT ); Tue, 14 Jun 2022 16:38:45 -0400 Received: from mail-oi1-x229.google.com (mail-oi1-x229.google.com [IPv6:2607:f8b0:4864:20::229]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ED56B43EE1 for ; Tue, 14 Jun 2022 13:38:43 -0700 (PDT) Received: by mail-oi1-x229.google.com with SMTP id p8so8714274oip.8 for ; Tue, 14 Jun 2022 13:38:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:in-reply-to:references:from:user-agent:date:message-id :subject:to:cc; bh=R9se4fkQIATOHeiM0V5pTwXbBCtBLskjJDXmy+aUXOg=; b=JyDOPWyTOJ/kfEgQJod7us/n3SDVipjiGbeeAOBgglFjHRLuM2AVFRnsoyoYtufeVk 8+X0h8frxvUBw4RfCtMwFXC3l/LL6NXMv5RgRUspMriCjRuw93ypQGxXMynXBBtCblkj u62nJDv0L++Msf99HE29mSBQ/NTHJfPPuoJJs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:in-reply-to:references:from :user-agent:date:message-id:subject:to:cc; bh=R9se4fkQIATOHeiM0V5pTwXbBCtBLskjJDXmy+aUXOg=; b=Udyz5JhpMGH8OXDzbUnwWOpRUcSpK3lymvSpl2k2CQuYWcvmTdAMHeRyAB88+RupF3 5JYbmjMcmtp2ABUtX3twEfDjl2DHzc3UTAwtuNWmlpBOWIcvDyxRZaTY/IQq4MS/VK50 6tg27BQzKQDVWvuCL9wpqB+TYxh+wkrZtcR2xDs3mTNP5jtwM7yCdWBkGvX/JhdP+pi1 GzhBWGLHf7Woda6YN9JUH5OFMw98058moeyVF23m4EGNrHtqF/Rx0EdexCsyBC2+gKbz 7ogbk4lu415w4peVSpzJc1Gni00m0us64fPtLs9pv8MyulEesyyVNnLV5a/0CDSnLw0k kvKg== X-Gm-Message-State: AOAM533xq1cJwrlPB/Dxuuzwh0O4Q3wDA1SSfPgW57NilFttMCjZIeuD j5SbM2YtvsEidJMwPctjGitRWH8hnt5dcEAxUp1FQg== X-Received: by 2002:a05:6808:1703:b0:32e:851e:7f81 with SMTP id bc3-20020a056808170300b0032e851e7f81mr3177251oib.63.1655239123282; Tue, 14 Jun 2022 13:38:43 -0700 (PDT) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Tue, 14 Jun 2022 13:38:42 -0700 MIME-Version: 1.0 In-Reply-To: References: <20220614161118.12458-1-quic_tdas@quicinc.com> From: Stephen Boyd User-Agent: alot/0.10 Date: Tue, 14 Jun 2022 13:38:42 -0700 Message-ID: Subject: Re: [PATCH v1] arm64: dts: qcom: sc7280: Update lpassaudio clock controller for resets To: Matthias Kaehlcke , Taniya Das Cc: Rob Herring , Bjorn Andersson , Douglas Anderson , Andy Gross , devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable 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 Quoting Matthias Kaehlcke (2022-06-14 09:51:57) > On Tue, Jun 14, 2022 at 09:41:18PM +0530, Taniya Das wrote: > > The lpass audio supports TX/RX/WSA block resets. The LPASS PIL clock > > driver is not supported and mark it disabled. Also to keep consistency > > update lpasscore to lpass_core. > > There is a driver for "qcom,sc7280-lpasscc", what does it mean that is > isn't supported? > > IIUC one problem is that 'lpasscc@3000000' and 'lpass_aon / clock-controller@3380000' > have overlapping register ranges, so they can't be used together. > > You could just say 'Disable the LPASS PIL clock by default, boards > can enable it if needed'. For the pinctrl driver we added a "qcom,adsp-bypass-mode" property[1] to indicate that the ADSP was being bypassed or not. Can we do the same here and combine the device nodes that have overlapping reg properties? [1] https://lore.kernel.org/r/1654921357-16400-2-git-send-email-quic_srivasam@quicinc.com