Работа с GPIO/en: различия между версиями

Строка 117:

<b>This method is NOT strongly recommended for use without sufficient reason. To work in C / C ++ is to use the files to work through sysfs, as described in the previous section</b>.

~~Driving~~ GPIO ~~can use~~ the direct access to the processor registers, bypassing the Linux interface/dev/mem. At the same time, compared to the work via sysfs ~~minimization of~~ costs. This method can be used,

You can manage GPIO using the direct access to the processor registers, bypassing the Linux interface/dev/mem. At the same time, compared to the work via sysfs, this case minimizes costs. This method can be used,

if you need a very fast access to GPIO, such bitbang protocols or PWM. It should be borne in mind that the process scheduler can still contribute to the work program of significant delays.

It is recommended to make time-critical tasks in the kernel.

@@ Строка 117: / Строка 117: @@
 <b>This method is NOT strongly recommended for use without sufficient reason. To work in C / C ++ is to use the files to work through sysfs, as described in the previous section</b>.
-Driving GPIO can use the direct access to the processor registers, bypassing the Linux interface/dev/mem. At the same time, compared to the work via sysfs minimization of costs. This method can be used,
+You can manage GPIO using the direct access to the processor registers, bypassing the Linux interface/dev/mem. At the same time, compared to the work via sysfs, this case minimizes costs. This method can be used,
 if you need a very fast access to GPIO, such bitbang protocols or PWM. It should be borne in mind that the process scheduler can still contribute to the work program of significant delays.
 It is recommended to make time-critical tasks in the kernel.

Навигация