1 <title>RDS Interface</title>
3 <para>The Radio Data System transmits supplementary
4 information in binary format, for example the station name or travel
5 information, on an inaudible audio subcarrier of a radio program. This
6 interface is aimed at devices capable of receiving and/or transmitting RDS
9 <para>For more information see the core RDS standard <xref linkend="en50067" />
10 and the RBDS standard <xref linkend="nrsc4" />.</para>
12 <para>Note that the RBDS standard as is used in the USA is almost identical
13 to the RDS standard. Any RDS decoder/encoder can also handle RBDS. Only some of the
14 fields have slightly different meanings. See the RBDS standard for more
17 <para>The RBDS standard also specifies support for MMBS (Modified Mobile Search).
18 This is a proprietary format which seems to be discontinued. The RDS interface does not
19 support this format. Should support for MMBS (or the so-called 'E blocks' in general)
20 be needed, then please contact the linux-media mailing list: &v4l-ml;.</para>
23 <title>Querying Capabilities</title>
25 <para>Devices supporting the RDS capturing API set
26 the <constant>V4L2_CAP_RDS_CAPTURE</constant> flag in
27 the <structfield>capabilities</structfield> field of &v4l2-capability;
28 returned by the &VIDIOC-QUERYCAP; ioctl. Any tuner that supports RDS
29 will set the <constant>V4L2_TUNER_CAP_RDS</constant> flag in
30 the <structfield>capability</structfield> field of &v4l2-tuner;. If
31 the driver only passes RDS blocks without interpreting the data
32 the <constant>V4L2_TUNER_SUB_RDS_BLOCK_IO</constant> flag has to be
33 set, see <link linkend="reading-rds-data">Reading RDS data</link>.
35 flag <constant>V4L2_TUNER_SUB_RDS_CONTROLS</constant> has also been
36 defined. However, a driver for a radio tuner with this capability does
37 not yet exist, so if you are planning to write such a driver you
38 should discuss this on the linux-media mailing list: &v4l-ml;.</para>
40 <para> Whether an RDS signal is present can be detected by looking
41 at the <structfield>rxsubchans</structfield> field of &v4l2-tuner;:
42 the <constant>V4L2_TUNER_SUB_RDS</constant> will be set if RDS data
45 <para>Devices supporting the RDS output API
46 set the <constant>V4L2_CAP_RDS_OUTPUT</constant> flag in
47 the <structfield>capabilities</structfield> field of &v4l2-capability;
48 returned by the &VIDIOC-QUERYCAP; ioctl.
49 Any modulator that supports RDS will set the
50 <constant>V4L2_TUNER_CAP_RDS</constant> flag in the <structfield>capability</structfield>
51 field of &v4l2-modulator;.
52 In order to enable the RDS transmission one must set the <constant>V4L2_TUNER_SUB_RDS</constant>
53 bit in the <structfield>txsubchans</structfield> field of &v4l2-modulator;.
54 If the driver only passes RDS blocks without interpreting the data
55 the <constant>V4L2_TUNER_SUB_RDS_BLOCK_IO</constant> flag has to be set. If the
56 tuner is capable of handling RDS entities like program identification codes and radio
57 text, the flag <constant>V4L2_TUNER_SUB_RDS_CONTROLS</constant> should be set,
58 see <link linkend="writing-rds-data">Writing RDS data</link> and
59 <link linkend="fm-tx-controls">FM Transmitter Control Reference</link>.</para>
62 <section id="reading-rds-data">
63 <title>Reading RDS data</title>
65 <para>RDS data can be read from the radio device
66 with the &func-read; function. The data is packed in groups of three bytes.</para>
69 <section id="writing-rds-data">
70 <title>Writing RDS data</title>
72 <para>RDS data can be written to the radio device
73 with the &func-write; function. The data is packed in groups of three bytes,
78 <title>RDS datastructures</title>
79 <table frame="none" pgwide="1" id="v4l2-rds-data">
81 <structname>v4l2_rds_data</structname></title>
83 <colspec colname="c1" colwidth="1*" />
84 <colspec colname="c2" colwidth="1*" />
85 <colspec colname="c3" colwidth="5*" />
89 <entry><structfield>lsb</structfield></entry>
90 <entry>Least Significant Byte of RDS Block</entry>
94 <entry><structfield>msb</structfield></entry>
95 <entry>Most Significant Byte of RDS Block</entry>
99 <entry><structfield>block</structfield></entry>
100 <entry>Block description</entry>
105 <table frame="none" pgwide="1" id="v4l2-rds-block">
106 <title>Block description</title>
108 <colspec colname="c1" colwidth="1*" />
109 <colspec colname="c2" colwidth="5*" />
112 <entry>Bits 0-2</entry>
113 <entry>Block (aka offset) of the received data.</entry>
116 <entry>Bits 3-5</entry>
117 <entry>Deprecated. Currently identical to bits 0-2. Do not use these bits.</entry>
121 <entry>Corrected bit. Indicates that an error was corrected for this data block.</entry>
125 <entry>Error bit. Indicates that an uncorrectable error occurred during reception of this block.</entry>
131 <table frame="none" pgwide="1" id="v4l2-rds-block-codes">
132 <title>Block defines</title>
134 <colspec colname="c1" colwidth="1*" />
135 <colspec colname="c2" colwidth="1*" />
136 <colspec colname="c3" colwidth="1*" />
137 <colspec colname="c4" colwidth="5*" />
140 <entry>V4L2_RDS_BLOCK_MSK</entry>
143 <entry>Mask for bits 0-2 to get the block ID.</entry>
146 <entry>V4L2_RDS_BLOCK_A</entry>
149 <entry>Block A.</entry>
152 <entry>V4L2_RDS_BLOCK_B</entry>
155 <entry>Block B.</entry>
158 <entry>V4L2_RDS_BLOCK_C</entry>
161 <entry>Block C.</entry>
164 <entry>V4L2_RDS_BLOCK_D</entry>
167 <entry>Block D.</entry>
170 <entry>V4L2_RDS_BLOCK_C_ALT</entry>
173 <entry>Block C'.</entry>
176 <entry>V4L2_RDS_BLOCK_INVALID</entry>
177 <entry>read-only</entry>
179 <entry>An invalid block.</entry>
182 <entry>V4L2_RDS_BLOCK_CORRECTED</entry>
183 <entry>read-only</entry>
185 <entry>A bit error was detected but corrected.</entry>
188 <entry>V4L2_RDS_BLOCK_ERROR</entry>
189 <entry>read-only</entry>
191 <entry>An uncorrectable error occurred.</entry>
201 sgml-parent-document: "v4l2.sgml"
202 indent-tabs-mode: nil