Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp7447731rwl; Tue, 10 Jan 2023 00:33:21 -0800 (PST) X-Google-Smtp-Source: AMrXdXsqOICiwEwww3B0LXosAAP3rWneiWH2DVqiGWEJEPC5F1S0hSeXVyC8piXRO4It23vCAt72 X-Received: by 2002:a17:903:2ca:b0:192:d2d4:d6a8 with SMTP id s10-20020a17090302ca00b00192d2d4d6a8mr31902358plk.6.1673339601184; Tue, 10 Jan 2023 00:33:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673339601; cv=none; d=google.com; s=arc-20160816; b=WQw1KCqeudkeFh5XvO5XtbANLK+zvnYzw/39y6iKQ82qXRMDdPECETWWoLP6NcG7Fl xr5oxUVeH+loVZNqnU2RaQMmWIAc/lsBFLT5NxkzqQMg44w8sXxY+YgT5oOjDlNx+M7R HHAPImxWRkIYt1hjZI1zJR5s3QoRdR73iy+S7Mez+8z0Bt4lskeQtkv72B4FmCTcu+yF 9MB1icarQktTEsDsoSTNx2vY+ngLZVldQdiHwK8tYZfp3pTmmVZl1FqQP/mSOtFDTIWE bwEhlGXBejAE6K5el7IpeaB1kDut7r1UMh1gKtSGEtgoWpnSjFZGNmk2+jxI/Bzv5lC4 b52A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=BvmrsO2wFPW4UkzHnUm2F4oYnGhEQj0M0Tj+WlrTJ2s=; b=dZwH5zoh8QSCFKtiWrXhBoU8HHpS9Q/wC+QajIcPrP1tnPIHRFmkMuLpVf0aLvr1bU qmqdFrRHLjvnBWTNjH8PBkNi2s6NLUo4AF0EG0UwadZmQcrowDtn16XmR1N8Xk8KbGER zHQrS09v7NVxfVnniMPmZ5ILM2wXF4QHmrZ6mnzLOTHXV8ODs2Nrl62J4DVSO4oMvoRg qRLmbW4TW1Wabneb/jOlw65MU6wNAbtooEyP+Cqn1d5gSD1R08Kx6TGrpTR+9V2dTIs3 tXiEDlwqBQbDrppnV3iSBxDjkkrWKwmt1m8Z0kA7adQzkn6wwpbJJfU8fZuYEfOuH24m IcPg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcdkim header.b="h/rucVaS"; 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=quicinc.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id t18-20020a170902d15200b00189655d7144si7691855plt.161.2023.01.10.00.33.14; Tue, 10 Jan 2023 00:33:21 -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=@quicinc.com header.s=qcdkim header.b="h/rucVaS"; 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=quicinc.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230020AbjAJIO2 (ORCPT + 53 others); Tue, 10 Jan 2023 03:14:28 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46524 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237523AbjAJIOQ (ORCPT ); Tue, 10 Jan 2023 03:14:16 -0500 Received: from alexa-out-sd-01.qualcomm.com (alexa-out-sd-01.qualcomm.com [199.106.114.38]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9501664CC; Tue, 10 Jan 2023 00:14:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; i=@quicinc.com; q=dns/txt; s=qcdkim; t=1673338454; x=1704874454; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=BvmrsO2wFPW4UkzHnUm2F4oYnGhEQj0M0Tj+WlrTJ2s=; b=h/rucVaSrBb/5fcqa3i1Yp4Yf+3NSxhqtaD8Rl4+3aGSlHDc+/Sv45Id QqucjQH19u43sws7AA/d0mC0GpbXpTZf8UXhz0Q6/T4uRHArlP7DcsM80 IS2F7JdIy7PaK4bs4WHAZCs7qtU41un35ZhZog7tlbDeS81J9RHkRBwpS M=; Received: from unknown (HELO ironmsg-SD-alpha.qualcomm.com) ([10.53.140.30]) by alexa-out-sd-01.qualcomm.com with ESMTP; 10 Jan 2023 00:14:14 -0800 X-QCInternal: smtphost Received: from nasanex01b.na.qualcomm.com ([10.46.141.250]) by ironmsg-SD-alpha.qualcomm.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Jan 2023 00:14:13 -0800 Received: from quicinc.com (10.80.80.8) by nasanex01b.na.qualcomm.com (10.46.141.250) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.36; Tue, 10 Jan 2023 00:14:12 -0800 Date: Tue, 10 Jan 2023 00:14:11 -0800 From: Guru Das Srinagesh To: Sibi Sankar CC: , , , , , , , , Subject: Re: [PATCH V7 2/2] firmware: qcom: scm: Add wait-queue handling logic Message-ID: <20230110081410.GB2082@quicinc.com> References: <20230110063745.16739-1-quic_sibis@quicinc.com> <20230110063745.16739-3-quic_sibis@quicinc.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20230110063745.16739-3-quic_sibis@quicinc.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01b.na.qualcomm.com (10.46.141.250) To nasanex01b.na.qualcomm.com (10.46.141.250) X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,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 On Jan 10 2023 12:07, Sibi Sankar wrote: ... > +static int __scm_smc_do_quirk_handle_waitq(struct device *dev, struct arm_smccc_args *waitq, > + struct arm_smccc_res *res) > +{ > + int ret; > + struct arm_smccc_args resume; > + u32 wq_ctx, smc_call_ctx, flags; > + struct arm_smccc_args *smc = waitq; > + > + do { > + __scm_smc_do_quirk(smc, res); > + > + if (res->a0 == QCOM_SCM_WAITQ_SLEEP) { > + wq_ctx = res->a1; > + smc_call_ctx = res->a2; > + flags = res->a3; > + > + if (!dev) > + return -EPROBE_DEFER; > + > + ret = qcom_scm_lookup_completion(wq_ctx); I see that this function has been created in response to Bjorn's comment [1] about avoiding the dev_get_drvdata() call, but I would prefer to not use this function as it hides the fact that the wait_for_completion() is occurring here. Knowing where the waiting is happening is useful not just for understanding code flow but also for debugging issues in the future. ... > +static struct completion *qcom_scm_lookup_wq(struct qcom_scm *scm, u32 wq_ctx) > +{ This function is called qcom_scm_lookup_wq() but there is no looking up occurring here. Could this comment be added for context? /* FW currently only supports a single wq_ctx (zero). * TODO: Update this logic to include dynamic allocation and lookup of * completion structs when FW supports more wq_ctx values. */ > + /* assert wq_ctx is zero */ > + if (wq_ctx != 0) { > + dev_err(scm->dev, "No waitqueue found for wq_ctx %d\n", wq_ctx); > + return ERR_PTR(-EINVAL); > + } > + > + return &scm->waitq_comp; > +} > + ... [1] https://lore.kernel.org/lkml/20221208221125.bflo7unhcrgfsgbr@builder.lan/