Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2574961pxb; Thu, 11 Feb 2021 16:37:47 -0800 (PST) X-Google-Smtp-Source: ABdhPJzPUQ7aea8Lp2dQmZbhRWSmvC7wR7g2ZsBxQwKbYnSctYPrgJg0de1Q7VXpF/RRGr1fMRg0 X-Received: by 2002:a17:906:1c1b:: with SMTP id k27mr360677ejg.402.1613090267271; Thu, 11 Feb 2021 16:37:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613090267; cv=none; d=google.com; s=arc-20160816; b=ihPTdcVJVdm4HGTf9DHeY6hc3132oCDNwhUVmM0wEIZFjoZRrjB/ge57pT8coO2L9Y uA6eU7TPKiQDmITKsxmQ7FkNDI0F2DE/5bFgMzJb5iEk5jkMkgKaBY7x7zy5xC9kU9Eh +nTe+wqVFND3I39rKdptPI3BR9zAQsDW2Eortw+um/id3RBD9yFh2UhjnibznxTdDEhx jW2HPq8YeI8S7GXfdn7UeqfJpRCw2bMMlh4Vl00BF8GCNdpdmKlVhE86UvnOToVxdkiH pe5y3Zy+bvA865d9HsxMtYoTd81Ww/nDET0feRM3zaE5jUrOP77x6eup8CgdYQiQG1YM W9sQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=3TjKSEVHUCuYyh3OcPWvBxul+LPuyfEayRgdZEUem+4=; b=w7FQUtDTXftb+0c8xI8NIR69kNsXc4PnVhPBHW5jSRnwsoTVpg9RO3TPAn5MMFI3Ns rZGMY+rbt+1tsXZ/xpF+X2oZ86d+iySDmpI1GuOXwssy9xx+IqjzSFukyqCGLwoxbHm3 X2l3HO4Jtk3R886Z1bUHVAt6uhuvaVIZTDlkXqmn97RmBMVHgph0iCjxAwmMtm84+N4c 332+p2WnUSLr0Ilzx7+EgCDcz7NAswHy58ktx3zOPkmFxQvoS3BpNKxVcWwNxWt0zCtH tEZtEhExLhXJaZv/1fKsrqQhXUo8mgvS9FvJHEtk5FrElEC2NDOvvTxY/q90wvOCzGGS haNw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nigauri-org.20150623.gappssmtp.com header.s=20150623 header.b=AdCz+zJe; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z9si5070908ejm.194.2021.02.11.16.37.24; Thu, 11 Feb 2021 16:37:47 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@nigauri-org.20150623.gappssmtp.com header.s=20150623 header.b=AdCz+zJe; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229675AbhBKXT1 (ORCPT + 99 others); Thu, 11 Feb 2021 18:19:27 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40884 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229625AbhBKXT0 (ORCPT ); Thu, 11 Feb 2021 18:19:26 -0500 Received: from mail-oo1-xc29.google.com (mail-oo1-xc29.google.com [IPv6:2607:f8b0:4864:20::c29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 074D1C061574 for ; Thu, 11 Feb 2021 15:18:46 -0800 (PST) Received: by mail-oo1-xc29.google.com with SMTP id s23so808687oot.12 for ; Thu, 11 Feb 2021 15:18:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nigauri-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=3TjKSEVHUCuYyh3OcPWvBxul+LPuyfEayRgdZEUem+4=; b=AdCz+zJeBhRM1ldCeGYNjIfs0hIYrhDGMgLvzyLTV0xYtLD5v40wAQs/kzBfVzOcJ9 klndgb+X00mhlhyfdpckBCuFHDuYtBo9GfLCX+rdCY8ddTttGe21zvvp97kyPLDOPHmW RgPAb7IF6rJKxKYhVbqocsky2VLCGIWx31B913SRt5W7Uq5kgfylDC2y5DC/oK6PI50i BFd/X99hFeVNHEZXAZIFMluT7ARvC7j2+nFdV/O2mTJ9pE4dAMYsKnqTxWOs+4RE9dik aAzOJDCwAY7Es95He1aInqbyMh8gKcaFjJak6Ya44QaVqe2oYnECbNXld/CKDV6XjJ38 aSsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=3TjKSEVHUCuYyh3OcPWvBxul+LPuyfEayRgdZEUem+4=; b=lR98ZQQXBI/APCHzYJpxPfAaYyQFLuf1SJFnm26460x58DCYCuGYvm92SpbjNAHnQ8 B8HwtPjujVs2H69O1RMkBACeeyjyoBYHt3ezIZ09E/+8J6UxnTCIhl9kywSnIeatHfQW pLvq1D5v5AdXrjQs5soQy/VnM5SHbChcWhtu5MHeSZd0REbgFCz84jOpFJO/NPtsRgyi 0jHo3I1x2TwfWh5NSsu+TupqppZ2kOQ0takW1Jtt/SYvX0Rd/+0dR/+xQVOvLVG1RThV LWvHP3asDJIyyYqyj55cIbCLqD/l+HOZjOqy52dEtflnaBMO5r+EKeY52+I+PTpQBqeV HRTg== X-Gm-Message-State: AOAM532TZdzbCK9x/7TJKHUB/KAmZz67vhHUXzFSnlOHxshker8b/lWg c8AdCz3suuTrHiST46wsKx0PWR4fSJKNkbOm6Gm0HCPaQ2zI X-Received: by 2002:a4a:c896:: with SMTP id t22mr201496ooq.8.1613085525473; Thu, 11 Feb 2021 15:18:45 -0800 (PST) MIME-Version: 1.0 References: <20210131143033.7441-1-iwamatsu@nigauri.org> In-Reply-To: From: Nobuhiro Iwamatsu Date: Fri, 12 Feb 2021 08:18:19 +0900 Message-ID: Subject: Re: [PATCH] firmware: xilinx: Remove zynqmp_pm_get_eemi_ops() in IS_REACHABLE(CONFIG_ZYNQMP_FIRMWARE) To: Michal Simek Cc: linux ARM , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Thanks for your review. 2021=E5=B9=B42=E6=9C=881=E6=97=A5(=E6=9C=88) 19:08 Michal Simek : > > Hi, > > On 1/31/21 3:30 PM, Nobuhiro Iwamatsu wrote: > > zynqmp_pm_get_eemi_ops() was removed in commit 4db8180ffe7c: "Firmware:= xilinx: > > Remove eemi ops for fpga related APIs", but not in IS_REACHABLE(CONFIG_= ZYNQMP_FIRMWARE). > > This removed zynqmp_pm_get_eemi_ops() in IS_REACHABLE(CONFIG_ZYNQMP_FIR= MWARE), and also > > modify the documentation for this driver. > > > > Fixes: 4db8180ffe7c ("firmware: xilinx: Remove eemi ops for fpga relate= d APIs") > > Signed-off-by: Nobuhiro Iwamatsu > > --- > > Documentation/driver-api/xilinx/eemi.rst | 27 +----------------------- > > include/linux/firmware/xlnx-zynqmp.h | 5 ----- > > 2 files changed, 1 insertion(+), 31 deletions(-) > > > > diff --git a/Documentation/driver-api/xilinx/eemi.rst b/Documentation/d= river-api/xilinx/eemi.rst > > index 9dcbc6f18d75df..53416d25d309a8 100644 > > --- a/Documentation/driver-api/xilinx/eemi.rst > > +++ b/Documentation/driver-api/xilinx/eemi.rst > > @@ -19,32 +19,7 @@ device to issue or respond to power management reque= sts. > > EEMI ops is a structure containing all eemi APIs supported by Zynq MPS= oC. > > The zynqmp-firmware driver maintain all EEMI APIs in zynqmp_eemi_ops > > structure. Any driver who want to communicate with PMC using EEMI APIs > > The whole paragraph should be tuned. I would leave here just > > "Any driver who want to communicate with PMC using EEMI APIs > use the functions provided for each function." > > Because there is no reference to any eemi ops structure. > > The rest looks good to me. Thank you. I will add your point to the commit log and resend. Best regards, Nobuhiro --=20 Nobuhiro Iwamatsu iwamatsu at {nigauri.org / debian.org} GPG ID: 40AD1FA6