-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge tag 'devicetree-fixes-for-5.16-1' of git://git.kernel.org/pub/s…
…cm/linux/kernel/git/robh/linux Pull devicetree fixes from Rob Herring: - Two fixes due to DT node name changes on Arm, Ltd. boards - Treewide rename of Ingenic CGU headers - Update ST email addresses - Remove Netlogic DT bindings - Dropping few more cases of redundant 'maxItems' in schemas - Convert toshiba,tc358767 bridge binding to schema * tag 'devicetree-fixes-for-5.16-1' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux: dt-bindings: watchdog: sunxi: fix error in schema bindings: media: venus: Drop redundant maxItems for power-domain-names dt-bindings: Remove Netlogic bindings clk: versatile: clk-icst: Ensure clock names are unique of: Support using 'mask' in making device bus id dt-bindings: treewide: Update @st.com email address to @foss.st.com dt-bindings: media: Update maintainers for st,stm32-hwspinlock.yaml dt-bindings: media: Update maintainers for st,stm32-cec.yaml dt-bindings: mfd: timers: Update maintainers for st,stm32-timers dt-bindings: timer: Update maintainers for st,stm32-timer dt-bindings: i2c: imx: hardware do not restrict clock-frequency to only 100 and 400 kHz dt-bindings: display: bridge: Convert toshiba,tc358767.txt to yaml dt-bindings: Rename Ingenic CGU headers to ingenic,*.h
- Loading branch information
Showing
107 changed files
with
277 additions
and
277 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
54 changes: 0 additions & 54 deletions
54
Documentation/devicetree/bindings/display/bridge/toshiba,tc358767.txt
This file was deleted.
Oops, something went wrong.
158 changes: 158 additions & 0 deletions
158
Documentation/devicetree/bindings/display/bridge/toshiba,tc358767.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,158 @@ | ||
| # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) | ||
| %YAML 1.2 | ||
| --- | ||
| $id: http://devicetree.org/schemas/display/bridge/toshiba,tc358767.yaml# | ||
| $schema: http://devicetree.org/meta-schemas/core.yaml# | ||
|
|
||
| title: Toshiba TC358767 eDP bridge bindings | ||
|
|
||
| maintainers: | ||
| - Andrey Gusakov <andrey.gusakov@cogentembedded.com> | ||
|
|
||
| description: The TC358767 is bridge device which converts DSI/DPI to eDP/DP | ||
|
|
||
| properties: | ||
| compatible: | ||
| const: toshiba,tc358767 | ||
|
|
||
| reg: | ||
| enum: | ||
| - 0x68 | ||
| - 0x0f | ||
| description: | | ||
| i2c address of the bridge, 0x68 or 0x0f, depending on bootstrap pins | ||
| clock-names: | ||
| const: "ref" | ||
|
|
||
| clocks: | ||
| maxItems: 1 | ||
| description: | | ||
| OF device-tree clock specification for refclk input. The reference. | ||
| clock rate must be 13 MHz, 19.2 MHz, 26 MHz, or 38.4 MHz. | ||
| shutdown-gpios: | ||
| maxItems: 1 | ||
| description: | | ||
| OF device-tree gpio specification for SD pin(active high shutdown input) | ||
| reset-gpios: | ||
| maxItems: 1 | ||
| description: | | ||
| OF device-tree gpio specification for RSTX pin(active low system reset) | ||
| toshiba,hpd-pin: | ||
| $ref: /schemas/types.yaml#/definitions/uint32 | ||
| enum: | ||
| - 0 | ||
| - 1 | ||
| description: TC358767 GPIO pin number to which HPD is connected to (0 or 1) | ||
|
|
||
| ports: | ||
| $ref: /schemas/graph.yaml#/properties/ports | ||
|
|
||
| properties: | ||
| port@0: | ||
| $ref: /schemas/graph.yaml#/properties/port | ||
| description: | | ||
| DSI input port. The remote endpoint phandle should be a | ||
| reference to a valid DSI output endpoint node | ||
| port@1: | ||
| $ref: /schemas/graph.yaml#/properties/port | ||
| description: | | ||
| DPI input port. The remote endpoint phandle should be a | ||
| reference to a valid DPI output endpoint node | ||
| port@2: | ||
| $ref: /schemas/graph.yaml#/properties/port | ||
| description: | | ||
| eDP/DP output port. The remote endpoint phandle should be a | ||
| reference to a valid eDP panel input endpoint node. This port is | ||
| optional, treated as DP panel if not defined | ||
| oneOf: | ||
| - required: | ||
| - port@0 | ||
| - required: | ||
| - port@1 | ||
|
|
||
|
|
||
| required: | ||
| - compatible | ||
| - reg | ||
| - clock-names | ||
| - clocks | ||
| - ports | ||
|
|
||
| additionalProperties: false | ||
|
|
||
| examples: | ||
| - | | ||
| #include <dt-bindings/gpio/gpio.h> | ||
| /* DPI input and eDP output */ | ||
| i2c { | ||
| #address-cells = <1>; | ||
| #size-cells = <0>; | ||
| edp-bridge@68 { | ||
| compatible = "toshiba,tc358767"; | ||
| reg = <0x68>; | ||
| shutdown-gpios = <&gpio3 23 GPIO_ACTIVE_HIGH>; | ||
| reset-gpios = <&gpio3 24 GPIO_ACTIVE_LOW>; | ||
| clock-names = "ref"; | ||
| clocks = <&edp_refclk>; | ||
| ports { | ||
| #address-cells = <1>; | ||
| #size-cells = <0>; | ||
| port@1 { | ||
| reg = <1>; | ||
| bridge_in_0: endpoint { | ||
| remote-endpoint = <&dpi_out>; | ||
| }; | ||
| }; | ||
| port@2 { | ||
| reg = <2>; | ||
| bridge_out: endpoint { | ||
| remote-endpoint = <&panel_in>; | ||
| }; | ||
| }; | ||
| }; | ||
| }; | ||
| }; | ||
| - | | ||
| /* DPI input and DP output */ | ||
| i2c { | ||
| #address-cells = <1>; | ||
| #size-cells = <0>; | ||
| edp-bridge@68 { | ||
| compatible = "toshiba,tc358767"; | ||
| reg = <0x68>; | ||
| shutdown-gpios = <&gpio3 23 GPIO_ACTIVE_HIGH>; | ||
| reset-gpios = <&gpio3 24 GPIO_ACTIVE_LOW>; | ||
| clock-names = "ref"; | ||
| clocks = <&edp_refclk>; | ||
| ports { | ||
| #address-cells = <1>; | ||
| #size-cells = <0>; | ||
| port@1 { | ||
| reg = <1>; | ||
| bridge_in_1: endpoint { | ||
| remote-endpoint = <&dpi_out>; | ||
| }; | ||
| }; | ||
| }; | ||
| }; | ||
| }; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.