From: Changming Huang <jerry.huang@nxp.com> To: broonie@kernel.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, linux-spi@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, shawnguo@kernel.org, leoyang.li@nxp.com, linux-arm-kernel@lists.infradead.org Cc: Changming Huang <jerry.huang@nxp.com> Subject: [PATCH 1/3 v5] dt-bindings: dspi: added for MikcroBus socket Date: Tue, 26 Apr 2022 10:24:11 +0800 [thread overview] Message-ID: <20220426022413.885092-1-jerry.huang@nxp.com> (raw) Signed-off-by: Changming Huang <jerry.huang@nxp.com> --- changes in v5: - rename compatible name to mikcroe,mikcroe-socket changes in v4: - rename example node, adjust description changes in v3: - add the dt-bindings .../bindings/spi/mikcroe,mikcroe-socket.yaml | 50 +++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 Documentation/devicetree/bindings/spi/mikcroe,mikcroe-socket.yaml diff --git a/Documentation/devicetree/bindings/spi/mikcroe,mikcroe-socket.yaml b/Documentation/devicetree/bindings/spi/mikcroe,mikcroe-socket.yaml new file mode 100644 index 000000000000..2b0abf7f1d84 --- /dev/null +++ b/Documentation/devicetree/bindings/spi/mikcroe,mikcroe-socket.yaml @@ -0,0 +1,50 @@ +# SPDX-License-Identifier: GPL-2.0 +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/spi/mikcroe,mikcroe-spi# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: MikcroBus SPI device bindings + +maintainers: + - Changming Huang <jerry.huang@nxp.com> + +allOf: + - $ref: "spi-controller.yaml" + +properties: + compatible: + const: mikcroe,mikcroe-socket + + reg: + maxItems: 1 + + spi-max-frequency: true + + fsl,spi-cs-sck-delay: true + + fsl,spi-sck-cs-delay: true + +required: + - compatible + - reg + - spi-max-frequency + +additionalProperties: false + +examples: + - | + &dspi2 { + bus-num = <2>; + status = "okay"; + + spi@0 { + compatible = "mikcroe,mikcroe-socket"; + reg = <0>; + spi-max-frequency = <2000000>; + fsl,spi-cs-sck-delay = <1000000>; + fsl,spi-sck-cs-delay = <50>; + }; + }; + +... -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Changming Huang <jerry.huang@nxp.com> To: broonie@kernel.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, linux-spi@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, shawnguo@kernel.org, leoyang.li@nxp.com, linux-arm-kernel@lists.infradead.org Cc: Changming Huang <jerry.huang@nxp.com> Subject: [PATCH 1/3 v5] dt-bindings: dspi: added for MikcroBus socket Date: Tue, 26 Apr 2022 10:24:11 +0800 [thread overview] Message-ID: <20220426022413.885092-1-jerry.huang@nxp.com> (raw) Signed-off-by: Changming Huang <jerry.huang@nxp.com> --- changes in v5: - rename compatible name to mikcroe,mikcroe-socket changes in v4: - rename example node, adjust description changes in v3: - add the dt-bindings .../bindings/spi/mikcroe,mikcroe-socket.yaml | 50 +++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 Documentation/devicetree/bindings/spi/mikcroe,mikcroe-socket.yaml diff --git a/Documentation/devicetree/bindings/spi/mikcroe,mikcroe-socket.yaml b/Documentation/devicetree/bindings/spi/mikcroe,mikcroe-socket.yaml new file mode 100644 index 000000000000..2b0abf7f1d84 --- /dev/null +++ b/Documentation/devicetree/bindings/spi/mikcroe,mikcroe-socket.yaml @@ -0,0 +1,50 @@ +# SPDX-License-Identifier: GPL-2.0 +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/spi/mikcroe,mikcroe-spi# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: MikcroBus SPI device bindings + +maintainers: + - Changming Huang <jerry.huang@nxp.com> + +allOf: + - $ref: "spi-controller.yaml" + +properties: + compatible: + const: mikcroe,mikcroe-socket + + reg: + maxItems: 1 + + spi-max-frequency: true + + fsl,spi-cs-sck-delay: true + + fsl,spi-sck-cs-delay: true + +required: + - compatible + - reg + - spi-max-frequency + +additionalProperties: false + +examples: + - | + &dspi2 { + bus-num = <2>; + status = "okay"; + + spi@0 { + compatible = "mikcroe,mikcroe-socket"; + reg = <0>; + spi-max-frequency = <2000000>; + fsl,spi-cs-sck-delay = <1000000>; + fsl,spi-sck-cs-delay = <50>; + }; + }; + +... -- 2.25.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-04-26 2:24 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-26 2:24 Changming Huang [this message] 2022-04-26 2:24 ` [PATCH 1/3 v5] dt-bindings: dspi: added for MikcroBus socket Changming Huang 2022-04-26 2:24 ` [PATCH 2/3 v5] arm64: dts: fsl-ls1028a: add dspi2 support Changming Huang 2022-04-26 2:24 ` Changming Huang 2022-04-26 2:24 ` [PATCH 3/3 v5] spi: spidev: add MikcroBus socket to device tree compatibility list Changming Huang 2022-04-26 2:24 ` Changming Huang 2022-04-26 13:39 ` [PATCH 1/3 v5] dt-bindings: dspi: added for MikcroBus socket Rob Herring 2022-04-26 13:39 ` Rob Herring 2022-04-26 15:55 ` Rob Herring 2022-04-26 15:55 ` Rob Herring 2022-04-27 9:37 ` Michael Walle 2022-04-27 9:37 ` Michael Walle
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=20220426022413.885092-1-jerry.huang@nxp.com \ --to=jerry.huang@nxp.com \ --cc=broonie@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=leoyang.li@nxp.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-spi@vger.kernel.org \ --cc=robh+dt@kernel.org \ --cc=shawnguo@kernel.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.