Skip to content

Commit 2da5cf4

Browse files
dlechdlech
committed
Automatically generated changes for kernel release
lego-linux-drivers level 9
1 parent ec236d2 commit 2da5cf4

File tree

98 files changed

+677
-460
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

98 files changed

+677
-460
lines changed

‎_data/ports.json‎

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -99,10 +99,10 @@
9999
],
100100
"module": "ht-nxt-smux",
101101
"name": "ht-nxt-smux-port",
102-
"notes": "\n[^port-name-prefix]: The full `port_name` is in the format:\n ^\n [<parent-port-name>:]mux<n>\n ^\n For example, if we are looking at port 1 of this mux plugged into\n input port 2 on the EV3, the port name will be `in2:i2c08:mux1`.\n \n ",
102+
"notes": "\n[^address-prefix]: The full `address` is in the format:\n ^\n [<parent-address>:]mux<n>\n ^\n For example, if we are looking at port 1 of this mux plugged into\n input port 2 on the EV3, the address will be `in2:i2c08:mux1`.\n \n ",
103103
"num_modes": 2,
104104
"prefix": "mux",
105-
"prefix_footnote": "[^port-name-prefix]",
105+
"prefix_footnote": "[^address-prefix]",
106106
"source_file": "drivers/lego/sensors/ht_nxt_smux.c",
107107
"source_line": 39,
108108
"url_name": "ht-nxt-smux-port"
@@ -237,10 +237,10 @@
237237
],
238238
"module": "ms-ev3-smux",
239239
"name": "ms-ev3-smux-port",
240-
"notes": "\n[^port-name-prefix]: The full `port_name` is in the format:\n ^\n [<parent-port-name>:]mux<n>\n ^\n For example, if we are looking at port 1 of this mux plugged into\n input port 2 on the EV3, the port name will be `in2:i2c50:mux1`.\n \n ",
240+
"notes": "\n[^address-prefix]: The full `address` is in the format:\n ^\n [<parent-address>:]mux<n>\n ^\n For example, if we are looking at port 1 of this mux plugged into\n input port 2 on the EV3, the address will be `in2:i2c50:mux1`.\n \n ",
241241
"num_modes": 2,
242242
"prefix": "mux",
243-
"prefix_footnote": "[^port-name-prefix]",
243+
"prefix_footnote": "[^address-prefix]",
244244
"source_file": "drivers/lego/sensors/ms_ev3_smux.c",
245245
"source_line": 42,
246246
"url_name": "ms-ev3-smux-port"
@@ -257,7 +257,7 @@
257257
],
258258
"module": "ms-nxtmmx",
259259
"name": "ms-nxtmmx-out-port",
260-
"notes": "\n[^prefix]: The full port name will be something like `in2:i2c3:M1`\n depending on what port the motor multiplexer is plugged into.\n \n ",
260+
"notes": "\n[^prefix]: The full address will be something like `in2:i2c3:M1`\n depending on what port the motor multiplexer is plugged into.\n \n ",
261261
"num_modes": 1,
262262
"prefix": "M",
263263
"prefix_footnote": "[^prefix]",
@@ -310,10 +310,10 @@
310310
],
311311
"module": "pistorms-ports-in",
312312
"name": "pistorms-in-port",
313-
"notes": "\n[^port-name-prefix]: The full `port_name` is in the format:\n ^\n pistorms:B<b>:<prefix><n>\n ^\n For example, if we are looking at the port labeled \"BBS2\" on the\n PiStorms, the port name will be `pistorms:BB:S2`.\n \n ",
313+
"notes": "\n[^address-prefix]: The full `address` is in the format:\n ^\n pistorms:B<b>:<prefix><n>\n ^\n For example, if we are looking at the port labeled \"BBS2\" on the\n PiStorms, the address will be `pistorms:BB:S2`.\n \n ",
314314
"num_modes": 6,
315315
"prefix": "S",
316-
"prefix_footnote": "[^port-name-prefix]",
316+
"prefix_footnote": "[^address-prefix]",
317317
"source_file": "drivers/lego/pistorms/pistorms_ports_in.c",
318318
"source_line": 134,
319319
"url_name": "pistorms-in-port"
@@ -330,7 +330,7 @@
330330
],
331331
"module": "pistorms-ports-out",
332332
"name": "pistorms-out-port",
333-
"notes": "\n[^prefix]: The full port name will be something like `pistorms:BAM1`\n depending on what port the motor multiplexer is plugged into.\n \n ",
333+
"notes": "\n[^prefix]: The full address will be something like `pistorms:BAM1`.\n \n ",
334334
"num_modes": 1,
335335
"prefix": "M",
336336
"prefix_footnote": "[^prefix]",
@@ -350,10 +350,10 @@
350350
],
351351
"module": "wedo",
352352
"name": "wedo-port",
353-
"notes": "\n[^port-name-prefix]: The full `port_name` is in the format:\n ^\n usb<usb-path>:wedo<n>\n ^\n The USB path might be something like `1-1.3:1.0`. Read more about\n it [here](http://gajjarpremal.blogspot.in/2015/04/sysfs-structures-for-linux-usb.html).\n Run `lsusb -t` to help figure out the correct path for your WeDo hub.\n ^\n For example, this...\n ^\n /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M\n |__ Port 4: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M\n |__ Port 2: Dev 6, If 0, Class=Human Interface Device, Driver=wedo, 1.5M\n ^\n ...translates to `usb5-4.2:1.0:wedo1`. You can see how `Bus 05`,\n `Port 4` and `Port 2` result in `5-4.2`. The last bit (configuration\n and interface) will always be `:1.0`.\n \n ",
353+
"notes": "\n[^address-prefix]: The full `address` is in the format:\n ^\n usb<usb-path>:wedo<n>\n ^\n The USB path might be something like `1-1.3:1.0`. Read more about\n it [here](http://gajjarpremal.blogspot.in/2015/04/sysfs-structures-for-linux-usb.html).\n Run `lsusb -t` to help figure out the correct path for your WeDo hub.\n ^\n For example, this...\n ^\n /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M\n |__ Port 4: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M\n |__ Port 2: Dev 6, If 0, Class=Human Interface Device, Driver=wedo, 1.5M\n ^\n ...translates to `usb5-4.2:1.0:wedo1`. You can see how `Bus 05`,\n `Port 4` and `Port 2` result in `5-4.2`. The last bit (configuration\n and interface) will always be `:1.0`.\n \n ",
354354
"num_modes": 1,
355355
"prefix": "wedo",
356-
"prefix_footnote": "[^port-name-prefix]",
356+
"prefix_footnote": "[^address-prefix]",
357357
"source_file": "drivers/lego/wedo/wedo_port.c",
358358
"source_line": 417,
359359
"url_name": "wedo-port"

‎_data/sensors.json‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2036,7 +2036,7 @@
20362036
"si_max": "1000",
20372037
"units": "pct",
20382038
"units_description": "percent",
2039-
"value0": "Reflected light intensity (0 to 100)"
2039+
"value0": "Reflected light intensity (0 to 1000)"
20402040
},
20412041
{
20422042
"data_sets": "1",
@@ -2051,7 +2051,7 @@
20512051
"si_max": "1000",
20522052
"units": "pct",
20532053
"units_description": "percent",
2054-
"value0": "Ambient light intensity (0 to 100)"
2054+
"value0": "Ambient light intensity (0 to 1000)"
20552055
}
20562056
],
20572057
"name": "lego-nxt-light",
@@ -2472,7 +2472,7 @@
24722472
"units_description": "degrees",
24732473
"value0": "X-axis angle (0 to 180)",
24742474
"value1": "Y-axis angle (0 to 180)",
2475-
"value2": "Y-axis angle (0 to 180)"
2475+
"value2": "Z-axis angle (0 to 180)"
24762476
},
24772477
{
24782478
"data_sets": "3",
@@ -3193,7 +3193,7 @@
31933193
}
31943194
],
31953195
"name": "ms-nxtmmx",
3196-
"notes": "\n[^address]: The address is programmable. See manufacturer\n documentation for more information.\n \n[^tacho-motor-devices]: The NxtMMX driver also loads two\n [tacho-motor] class devices. Use the tacho-motor class devices\n to actually control the motors. You can identify the motors\n by the `port_name` attribute. It will be `in<X>:i2c<Y>:mux<Z>`\n where `<X>` is 1-4, `<Y>` is 3 (unless you changed the address)\n and `<Z>` is 1 or 2 (matches M1 or M2 printed on the NxtMMX).\n ^\n [tacho-motor]: /docs/drivers/tacho-motor-class\n \n ",
3196+
"notes": "\n[^address]: The address is programmable. See manufacturer\n documentation for more information.\n \n[^tacho-motor-devices]: The NxtMMX driver also loads two\n [tacho-motor] class devices. Use the tacho-motor class devices\n to actually control the motors. You can identify the motors\n by the `address` attribute. It will be `in<X>:i2c<Y>:mux<Z>`\n where `<X>` is 1-4, `<Y>` is 3 (unless you changed the address)\n and `<Z>` is 1 or 2 (matches M1 or M2 printed on the NxtMMX).\n ^\n [tacho-motor]: /docs/drivers/tacho-motor-class\n \n ",
31973197
"num_modes": "2",
31983198
"ops": [],
31993199
"product_id": "NxTMMX",
@@ -3256,7 +3256,7 @@
32563256
}
32573257
],
32583258
"name": "ms-8ch-servo",
3259-
"notes": "\n[^address]: The address is programmable. See manufacturer\n documentation for more information.\n \n[^servo-motor-devices]: The `ms-8ch-servo` driver loads separate\n servo motor devices (one for each of the 8 channels) in addition\n to the [lego-sensor class] device. See the [servo-motor class]\n for more information. The `servo-motor` class `port_name` attribute\n will return `in<X>:i2c<Y>:sv<Z>` where `<X>` is the input port\n the servo controller is connected to, `<Y>` is the address and\n `<Z>` is the channel as indicated on the servo controller itself.\n ^\n [lego-sensor class]: /docs/drivers/lego-sensor-class\n [servo-motor class]: /docs/drivers/servo-motor-class\n \n ",
3259+
"notes": "\n[^address]: The address is programmable. See manufacturer\n documentation for more information.\n \n[^servo-motor-devices]: The `ms-8ch-servo` driver loads separate\n servo motor devices (one for each of the 8 channels) in addition\n to the [lego-sensor class] device. See the [servo-motor class]\n for more information. The `servo-motor` class `address` attribute\n will return `in<X>:i2c<Y>:sv<Z>` where `<X>` is the input port\n the servo controller is connected to, `<Y>` is the address and\n `<Z>` is the channel as indicated on the servo controller itself.\n ^\n [lego-sensor class]: /docs/drivers/lego-sensor-class\n [servo-motor class]: /docs/drivers/servo-motor-class\n \n ",
32603260
"num_modes": "2",
32613261
"ops": [],
32623262
"product_id": "NXTServo",

‎docs/drivers/brickpi-battery.markdown‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
autogen: This file was automatically generated by kernel-doc-text-to-markdown.py
3-
kernel_version: 3.16.7-ckt19-8-ev3dev-ev3
3+
kernel_version: 3.16.7-ckt21-9-ev3dev-ev3
44
source_file: drivers/lego/brickpi/brickpi_battery.c
55
title: Dexter Industries BrickPi+ Battery Driver
66
---

‎docs/drivers/brickpi-i2c-sensor.markdown‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
autogen: This file was automatically generated by kernel-doc-text-to-markdown.py
3-
kernel_version: 3.16.7-ckt19-8-ev3dev-ev3
3+
kernel_version: 3.16.7-ckt21-9-ev3dev-ev3
44
source_file: drivers/lego/brickpi/brickpi_i2c_sensor.c
55
title: Dexter Industries BrickPi I2C Sensor Driver
66
---

‎docs/drivers/brickpi-ld.markdown‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
autogen: This file was automatically generated by kernel-doc-text-to-markdown.py
3-
kernel_version: 3.16.7-ckt19-8-ev3dev-ev3
3+
kernel_version: 3.16.7-ckt21-9-ev3dev-ev3
44
source_file: drivers/lego/brickpi/brickpi_ld.c
55
title: Dexter Industries BrickPi Line Discipline
66
---

‎docs/drivers/dc-motor-class.markdown‎

Lines changed: 79 additions & 61 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
autogen: This file was automatically generated by kernel-doc-text-to-markdown.py
3-
kernel_version: 3.16.7-ckt19-8-ev3dev-ev3
3+
kernel_version: 3.16.7-ckt21-9-ev3dev-ev3
44
source_file: drivers/lego/motors/dc_motor_class.c
55
title: DC Motor Class
66
---
@@ -15,66 +15,84 @@ DC motors can be found at `/sys/class/dc-motor/motor<N>`, where `<N>`
1515
is incremented each time a motor is loaded (it is not related to which port
1616
the motor is plugged in to).
1717

18-
`command` (write-only)
19-
: Sets the command for the motor. Possible values are `run-forever`,
20-
`run-timed`, `run-direct` and `stop`. Not all commands may be supported.
21-
`run-forever` will cause the motor to run until another command is sent.
22-
`run-timed` will run the motor for the amount of time specified in `time_sp`
23-
and then stop the motor using the command specified by `stop_command`.
24-
`run-direct` will run the motor at the duty cycle specified by `duty_cycle_sp`.
25-
Unlike other run commands, changing `duty_cycle_sp` while running *will*
26-
take effect immediately.
27-
`stop` will stop any of the run commands before they are complete using the
28-
command specified by `stop_command`.
29-
30-
`commands` (read-only)
31-
: Returns a space separated list of commands supported by the motor
32-
controller.
33-
34-
`driver_name` (read-only)
35-
: Returns the name of the motor driver that loaded this device. See the list
36-
of [supported devices] for a list of drivers.
37-
38-
`duty_cycle` (read)
39-
: Shows the current duty cycle of the PWM signal sent to the motor. Values
40-
are -100 to 100 (-100% to 100%).
41-
42-
`duty_cycle_sp` (read/write)
43-
: Writing sets the duty cycle setpoint of the PWM signal sent to the motor.
44-
Valid values are -100 to 100 (-100% to 100%). Reading returns the current
45-
setpoint.
46-
47-
`polarity`: (read/write)
48-
: Sets the polarity of the motor. Valid values are `normal` and `inversed`.
49-
50-
`port_name` (read-only)
51-
: Returns the name of the port that the motor is connected to.
52-
53-
`state` (read-only)
54-
: Gets a space separated list of flags indicating the motor status. Possible
55-
flags are `running` and `ramping`. `running` indicates that the motor is
56-
powered. `ramping` indicates that the motor has not yet reached the
57-
`duty_cycle_sp`.
58-
59-
`stop_command` (write-only)
60-
: Sets the stop command that will be used when the motor stops. Read
61-
`stop_commands` to get the list of valid values.
62-
63-
`stop_commands` (read-only)
64-
: Gets a space separated list of stop commands. Valid values are `coast`
65-
and `brake`.
66-
67-
`ramp_down_sp` (read/write)
68-
: Sets the time in milliseconds that it take the motor to ramp down from 100%
69-
to 0%. Valid values are 0 to 10000 (10 seconds). Default is 0.
70-
71-
`ramp_up_sp` (read/write)
72-
: Sets the time in milliseconds that it take the motor to up ramp from 0% to
73-
100%. Valid values are 0 to 10000 (10 seconds). Default is 0.
74-
75-
`time_sp`: (read/write)
76-
: Sets the time setpoint used with the `run-timed` command. Units are in
77-
milliseconds.
18+
`address`
19+
: (read-only) Returns the name of the port that the motor is connected to.
20+
21+
`command`
22+
: (write-only) Sets the command for the motor. Possible values are:
23+
24+
- `run-forever`: Causes the motor to run until another command is sent.
25+
- `run-timed`: Runs the motor for the amount of time specified in
26+
`time_sp` and then stops the motor using the command specified by
27+
`stop_command`.
28+
- `run-direct`: Runs the motor at the duty cycle specified by
29+
`duty_cycle_sp`. Unlike other run commands, changing `duty_cycle_sp`
30+
while running *will* take effect immediately.
31+
- `stop`: Stops any of the run commands before they are complete using
32+
the command specified by `stop_command`.
33+
34+
Not all commands may be supported. Read `commands` to find out which
35+
commands are supported for a particular driver.
36+
37+
`commands`
38+
: (read-only) Returns a space separated list of commands supported by the
39+
motor controller.
40+
41+
`driver_name`
42+
: (read-only) Returns the name of the motor driver that loaded this device.
43+
See the list of [supported devices] for a list of drivers.
44+
45+
`duty_cycle`
46+
: (read-only) Shows the current duty cycle of the PWM signal sent to the
47+
motor. Values are -100 to 100 (-100% to 100%).
48+
49+
`duty_cycle_sp`
50+
: (read/write) Writing sets the duty cycle setpoint of the PWM signal sent to
51+
the motor. Valid values are -100 to 100 (-100% to 100%). Reading returns
52+
the current setpoint.
53+
54+
`polarity`
55+
: (read/write) Sets the polarity of the motor. Valid values are:
56+
57+
- `normal`: Causes the motor to turn in the direction indicated by the
58+
sign (+/-) of the `duty_cycle_sp`.
59+
- `inversed`: Causes the motor to turn in the opposite direction of the
60+
sign (+/-) of the `duty_cycle_sp`.
61+
62+
`state`
63+
: (read-only) Gets a space separated list of flags indicating the motor
64+
status. Possible flags are:
65+
66+
- `running`: Indicates that the motor is powered.
67+
- `ramping`: Indicates that the motor has not yet reached the
68+
`duty_cycle_sp`.
69+
70+
`stop_command`
71+
: (write-only) Sets the stop command that will be used when the motor stops.
72+
Possible values are:
73+
74+
- `coast`: Causes the motor to coast to a stop by floating the outputs.
75+
- `brake`: Causes the motor to stop more quickly by shorting the outputs.
76+
77+
Not all values may be supported. Read `stop_commands` to find out which
78+
commands are supported for a particular driver.
79+
80+
`stop_commands`
81+
: (read-only) Gets a space separated list of supported stop commands.
82+
83+
`ramp_down_sp`
84+
: (read/write) Sets the time in milliseconds that it take the motor to ramp
85+
down from 100% to 0%. Valid values are 0 to 10000 (10 seconds). Default is
86+
0.
87+
88+
`ramp_up_sp`
89+
: (read/write) Sets the time in milliseconds that it take the motor to up
90+
ramp from 0% to 100%. Valid values are 0 to 10000 (10 seconds). Default is
91+
0.
92+
93+
`time_sp`
94+
: (read/write) Sets the time setpoint used with the `run-timed` command.
95+
Units are in milliseconds.
7896

7997
[supported devices]: /docs/motors/#supported-devices
8098

‎docs/drivers/ev3-analog-sensor.markdown‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
autogen: This file was automatically generated by kernel-doc-text-to-markdown.py
3-
kernel_version: 3.16.7-ckt19-8-ev3dev-ev3
3+
kernel_version: 3.16.7-ckt21-9-ev3dev-ev3
44
source_file: drivers/lego/sensors/ev3_analog_sensor_core.c
55
title: EV3 Analog Sensor Driver
66
---

‎docs/drivers/ev3-uart-sensor-ld.markdown‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
autogen: This file was automatically generated by kernel-doc-text-to-markdown.py
3-
kernel_version: 3.16.7-ckt19-8-ev3dev-ev3
3+
kernel_version: 3.16.7-ckt21-9-ev3dev-ev3
44
source_file: drivers/lego/sensors/ev3_uart_sensor_ld.c
55
title: EV3 UART Sensor Line Discipline
66
---

‎docs/drivers/ht-nxt-smux-i2c-sensor.markdown‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
autogen: This file was automatically generated by kernel-doc-text-to-markdown.py
3-
kernel_version: 3.16.7-ckt19-8-ev3dev-ev3
3+
kernel_version: 3.16.7-ckt21-9-ev3dev-ev3
44
source_file: drivers/lego/sensors/ht_nxt_smux_i2c_sensor.c
55
title: HiTechnic NXT Sensor Multiplexer I2C sensor driver
66
---

0 commit comments

Comments
 (0)