Loading Documentation/DocBook/media/v4l/dev-codec.xml +22 −13 Original line number Diff line number Diff line <title>Codec Interface</title> <note> <title>Suspended</title> <para>A V4L2 codec can compress, decompress, transform, or otherwise convert video data from one format into another format, in memory. Typically such devices are memory-to-memory devices (i.e. devices with the <constant>V4L2_CAP_VIDEO_M2M</constant> or <constant>V4L2_CAP_VIDEO_M2M_MPLANE</constant> capability set). </para> <para>This interface has been be suspended from the V4L2 API implemented in Linux 2.6 until we have more experience with codec device interfaces.</para> </note> <para>A memory-to-memory video node acts just like a normal video node, but it supports both output (sending frames from memory to the codec hardware) and capture (receiving the processed frames from the codec hardware into memory) stream I/O. An application will have to setup the stream I/O for both sides and finally call &VIDIOC-STREAMON; for both capture and output to start the codec.</para> <para>A V4L2 codec can compress, decompress, transform, or otherwise convert video data from one format into another format, in memory. Applications send data to be converted to the driver through a &func-write; call, and receive the converted data through a &func-read; call. For efficiency a driver may also support streaming I/O.</para> <para>Video compression codecs use the MPEG controls to setup their codec parameters (note that the MPEG controls actually support many more codecs than just MPEG). See <xref linkend="mpeg-controls"></xref>.</para> <para>[to do]</para> <para>Memory-to-memory devices can often be used as a shared resource: you can open the video node multiple times, each application setting up their own codec properties that are local to the file handle, and each can use it independently from the others. The driver will arbitrate access to the codec and reprogram it whenever another file handler gets access. This is different from the usual video node behavior where the video properties are global to the device (i.e. changing something through one file handle is visible through another file handle).</para> Documentation/DocBook/media/v4l/v4l2.xml +1 −1 Original line number Diff line number Diff line Loading @@ -493,7 +493,7 @@ and discussions on the V4L mailing list.</revremark> </partinfo> <title>Video for Linux Two API Specification</title> <subtitle>Revision 3.9</subtitle> <subtitle>Revision 3.10</subtitle> <chapter id="common"> &sub-common; Loading Documentation/devicetree/bindings/media/exynos-fimc-lite.txt +1 −1 Original line number Diff line number Diff line Loading @@ -2,7 +2,7 @@ Exynos4x12/Exynos5 SoC series camera host interface (FIMC-LITE) Required properties: - compatible : should be "samsung,exynos4212-fimc" for Exynos4212 and - compatible : should be "samsung,exynos4212-fimc-lite" for Exynos4212 and Exynos4412 SoCs; - reg : physical base address and size of the device memory mapped registers; Loading Documentation/devicetree/bindings/mfd/arizona.txt 0 → 100644 +62 −0 Original line number Diff line number Diff line Wolfson Arizona class audio SoCs These devices are audio SoCs with extensive digital capabilites and a range of analogue I/O. Required properties: - compatible : one of the following chip-specific strings: "wlf,wm5102" "wlf,wm5110" - reg : I2C slave address when connected using I2C, chip select number when using SPI. - interrupts : The interrupt line the /IRQ signal for the device is connected to. - interrupt-controller : Arizona class devices contain interrupt controllers and may provide interrupt services to other devices. - interrupt-parent : The parent interrupt controller. - #interrupt-cells: the number of cells to describe an IRQ, this should be 2. The first cell is the IRQ number. The second cell is the flags, encoded as the trigger masks from Documentation/devicetree/bindings/interrupts.txt - gpio-controller : Indicates this device is a GPIO controller. - #gpio-cells : Must be 2. The first cell is the pin number and the second cell is used to specify optional parameters (currently unused). - AVDD1-supply, DBVDD1-supply, DBVDD2-supply, DBVDD3-supply, CPVDD-supply, SPKVDDL-supply, SPKVDDR-supply : power supplies for the device, as covered in Documentation/devicetree/bindings/regulator/regulator.txt Optional properties: - wlf,reset : GPIO specifier for the GPIO controlling /RESET - wlf,ldoena : GPIO specifier for the GPIO controlling LDOENA - wlf,gpio-defaults : A list of GPIO configuration register values. If absent, no configuration of these registers is performed. If any entry has a value that is out of range for a 16 bit register then the chip default will be used. If present exactly five values must be specified. Example: codec: wm5102@1a { compatible = "wlf,wm5102"; reg = <0x1a>; interrupts = <347>; #interrupt-cells = <2>; interrupt-parent = <&gic>; gpio-controller; #gpio-cells = <2>; wlf,gpio-defaults = < 0x00000000, /* AIF1TXLRCLK */ 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, >; }; Documentation/devicetree/bindings/sound/adi,adau1701.txt 0 → 100644 +35 −0 Original line number Diff line number Diff line Analog Devices ADAU1701 Required properties: - compatible: Should contain "adi,adau1701" - reg: The i2c address. Value depends on the state of ADDR0 and ADDR1, as wired in hardware. Optional properties: - reset-gpio: A GPIO spec to define which pin is connected to the chip's !RESET pin. If specified, the driver will assert a hardware reset at probe time. - adi,pll-mode-gpios: An array of two GPIO specs to describe the GPIOs the ADAU's PLL config pins are connected to. The state of the pins are set according to the configured clock divider on ASoC side before the firmware is loaded. - adi,pin-config: An array of 12 numerical values selecting one of the pin configurations as described in the datasheet, table 53. Note that the value of this property has to be prefixed with '/bits/ 8'. Examples: i2c_bus { adau1701@34 { compatible = "adi,adau1701"; reg = <0x34>; reset-gpio = <&gpio 23 0>; adi,pll-mode-gpios = <&gpio 24 0 &gpio 25 0>; adi,pin-config = /bits/ 8 <0x4 0x7 0x5 0x5 0x4 0x4 0x4 0x4 0x4 0x4 0x4 0x4>; }; }; Loading
Documentation/DocBook/media/v4l/dev-codec.xml +22 −13 Original line number Diff line number Diff line <title>Codec Interface</title> <note> <title>Suspended</title> <para>A V4L2 codec can compress, decompress, transform, or otherwise convert video data from one format into another format, in memory. Typically such devices are memory-to-memory devices (i.e. devices with the <constant>V4L2_CAP_VIDEO_M2M</constant> or <constant>V4L2_CAP_VIDEO_M2M_MPLANE</constant> capability set). </para> <para>This interface has been be suspended from the V4L2 API implemented in Linux 2.6 until we have more experience with codec device interfaces.</para> </note> <para>A memory-to-memory video node acts just like a normal video node, but it supports both output (sending frames from memory to the codec hardware) and capture (receiving the processed frames from the codec hardware into memory) stream I/O. An application will have to setup the stream I/O for both sides and finally call &VIDIOC-STREAMON; for both capture and output to start the codec.</para> <para>A V4L2 codec can compress, decompress, transform, or otherwise convert video data from one format into another format, in memory. Applications send data to be converted to the driver through a &func-write; call, and receive the converted data through a &func-read; call. For efficiency a driver may also support streaming I/O.</para> <para>Video compression codecs use the MPEG controls to setup their codec parameters (note that the MPEG controls actually support many more codecs than just MPEG). See <xref linkend="mpeg-controls"></xref>.</para> <para>[to do]</para> <para>Memory-to-memory devices can often be used as a shared resource: you can open the video node multiple times, each application setting up their own codec properties that are local to the file handle, and each can use it independently from the others. The driver will arbitrate access to the codec and reprogram it whenever another file handler gets access. This is different from the usual video node behavior where the video properties are global to the device (i.e. changing something through one file handle is visible through another file handle).</para>
Documentation/DocBook/media/v4l/v4l2.xml +1 −1 Original line number Diff line number Diff line Loading @@ -493,7 +493,7 @@ and discussions on the V4L mailing list.</revremark> </partinfo> <title>Video for Linux Two API Specification</title> <subtitle>Revision 3.9</subtitle> <subtitle>Revision 3.10</subtitle> <chapter id="common"> &sub-common; Loading
Documentation/devicetree/bindings/media/exynos-fimc-lite.txt +1 −1 Original line number Diff line number Diff line Loading @@ -2,7 +2,7 @@ Exynos4x12/Exynos5 SoC series camera host interface (FIMC-LITE) Required properties: - compatible : should be "samsung,exynos4212-fimc" for Exynos4212 and - compatible : should be "samsung,exynos4212-fimc-lite" for Exynos4212 and Exynos4412 SoCs; - reg : physical base address and size of the device memory mapped registers; Loading
Documentation/devicetree/bindings/mfd/arizona.txt 0 → 100644 +62 −0 Original line number Diff line number Diff line Wolfson Arizona class audio SoCs These devices are audio SoCs with extensive digital capabilites and a range of analogue I/O. Required properties: - compatible : one of the following chip-specific strings: "wlf,wm5102" "wlf,wm5110" - reg : I2C slave address when connected using I2C, chip select number when using SPI. - interrupts : The interrupt line the /IRQ signal for the device is connected to. - interrupt-controller : Arizona class devices contain interrupt controllers and may provide interrupt services to other devices. - interrupt-parent : The parent interrupt controller. - #interrupt-cells: the number of cells to describe an IRQ, this should be 2. The first cell is the IRQ number. The second cell is the flags, encoded as the trigger masks from Documentation/devicetree/bindings/interrupts.txt - gpio-controller : Indicates this device is a GPIO controller. - #gpio-cells : Must be 2. The first cell is the pin number and the second cell is used to specify optional parameters (currently unused). - AVDD1-supply, DBVDD1-supply, DBVDD2-supply, DBVDD3-supply, CPVDD-supply, SPKVDDL-supply, SPKVDDR-supply : power supplies for the device, as covered in Documentation/devicetree/bindings/regulator/regulator.txt Optional properties: - wlf,reset : GPIO specifier for the GPIO controlling /RESET - wlf,ldoena : GPIO specifier for the GPIO controlling LDOENA - wlf,gpio-defaults : A list of GPIO configuration register values. If absent, no configuration of these registers is performed. If any entry has a value that is out of range for a 16 bit register then the chip default will be used. If present exactly five values must be specified. Example: codec: wm5102@1a { compatible = "wlf,wm5102"; reg = <0x1a>; interrupts = <347>; #interrupt-cells = <2>; interrupt-parent = <&gic>; gpio-controller; #gpio-cells = <2>; wlf,gpio-defaults = < 0x00000000, /* AIF1TXLRCLK */ 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, >; };
Documentation/devicetree/bindings/sound/adi,adau1701.txt 0 → 100644 +35 −0 Original line number Diff line number Diff line Analog Devices ADAU1701 Required properties: - compatible: Should contain "adi,adau1701" - reg: The i2c address. Value depends on the state of ADDR0 and ADDR1, as wired in hardware. Optional properties: - reset-gpio: A GPIO spec to define which pin is connected to the chip's !RESET pin. If specified, the driver will assert a hardware reset at probe time. - adi,pll-mode-gpios: An array of two GPIO specs to describe the GPIOs the ADAU's PLL config pins are connected to. The state of the pins are set according to the configured clock divider on ASoC side before the firmware is loaded. - adi,pin-config: An array of 12 numerical values selecting one of the pin configurations as described in the datasheet, table 53. Note that the value of this property has to be prefixed with '/bits/ 8'. Examples: i2c_bus { adau1701@34 { compatible = "adi,adau1701"; reg = <0x34>; reset-gpio = <&gpio 23 0>; adi,pll-mode-gpios = <&gpio 24 0 &gpio 25 0>; adi,pin-config = /bits/ 8 <0x4 0x7 0x5 0x5 0x4 0x4 0x4 0x4 0x4 0x4 0x4 0x4>; }; };