From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5999BECAAD5 for ; Mon, 5 Sep 2022 17:09:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232093AbiIERJE (ORCPT ); Mon, 5 Sep 2022 13:09:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32774 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237933AbiIERIn (ORCPT ); Mon, 5 Sep 2022 13:08:43 -0400 Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 776B95E652; Mon, 5 Sep 2022 10:08:42 -0700 (PDT) Received: by mail-ej1-x62d.google.com with SMTP id bj12so18197222ejb.13; Mon, 05 Sep 2022 10:08:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date; bh=6LIxTAJug7A8Tl6xx53DgoK4IuE8wAXvJAt6gsPG4/M=; b=DIYJ34b0XROdRhN0VH5YQXvj/AmF++L/yE0vQJEQJku2kxmxEskSiuEDtO0qSDzJRt L7m6VgUMwLFPdxyp8u6lq1Pw7VR4Vf/ejZIrtSUii/WDVs+LIlNUjfkuK0FQk4hWD6gw hVeL2+tfa7RfOzThsSSsWYL3xxp10QIdwJz+NDeBRaYcMP3/feulftTJbNl3qcIRW+t0 nrcdsXVHw9DbYcYfsHRanpnBhp9BcXxw3pPbtaNQSVPYQO4n5FrKMCvDE4dynwnO1pr3 6DHUE46e3b3qZFeCEh6Qre1ocXYBylMBz/3ofdE5dwVXxe1c0h4okNIOiYrxhlsCq3ts ygRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date; bh=6LIxTAJug7A8Tl6xx53DgoK4IuE8wAXvJAt6gsPG4/M=; b=kYaNXHPbmQY4Lx1CoVyKsrFZU5XtLC17ZutJCykZ55MGlbx4tC0ZacFiNZAJWnRGxi X6F6GcBoOesf8ebUXmPlS4vPlOJwv/diwOrFRh1acikp33OR5PvYhGD59SzrC0gcB+ah /SnpyQt7TrYWf6qOe2TkcK2Ww6XpimTfnPapnGhMA32y225/PdaG8xSd4TVcwi0W3HfH Me8AGJh6nrqPp6ZjzatniC0ANbs3Nh0979c81GD08n7/mC9DmH9/pRRDK/raQv5ZR0Dr yIcXEo2yJ/YQtOFY5+SkKmhbXyufYAcinDSkuIJa4uCNgE/laj7lvI4pW3Q4gpcImBTB hSMQ== X-Gm-Message-State: ACgBeo3Nncr8Eu+J1v6jMyk9+3erwz9kvlW0TJws8sSwa/Joly4ynsrP cbQo90zV1QyMv22CHA6W7+U= X-Google-Smtp-Source: AA6agR6LTdgtPjgPGiwtUtFQVSfePKqDFFyzY7pRTngkDS49HXM+4HORfinbu6vlFAlmFnTc+k7wUA== X-Received: by 2002:a17:907:2d14:b0:73f:fabc:332c with SMTP id gs20-20020a1709072d1400b0073ffabc332cmr34145288ejc.704.1662397720893; Mon, 05 Sep 2022 10:08:40 -0700 (PDT) Received: from localhost (p200300e41f12c800f22f74fffe1f3a53.dip0.t-ipconnect.de. [2003:e4:1f12:c800:f22f:74ff:fe1f:3a53]) by smtp.gmail.com with ESMTPSA id 18-20020a170906301200b0073d6093ac93sm5397026ejz.16.2022.09.05.10.08.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 05 Sep 2022 10:08:39 -0700 (PDT) From: Thierry Reding To: Rob Herring , Joerg Roedel Cc: Will Deacon , Robin Murphy , Nicolin Chen , Krishna Reddy , Dmitry Osipenko , Alyssa Rosenzweig , Janne Grunau , Sameer Pujar , devicetree@vger.kernel.org, iommu@lists.linux-foundation.org, linux-tegra@vger.kernel.org, asahi@lists.linux.dev Subject: [PATCH v8 1/5] dt-bindings: reserved-memory: Document iommu-addresses Date: Mon, 5 Sep 2022 19:08:29 +0200 Message-Id: <20220905170833.396892-2-thierry.reding@gmail.com> X-Mailer: git-send-email 2.37.2 In-Reply-To: <20220905170833.396892-1-thierry.reding@gmail.com> References: <20220905170833.396892-1-thierry.reding@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-tegra@vger.kernel.org From: Thierry Reding This adds the "iommu-addresses" property to reserved-memory nodes, which allow describing the interaction of memory regions with IOMMUs. Two use- cases are supported: 1. Static mappings can be described by pairing the "iommu-addresses" property with a "reg" property. This is mostly useful for adopting firmware-allocated buffers via identity mappings. One common use- case where this is required is if early firmware or bootloaders have set up a bootsplash framebuffer that a display controller is actively scanning out from during the operating system boot process. 2. If an "iommu-addresses" property exists without a "reg" property, the reserved-memory node describes an IOVA reservation. Such memory regions are excluded from the IOVA space available to operating system drivers and can be used for regions that must not be used to map arbitrary buffers. Each mapping or reservation is tied to a specific device via a phandle to the device's device tree node. This allows a reserved-memory region to be reused across multiple devices. Signed-off-by: Thierry Reding --- Changes in v8: - include validation warning fixes that had crept into an unrelated patch Changes in v7: - keep reserved-memory.txt to avoid broken references Changes in v6: - add device phandle to iommu-addresses property in examples - remove now unused dt-bindings/reserved-memory.h header .../reserved-memory/reserved-memory.yaml | 70 +++++++++++++++++++ 1 file changed, 70 insertions(+) diff --git a/Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml b/Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml index 44f72bcf1782..fb48d016e368 100644 --- a/Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml +++ b/Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml @@ -52,6 +52,30 @@ properties: Address and Length pairs. Specifies regions of memory that are acceptable to allocate from. + iommu-addresses: + $ref: /schemas/types.yaml#/definitions/phandle-array + description: > + A list of phandle and specifier pairs that describe static IO virtual + address space mappings and carveouts associated with a given reserved + memory region. The phandle in the first cell refers to the device for + which the mapping or carveout is to be created. + + The specifier consists of an address/size pair and denotes the IO + virtual address range of the region for the given device. The exact + format depends on the values of the "#address-cells" and "#size-cells" + properties of the device referenced via the phandle. + + When used in combination with a "reg" property, an IOVA mapping is to + be established for this memory region. One example where this can be + useful is to create an identity mapping for physical memory that the + firmware has configured some hardware to access (such as a bootsplash + framebuffer). + + If no "reg" property is specified, the "iommu-addresses" property + defines carveout regions in the IOVA space for the given device. This + can be useful if a certain memory region should not be mapped through + the IOMMU. + no-map: type: boolean description: > @@ -97,4 +121,50 @@ oneOf: additionalProperties: true +examples: + - | + / { + compatible = "foo"; + model = "foo"; + + #address-cells = <2>; + #size-cells = <2>; + + reserved-memory { + #address-cells = <2>; + #size-cells = <2>; + ranges; + + adsp_resv: reservation-adsp { + /* + * Restrict IOVA mappings for ADSP buffers to the 512 MiB region + * from 0x40000000 - 0x5fffffff. Anything outside is reserved by + * the ADSP for I/O memory and private memory allocations. + */ + iommu-addresses = <&adsp 0x0 0x00000000 0x00 0x40000000>, + <&adsp 0x0 0x60000000 0xff 0xa0000000>; + }; + + fb: framebuffer@90000000 { + reg = <0x0 0x90000000 0x0 0x00800000>; + iommu-addresses = <&dc0 0x0 0x90000000 0x0 0x00800000>; + }; + }; + + bus@0 { + #address-cells = <1>; + #size-cells = <1>; + ranges = <0x0 0x0 0x0 0x40000000>; + + adsp: adsp@2990000 { + reg = <0x2990000 0x2000>; + memory-region = <&adsp_resv>; + }; + + dc0: display@15200000 { + reg = <0x15200000 0x10000>; + memory-region = <&fb>; + }; + }; + }; ... -- 2.37.2