From mboxrd@z Thu Jan 1 00:00:00 1970 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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id CF511E7B5FB for ; Wed, 4 Oct 2023 12:15:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=C0sIXIuuwojLgisg4gBxxJmZR52Cwq+Ix3tIoShtd+0=; b=o717dLysvmwBRm A3ngy7mcWqNfufDu6Vz51rfPPNPgNhqdl9fz00UCIWJmMX9RJXUOHPuQyWjU337pRzo6Iz297bzE3 fE3t4RqwnLQLgVvK2OOulBRkAAfbCkPe/EZrwqueWXjOt7g0B0cjD5h3JV+oyxat74/nFLyyt0kKa b5AQmbZmFlooaY/GP8vJl+f0/6cXuOTV2RovapObAZnrSbcbSawDMP3/+SK4xq06+8dRwudKtxUm4 K/UBz7oQmuM+YVBXhuBvosTt1F5dxC4iPZmox6N2Mq5K+ogla0+bckBAgNzqTwsMGGLcK2YXtsX/z +PL3WX3xHqfypN1X0CkQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qo0mc-00Ha5J-02; Wed, 04 Oct 2023 12:15:18 +0000 Received: from sin.source.kernel.org ([2604:1380:40e1:4800::1]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qo0mZ-00Ha4l-08 for linux-arm-kernel@lists.infradead.org; Wed, 04 Oct 2023 12:15:16 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id 3F10BCE1BF9; Wed, 4 Oct 2023 12:15:13 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id EFCF7C433C8; Wed, 4 Oct 2023 12:15:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1696421712; bh=xIXg9Ur+n+C90t8y/vlj+q0jEq7ejIRCVP+YY/RGSfU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=j0X2Kj9N2cUtkmGzDKcacXgLyCyXLakHTgfWDMWA28EdwTu6yCV6Y+LK4L9kIXjhu kLMXt3zTQwBT4VFKjACSQfIlaLPUG1KMC4gHd53jwG24XNbJoR5+pMOFiRl+Dq8nwZ u2thoh503Dwfy9KWRiCIOwYz+9GpS/bLmH5GHnU4= Date: Wed, 4 Oct 2023 14:15:09 +0200 From: Greg KH To: Jay Buddhabhatti Cc: michal.simek@amd.com, tanmay.shah@amd.com, nava.kishore.manne@amd.com, ben.levinsky@amd.com, robh@kernel.org, dhaval.r.shah@amd.com, marex@denx.de, izhar.ameer.shaikh@amd.com, arnd@arndb.de, ruanjinjie@huawei.com, mathieu.poirier@linaro.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 4/6] drivers: soc: xilinx: Fix error message on SGI registration failure Message-ID: <2023100425-chivalry-pound-78d0@gregkh> References: <20231004094116.27128-1-jay.buddhabhatti@amd.com> <20231004094116.27128-5-jay.buddhabhatti@amd.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20231004094116.27128-5-jay.buddhabhatti@amd.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231004_051515_253388_73738340 X-CRM114-Status: GOOD ( 22.62 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Oct 04, 2023 at 02:41:14AM -0700, Jay Buddhabhatti wrote: > Failure to register SGI for firmware event notification is non-fatal error > when feature is not supported by other modules such as Xen and TF-A. Add > _info level log message for such special case. > > Also add XST_PM_INVALID_VERSION error code and map it to -EOPNOSUPP Linux > kernel error code. If feature is not supported or EEMI API version is > mismatch, firmware can return XST_PM_INVALID_VERSION = 4 or > XST_PM_NO_FEATURE = 19 error code. > > Co-developed-by: Tanmay Shah > Signed-off-by: Tanmay Shah > Signed-off-by: Jay Buddhabhatti > --- > drivers/firmware/xilinx/zynqmp.c | 4 +++- > drivers/soc/xilinx/xlnx_event_manager.c | 7 ++++++- > include/linux/firmware/xlnx-zynqmp.h | 1 + > 3 files changed, 10 insertions(+), 2 deletions(-) > > diff --git a/drivers/firmware/xilinx/zynqmp.c b/drivers/firmware/xilinx/zynqmp.c > index 00ea2508f692..de09d77cf1e4 100644 > --- a/drivers/firmware/xilinx/zynqmp.c > +++ b/drivers/firmware/xilinx/zynqmp.c > @@ -92,6 +92,8 @@ static int zynqmp_pm_ret_code(u32 ret_status) > return 0; > case XST_PM_NO_FEATURE: > return -ENOTSUPP; > + case XST_PM_INVALID_VERSION: > + return -EOPNOTSUPP; > case XST_PM_NO_ACCESS: > return -EACCES; > case XST_PM_ABORT_SUSPEND: > @@ -379,7 +381,7 @@ int zynqmp_pm_register_sgi(u32 sgi_num, u32 reset) > > ret = zynqmp_pm_invoke_fn(TF_A_PM_REGISTER_SGI, sgi_num, reset, 0, 0, > 0, NULL); > - if (!ret) > + if (ret != -EOPNOTSUPP && !ret) > return ret; > > /* try old implementation as fallback strategy if above fails */ > diff --git a/drivers/soc/xilinx/xlnx_event_manager.c b/drivers/soc/xilinx/xlnx_event_manager.c > index 38cfc161a713..bfa5cf4a0cab 100644 > --- a/drivers/soc/xilinx/xlnx_event_manager.c > +++ b/drivers/soc/xilinx/xlnx_event_manager.c > @@ -653,7 +653,12 @@ static int xlnx_event_manager_probe(struct platform_device *pdev) > > ret = zynqmp_pm_register_sgi(sgi_num, 0); > if (ret) { > - dev_err(&pdev->dev, "SGI %d Registration over TF-A failed with %d\n", sgi_num, ret); > + if (ret == -EOPNOTSUPP) > + dev_info(&pdev->dev, "PM firmware event notification not supported\n"); Why is this "info"? Why not error? And what is userspace supposed to do with this information if it sees it? thanks, greg k-h _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel