Received: by 10.223.185.116 with SMTP id b49csp526705wrg; Fri, 23 Feb 2018 02:37:47 -0800 (PST) X-Google-Smtp-Source: AH8x225DJzL2Jo4GACJezkjKDDtTGA1ZJH2rJu8GJTTUQjcWGwkO2hqfgt03oSDWEl3e5toNu90W X-Received: by 2002:a17:902:684:: with SMTP id 4-v6mr1273556plh.262.1519382267216; Fri, 23 Feb 2018 02:37:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519382267; cv=none; d=google.com; s=arc-20160816; b=S8ErgpzOxlz4fq5fZm7oDLU2j7uBi9pG2uDgH3BgIGO5s+c2EMhqN1He6lMt8ClI38 J1wTZdRf6GGXWH8H+1Wf70G1qwr8pvAJN7VQXxBAZiOc2FX2kMi/oAMQSlTXVE7btK9T 62yJjHfk6rUYwqNJKIOP+FSnO7olJF1g7RISav2Kp9lOLn3gddk+Re7ZkeiSY2ShPluY o5+hCtPc9uHooc4Yfi3MBkCizP3pt3TLGO0crDGJt4/HBsbNubP9DFsQqIzu98ks890j hptFQho+OllZ2UYE6LhO3V80OCR7xSZyWfMLkTE5MfkOvpbEMWmkT5VKuH6FbMzYrPVD 6n6w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:subject:message-id:date:from :references:in-reply-to:mime-version:dmarc-filter:dkim-signature :dkim-signature:arc-authentication-results; bh=c9GYaf/36Al8Zyg4ulz8yZ9piEcM2EeIGVUfp6ezTic=; b=e2VJrFlup6QlQsgoyHd0ipNxXY+bPMLrO3BCH88jxMLV0OK/r696Y1Y1UrEi0HZd1B Ja+0bigIKADe3Ed5aRSMgDwG42PFBS63Si/NChsBSxDldfTiLJ9uchIWZ2B3AQzstoGw yyk6/uIdsxAUoi9Ylc5dTO5DF2ekyhCuE/032OPK4Cgnape0BCicPuoEWVnWEEBSSbz4 ADCHjcSRTCUSHNHGONIKMa2aS1HDt11NuoMHx7FLooq1fLsHOVfleW7awOtQq+llliTq OoHFOyTd20ymrdvXIuJAZrRARyLnnkVBRz0QC2sVQ4eCIizpRbfbvkqbrkBOTWuM8wPf 7/pw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=BcFILiZZ; dkim=pass header.i=@codeaurora.org header.s=default header.b=kO+VvHtu; 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 t1-v6si1619491plr.558.2018.02.23.02.37.33; Fri, 23 Feb 2018 02:37:47 -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=@codeaurora.org header.s=default header.b=BcFILiZZ; dkim=pass header.i=@codeaurora.org header.s=default header.b=kO+VvHtu; 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 S1751449AbeBWKgp (ORCPT + 99 others); Fri, 23 Feb 2018 05:36:45 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:56534 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750861AbeBWKgm (ORCPT ); Fri, 23 Feb 2018 05:36:42 -0500 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id C3122607CF; Fri, 23 Feb 2018 10:36:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1519382201; bh=jLc6m9SiWpA9NPVop3TbvMbv6sTw3eWH3FeslPrq6es=; h=In-Reply-To:References:From:Date:Subject:To:From; b=BcFILiZZBLPnuF3Mkuj17gIw3T3bCGVXaVXMinUGROKK9wEzQgMP/GM9CHIIAXJJ2 LLQT3MINa99sgy3qcCYMRKeFuMQYmf44c2iOYOfLJgjVu3R96dGVUMwtkkgL9Zd6dH KYAMZ7mcCWeNRdJsZk6xdJlRN3P0ukfeqk/TGum4= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from mail-qk0-f182.google.com (mail-qk0-f182.google.com [209.85.220.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: vivek.gautam@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 9124D60F71; Fri, 23 Feb 2018 10:36:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1519382200; bh=jLc6m9SiWpA9NPVop3TbvMbv6sTw3eWH3FeslPrq6es=; h=In-Reply-To:References:From:Date:Subject:To:From; b=kO+VvHtuDlNO/adHDkjFJVBq/EYCkS/fr15UtmrhLwHr8ZBLnFf9Gu05wBduY7vON 9LxZP/5WVl8u6P26Y7FhGxNYL72Nj6vkh0iNORh57MIJ2MqarWD/PtxlVAkIABWMnT uIOzhznOyAIqwozsEzdQgWKPaR0cg3vdSQ/RdeyM= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 9124D60F71 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=vivek.gautam@codeaurora.org Received: by mail-qk0-f182.google.com with SMTP id h129so10206630qke.8; Fri, 23 Feb 2018 02:36:40 -0800 (PST) X-Gm-Message-State: APf1xPBIvhqwbA3BXyfFaW7YZzIfQcHLNy69PEBmz5+5PwETZqAdhE2e gCSigpNgdPOL4uzhDh40Bl1hUUVY3vZBEa7MAS4= X-Received: by 10.55.215.205 with SMTP id t74mr1696777qkt.259.1519382199750; Fri, 23 Feb 2018 02:36:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.97.86 with HTTP; Fri, 23 Feb 2018 02:36:39 -0800 (PST) In-Reply-To: <20180222235200.GA18743@jcrouse-lnx.qualcomm.com> References: <1517999482-17317-1-git-send-email-vivek.gautam@codeaurora.org> <1517999482-17317-4-git-send-email-vivek.gautam@codeaurora.org> <20180222235200.GA18743@jcrouse-lnx.qualcomm.com> From: Vivek Gautam Date: Fri, 23 Feb 2018 16:06:39 +0530 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v7 3/6] iommu/arm-smmu: Invoke pm_runtime during probe, add/remove device To: Vivek Gautam , "list@263.net:IOMMU DRIVERS , Joerg Roedel ," , "robh+dt" , Mark Rutland , "Rafael J. Wysocki" , Robin Murphy , Will Deacon , Rob Clark , "list@263.net:IOMMU DRIVERS , Joerg Roedel ," , devicetree@vger.kernel.org, open list , Linux PM , dri-devel , freedreno , David Airlie , Greg KH , Stephen Boyd , 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 On Fri, Feb 23, 2018 at 5:22 AM, Jordan Crouse wrote: > On Wed, Feb 07, 2018 at 04:01:19PM +0530, Vivek Gautam wrote: >> From: Sricharan R >> >> The smmu device probe/remove and add/remove master device callbacks >> gets called when the smmu is not linked to its master, that is without >> the context of the master device. So calling runtime apis in those places >> separately. >> >> Signed-off-by: Sricharan R >> [vivek: Cleanup pm runtime calls] >> Signed-off-by: Vivek Gautam >> --- >> drivers/iommu/arm-smmu.c | 42 ++++++++++++++++++++++++++++++++++++++---- >> 1 file changed, 38 insertions(+), 4 deletions(-) >> >> diff --git a/drivers/iommu/arm-smmu.c b/drivers/iommu/arm-smmu.c >> index 9e2f917e16c2..c024f69c1682 100644 >> --- a/drivers/iommu/arm-smmu.c >> +++ b/drivers/iommu/arm-smmu.c >> @@ -913,11 +913,15 @@ static void arm_smmu_destroy_domain_context(struct iommu_domain *domain) >> struct arm_smmu_domain *smmu_domain = to_smmu_domain(domain); >> struct arm_smmu_device *smmu = smmu_domain->smmu; >> struct arm_smmu_cfg *cfg = &smmu_domain->cfg; >> - int irq; >> + int ret, irq; >> >> if (!smmu || domain->type == IOMMU_DOMAIN_IDENTITY) >> return; >> >> + ret = pm_runtime_get_sync(smmu->dev); >> + if (ret) >> + return; >> + >> /* >> * Disable the context bank and free the page tables before freeing >> * it. >> @@ -932,6 +936,8 @@ static void arm_smmu_destroy_domain_context(struct iommu_domain *domain) >> >> free_io_pgtable_ops(smmu_domain->pgtbl_ops); >> __arm_smmu_free_bitmap(smmu->context_map, cfg->cbndx); >> + >> + pm_runtime_put_sync(smmu->dev); >> } >> >> static struct iommu_domain *arm_smmu_domain_alloc(unsigned type) >> @@ -1407,14 +1413,22 @@ static int arm_smmu_add_device(struct device *dev) >> while (i--) >> cfg->smendx[i] = INVALID_SMENDX; >> >> - ret = arm_smmu_master_alloc_smes(dev); >> + ret = pm_runtime_get_sync(smmu->dev); >> if (ret) >> goto out_cfg_free; > > Hey Vivek, I just hit a problem with this on sdm845. It turns out that > pm_runtime_get_sync() returns a positive 1 if the device is already active. > > I hit this in the GPU code. The a6xx has two platform devices that each use a > different sid on the iommu. The GPU is probed normally from a platform driver > and it in turn initializes the GMU device by way of a phandle. > > Because the GMU isn't probed with a platform driver we need to call > of_dma_configure() on the device to set up the IOMMU for the device which ends > up calling through this path and we discover that the smmu->dev is already > powered (pm_runtime_get_sync returns 1). > > I'm not immediately sure if this is a bug on sdm845 or not because a cursory > inspection says that the SMMU device shouldn't be powered at this time but there > might be a connection that I'm not seeing. Obviously if the SMMU was left > powered thats a bad thing. But putting that aside it is obvious that this > code should be accommodating of the possibility that the device is already > powered, and so this should be > > if (ret < 0) > goto out_cfg_free; Right, as Tomasz also pointed, we should surely check the negative value of pm_runtime_get_sync(). From your description, it may be that the GPU has turned on the smmu, and then once if goes and probes the GMU, the GMU device also wants to turn-on the same smmu device. But that's already active. So pm_runtime_get_sync() returns 1. Am i making sense? regards Vivek > > With that the GPU/GMU successfully comes up on Sean Paul's display testing > branch. > > Jordan > > -- > The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, > a Linux Foundation Collaborative Project > -- > 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 -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation