Received: by 10.213.65.68 with SMTP id h4csp2165851imn; Sun, 8 Apr 2018 21:26:30 -0700 (PDT) X-Google-Smtp-Source: AIpwx48FsQ8hAcEMTui6zJXfxeD+aO9cI52mDpF1FSGlBZJ3OZHdqCKFoZsPp6A1M3x2w/fDhAMr X-Received: by 2002:a17:902:aa03:: with SMTP id be3-v6mr14152452plb.299.1523247990679; Sun, 08 Apr 2018 21:26:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523247990; cv=none; d=google.com; s=arc-20160816; b=OOJmk53F4Zs93YUsO7XcLIAeBtzhKbLi3HftMnp+4uKPd3D+B7QFyAwc/Hb76wFeXl Kb6x+Y30N7HtrO8EneAeKDxHe0Ide3r2ggpSrmSJpHUoO9Z9nxIfKjv3T3GhaWKV2fWp JO3ZSoBugThHxdLW9xmF67sitPAacCL91/YlQaRVqoeXbOLNE3gHlk+9rQZbuIyX/Bn6 fdodRAfwe/qjxE97DO2Ee8vQE6Re/DND6pqp13TD3A/mCg/y94IH0qI0QJX+O3Jp0jB3 CikJdMU8tVjDiZKwPf8JEtoy5S88WBXqDJFmIu5l2mwCbkld0S/pKEX21jRU6vt88VZs 2Pgw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature :arc-authentication-results; bh=JNsk8MZ3X5ltyYd6plA7v+YP3VofQg/3DOHv+TbFdg8=; b=DBD5DBhoSxqrbciMDGto9nEd5JCH2bLI83otuVeK35DdoqCWTKpBqK41/cH9Hma9/S VtSG/RpClEUFpuqR4s53dh9+0wjJs88rWdHXpA7zsKVeGTWYMaS+fpslBCE26k94I1MU DqfNj0IrfQGqwTpGYOD3Pajbr0kS53zD+eKCp/tYQ/yIkaHqcsa2mS3yGEc1IfGVveZ0 7M1gSdFN1r1/6UJTzXpB/+Xah3ESSFKkOTxSuN3Xcic/FDvi7q7PXtwdIqlrDccms6w3 nqYImY5bvCOEvTQUNz1Inv/rhEpR7hcXkUX0B5nxCv7HmJ/H2BQQXWAr6QE485UooGeA x3kQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=W5sdZdRh; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n3si1448833pgq.510.2018.04.08.21.25.53; Sun, 08 Apr 2018 21:26:30 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=W5sdZdRh; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751676AbeDIEWY (ORCPT + 99 others); Mon, 9 Apr 2018 00:22:24 -0400 Received: from mail-vk0-f47.google.com ([209.85.213.47]:43398 "EHLO mail-vk0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751464AbeDIEWW (ORCPT ); Mon, 9 Apr 2018 00:22:22 -0400 Received: by mail-vk0-f47.google.com with SMTP id v134so3948993vkd.10 for ; Sun, 08 Apr 2018 21:22:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JNsk8MZ3X5ltyYd6plA7v+YP3VofQg/3DOHv+TbFdg8=; b=W5sdZdRhNHpMh3i/GiGnw6GpOe53bN6eTMVVksrzx7xjkhVNtJ1lNAPoMzyyTCP8P5 MYg9tPXvbYrKTLtqbXzr1xEuq3Pd76asomnLkwgMR2L7X2v2WRTzX5fLntWUdrD9aWFC DjmDb6myH2FogKa2KLjlEcH1QtWpswBX4OrZg= 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; bh=JNsk8MZ3X5ltyYd6plA7v+YP3VofQg/3DOHv+TbFdg8=; b=oDZDM9++UJV4Nok1RK1DK2wXjgLlcZUZWbtORoe9jxY8kPJKTwY6lNKmB0XDAM5lIl D9CE/4fe/ILVidIwCl1A7dd1ICgsV5groXRLmZ7BLIcUoNOmAMPQAFQxKWZ4Se9B0RYc /LpOQ8rIzF2l0jj6eaBs/9knU04uYEKB1n1ir9ViHZd2SeCBkgdWo9dvommVCo+Hdte/ 5+HOILA6Nba+dQybOA6l3RIhPhsYUvWHNJZlcQ1gdeI95qa2CIIMRsYZnn+OqeP8sxXE LRvKA+ePuLoMQYFpdvlQ2zIFVXI8npNslt2CUHdFPHV0oknWKLdMTCkid34xhMm27xaR 9grw== X-Gm-Message-State: ALQs6tAne4F/tZlX9PZ5CKTKzNJZoE9UOVOO/pBZuCDSDuEmBAwhi161 54qht49wJu3D9DPYuPfZ3X9DMTInfKQ= X-Received: by 10.31.49.132 with SMTP id x126mr10270538vkx.75.1523247741624; Sun, 08 Apr 2018 21:22:21 -0700 (PDT) Received: from mail-vk0-f52.google.com (mail-vk0-f52.google.com. [209.85.213.52]) by smtp.gmail.com with ESMTPSA id q71sm3481329vke.6.2018.04.08.21.22.19 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 08 Apr 2018 21:22:20 -0700 (PDT) Received: by mail-vk0-f52.google.com with SMTP id n124so3958993vkd.6 for ; Sun, 08 Apr 2018 21:22:19 -0700 (PDT) X-Received: by 10.31.188.13 with SMTP id m13mr22596622vkf.86.1523247739504; Sun, 08 Apr 2018 21:22:19 -0700 (PDT) MIME-Version: 1.0 References: <20180322102204.14760-1-vivek.gautam@codeaurora.org> In-Reply-To: <20180322102204.14760-1-vivek.gautam@codeaurora.org> From: Tomasz Figa Date: Mon, 09 Apr 2018 04:22:09 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v11 0/4] iommu/arm-smmu: Add runtime pm/sleep support To: Robin Murphy , Will Deacon Cc: "list@263.net:IOMMU DRIVERS , Joerg Roedel ," , Rob Herring , Mark Rutland , "list@263.net:IOMMU DRIVERS , Joerg Roedel ," , devicetree@vger.kernel.org, Linux Kernel Mailing List , "Rafael J. Wysocki" , Rob Clark , Stephen Boyd , Sricharan R , Marek Szyprowski , Archit Taneja , Lukas Wunner , linux-arm-msm , Vivek Gautam Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Will, Robin, On Thu, Mar 22, 2018 at 7:22 PM Vivek Gautam wrote: > This series provides the support for turning on the arm-smmu's > clocks/power domains using runtime pm. This is done using the > recently introduced device links patches, which lets the smmu's > runtime to follow the master's runtime pm, so the smmu remains > powered only when the masters use it. > As not all implementations support clock/power gating, we are checking > for a valid 'smmu->dev's pm_domain' to conditionally enable the runtime > power management for such smmu implementations that can support it. > This series also adds support for Qcom's arm-smmu-v2 variant that > has different clocks and power requirements. > Took some reference from the exynos runtime patches [1]. > With conditional runtime pm now, we avoid touching dev->power.lock > in fastpaths for smmu implementations that don't need to do anything > useful with pm_runtime. > This lets us to use the much-argued pm_runtime_get_sync/put_sync() > calls in map/unmap callbacks so that the clients do not have to > worry about handling any of the arm-smmu's power. > Previous version of this patch series is @ [5]. > [v11] > * Some more cleanups for device link. We don't need an explicit > delete for device link from the driver, but just set the flag > DL_FLAG_AUTOREMOVE. > device_link_add() API description says - > "If the DL_FLAG_AUTOREMOVE is set, the link will be removed > automatically when the consumer device driver unbinds." > * Addressed the comments for 'smmu' in arm_smmu_map/unmap(). > * Dropped the patch [10] that introduced device_link_del_dev() API. As far as I can see, this version addresses all the earlier comments. Do you think this is something that you could apply? Best regards, Tomasz