Received: by 10.223.185.116 with SMTP id b49csp2631218wrg; Mon, 5 Mar 2018 06:18:32 -0800 (PST) X-Google-Smtp-Source: AG47ELvE9Mco3BSm0PisLG2doT8eVAe8NKSLEXm3tcpXIhb3BvzVOBVrnBtu1p2EAoof3bybjgRu X-Received: by 10.98.218.7 with SMTP id c7mr10630125pfh.162.1520259512391; Mon, 05 Mar 2018 06:18:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520259512; cv=none; d=google.com; s=arc-20160816; b=FfftJ7o8MBx94a+cGkOg2xmEL5Jh0s182ZmZWDnxOLgJCbBnsrq5feLEFAGEpDI4TI NwcJXIE8qgiEm8ieVGjdEfC8N2GWnb5GRps+f97y5ppZv9Abj+MVx59nyEWBw+Lok5nL dFjrqPv5sqWHOqC1/PCiBOnkEgFLbtzlHtpHKvpT7k8rXDbVxkqkYzyZ7F9uAiGf+SPO 5rZlgK8eVo5ajHSaDlXqMesRCF4O0J52FlSMeHR8kpvrW62KNyDSaE9ZdKayjOweDDTh rbF4GjtFYeyPMvmJN1KtTpQN7beWHtZklEhVA/Frr0PoM6OgfLISyaBjm2siuxWcvxuj WIPA== 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 :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=XNOx4cz75HlTNXc0/gIOSD2yLr1avCeB4KyxEge+jys=; b=PI6lhC1IE3as0y0cd602wWGfbhYmj1yDTeniNuB6V1bw8gHTHGKp1xguOVWhWnQvq4 A/6rsr3vo4lQ4RrZPZB0hR5BekoL8FL6ElHyaYnEsw19CLTeBO+YYdObzgBmVu1qxyZ/ qLFM0guM8+2iC91Usuf7yWKXmu8+lNW1Fg15vwdzbUEJ8D5TQr7aSchgQFRbyWijpBKo PGqNmqRv6marNe952VkOYtWfipy6hiXbW6qjLFU1hq9M9TU30mBqRj4+X7SU4ae/A6d+ h0ZgpEY3fr84AJWRUbMwGTwqogO12uzQdAaqJp/U8NJFifNUY3diQ2sMwAudKcyMi1wL qv6Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=kjKLT9Ql; 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 v22si8397800pgc.724.2018.03.05.06.18.17; Mon, 05 Mar 2018 06:18:32 -0800 (PST) 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=kjKLT9Ql; 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 S935138AbeCEN0K (ORCPT + 99 others); Mon, 5 Mar 2018 08:26:10 -0500 Received: from mail-vk0-f43.google.com ([209.85.213.43]:35125 "EHLO mail-vk0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935124AbeCEN0H (ORCPT ); Mon, 5 Mar 2018 08:26:07 -0500 Received: by mail-vk0-f43.google.com with SMTP id b65so9764064vka.2 for ; Mon, 05 Mar 2018 05:26:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XNOx4cz75HlTNXc0/gIOSD2yLr1avCeB4KyxEge+jys=; b=kjKLT9Ql0VLzGUIUQT6Yr8hVdCh9amHb3KjaP28J+irbdB94I5kIORQzDeDYqQ5vGa 6QOKsMUcY8fbfWCUZQoVpsJ7ZWReDSe+RCnoXx3rx5KYh8Wd0SZGbgMjoBSbDNgE01gd iM4W/CV0BZPbSwuounH1de2t8hZMGcsJ/6jfI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=XNOx4cz75HlTNXc0/gIOSD2yLr1avCeB4KyxEge+jys=; b=Mwo3quo6gUHMHnIUdRab4FHWbymZSrYMd3tIIs3kHJzqr/YVZycv3G/2rn4jqvksbK hwIyDaDYage6v6gx8xEtFn8hU9okEwernxCGQDTq//MbNOlsdb74bCNyVDxZjVFLTAr9 B7Y9hwQRpW/BhtxWQOhym+8j0VPrYJrpMXHsJwbM2k9nfMEMb5VwSX6WT+Ccu6VeTSTD FKfvaQsJk/zxd3xO9e5dytmE/TQjs0OclAksXcKE6g973nvIEVgBOnJFEkuM+zDQUqib dCKetpkNMYsDMhm7sUuo9LZZD7CU21yHG3T+0eDgpElALh3ek1HP8bh9Y7rZi//w/t0G ySBA== X-Gm-Message-State: APf1xPAJipq3CJtqfQQHq/XKGv2Hv68fcz1/iVLEXK3LhhyaPU62G12E NZLTcs+Fx/hObB6tbXpGMZ5JLojA+5k= X-Received: by 10.31.86.69 with SMTP id k66mr9428306vkb.127.1520256366701; Mon, 05 Mar 2018 05:26:06 -0800 (PST) Received: from mail-vk0-f41.google.com (mail-vk0-f41.google.com. [209.85.213.41]) by smtp.gmail.com with ESMTPSA id b18sm991163vka.38.2018.03.05.05.26.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Mar 2018 05:26:04 -0800 (PST) Received: by mail-vk0-f41.google.com with SMTP id z130so9770684vkd.0 for ; Mon, 05 Mar 2018 05:26:03 -0800 (PST) X-Received: by 10.31.99.130 with SMTP id x124mr9214406vkb.155.1520256363360; Mon, 05 Mar 2018 05:26:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.0.99 with HTTP; Mon, 5 Mar 2018 05:25:42 -0800 (PST) In-Reply-To: <20180302101050.6191-1-vivek.gautam@codeaurora.org> References: <20180302101050.6191-1-vivek.gautam@codeaurora.org> From: Tomasz Figa Date: Mon, 5 Mar 2018 22:25:42 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v8 0/5] iommu/arm-smmu: Add runtime pm/sleep support To: Vivek Gautam Cc: Joerg Roedel , Rob Herring , Mark Rutland , "Rafael J. Wysocki" , Robin Murphy , Will Deacon , Rob Clark , "open list:IOMMU DRIVERS" , devicetree@vger.kernel.org, Linux Kernel Mailing List , jcrouse@codeaurora.org, Stephen Boyd , Sricharan R , Marek Szyprowski , Archit Taneja , linux-arm-msm 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 Vivek, On Fri, Mar 2, 2018 at 7:10 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. > > It 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]. > > After another round of discussion [3], we now finally seem to be > in agreement to add a flag based on compatible, a flag that would > indicate if a particular implementation of arm-smmu supports > runtime pm or not. > 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. > The patch that exported couple of pm_runtime suppliers APIS, viz. > pm_runtime_get_suppliers(), and pm_runtime_put_suppliers() can be > dropped since we don't have a user now for these APIs. > Thanks Rafael for reviewing the changes, but looks like we don't > need to export those APIs for some more time. :) > > Previous version of this patch series is @ [5]. Thanks for addressing my comments. There is still a bit of space for improving the granularity of power management, as far as I understood how it works on SDM845 correctly, but as a first step, this should at least let things work. Reviewed-by: Tomasz Figa Best regards, Tomasz