Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp2872426rwl; Mon, 27 Mar 2023 06:30:06 -0700 (PDT) X-Google-Smtp-Source: AKy350aa2sd6ONAj3lqc46ffiQp49BIkHUbbsHVdJIbXf1zkbiMH02/Zv+xlpr7AfplTQKnRVIyX X-Received: by 2002:a17:907:11cf:b0:93d:7ad:a954 with SMTP id va15-20020a17090711cf00b0093d07ada954mr12401220ejb.37.1679923806484; Mon, 27 Mar 2023 06:30:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1679923806; cv=none; d=google.com; s=arc-20160816; b=rMS/GPGykj4LZwcIybR0srFluIryE42+VoJ6eaAa/pzvpjfqIt86DRf6qB8/v1g8O3 xHNq16UAXu7LXj+QaQFPLpCQyN0dxIK83w/BTPWGGefbDign5FDQPd1RSf1shS7DG/mC l/1/YpFnen8Adur/qzcaLB4BFRDqBfz4vkP2Ny3yYewixpZO6UpAh4zbB7PSTlLiYFYg DGEsPjB8YVOBBnU94zuUH9aWVofXyBE45O6KTQFVUZto0IO8Yp6HWkcu8hHsYWVXdzCs 4fVj+oSme0gLDUxfBeMRtCPYPtzKreimXlQOAfJBmCDECGtKxjaijigtK0XvbK++Jsvx 0yLQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=lWhJCR0e9BREp+MV3M7Q2CYC5NXfwPA3LDDgjVjrKrg=; b=o96hJight2JGjnIpfEG4WyFVAbKtC2DbD+sy2FzOKlxL7En6k5thvUC0wFjYjH3Pn8 gftrJGoL7NX1BtbMRiowUhTM9Le9htJ07BBRU6ct+P7w5iy7j9NDHG8XIT1mG66psDas 8pFTbqUcWlCNqdfHfcFPWljhmebPIpRTu22IQ9U2jyRiutfgJJq2M3/G8c/o1ZzXaopq IKIhotXA0yEwCC1DsMZ+cRdmjuIMr9lb1IOrPiFfbCnsqXlsWFkyytKJ6yfLyBBtn92/ IVnPI8eHTCskoutkI9KkIVbQxAV7CNLkosQSZNI4M/NoPWwZ0I44q2nYDLeFv6inN9/c YjNw== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id mp28-20020a1709071b1c00b009333705a9edsi7168579ejc.746.2023.03.27.06.29.41; Mon, 27 Mar 2023 06:30:06 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232815AbjC0N3B (ORCPT + 99 others); Mon, 27 Mar 2023 09:29:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46424 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232127AbjC0N2e (ORCPT ); Mon, 27 Mar 2023 09:28:34 -0400 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 553A55260; Mon, 27 Mar 2023 06:28:33 -0700 (PDT) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 214201042; Mon, 27 Mar 2023 06:29:17 -0700 (PDT) Received: from bogus (unknown [10.57.52.160]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id F07183F663; Mon, 27 Mar 2023 06:28:29 -0700 (PDT) Date: Mon, 27 Mar 2023 14:27:55 +0100 From: Sudeep Holla To: "lihuisong (C)" Cc: robbiek@xsightlabs.com, linux-acpi@vger.kernel.org, Sudeep Holla , linux-kernel@vger.kernel.org, rafael@kernel.org, rafael.j.wysocki@intel.com, wanghuiqiang@huawei.com, zhangzekun11@huawei.com, wangxiongfeng2@huawei.com, tanxiaofei@huawei.com, guohanjun@huawei.com, xiexiuqi@huawei.com, wangkefeng.wang@huawei.com, huangdaode@huawei.com Subject: Re: [PATCH v2 1/2] mailbox: pcc: Add support for platform notification handling Message-ID: <20230327132755.tzflaqxp2cwsgs63@bogus> References: <20221016034043.52227-1-lihuisong@huawei.com> <20230314111135.16520-1-lihuisong@huawei.com> <20230314111135.16520-2-lihuisong@huawei.com> <20230327113057.cc2ufila5z25mgic@bogus> <4bf0da8a-008a-7363-d1cd-53e4296e3436@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4bf0da8a-008a-7363-d1cd-53e4296e3436@huawei.com> X-Spam-Status: No, score=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE 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 On Mon, Mar 27, 2023 at 08:25:04PM +0800, lihuisong (C) wrote: > > 在 2023/3/27 19:30, Sudeep Holla 写道: > > On Tue, Mar 14, 2023 at 07:11:34PM +0800, Huisong Li wrote: > > > Currently, PCC driver doesn't support the processing of platform > > > notification for type 4 PCC subspaces. > > > > > > According to ACPI specification, if platform sends a notification > > > to OSPM, it must clear the command complete bit and trigger platform > > > interrupt. OSPM needs to check whether the command complete bit is > > > cleared, clear platform interrupt, process command, and then set the > > > command complete and ring doorbell to the Platform. > > > > > > Let us stash the value of the pcc type and use the same while processing > > > the interrupt of the channel. We also need to set the command complete > > > bit and ring doorbell in the interrupt handler for the type 4 channel to > > > complete the communication flow after processing the notification from > > > the Platform. > > > > > > Signed-off-by: Huisong Li > > > --- > > > drivers/mailbox/pcc.c | 50 +++++++++++++++++++++++++++++++++++-------- > > > 1 file changed, 41 insertions(+), 9 deletions(-) > > > > > > diff --git a/drivers/mailbox/pcc.c b/drivers/mailbox/pcc.c > > > index 105d46c9801b..a0a87c480d8b 100644 > > > --- a/drivers/mailbox/pcc.c > > > +++ b/drivers/mailbox/pcc.c > > > @@ -91,6 +91,7 @@ struct pcc_chan_reg { > > > * @cmd_update: PCC register bundle for the command complete update register > > > * @error: PCC register bundle for the error status register > > > * @plat_irq: platform interrupt > > > + * @type: PCC subspace type > > > */ > > > struct pcc_chan_info { > > > struct pcc_mbox_chan chan; > > > @@ -100,12 +101,15 @@ struct pcc_chan_info { > > > struct pcc_chan_reg cmd_update; > > > struct pcc_chan_reg error; > > > int plat_irq; > > > + u8 type; > > > }; > > > #define to_pcc_chan_info(c) container_of(c, struct pcc_chan_info, chan) > > > static struct pcc_chan_info *chan_info; > > > static int pcc_chan_count; > > > +static int pcc_send_data(struct mbox_chan *chan, void *data); > > > + > > > /* > > > * PCC can be used with perf critical drivers such as CPPC > > > * So it makes sense to locally cache the virtual address and > > > @@ -221,6 +225,34 @@ static int pcc_map_interrupt(u32 interrupt, u32 flags) > > > return acpi_register_gsi(NULL, interrupt, trigger, polarity); > > > } > > > +static bool pcc_mbox_cmd_complete_check(struct pcc_chan_info *pchan) > > > +{ > > > + u64 val; > > > + int ret; > > > + > > > + ret = pcc_chan_reg_read(&pchan->cmd_complete, &val); > > > + if (ret) > > > + return false; > > > + > > > + if (!pchan->cmd_complete.gas) > > > + return true; > > > + > > > + /* > > > + * Judge if the channel respond the interrupt based on the value of > > > + * command complete. > > > + */ > > > + val &= pchan->cmd_complete.status_mask; > > [super nit] Would prefer an blank line here. > > > Yeah, it would be better if there is an blank line here. > Is it necessary to send v3 for this? Let us see once you have Robbie's tested-by. Depending on who picks up we can check with them. -- Regards, Sudeep