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 B4632C76195 for ; Fri, 17 Mar 2023 18:30:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230210AbjCQSae (ORCPT ); Fri, 17 Mar 2023 14:30:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39664 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229517AbjCQSab (ORCPT ); Fri, 17 Mar 2023 14:30:31 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2874E4A1F8; Fri, 17 Mar 2023 11:30:30 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id D016BB826AE; Fri, 17 Mar 2023 18:30:28 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5030CC433D2; Fri, 17 Mar 2023 18:30:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1679077827; bh=B7OSJyjdwKWY48GIx7sDwmRKjhiHNgvWng4QzsAwV84=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=nwwi4JG5I1IYOhStnJN394y1Zn5VO4TEtmLeapCjCzjIDJvkNtSbmazFBMWnaJQFi RnDwc4K44CU+GCouF7bW7H27yje0alaQazaVyIvyHMPIbZPgW3xJUD7Ivg9puP8hQY CvK2gIm+YaoXVhN3b5uJaZTLRx32qBtW7TJv4fKwBG3dHF86Jry5cPKiXvREUBXiFl IsWfW2tddyFQ5EK7sef3PzA83HE6riToguObK9pGiz6scyVpyUT91TZHhdg7pN0FWV L8D2SNDM3dcy4Z8WJwqTg/TGGmfPXY2wUbThz6vvYh102VxDqwEuU+1mhHD/ga285T FmX+UsPsStZSg== Message-ID: <51362ea7a2e0571ccc5154939030d37b.sboyd@kernel.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20230317141622.1926573-3-quic_mohs@quicinc.com> References: <20230317141622.1926573-1-quic_mohs@quicinc.com> <20230317141622.1926573-3-quic_mohs@quicinc.com> Subject: Re: [PATCH v9 2/4] clk: qcom: lpasscc-sc7280: Skip qdsp6ss clock registration From: Stephen Boyd Cc: Srinivasa Rao Mandadapu , Mohammad Rafi Shaik To: Mohammad Rafi Shaik , agross@kernel.org, andersson@kernel.org, broonie@kernel.org, konrad.dybcio@somainline.org, krzysztof.kozlowski+dt@linaro.org, linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, mturquette@baylibre.com, quic_plai@quicinc.com, quic_visr@quicinc.com, robh+dt@kernel.org, swboyd@chromium.org Date: Fri, 17 Mar 2023 11:30:25 -0700 User-Agent: alot/0.10 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Mohammad Rafi Shaik (2023-03-17 07:16:20) > From: Srinivasa Rao Mandadapu >=20 > The qdsp6ss memory region is being shared by ADSP remoteproc device and > lpasscc clock device, hence causing memory conflict. > As the qdsp6ss clocks are being enabled in remoteproc driver, skip qdsp6ss > clock registration if "qcom,adsp-pil-mode" is enabled. >=20 > Fixes: 4ab43d171181 ("clk: qcom: Add lpass clock controller driver for SC= 7280") > Signed-off-by: Srinivasa Rao Mandadapu > Signed-off-by: Mohammad Rafi Shaik > Reviewed-by: Stephen Boyd > --- > drivers/clk/qcom/lpasscc-sc7280.c | 12 +++++++----- > 1 file changed, 7 insertions(+), 5 deletions(-) >=20 > diff --git a/drivers/clk/qcom/lpasscc-sc7280.c b/drivers/clk/qcom/lpasscc= -sc7280.c > index 5c1e17bd0d76..85dd5b9d64f0 100644 > --- a/drivers/clk/qcom/lpasscc-sc7280.c > +++ b/drivers/clk/qcom/lpasscc-sc7280.c > @@ -118,12 +118,14 @@ static int lpass_cc_sc7280_probe(struct platform_de= vice *pdev) > goto destroy_pm_clk; > } > =20 > - lpass_regmap_config.name =3D "qdsp6ss"; > - desc =3D &lpass_qdsp6ss_sc7280_desc; > + if (!of_property_read_bool(pdev->dev.of_node, "qcom,adsp-pil-mode= ")) { > + lpass_regmap_config.name =3D "qdsp6ss"; > + desc =3D &lpass_qdsp6ss_sc7280_desc; > =20 > - ret =3D qcom_cc_probe_by_index(pdev, 0, desc); > - if (ret) > - goto destroy_pm_clk; > + ret =3D qcom_cc_probe_by_index(pdev, 0, desc); > + if (ret) > + goto destroy_pm_clk; > + } I noticed that we don't set any max_register on the regmap_config. Can you also do that in a patch before this patch? I think without that set you can oops the kernel by reading the debugfs file for the regmap. > =20 > lpass_regmap_config.name =3D "top_cc"; > desc =3D &lpass_cc_top_sc7280_desc;