Skip to contentSkip to conversation

dt-bindings: spi: tegra-slink: Convert to json-schema

PATCH In review Thierry Reding 3 participants 7 messages Jul 5, 2023 – Jul 11, 2023

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/3 dt-bindings: spi: tegra-slink: Convert to json-schema

From: Thierry Reding <[email protected]>

Convert the Tegra SLINK bindings from the free-form text format to json-schema.

---
 .../bindings/spi/nvidia,tegra20-slink.txt     | 37 --------
 .../bindings/spi/nvidia,tegra20-slink.yaml    | 90 +++++++++++++++++++
 2 files changed, 90 insertions(+), 37 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra20-slink.txt
 create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra20-slink.yaml
Documentation/devicetree/bindings/spi/nvidia,tegra20-slink.txt deleted +0 -37
deleted file mode 100644
index 40d80b93e327..000000000000
@@ -1,37 +0,0 @@
-NVIDIA Tegra20/Tegra30 SLINK controller.
-
-Required properties:
-- compatible : should be "nvidia,tegra20-slink", "nvidia,tegra30-slink".
-- reg: Should contain SLINK registers location and length.
-- interrupts: Should contain SLINK interrupts.
-- clocks : Must contain one entry, for the module clock.
-  See ../clocks/clock-bindings.txt for details.
-- resets : Must contain an entry for each entry in reset-names.
-  See ../reset/reset.txt for details.
-- reset-names : Must include the following entries:
-  - spi
-- dmas : Must contain an entry for each entry in clock-names.
-  See ../dma/dma.txt for details.
-- dma-names : Must include the following entries:
-  - rx
-  - tx
-
-Recommended properties:
-- spi-max-frequency: Definition as per
-                     Documentation/devicetree/bindings/spi/spi-bus.txt
-
-Example:
-
-spi@7000d600 {
-	compatible = "nvidia,tegra20-slink";
-	reg = <0x7000d600 0x200>;
-	interrupts = <0 82 0x04>;
-	spi-max-frequency = <25000000>;
-	#address-cells = <1>;
-	#size-cells = <0>;
-	clocks = <&tegra_car 44>;
-	resets = <&tegra_car 44>;
-	reset-names = "spi";
-	dmas = <&apbdma 16>, <&apbdma 16>;
-	dma-names = "rx", "tx";
-};
Documentation/devicetree/bindings/spi/nvidia,tegra20-slink.yaml new file +90 -0

90 lines not on this page · raw message

Signature · 1 line
2.41.0
#1 lore raw

PATCH 2/3 dt-bindings: spi: tegra-sflash: Convert to json-schema

From: Thierry Reding <[email protected]>

Convert the Tegra SFLASH controller bindings from the free-form text format to json-schema.

---
 .../bindings/spi/nvidia,tegra20-sflash.txt    | 37 ---------
 .../bindings/spi/nvidia,tegra20-sflash.yaml   | 81 +++++++++++++++++++
 2 files changed, 81 insertions(+), 37 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra20-sflash.txt
 create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra20-sflash.yaml
Documentation/devicetree/bindings/spi/nvidia,tegra20-sflash.txt deleted +0 -37
deleted file mode 100644
index c212491929b5..000000000000
@@ -1,37 +0,0 @@
-NVIDIA Tegra20 SFLASH controller.
-
-Required properties:
-- compatible : should be "nvidia,tegra20-sflash".
-- reg: Should contain SFLASH registers location and length.
-- interrupts: Should contain SFLASH interrupts.
-- clocks : Must contain one entry, for the module clock.
-  See ../clocks/clock-bindings.txt for details.
-- resets : Must contain an entry for each entry in reset-names.
-  See ../reset/reset.txt for details.
-- reset-names : Must include the following entries:
-  - spi
-- dmas : Must contain an entry for each entry in clock-names.
-  See ../dma/dma.txt for details.
-- dma-names : Must include the following entries:
-  - rx
-  - tx
-
-Recommended properties:
-- spi-max-frequency: Definition as per
-                     Documentation/devicetree/bindings/spi/spi-bus.txt
-
-Example:
-
-spi@7000c380 {
-	compatible = "nvidia,tegra20-sflash";
-	reg = <0x7000c380 0x80>;
-	interrupts = <0 39 0x04>;
-	spi-max-frequency = <25000000>;
-	#address-cells = <1>;
-	#size-cells = <0>;
-	clocks = <&tegra_car 43>;
-	resets = <&tegra_car 43>;
-	reset-names = "spi";
-	dmas = <&apbdma 11>, <&apbdma 11>;
-	dma-names = "rx", "tx";
-};
Documentation/devicetree/bindings/spi/nvidia,tegra20-sflash.yaml new file +81 -0

81 lines not on this page · raw message

Signature · 1 line
2.41.0
maintainer Reviewed-by on v1 2/3
#2 lore raw

Re: [PATCH 2/3] dt-bindings: spi: tegra-sflash: Convert to json-schema

Quoted 5 lines · Thierry Reding

From: Thierry Reding <[email protected]>

Convert the Tegra SFLASH controller bindings from the free-form text format to json-schema.

Quoted 8 lines
---
 .../bindings/spi/nvidia,tegra20-sflash.txt    | 37 ---------
 .../bindings/spi/nvidia,tegra20-sflash.yaml   | 81 +++++++++++++++++++
 2 files changed, 81 insertions(+), 37 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra20-sflash.txt
 create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra20-sflash.yaml
#3 lore raw

PATCH 3/3 dt-bindings: spi: Convert Tegra114 SPI to json-schema

In reply to Thierry Reding

From: Thierry Reding <[email protected]>

Convert the Tegra114 SPI controller device tree bindings from plain text to json-schema format.

---
 .../bindings/spi/nvidia,tegra114-spi.txt      |  61 -----------
 .../bindings/spi/nvidia,tegra114-spi.yaml     | 100 ++++++++++++++++++
 2 files changed, 100 insertions(+), 61 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra114-spi.txt
 create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra114-spi.yaml
Documentation/devicetree/bindings/spi/nvidia,tegra114-spi.txt deleted +0 -61
deleted file mode 100644
index db8e0d71c5bc..000000000000
@@ -1,61 +0,0 @@
-NVIDIA Tegra114 SPI controller.
-
-Required properties:
-- compatible : For Tegra114, must contain "nvidia,tegra114-spi".
-  Otherwise, must contain '"nvidia,<chip>-spi", "nvidia,tegra114-spi"' where
-  <chip> is tegra124, tegra132, or tegra210.
-- reg: Should contain SPI registers location and length.
-- interrupts: Should contain SPI interrupts.
-- clock-names : Must include the following entries:
-  - spi
-- resets : Must contain an entry for each entry in reset-names.
-  See ../reset/reset.txt for details.
-- reset-names : Must include the following entries:
-  - spi
-- dmas : Must contain an entry for each entry in clock-names.
-  See ../dma/dma.txt for details.
-- dma-names : Must include the following entries:
-  - rx
-  - tx
-- clocks : Must contain an entry for each entry in clock-names.
-  See ../clocks/clock-bindings.txt for details.
-
-Recommended properties:
-- spi-max-frequency: Definition as per
-                     Documentation/devicetree/bindings/spi/spi-bus.txt
-Optional properties:
-- nvidia,tx-clk-tap-delay: Delays the clock going out to the external device
-  with this tap value. This property is used to tune the outgoing data from
-  Tegra SPI master with respect to outgoing Tegra SPI master clock.
-  Tap values vary based on the platform design trace lengths from Tegra SPI
-  to corresponding slave devices. Valid tap values are from 0 thru 63.
-- nvidia,rx-clk-tap-delay: Delays the clock coming in from the external device
-  with this tap value. This property is used to adjust the Tegra SPI master
-  clock with respect to the data from the SPI slave device.
-  Tap values vary based on the platform design trace lengths from Tegra SPI
-  to corresponding slave devices. Valid tap values are from 0 thru 63.
-
-Example:
-
-spi@7000d600 {
-	compatible = "nvidia,tegra114-spi";
-	reg = <0x7000d600 0x200>;
-	interrupts = <0 82 0x04>;
-	spi-max-frequency = <25000000>;
-	#address-cells = <1>;
-	#size-cells = <0>;
-	clocks = <&tegra_car 44>;
-	clock-names = "spi";
-	resets = <&tegra_car 44>;
-	reset-names = "spi";
-	dmas = <&apbdma 16>, <&apbdma 16>;
-	dma-names = "rx", "tx";
-	<spi-client>@<bus_num> {
-		...
-		...
-		nvidia,rx-clk-tap-delay = <0>;
-		nvidia,tx-clk-tap-delay = <16>;
-		...
-	};
-
-};
Documentation/devicetree/bindings/spi/nvidia,tegra114-spi.yaml new file +100 -0

100 lines not on this page · raw message

Signature · 1 line
2.41.0
maintainer Reviewed-by on v1 3/3
#4 lore raw

Re: [PATCH 3/3] dt-bindings: spi: Convert Tegra114 SPI to json-schema

Quoted 5 lines · Thierry Reding

From: Thierry Reding <[email protected]>

Convert the Tegra114 SPI controller device tree bindings from plain text to json-schema format.

Quoted 8 lines
---
 .../bindings/spi/nvidia,tegra114-spi.txt      |  61 -----------
 .../bindings/spi/nvidia,tegra114-spi.yaml     | 100 ++++++++++++++++++
 2 files changed, 100 insertions(+), 61 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra114-spi.txt
 create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra114-spi.yaml
maintainer Reviewed-by on v1 1/3
#5 lore raw
In reply to Thierry Reding
Quoted 5 lines · Thierry Reding

From: Thierry Reding <[email protected]>

Convert the Tegra SLINK bindings from the free-form text format to json-schema.

Quoted 8 lines
---
 .../bindings/spi/nvidia,tegra20-slink.txt     | 37 --------
 .../bindings/spi/nvidia,tegra20-slink.yaml    | 90 +++++++++++++++++++
 2 files changed, 90 insertions(+), 37 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra20-slink.txt
 create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra20-slink.yaml
maintainer
#6 lore raw
In reply to Thierry Reding
Quoted 4 lines · Thierry Reding

Convert the Tegra SLINK bindings from the free-form text format to json-schema.

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/3] dt-bindings: spi: tegra-slink: Convert to json-schema

      commit: 8c87a46e2ce3d5aaf315ffb61dcda62417e41bbf
[2/3] dt-bindings: spi: tegra-sflash: Convert to json-schema
      commit: 17a9ab02f72c832293155a432895c889842b7da4
[3/3] dt-bindings: spi: Convert Tegra114 SPI to json-schema
      commit: b8968c388b69d9cf31d7f5b1721ac7fe9f932cb9

All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying to this mail.

Thanks,
Mark