Received: by 2002:a05:6358:bb9e:b0:b9:5105:a5b4 with SMTP id df30csp4525486rwb; Tue, 6 Sep 2022 08:41:45 -0700 (PDT) X-Google-Smtp-Source: AA6agR7r8vnfZqR9yg/pbYxCjX5PhBuzObiC5gynh6c9IwHfH5ftv2UVfZLrZ2GvzEHEG2If05Py X-Received: by 2002:a63:84c6:0:b0:42b:e461:348a with SMTP id k189-20020a6384c6000000b0042be461348amr39086810pgd.87.1662478905099; Tue, 06 Sep 2022 08:41:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1662478905; cv=none; d=google.com; s=arc-20160816; b=Ys1y8TJIeM4Dekzf3asxJTvtN2soWi/LI2zwS/HyCuFwZNKG9xDjHTOh5+eoi3xFQ5 YGjprbUJ7J9qPxI0h+Yv4bmXpF4TynzqDQhoZnIwO8qubXld7U/O6ICI6xxv1R7+Wnip Ku9H0mtbYgSWR2VRGy6fCzNBBmSRf9qksnox2pdarVsum6bEnaQ7XMVoJeJARCM2Bc3/ aK7qiMl2PeavnNsI7QldhxaECgiCT3f36psBIXxZ77Pqfwxyez/7eNiGTmos1DkxKOg2 t2+QL/giKF+O39JhBl33jzffCZC5FNloNda2O1JfBo5wYVz7QYLNKsRIxHdi0pbbh+ju Wd3w== 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=tsvWDg5Qw6FHru4RBeFNSs0datG/wUGFHEHf/M/3yFo=; b=Z48RLMKZ+V0xqW9NMLiIMvyeTVjiN4AKqI+4x98yGjWlWDE/JRb8ac7/xs7x2KlHhO 2tbtWFqF/lnbS93apQ7/AvZlZom53F5qGE0nW8sW1rZZtY7z/I8S/QF+jd0JxeDlNvdQ C2LdbHyU7rU3nHorUaBOc29+UB4vMCB4ImFtEqCZaIqfWtCP5xXSefZEt1sf6vwTEdS5 0uxaA8HfiqavS6oj7tl7Yk6biPVIGqv3KXBT+893+tiTMGWJYNzHFaJtaJS/+wTGs1F2 3oJsLaxWDwO2jyJdm7IUDNOvrJnfIgEpYTJ99E6s3EoallOqTrXGwt4dz19BcDjfao/J bJCQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@kapsi.fi header.s=20161220 header.b=T4ZX30n3; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kapsi.fi Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z15-20020a170903018f00b0016f002733e3si15557123plg.497.2022.09.06.08.41.33; Tue, 06 Sep 2022 08:41:45 -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=T4ZX30n3; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kapsi.fi Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241943AbiIFOXd (ORCPT + 99 others); Tue, 6 Sep 2022 10:23:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39428 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242101AbiIFOTf (ORCPT ); Tue, 6 Sep 2022 10:19:35 -0400 Received: from mail.kapsi.fi (mail.kapsi.fi [IPv6:2001:67c:1be8::25]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BBBB57AC1B; Tue, 6 Sep 2022 06:50:45 -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=tsvWDg5Qw6FHru4RBeFNSs0datG/wUGFHEHf/M/3yFo=; b=T4ZX30n3HZKZ4nTtNu+Gw1e7io xZ54pVXfYL82NXnttqHf6NXUA88EjYXK73fFIpFFO7gZEy6SQOSRGioOqJXpKsJ0j9iwYMSCVv3Cz yx5VL+dZ9dNQzisKe75Q4nx+6LB5i0LfOVe3V5URUOvjMb5KSo55OK4R9cCeTZSZYZHqxNzeL+jFr C5KW37IO/Z30LSLYGs7f9yzR73FzywsJ6o/I/KJOMq+bexoS6wDAQ6Gpo0BQujBhY8d/mgyKWnjkU KqIRH7B4QqRe9yGqVdwNlJil6/rl9eU92jc4eGxBbWo7S+pimyYlvCv5sNN7EBdu8NyvcEEDQ80Jt JEXjbBag==; Received: from 91-158-25-70.elisa-laajakaista.fi ([91.158.25.70] helo=toshino.localdomain) by mail.kapsi.fi with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1oVYdX-008sZV-Cm; Tue, 06 Sep 2022 16:29:07 +0300 From: Mikko Perttunen To: Thierry Reding , David Airlie , Daniel Vetter , Rob Herring , Krzysztof Kozlowski , Jonathan Hunter Cc: Mikko Perttunen , Ashish Mhetre , Sameer Pujar , dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 3/8] dt-bindings: Add bindings for Tegra234 NVDEC Date: Tue, 6 Sep 2022 16:28:18 +0300 Message-Id: <20220906132823.2390953-4-cyndis@kapsi.fi> X-Mailer: git-send-email 2.37.0 In-Reply-To: <20220906132823.2390953-1-cyndis@kapsi.fi> References: <20220906132823.2390953-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 Update NVDEC bindings for Tegra234. This new engine version only has two memory clients, but now requires three clocks, and as a bigger change the engine loads firmware from a secure carveout configured by the bootloader. For the latter, we need to add a phandle to the memory controller to query the location of this carveout, and several other properties containing offsets into the firmware inside the carveout. These properties are intended to be populated through a device tree overlay configured at flashing time, so that the values correspond to the flashed NVDEC firmware. Signed-off-by: Mikko Perttunen --- .../gpu/host1x/nvidia,tegra210-nvdec.yaml | 118 +++++++++++++++--- 1 file changed, 98 insertions(+), 20 deletions(-) diff --git a/Documentation/devicetree/bindings/gpu/host1x/nvidia,tegra210-nvdec.yaml b/Documentation/devicetree/bindings/gpu/host1x/nvidia,tegra210-nvdec.yaml index 3cf862976448..27128a195b66 100644 --- a/Documentation/devicetree/bindings/gpu/host1x/nvidia,tegra210-nvdec.yaml +++ b/Documentation/devicetree/bindings/gpu/host1x/nvidia,tegra210-nvdec.yaml @@ -24,17 +24,11 @@ properties: - nvidia,tegra210-nvdec - nvidia,tegra186-nvdec - nvidia,tegra194-nvdec + - nvidia,tegra234-nvdec reg: maxItems: 1 - clocks: - maxItems: 1 - - clock-names: - items: - - const: nvdec - resets: maxItems: 1 @@ -50,18 +44,6 @@ properties: dma-coherent: true - interconnects: - items: - - description: DMA read memory client - - description: DMA read 2 memory client - - description: DMA write memory client - - interconnect-names: - items: - - const: dma-mem - - const: read-1 - - const: write - nvidia,host1x-class: description: | Host1x class of the engine, used to specify the targeted engine @@ -79,7 +61,103 @@ required: - reset-names - power-domains -additionalProperties: false +unevaluatedProperties: false + +allOf: + - if: + properties: + compatible: + contains: + enum: + - nvidia,tegra234-nvdec + then: + properties: + clocks: + items: + - description: NVDEC clock + - description: FUSE clock + - description: TSEC_PKA clock + clock-names: + items: + - const: nvdec + - const: fuse + - const: tsec_pka + interconnects: + items: + - description: DMA read memory client + - description: DMA write memory client + interconnect-names: + items: + - const: dma-mem + - const: write + nvidia,memory-controller: + $ref: /schemas/types.yaml#/definitions/phandle + description: + phandle to the memory controller for determining carveout information. + nvidia,bl-manifest-offset: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + Offset to bootloader manifest from beginning of firmware. Typically set as + part of a device tree overlay corresponding to flashed firmware. + nvidia,bl-code-offset: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + Offset to bootloader code section from beginning of firmware. Typically set as + part of a device tree overlay corresponding to flashed firmware. + nvidia,bl-data-offset: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + Offset to bootloader data section from beginning of firmware. Typically set as + part of a device tree overlay corresponding to flashed firmware. + nvidia,os-manifest-offset: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + Offset to operating system manifest from beginning of firmware. Typically set as + part of a device tree overlay corresponding to flashed firmware. + nvidia,os-code-offset: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + Offset to operating system code section from beginning of firmware. Typically set as + part of a device tree overlay corresponding to flashed firmware. + nvidia,os-data-offset: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + Offset to operating system data section from beginning of firmware. Typically set as + part of a device tree overlay corresponding to flashed firmware. + required: + - nvidia,memory-controller + - nvidia,bl-manifest-offset + - nvidia,bl-code-offset + - nvidia,bl-data-offset + - nvidia,os-manifest-offset + - nvidia,os-code-offset + - nvidia,os-data-offset + - if: + properties: + compatible: + contains: + enum: + - nvidia,tegra210-nvdec + - nvidia,tegra186-nvdec + - nvidia,tegra194-nvdec + then: + properties: + clocks: + items: + - description: NVDEC clock + clock-names: + items: + - const: nvdec + interconnects: + items: + - description: DMA read memory client + - description: DMA read 2 memory client + - description: DMA write memory client + interconnect-names: + items: + - const: dma-mem + - const: read-1 + - const: write examples: - | -- 2.37.0