Received: by 10.213.65.68 with SMTP id h4csp3893560imn; Tue, 10 Apr 2018 06:19:50 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+w0eRFrMkYK3uvhV0nSUFegemnKzSqpFTALbOrolyk2xOwWO79bbEE/NGrSEetwDCORbRm X-Received: by 10.99.96.19 with SMTP id u19mr264376pgb.261.1523366390843; Tue, 10 Apr 2018 06:19:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523366390; cv=none; d=google.com; s=arc-20160816; b=U/dfRpNFNcLuKmQUGNRlV+FNNoEfNfWb1o3Z2AY6JpcvLWTtAQf7lQHxvZjIfzOhhj qpurbPTlyxnKF83i0ruTKHl6+fUqOtE16Lvwmh+Q5MMqh6OUEAmwrU+B1joXmShLtBFr KjTK/90bP6FpLCIkmOaMVn5t/HK5FSLZ0i+ByAHPS1/JVIR2sGzYiWslrRDP8VmLQjJy 8Es6G04S11mUJzhSFlZmtGnoiItN2WVRlC3+ODbFmvaxUKrpnlQrIx+Vfr3ktmSrVGKj AskgLFRvK4zJQvFI2v0yym2rBYcUWf+JAySHs9NzYvyvNReERcZBvHEx9jxb1gPffEjD PgHQ== 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=PrhhLLo6qTFx4YfbZJL9cJX98Vc5qrdlBHUrcXKpZoE=; b=ysamTInpgwP/u553FWgjg/KAX24a8DIz7qxauXwty3Lh9a+Uu/RYFEyuwFLJcfjJ29 76mzEnivwythWzAoCJMd3viUfpsY/rEjikiZrHog2KrYFqB7N5iMajnJ0oqFH/OIzDx3 IRKtcjhigF4HJFrWkNJcmCiQN59ZvrjloW+LaWqSqTeWfZFEXFs39mZAxB9N9vXqwU5Q z/stNZYfAbdRH8aLoj+I6B0MiAi+zHeaE4XDtbiNAXxhnvv3G4qPdWctStYRc44N2NSF ld8P7PK08ud52YVByPGe/ZTPdHYsTg6QHqfUHMoeGqS9flKmz/PgQXIIF8jz7krrBssO SbRQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=hwJT9RER; 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 d67si2134713pfb.232.2018.04.10.06.19.13; Tue, 10 Apr 2018 06:19:50 -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=hwJT9RER; 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 S1753848AbeDJNPO (ORCPT + 99 others); Tue, 10 Apr 2018 09:15:14 -0400 Received: from mail-ua0-f178.google.com ([209.85.217.178]:43109 "EHLO mail-ua0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753826AbeDJNPL (ORCPT ); Tue, 10 Apr 2018 09:15:11 -0400 Received: by mail-ua0-f178.google.com with SMTP id u4so7259695uaf.10 for ; Tue, 10 Apr 2018 06:15:11 -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=PrhhLLo6qTFx4YfbZJL9cJX98Vc5qrdlBHUrcXKpZoE=; b=hwJT9RER03bWLCrEoN3bi0lGls3GIiofgdHW55pre0qGIGDQS/26giTsrRI21u9Yjt n0NYLCgP5Knjl0cBN88+5mQNIEYxHjra0rIY3bJt7w/4xWuiXsyl/WoAjY9j32PUydgz Q/HUKvc/DI6fBM5tfVgMBzdnuKDipMkrn/a2o= 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=PrhhLLo6qTFx4YfbZJL9cJX98Vc5qrdlBHUrcXKpZoE=; b=MX8NOrE6hwXq8kSXZc/rjGSL2Rc1omZk2hfSD2+FCKT/uFrqnR5MlrvFHeqz2NSJBi IPUm9Y9+ZV7x8CPx6e5LWrnNpUhr56bm9hiOS2mqDjkIIngrOoUMqePVCrpncOiWtQ4e Jbx5TiahGxYD7rMa+MUPm76muV0STlKWrjpOmePBRCiVkQ2hl231FzjiGaThjeDEhrzo d5Wo2N98N9sME2PuCT/7EcKNK23vl0wm6Mnf+WUhjc+H/1V07GtbPJ4Vy0FZe/+qbVzj Qtyel32C1o6DUZqjng1GE9Y1MEYw9QtSXMH7GPbMkJD0dyZkUn7gZlNsXcNC9Ntpf0lF JtZQ== X-Gm-Message-State: ALQs6tAlrSWMJUzaUH3t1gV7QVOGXSsfugT3YlcqDmdWetuopGZpCTIU o0jE4ntsXa1jLW+Nwf8nzVatiHfaQyQ= X-Received: by 10.176.35.212 with SMTP id c20mr310551uan.90.1523366110674; Tue, 10 Apr 2018 06:15:10 -0700 (PDT) Received: from mail-ua0-f176.google.com (mail-ua0-f176.google.com. [209.85.217.176]) by smtp.gmail.com with ESMTPSA id m28sm441636uai.12.2018.04.10.06.15.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Apr 2018 06:15:09 -0700 (PDT) Received: by mail-ua0-f176.google.com with SMTP id o34so7270239uae.9 for ; Tue, 10 Apr 2018 06:15:09 -0700 (PDT) X-Received: by 10.176.68.197 with SMTP id n63mr308152uan.132.1523366108842; Tue, 10 Apr 2018 06:15:08 -0700 (PDT) MIME-Version: 1.0 References: <20180313085534.11650-1-vivek.gautam@codeaurora.org> <20180313085534.11650-6-vivek.gautam@codeaurora.org> <61d30fff-1bf8-d2c1-bbe9-f93de836ae77@huawei.com> <7d5af071-ef98-8461-3ce9-e84fc0b3956a@codeaurora.org> In-Reply-To: From: Tomasz Figa Date: Tue, 10 Apr 2018 13:14:57 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v9 5/5] iommu/arm-smmu: Add support for qcom,smmu-v2 variant To: xieyisheng1@huawei.com Cc: Vivek Gautam , Mark Rutland , devicetree@vger.kernel.org, linux-arm-msm , Will Deacon , Linux Kernel Mailing List , "list@263.net:IOMMU DRIVERS , Joerg Roedel ," , gaojianbo@hisilicon.com 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 Yisheng, Sorry, I think we missed your question here. On Wed, Mar 28, 2018 at 3:12 PM Yisheng Xie wrote: > Hi Vivek, > On 2018/3/28 12:37, Vivek Gautam wrote: > > Hi Yisheng > > > > > > On 3/28/2018 6:54 AM, Yisheng Xie wrote: > >> Hi Vivek, > >> > >> On 2018/3/13 16:55, Vivek Gautam wrote: > >>> +- power-domains: Specifiers for power domains required to be powered on for > >>> + the SMMU to operate, as per generic power domain bindings. > >>> + > >> In this patchset, power-domains is not used right? And you just do the clock gating, > >> but not power gating, right? > > > > We are handling the power-domains too. Please see the example in this binding doc. > I see, but I do not find the point in code of these patchset, do you mean PMIC(e.g mmcc) > will gate the power domain of SMMU(e.g. MDSS_GDSC of mmcc) when PMIC suspend? If respective SoC power domains is registered as a standard genpd PM domain, then the runtime PM subsystem will take care of power domain control at runtime suspend and resume. Best regards, Tomasz