From: "Rafał Miłecki" <zajec5@gmail.com> To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> Cc: "Matthias Brugger" <matthias.bgg@gmail.com>, "Kunihiko Hayashi" <hayashi.kunihiko@socionext.com>, "Masami Hiramatsu" <mhiramat@kernel.org>, linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl> Subject: [PATCH 1/4] dt-bindings: nvmem: mmio: new binding for MMIO accessible NVMEM devices Date: Wed, 1 Feb 2023 07:47:14 +0100 [thread overview] Message-ID: <20230201064717.18410-2-zajec5@gmail.com> (raw) In-Reply-To: <20230201064717.18410-1-zajec5@gmail.com> From: Rafał Miłecki <rafal@milecki.pl> With the NVMEM layouts binding in place we should now use: 1. NVMEM device access bindings 2. NVMEM content description bindings This binding allows describing NVMEM devices that can be MMIO accessed. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> --- .../devicetree/bindings/nvmem/mmio.yaml | 46 +++++++++++++++++++ 1 file changed, 46 insertions(+) create mode 100644 Documentation/devicetree/bindings/nvmem/mmio.yaml diff --git a/Documentation/devicetree/bindings/nvmem/mmio.yaml b/Documentation/devicetree/bindings/nvmem/mmio.yaml new file mode 100644 index 000000000000..27e3f6142769 --- /dev/null +++ b/Documentation/devicetree/bindings/nvmem/mmio.yaml @@ -0,0 +1,46 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/nvmem/mmio.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: MMIO access based NVMEM + +description: | + This binding describes simple NVMEM devices that can be accessed by using MMIO + (memory-mapped I/O access). + + It's a generic solution for providing NVMEM content access. The way of + handling actual content may be device specific and can be described using a + proper layout. + +maintainers: + - Rafał Miłecki <rafal@milecki.pl> + +allOf: + - $ref: nvmem.yaml# + +properties: + compatible: + const: mmio-nvmem + + reg: + maxItems: 1 + + reg-io-width: + description: | + The size (in bytes) of the IO accesses that should be performed + on the device. + enum: [1, 2, 4, 8] + +required: + - reg + +unevaluatedProperties: false + +examples: + - | + nvmem@10000 { + compatible = "mmio-nvmem"; + reg = <0x10000000 0x10000>; + }; -- 2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: "Rafał Miłecki" <zajec5@gmail.com> To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> Cc: "Matthias Brugger" <matthias.bgg@gmail.com>, "Kunihiko Hayashi" <hayashi.kunihiko@socionext.com>, "Masami Hiramatsu" <mhiramat@kernel.org>, linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl> Subject: [PATCH 1/4] dt-bindings: nvmem: mmio: new binding for MMIO accessible NVMEM devices Date: Wed, 1 Feb 2023 07:47:14 +0100 [thread overview] Message-ID: <20230201064717.18410-2-zajec5@gmail.com> (raw) In-Reply-To: <20230201064717.18410-1-zajec5@gmail.com> From: Rafał Miłecki <rafal@milecki.pl> With the NVMEM layouts binding in place we should now use: 1. NVMEM device access bindings 2. NVMEM content description bindings This binding allows describing NVMEM devices that can be MMIO accessed. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> --- .../devicetree/bindings/nvmem/mmio.yaml | 46 +++++++++++++++++++ 1 file changed, 46 insertions(+) create mode 100644 Documentation/devicetree/bindings/nvmem/mmio.yaml diff --git a/Documentation/devicetree/bindings/nvmem/mmio.yaml b/Documentation/devicetree/bindings/nvmem/mmio.yaml new file mode 100644 index 000000000000..27e3f6142769 --- /dev/null +++ b/Documentation/devicetree/bindings/nvmem/mmio.yaml @@ -0,0 +1,46 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/nvmem/mmio.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: MMIO access based NVMEM + +description: | + This binding describes simple NVMEM devices that can be accessed by using MMIO + (memory-mapped I/O access). + + It's a generic solution for providing NVMEM content access. The way of + handling actual content may be device specific and can be described using a + proper layout. + +maintainers: + - Rafał Miłecki <rafal@milecki.pl> + +allOf: + - $ref: nvmem.yaml# + +properties: + compatible: + const: mmio-nvmem + + reg: + maxItems: 1 + + reg-io-width: + description: | + The size (in bytes) of the IO accesses that should be performed + on the device. + enum: [1, 2, 4, 8] + +required: + - reg + +unevaluatedProperties: false + +examples: + - | + nvmem@10000 { + compatible = "mmio-nvmem"; + reg = <0x10000000 0x10000>; + }; -- 2.34.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-01 6:52 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-01 6:47 [PATCH 0/4] nvmem: add and use generic MMIO NVMEM Rafał Miłecki 2023-02-01 6:47 ` Rafał Miłecki 2023-02-01 6:47 ` Rafał Miłecki [this message] 2023-02-01 6:47 ` [PATCH 1/4] dt-bindings: nvmem: mmio: new binding for MMIO accessible NVMEM devices Rafał Miłecki 2023-02-03 21:06 ` Rob Herring 2023-02-03 21:06 ` Rob Herring 2023-02-01 6:47 ` [PATCH 2/4] nvmem: add generic driver for devices with MMIO access Rafał Miłecki 2023-02-01 6:47 ` Rafał Miłecki 2023-02-01 9:41 ` Kunihiko Hayashi 2023-02-01 9:41 ` Kunihiko Hayashi 2023-02-01 11:52 ` Srinivas Kandagatla 2023-02-01 11:52 ` Srinivas Kandagatla 2023-02-02 9:24 ` AngeloGioacchino Del Regno 2023-02-02 9:24 ` AngeloGioacchino Del Regno 2023-02-01 6:47 ` [PATCH 3/4] nvmem: mtk-efuse: replace driver with a generic MMIO one Rafał Miłecki 2023-02-01 6:47 ` Rafał Miłecki 2023-02-01 8:48 ` Michael Walle 2023-02-01 8:48 ` Michael Walle 2023-02-01 9:30 ` Rafał Miłecki 2023-02-01 9:30 ` Rafał Miłecki 2023-02-01 10:46 ` Michael Walle 2023-02-01 10:46 ` Michael Walle 2023-02-01 11:01 ` Rafał Miłecki 2023-02-01 11:01 ` Rafał Miłecki 2023-02-01 11:11 ` Michael Walle 2023-02-01 11:11 ` Michael Walle 2023-02-01 18:54 ` Rob Herring 2023-02-01 18:54 ` Rob Herring 2023-02-01 20:15 ` Michael Walle 2023-02-01 20:15 ` Michael Walle 2023-02-02 23:44 ` Rob Herring 2023-02-02 23:44 ` Rob Herring 2023-02-01 6:47 ` [PATCH 4/4] nvmem: uniphier-efuse: " Rafał Miłecki 2023-02-01 6:47 ` Rafał Miłecki 2023-02-01 7:50 ` [PATCH 0/4] nvmem: add and use generic MMIO NVMEM Rafał Miłecki 2023-02-01 7:50 ` Rafał Miłecki
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230201064717.18410-2-zajec5@gmail.com \ --to=zajec5@gmail.com \ --cc=devicetree@vger.kernel.org \ --cc=hayashi.kunihiko@socionext.com \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=matthias.bgg@gmail.com \ --cc=mhiramat@kernel.org \ --cc=rafal@milecki.pl \ --cc=robh+dt@kernel.org \ --cc=srinivas.kandagatla@linaro.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.