dt-bindings: sound: Remove unused 'linux,hdmi-audio'
Subsystems (4)
Rob Herring
maintainerPATCH 1/3 dt-bindings: sound: Remove unused 'linux,hdmi-audio'
The binding was added in 2013 and has had no driver since 2015.
--- Documentation/devicetree/bindings/sound/hdmi.txt | 16 ---------------- 1 file changed, 16 deletions(-) delete mode 100644 Documentation/devicetree/bindings/sound/hdmi.txt
Documentation/devicetree/bindings/sound/hdmi.txt deleted +0 -16
@@ -1,16 +0,0 @@ -Device-Tree bindings for dummy HDMI codec - -Required properties: - - compatible: should be "linux,hdmi-audio". - -CODEC output pins: - * TX - -CODEC input pins: - * RX - -Example node: - - hdmi_audio: hdmi_audio@0 { - compatible = "linux,hdmi-audio"; - };
Signature · 1 line
2.25.1
Rob Herring
maintainerPATCH 2/3 dt-bindings: phy: Remove phy-stih41x-usb binding
The driver was removed in 2016 in commit fb954c48aea6 ("phy:
stih41x-usb: Remove usb phy driver and dt binding documentation.") and somehow the DT binding got dropped despite the subject.
--- .../bindings/phy/phy-stih41x-usb.txt | 24 ------------------- 1 file changed, 24 deletions(-) delete mode 100644 Documentation/devicetree/bindings/phy/phy-stih41x-usb.txt
Documentation/devicetree/bindings/phy/phy-stih41x-usb.txt deleted +0 -24
@@ -1,24 +0,0 @@ -STMicroelectronics STiH41x USB PHY binding ------------------------------------------- - -This file contains documentation for the usb phy found in STiH415/6 SoCs from -STMicroelectronics. - -Required properties: -- compatible : should be "st,stih416-usb-phy" or "st,stih415-usb-phy" -- st,syscfg : should be a phandle of the syscfg node -- clock-names : must contain "osc_phy" -- clocks : must contain an entry for each name in clock-names. -See: Documentation/devicetree/bindings/clock/clock-bindings.txt -- #phy-cells : must be 0 for this phy -See: Documentation/devicetree/bindings/phy/phy-bindings.txt - -Example: - -usb2_phy: usb2phy@0 { - compatible = "st,stih416-usb-phy"; - #phy-cells = <0>; - st,syscfg = <&syscfg_rear>; - clocks = <&clk_sysin>; - clock-names = "osc_phy"; -};
Signature · 1 line
2.25.1
Rob Herring
maintainerPATCH 3/3 dt-bindings: interrupt-controller: Remove obsolete 'img,meta-intc'
In reply to Rob HerringThe driver and metag arch were removed in 2018.
--- .../interrupt-controller/img,meta-intc.txt | 82 ------------------- 1 file changed, 82 deletions(-) delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/img,meta-intc.txt
Documentation/devicetree/bindings/interrupt-controller/img,meta-intc.txt deleted +0 -82
@@ -1,82 +0,0 @@ -* Meta External Trigger Controller Binding - -This binding specifies what properties must be available in the device tree -representation of a Meta external trigger controller. - -Required properties: - - - compatible: Specifies the compatibility list for the interrupt controller. - The type shall be <string> and the value shall include "img,meta-intc". - - - num-banks: Specifies the number of interrupt banks (each of which can - handle 32 interrupt sources). - - - interrupt-controller: The presence of this property identifies the node - as an interrupt controller. No property value shall be defined. - - - #interrupt-cells: Specifies the number of cells needed to encode an - interrupt source. The type shall be a <u32> and the value shall be 2. - - - #address-cells: Specifies the number of cells needed to encode an - address. The type shall be <u32> and the value shall be 0. As such, - 'interrupt-map' nodes do not have to specify a parent unit address. - -Optional properties: - - - no-mask: The controller doesn't have any mask registers. - -* Interrupt Specifier Definition - - Interrupt specifiers consists of 2 cells encoded as follows: - - - <1st-cell>: The interrupt-number that identifies the interrupt source. - - - <2nd-cell>: The Linux interrupt flags containing level-sense information, - encoded as follows: - 1 = edge triggered - 4 = level-sensitive - -* Examples - -Example 1: - - /* - * Meta external trigger block - */ - intc: intc { - // This is an interrupt controller node. - interrupt-controller; - - // No address cells so that 'interrupt-map' nodes which - // reference this interrupt controller node do not need a parent - // address specifier. - #address-cells = <0>; - - // Two cells to encode interrupt sources. - #interrupt-cells = <2>; - - // Number of interrupt banks - num-banks = <2>; - - // No HWMASKEXT is available (specify on Chorus2 and Comet ES1) - no-mask; - - // Compatible with Meta hardware trigger block. - compatible = "img,meta-intc"; - }; - -Example 2: - - /* - * An interrupt generating device that is wired to a Meta external - * trigger block. - */ - uart1: uart@02004c00 { - // Interrupt source '5' that is level-sensitive. - // Note that there are only two cells as specified in the - // interrupt parent's '#interrupt-cells' property. - interrupts = <5 4 /* level */>; - - // The interrupt controller that this device is wired to. - interrupt-parent = <&intc>; - };
Signature · 1 line
2.25.1
Mark Brown
maintainerQuoted 1 line · Rob Herring
The binding was added in 2013 and has had no driver since 2015.
There is the hdmi-codec driver that covers such hardware and would be compatible with the binding. Of course there are no current users so...
Rob Herring
maintainerQuoted 6 lines · Mark Brown
Quoted 1 line · Rob Herring
The binding was added in 2013 and has had no driver since 2015.
There is the hdmi-codec driver that covers such hardware and would be compatible with the binding. Of course there are no current users so...
I didn't dig into how TI restructured things to not need the binding anymore, but I'd assume the hdmi-codec is instantiated as part of some hdmi bridge device rather than being some standalone thing.
Rob
Mark Brown
maintainerQuoted 1 line · Rob Herring
The binding was added in 2013 and has had no driver since 2015.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: Remove unused 'linux,hdmi-audio'
commit: 08dd413b9ddf253ec3ee783a0a21df3754823be9
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