summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/media/renesas,drif.txt
blob: 39516b94c28fbef0a4539e04d861332b04184637 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
Renesas R-Car Gen3 Digital Radio Interface controller (DRIF)
------------------------------------------------------------

R-Car Gen3 DRIF is a SPI like receive only slave device. A general
representation of DRIF interfacing with a master device is shown below.

+---------------------+                +---------------------+
|                     |-----SCK------->|CLK                  |
|       Master        |-----SS-------->|SYNC  DRIFn (slave)  |
|                     |-----SD0------->|D0                   |
|                     |-----SD1------->|D1                   |
+---------------------+                +---------------------+

As per datasheet, each DRIF channel (drifn) is made up of two internal
channels (drifn0 & drifn1). These two internal channels share the common
CLK & SYNC. Each internal channel has its own dedicated resources like
irq, dma channels, address space & clock. This internal split is not
visible to the external master device.

The device tree model represents each internal channel as a separate node.
The internal channels sharing the CLK & SYNC are tied together by their
phandles using a property called "renesas,bonding". For the rest of
the documentation, unless explicitly stated, the word channel implies an
internal channel.

When both internal channels are enabled they need to be managed together
as one (i.e.) they cannot operate alone as independent devices. Out of the
two, one of them needs to act as a primary device that accepts common
properties of both the internal channels. This channel is identified by a
property called "renesas,primary-bond".

To summarize,
   - When both the internal channels that are bonded together are enabled,
     the zeroth channel is selected as primary-bond. This channels accepts
     properties common to all the members of the bond.
   - When only one of the bonded channels need to be enabled, the property
     "renesas,bonding" or "renesas,primary-bond" will have no effect. That
     enabled channel can act alone as any other independent device.

Required properties of an internal channel:
-------------------------------------------
- compatible:	"renesas,r8a7795-drif" if DRIF controller is a part of R8A7795 SoC.
		"renesas,rcar-gen3-drif" for a generic R-Car Gen3 compatible device.

		When compatible with the generic version, nodes must list the
		SoC-specific version corresponding to the platform first
		followed by the generic version.

- reg: offset and length of that channel.
- interrupts: associated with that channel.
- clocks: phandle and clock specifier of that channel.
- clock-names: clock input name string: "fck".
- dmas: phandles to the DMA channels.
- dma-names: names of the DMA channel: "rx".
- renesas,bonding: phandle to the other channel.

Optional properties of an internal channel:
-------------------------------------------
- power-domains: phandle to the respective power domain.

Required properties of an internal channel when:
	- It is the only enabled channel of the bond (or)
	- If it acts as primary among enabled bonds
--------------------------------------------------------
- pinctrl-0: pin control group to be used for this channel.
- pinctrl-names: must be "default".
- renesas,primary-bond: empty property indicating the channel acts as primary
			among the bonded channels.
- port: child port node corresponding to the data input, in accordance with
	the video interface bindings defined in
	Documentation/devicetree/bindings/media/video-interfaces.txt. The port
	node must contain at least one endpoint.

Optional endpoint property:
---------------------------
- sync-active: Indicates sync signal polarity, 0/1 for low/high respectively.
	       This property maps to SYNCAC bit in the hardware manual. The
	       default is 1 (active high).

Example:
--------

(1) Both internal channels enabled:
-----------------------------------

When interfacing with a third party tuner device with two data pins as shown
below.

+---------------------+                +---------------------+
|                     |-----SCK------->|CLK                  |
|       Master        |-----SS-------->|SYNC  DRIFn (slave)  |
|                     |-----SD0------->|D0                   |
|                     |-----SD1------->|D1                   |
+---------------------+                +---------------------+

	drif00: rif@e6f40000 {
		compatible = "renesas,r8a7795-drif",
			     "renesas,rcar-gen3-drif";
		reg = <0 0xe6f40000 0 0x64>;
		interrupts = <GIC_SPI 12 IRQ_TYPE_LEVEL_HIGH>;
		clocks = <&cpg CPG_MOD 515>;
		clock-names = "fck";
		dmas = <&dmac1 0x20>, <&dmac2 0x20>;
		dma-names = "rx", "rx";
		power-domains = <&sysc R8A7795_PD_ALWAYS_ON>;
		renesas,bonding = <&drif01>;
		renesas,primary-bond;
		pinctrl-0 = <&drif0_pins>;
		pinctrl-names = "default";
		port {
			drif0_ep: endpoint {
			     remote-endpoint = <&tuner_ep>;
			};
		};
	};

	drif01: rif@e6f50000 {
		compatible = "renesas,r8a7795-drif",
			     "renesas,rcar-gen3-drif";
		reg = <0 0xe6f50000 0 0x64>;
		interrupts = <GIC_SPI 13 IRQ_TYPE_LEVEL_HIGH>;
		clocks = <&cpg CPG_MOD 514>;
		clock-names = "fck";
		dmas = <&dmac1 0x22>, <&dmac2 0x22>;
		dma-names = "rx", "rx";
		power-domains = <&sysc R8A7795_PD_ALWAYS_ON>;
		renesas,bonding = <&drif00>;
	};


(2) Internal channel 1 alone is enabled:
----------------------------------------

When interfacing with a third party tuner device with one data pin as shown
below.

+---------------------+                +---------------------+
|                     |-----SCK------->|CLK                  |
|       Master        |-----SS-------->|SYNC  DRIFn (slave)  |
|                     |                |D0 (unused)          |
|                     |-----SD-------->|D1                   |
+---------------------+                +---------------------+

	drif00: rif@e6f40000 {
		compatible = "renesas,r8a7795-drif",
			     "renesas,rcar-gen3-drif";
		reg = <0 0xe6f40000 0 0x64>;
		interrupts = <GIC_SPI 12 IRQ_TYPE_LEVEL_HIGH>;
		clocks = <&cpg CPG_MOD 515>;
		clock-names = "fck";
		dmas = <&dmac1 0x20>, <&dmac2 0x20>;
		dma-names = "rx", "rx";
		power-domains = <&sysc R8A7795_PD_ALWAYS_ON>;
		renesas,bonding = <&drif01>;
	};

	drif01: rif@e6f50000 {
		compatible = "renesas,r8a7795-drif",
			     "renesas,rcar-gen3-drif";
		reg = <0 0xe6f50000 0 0x64>;
		interrupts = <GIC_SPI 13 IRQ_TYPE_LEVEL_HIGH>;
		clocks = <&cpg CPG_MOD 514>;
		clock-names = "fck";
		dmas = <&dmac1 0x22>, <&dmac2 0x22>;
		dma-names = "rx", "rx";
		power-domains = <&sysc R8A7795_PD_ALWAYS_ON>;
		renesas,bonding = <&drif00>;
		pinctrl-0 = <&drif0_pins>;
		pinctrl-names = "default";
		port {
			drif0_ep: endpoint {
			     remote-endpoint = <&tuner_ep>;
			     sync-active = <0>;
			};
		};
	};
OpenPOWER on IntegriCloud