Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp3092555iob; Mon, 16 May 2022 12:55:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJywBvma7RrY/meAu30RH8Qty+sJ08Jmtxc5TLKeIXnLpffwv6lzuJQr7euYfwjCgLkckLnc X-Received: by 2002:a17:907:3e20:b0:6f4:805f:c2cd with SMTP id hp32-20020a1709073e2000b006f4805fc2cdmr16224083ejc.215.1652730917666; Mon, 16 May 2022 12:55:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652730917; cv=none; d=google.com; s=arc-20160816; b=COS8/p0gsvKpdITRx/Att+XSQGXrmnC+wL5Ik7MrUMP40wzkmYEZB2ougF9jLPHWJU pUWq5OIAod2NloUyKnGgth7T2ITHu1iTy1XdS6LgGpakRoELo1CCFyth9kx7svSlTZaS IZTFOKtdOZjZpF2dXiQYxRUxKTw4Ze+xwfK2EVv0F2NE+biPfMfgrrBPw6FxUv39PeC5 pgjA+FWAk4VAJgyAoIrT+1/atd4zGT7Qu3WkpcJy0uovlOfkjKaRObhALE5atwAwJ5cW me9Yf1Iosie87dUBIB4FThIRUPx+QaOQRPgKOaN/WqE94Mf/1UviP5rWtU9QYVK3Otsp 8cTw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=Ixmg90dyDmHAicFMf0z9UoK0XakUBMSYYi6CRfswppA=; b=vTn7l3YzJavJPbboqMYCnHA08Zlxwoz4w20CknB1EcSFSZMBuyGrWbgKHv2I/0mwT9 8UOeKd4MFtCWCxX3VEySYZpVn9jXqTkeRzVEz5+6gu4rcg9y9e9hdTO6io+SF4x92NIb 05nePZv/nlthc8RaUej1zCgLWx3dmJnoy/HIK5j8J8BBQdzgty5RIRT9kuMtQ6mW/bXf t8mPvqzaYBdlBasBwQZhKdKVZThUcjfSZJoCkZMXZ8CyXXY71HZslAXuRyR2qXPwn4xr zG4QGWaps3Nz9ceOV/ngX+hw8wW4pHfwIB5GcvRx5F0u2Dwk73SVPp317XFRQlMtrHNV u1Eg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@kapsi.fi header.s=20161220 header.b=UT5tkyrI; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id f12-20020a0564021e8c00b00421f487882fsi173190edf.322.2022.05.16.12.54.50; Mon, 16 May 2022 12:55:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=fail header.i=@kapsi.fi header.s=20161220 header.b=UT5tkyrI; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242178AbiEPKDY (ORCPT + 99 others); Mon, 16 May 2022 06:03:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50358 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238064AbiEPKCn (ORCPT ); Mon, 16 May 2022 06:02:43 -0400 Received: from mail.kapsi.fi (mail.kapsi.fi [IPv6:2001:67c:1be8::25]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8B5BF55AC; Mon, 16 May 2022 03:02:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kapsi.fi; s=20161220; h=Content-Transfer-Encoding:MIME-Version:References:In-Reply-To: Message-Id:Date:Subject:Cc:To:From:Sender:Reply-To:Content-Type:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=Ixmg90dyDmHAicFMf0z9UoK0XakUBMSYYi6CRfswppA=; b=UT5tkyrIaw45IEdY2km/R9q0wk aHqRzow2KrkX+t/yC+BN9Q877+DiPQtql+6L30v8ci0AoJ6hsazarTzNqGeT+uc3G5LjZIKO/6aPk RNN7gJ9C/0aGD32MVcMrGB/bnu7ref3sxkgD0FkWHHqtIr/w5jdiOcJCnajRGyr9jsbSBjr890/kC k4MGH646Hq0Xd7QR4iVBwlt1xwIJWoohNIXIwNwJ+TBgRLbHtGv/H0NiQ5JAg7jdYCA956lw//P2c To4K46vQ5jqIdw3hA1Eb8UakZ0i95YQVXlHezZw03kobx4WAsRhruq2gE4uvZbzMofg3l7DiMJbcC JYdSRG4Q==; Received: from 91-158-25-70.elisa-laajakaista.fi ([91.158.25.70] helo=toshino.localdomain) by mail.kapsi.fi with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nqXYg-0005yU-I6; Mon, 16 May 2022 13:02:34 +0300 From: cyndis@kapsi.fi To: thierry.reding@gmail.com, jonathanh@nvidia.com, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, digetx@gmail.com Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org, Mikko Perttunen Subject: [PATCH v1 11/13] gpu: host1x: Add MLOCK release code on Tegra234 Date: Mon, 16 May 2022 13:02:11 +0300 Message-Id: <20220516100213.1536571-12-cyndis@kapsi.fi> X-Mailer: git-send-email 2.36.1 In-Reply-To: <20220516100213.1536571-1-cyndis@kapsi.fi> References: <20220516100213.1536571-1-cyndis@kapsi.fi> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 91.158.25.70 X-SA-Exim-Mail-From: cyndis@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Mikko Perttunen With the full-featured opcode sequence using MLOCKs, we need to also unlock those MLOCKs in the event of a timeout. However, it turns out that on Tegra186/Tegra194, by default, we don't need to do this; furthermore, on Tegra234 it is much simpler to do; so only implement this on Tegra234 for the time being. Signed-off-by: Mikko Perttunen --- drivers/gpu/host1x/hw/cdma_hw.c | 34 ++++++++++++++++++++++ drivers/gpu/host1x/hw/hw_host1x08_common.h | 7 +++++ 2 files changed, 41 insertions(+) diff --git a/drivers/gpu/host1x/hw/cdma_hw.c b/drivers/gpu/host1x/hw/cdma_hw.c index e49cd5b8f735..1b65a10b9dfc 100644 --- a/drivers/gpu/host1x/hw/cdma_hw.c +++ b/drivers/gpu/host1x/hw/cdma_hw.c @@ -238,6 +238,37 @@ static void cdma_resume(struct host1x_cdma *cdma, u32 getptr) cdma_timeout_restart(cdma, getptr); } +static void timeout_release_mlock(struct host1x_cdma *cdma) +{ +#if HOST1X_HW >= 8 + /* Tegra186 and Tegra194 require a more complicated MLOCK release + * sequence. Furthermore, those chips by default don't enforce MLOCKs, + * so it turns out that if we don't /actually/ need MLOCKs, we can just + * ignore them. + * + * As such, for now just implement this on Tegra234 where things are + * stricter but also easy to implement. + */ + struct host1x_channel *ch = cdma_to_channel(cdma); + struct host1x *host1x = cdma_to_host1x(cdma); + u32 offset; + + switch (ch->client->class) { + case HOST1X_CLASS_VIC: + offset = HOST1X_COMMON_VIC_MLOCK; + break; + case HOST1X_CLASS_NVDEC: + offset = HOST1X_COMMON_NVDEC_MLOCK; + break; + default: + WARN(1, "%s was not updated for class %u", __func__, ch->client->class); + return; + } + + host1x_common_writel(host1x, 0x0, offset); +#endif +} + /* * If this timeout fires, it indicates the current sync_queue entry has * exceeded its TTL and the userctx should be timed out and remaining @@ -288,6 +319,9 @@ static void cdma_timeout_handler(struct work_struct *work) /* stop HW, resetting channel/module */ host1x_hw_cdma_freeze(host1x, cdma); + /* release any held MLOCK */ + timeout_release_mlock(cdma); + host1x_cdma_update_sync_queue(cdma, ch->dev); mutex_unlock(&cdma->lock); } diff --git a/drivers/gpu/host1x/hw/hw_host1x08_common.h b/drivers/gpu/host1x/hw/hw_host1x08_common.h index 4df28440b86b..8e0c99150ec2 100644 --- a/drivers/gpu/host1x/hw/hw_host1x08_common.h +++ b/drivers/gpu/host1x/hw/hw_host1x08_common.h @@ -2,3 +2,10 @@ /* * Copyright (c) 2022 NVIDIA Corporation. */ + +#define HOST1X_COMMON_OFA_MLOCK 0x4050 +#define HOST1X_COMMON_NVJPG1_MLOCK 0x4070 +#define HOST1X_COMMON_VIC_MLOCK 0x4078 +#define HOST1X_COMMON_NVENC_MLOCK 0x407c +#define HOST1X_COMMON_NVDEC_MLOCK 0x4080 +#define HOST1X_COMMON_NVJPG_MLOCK 0x4084 -- 2.36.1