Received: by 10.223.185.116 with SMTP id b49csp3267279wrg; Mon, 12 Feb 2018 23:46:04 -0800 (PST) X-Google-Smtp-Source: AH8x226EzDst7rAG5exq+Mt8OP4/dLuAVgDtAe5mk8cSjm8Bt+gJaalkLsPjJ/ZfOauERiCfi7Aj X-Received: by 10.98.8.141 with SMTP id 13mr345306pfi.213.1518507964382; Mon, 12 Feb 2018 23:46:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518507964; cv=none; d=google.com; s=arc-20160816; b=Haw2bpsck04Eleoze6O+qBPg8UGKUVIcJftKkHBv60J3U1z7lDFlHxu1FIOP6lsDHP WOXh251h9boeBPFNmfzlki224ie+eBraJ7lWJzud5HrUUwj12911+RVy81nqIEmRDCP8 LTgpcDNoGHvDYhu2l77SBWEKYgbMr5FjVFQB7npjOeT5O3+W2JHjV1nubrj4wizqEkLm k/IsVEDTYrkYlHxQo9PKNKyZZi6ho3V6IVK2KWrEpAEeOKM+Hv+8N06RdKjHlsXeDuOO Heu/V70ZTGr5hzOHwveLI1dsZoFHODnKtNU9Uu+MYKucgxj01mppBoKYoaSafrbpjbzM 9ziA== 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=V/E/6sa7xHuVnBUWHmdPakaMz6/8XRAwZ2yPyqE5G8w=; b=AlifGU4UPZJCJnK0h+NE75nOKf0MLEavExxrefXKMUOFoADh1w6vrzFoZi79fbcHfQ pzfOZdEYhiSeumSucQNuDSIrb1NtlUg0GlP+nykEQhyUm/n7M/GVrT+YTsXCqjshcUBQ D8RrPVQl4/PFHDcyNXWDbhGxzwZMmsgsaGPgD6rbgfO0DVyoL4FHr6PGHWvJeYT332ji vmt0Ta7bLAIosD9Ntf4SvWnV5z7Ip5E8PdoRLx6oREJRjqW9THdgiTq6yI/5YGsf6UNU VT6G0vDGt5SYOp51MIweR4dz2JSxIQH2vmLP5mdW5OaLvEug1eFxFzx8y/tZcXwOfbVp 0Zcw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=m+/AvhWB; 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 y21-v6si696871pll.534.2018.02.12.23.45.50; Mon, 12 Feb 2018 23:46:04 -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=m+/AvhWB; 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 S933661AbeBMHpF (ORCPT + 99 others); Tue, 13 Feb 2018 02:45:05 -0500 Received: from mail-ua0-f175.google.com ([209.85.217.175]:42794 "EHLO mail-ua0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933463AbeBMHpB (ORCPT ); Tue, 13 Feb 2018 02:45:01 -0500 Received: by mail-ua0-f175.google.com with SMTP id 47so11048831uau.9 for ; Mon, 12 Feb 2018 23:45:01 -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=V/E/6sa7xHuVnBUWHmdPakaMz6/8XRAwZ2yPyqE5G8w=; b=m+/AvhWB0uTxz6KYRYj/xngnbowvX+c/JYg/WU+yd1NikitQ1KGJ964qMhabWlvnm2 LargPcXnvsube5roB1jp43P/6EgR5muC93KeG/J6XY3sg9XYsWJT2OkcSCoFLyN94iO8 +rl4m5fphRB2xCzkrNComBtEdHZYn8SV0FYwg= 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=V/E/6sa7xHuVnBUWHmdPakaMz6/8XRAwZ2yPyqE5G8w=; b=kejC4wqWxQG/mnUSrOunym6ie20X2o6P1AuYpRqsoUduaFzrPR24DGDAXeWTcx6vzI nDh/FbI2+6SbIb4Kh+aIoX9DTXt3HXUkjyzH0C4y49jP8z/CC2/uUMGbxPPFlGSFyYgi QzAn2/6JNPD1556H3NB9nU2v542//kLXTCaiSsLYeBFXwzgxRBLFxoBXI8tqFPfyxO6L 4D9wdNJjbjdl1kXviEWn/mTQPM51ZP9tOBwgI4/ZUEEOTcWTFqySrlYojtDz6aBCQ1/v R3vY5y8Xx5errI0a+JIEd1gMvrqKU7pPnXQumo7Nh5BpYni6X56dWbUQ8rvvTKZohQQV ecVQ== X-Gm-Message-State: APf1xPD0/G1710JtI5lhOt+H8Q+xmXvDwXF5Zqh2S8Q1Q/7PYx+9NSd/ OWuRKEnNT/sTd+Gj3DtEZ7qJiwnswLM= X-Received: by 10.176.26.145 with SMTP id j17mr259076uai.99.1518507900602; Mon, 12 Feb 2018 23:45:00 -0800 (PST) Received: from mail-vk0-f43.google.com (mail-vk0-f43.google.com. [209.85.213.43]) by smtp.gmail.com with ESMTPSA id x33sm1770899uac.31.2018.02.12.23.44.58 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Feb 2018 23:44:59 -0800 (PST) Received: by mail-vk0-f43.google.com with SMTP id b132so3390390vke.9 for ; Mon, 12 Feb 2018 23:44:58 -0800 (PST) X-Received: by 10.31.139.138 with SMTP id n132mr293499vkd.133.1518507898201; Mon, 12 Feb 2018 23:44:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.0.68 with HTTP; Mon, 12 Feb 2018 23:44:37 -0800 (PST) In-Reply-To: <1517999482-17317-2-git-send-email-vivek.gautam@codeaurora.org> References: <1517999482-17317-1-git-send-email-vivek.gautam@codeaurora.org> <1517999482-17317-2-git-send-email-vivek.gautam@codeaurora.org> From: Tomasz Figa Date: Tue, 13 Feb 2018 16:44:37 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v7 1/6] base: power: runtime: Export pm_runtime_get/put_suppliers To: Vivek Gautam Cc: "list@263.net:IOMMU DRIVERS , Joerg Roedel ," , Rob Herring , Mark Rutland , "Rafael J. Wysocki" , Robin Murphy , Will Deacon , Rob Clark , "list@263.net:IOMMU DRIVERS , Joerg Roedel ," , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, dri-devel , freedreno@lists.freedesktop.org, David Airlie , Greg KH , sboyd@codeaurora.org, linux-arm-msm@vger.kernel.org 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 Wed, Feb 7, 2018 at 7:31 PM, Vivek Gautam wrote: > The device link allows the pm framework to tie the supplier and > consumer. So, whenever the consumer is powered-on the supplier > is powered-on first. > > There are however cases in which the consumer wants to power-on > the supplier, but not itself. > E.g., A Graphics or multimedia driver wants to power-on the SMMU > to unmap a buffer and finish the TLB operations without powering > on itself. This sounds strange to me. If the SMMU is powered down, wouldn't the TLB lose its contents as well (and so no flushing needed)? Other than that, what kind of hardware operations would be needed besides just updating the page tables from the CPU? Best regards, Tomasz