Received: by 10.192.165.156 with SMTP id m28csp1400190imm; Wed, 11 Apr 2018 19:01:37 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+xqs92SOWqcUP+3hMbsLgGT9Ia9kbQv9314ftk1BXLeejIJ526RVjp6Wj4GuIopnKCFfYF X-Received: by 10.98.194.195 with SMTP id w64mr5973636pfk.83.1523498497866; Wed, 11 Apr 2018 19:01:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523498497; cv=none; d=google.com; s=arc-20160816; b=0BzBHy3tp14VnhzOOkYf5s0LLF9KrEaptNpnw0VpWrNzqrzsuKMDoiE7i+Ng0hkUBm 95dCIUhNUBMKAzUVIeBNu0ZUw1T8AzoLtkUqB4KQVHyl0EhRGR4//wl0UGiBgsntShnx WPd11Z1oV92+EsIFXTY665CsuRxpG87mRiBe+UrPTZm3cWSW3LFCKpe78ncEc6isVIc1 1mbLpLwcRURZL5tdUOXOI00vQ6PbX5oHgPUz2V1N4gJexNG9HpIvG3r1pH94JgNLxbQJ BgF9IvzEAC/YmM48wIgsh+zMDkA3DdnyaWGoRfmIPtwyT1yQLa/DffSejJATAWUCyuoQ DJbw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject:arc-authentication-results; bh=MVg0p+W1r41TY4PX/Es+cAM4DlPx4ynZGDsH/fNfpUQ=; b=WSePBj0ruwn9y8WxxNTDs3B2HW8FZWIo7qrqSJ7qf+7Qzg34pZdynv311Et+HtU2hY o0UUJctGQRC8LSZqyRolldLelWCIJNf3oWe8C5MvtVppXbYFT8PUPsMc+W86QdiUxViG RbO9DfUtSM80mhrzWVIUpwulCARF3KNNSEtHUQZGVTlXy5cL7IDS4KueJPhweaBwiaNK s/TIlnAaU7Ci2uXu/fcwgU4XrO7pxGK2oBx6GN0d6fPP4Y8J6LcFTQkIh3ftjINmqJhu oQMXRX6odJPBfjN0xIaVHTNdSm2OgPB5+6dXd0e/SkN5z6RunTV87xvBNBpX+bGowhge wWjg== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b38-v6si2390246pla.124.2018.04.11.19.01.01; Wed, 11 Apr 2018 19:01:37 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752898AbeDLB4M (ORCPT + 99 others); Wed, 11 Apr 2018 21:56:12 -0400 Received: from szxga07-in.huawei.com ([45.249.212.35]:41550 "EHLO huawei.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751858AbeDLB4K (ORCPT ); Wed, 11 Apr 2018 21:56:10 -0400 Received: from DGGEMS401-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id A3FBF30E0D4CB; Thu, 12 Apr 2018 09:56:06 +0800 (CST) Received: from [127.0.0.1] (10.177.29.40) by DGGEMS401-HUB.china.huawei.com (10.3.19.201) with Microsoft SMTP Server id 14.3.361.1; Thu, 12 Apr 2018 09:55:58 +0800 Subject: Re: [PATCH v9 5/5] iommu/arm-smmu: Add support for qcom,smmu-v2 variant To: Vivek Gautam , Tomasz Figa 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> <65a57964-805b-3a38-71a2-0c383af30539@huawei.com> CC: Mark Rutland , , linux-arm-msm , Will Deacon , Linux Kernel Mailing List , "list@263.net:IOMMU DRIVERS" , Joerg Roedel , From: Yisheng Xie Message-ID: <76065271-c6e6-2ce7-8608-c18b621055ce@huawei.com> Date: Thu, 12 Apr 2018 09:55:35 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.29.40] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Vivek, On 2018/4/11 13:15, Vivek Gautam wrote: > Hi Yisheng, > > > On 4/11/2018 6:52 AM, Yisheng Xie wrote: >> Hi Tomasz, >> >> On 2018/4/10 21:14, Tomasz Figa wrote: >>> 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. >>> >> Get it, thanks for your explain, I should have learned about this. > > Sorry, i missed your subsequent question, and Tomasz has explained it now. Never mind about that. > Let me know if you have further questions. Presently, no other questions. Thanks for your kind help. Thanks Yisheng > > regards > Vivek >> >> Thanks >> Yisheng >> >>> Best regards, >>> Tomasz >>> >>> . >>> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > > . >