Searched +full:activate +full:- +full:to +full:- +full:activate (Results 1 – 25 of 98) sorted by relevance
1234
| /Documentation/driver-api/nvdimm/ |
| D | firmware-activate.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 "DIMM" to perform tasks like media management, capacity provisioning,
10 involves a reboot because it has implications for in-flight memory
16 A native sysfs interface is implemented in libnvdimm to allow platform
17 to advertise and control their local runtime firmware activation
20 The libnvdimm bus object, ndbusX, implements an ndbusX/firmware/activate
24 - idle:
25 No devices are set / armed to activate firmware
27 - armed:
30 - busy:
[all …]
|
| /Documentation/leds/ |
| D | ledtrig-transient.rst | 5 The leds timer trigger does not currently have an interface to activate
7 specifying how long a state to be on, and the second for how long the state
8 to be off. The delay_on value specifies the time period an LED should stay
11 gets deactivated. There is no provision for one time activation to implement
12 features that require an on or off state to be held just once and then stay in
15 Without one shot timer interface, user space can still use timer trigger to
16 set a timer to hold a state, however when user space application crashes or
30 trigger will be called, and LED state is changed to LED_OFF.
32 Driver suspend changes the LED state to LED_OFF and resume doesn't change
36 that are active at the time driver gets suspended, continue to run, without
[all …]
|
| D | leds-class.rst | 8 of the LED (taking a value 0-max_brightness). Most LEDs don't have hardware
9 brightness support so will just be turned on for non-zero brightness settings.
13 complex. A simple trigger isn't configurable and is designed to slot into
14 existing subsystems with minimal additional code. Examples are the disk-activity,
15 nand-disk and sharpsl-charge triggers. With led triggers disabled, the code
18 Complex triggers while available to all LEDs have LED specific
24 trigger. However, if you set the brightness value to LED_OFF it will
27 You can change triggers in a similar manner to the way an IO scheduler
37 and the aim is to keep a small amount of code giving as much functionality
48 - devicename:
[all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-reload.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 ``devlink-reload`` provides mechanism to reinit driver entities, applying
8 ``devlink-params`` and ``devlink-resources`` new values. It also provides
9 mechanism to activate firmware.
17 .. list-table:: Possible reload actions
20 * - Name
21 - Description
22 * - ``driver-reinit``
23 - Devlink driver entities re-initialization, including applying
24 new values to devlink entities which are used during driver
[all …]
|
| /Documentation/networking/device_drivers/atm/ |
| D | cxacru.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 driver and it is necessary to unplug/remove power to the device to fix this.
13 Note: support for cxacru-cf.bin has been removed. It was not loaded correctly
17 There is a script cxacru-cf.py to convert an existing file to the sysfs form.
21 named device points to the USB interface device's directory which contains
29 - Information about the remote headend.
33 - Configuration writing interface.
34 - Write parameters in hexadecimal format <index>=<value>,
39 - Up to 7 parameters at a time will be sent and the modem will restart
48 - Downstream stats.
[all …]
|
| /Documentation/devicetree/bindings/memory-controllers/ddr/ |
| D | jedec,lpddr3-timings.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/ddr/jedec,lpddr3-timings.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: LPDDR3 SDRAM AC timing parameters for a given speed-bin
10 - Krzysztof Kozlowski <krzk@kernel.org>
14 const: jedec,lpddr3-timings
19 Maximum DDR clock frequency for the speed-bin, in Hz.
20 Property is deprecated, use max-freq.
23 max-freq:
[all …]
|
| D | jedec,lpddr3.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/ddr/jedec,lpddr3.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: LPDDR3 SDRAM compliant to JEDEC JESD209-3
10 - Krzysztof Kozlowski <krzk@kernel.org>
13 - $ref: jedec,lpddr-props.yaml#
18 - items:
19 - enum:
20 - samsung,K3QF2F20DB
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-eud | 8 the user is able to activate the mini-usb hub of
|
| D | sysfs-driver-intel_sdsi | 27 ETIMEDOUT Failure to complete mailbox transaction in time.
38 is available at http://github.com/intel/intel-sdsi
45 (RO) Contains information needed by applications to provision
49 http://github.com/intel/intel-sdsi
56 (WO) Used to write an Authentication Key Certificate (AKC) to
57 the On Demand NVRAM for the CPU. The AKC is used to authenticate
65 (WO) Used to write a Capability Activation Payload (CAP) to the
66 On Demand NVRAM for the CPU. CAPs are used to activate a given
69 the CPU configuration is updated. A cold reboot is required to
70 fully activate the feature. Mailbox command.
[all …]
|
| D | sysfs-class-power-twl4030 | 4 Writing to this can disable charging.
12 "continuous" activate mode described as "linear" in
19 be taken that battery is not over-charged.
25 Writing to this can disable charging.
|
| D | sysfs-bus-coresight-devices-cti | 1 What: /sys/bus/coresight/devices/<cti-name>/enable
7 What: /sys/bus/coresight/devices/<cti-name>/powered
13 What: /sys/bus/coresight/devices/<cti-name>/ctmid
19 What: /sys/bus/coresight/devices/<cti-name>/nr_trigger_cons
23 Description: (Read) Number of devices connected to triggers on this CTI
25 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name
31 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals
37 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_types
44 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_signals
48 Description: (Read) Output trigger signals to connected device <N>
[all …]
|
| D | sysfs-bus-iio-trigger-sysfs | 3 Contact: linux-iio@vger.kernel.org
5 This file is provided by the iio-trig-sysfs stand-alone trigger
7 driven driver, associated with this trigger, to capture data
15 Contact: linux-iio@vger.kernel.org
18 trigger. In order to associate the trigger with an IIO device
19 one should write this name string to
24 Contact: linux-iio@vger.kernel.org
26 This attribute is provided by the iio-trig-sysfs stand-alone
27 driver and it is used to activate the creation of a new trigger.
28 In order to achieve this, one should write a positive integer
[all …]
|
| /Documentation/admin-guide/ |
| D | pnp.rst | 10 --------
14 services to compatible drivers.
18 ------------------
20 The Linux Plug and Play user interface provides a means to activate PnP devices
24 In addition to the standard sysfs file the following are created in each
26 - id - displays a list of support EISA IDs
27 - options - displays possible resource configurations
28 - resources - displays currently allocated resources and allows resource changes
37 this will invoke the automatic resource config system to activate the device
46 <depnum> - the configuration number
[all …]
|
| /Documentation/networking/dsa/ |
| D | b53.rst | 1 .. SPDX-License-Identifier: GPL-2.0
20 The switch is, if possible, configured to enable a Broadcom specific 4-bytes
21 switch tag which gets inserted by the switch for every packet forwarded to the
30 configuration described in the :ref:`dsa-config-showcases`.
33 ----------------------------------
35 The tagging based configuration is desired. It is not specific to the b53
38 See :ref:`dsa-tagged-configuration`.
41 -------------------------------------
48 The configuration slightly differ from the :ref:`dsa-vlan-configuration`.
54 In difference to the configuration described in :ref:`dsa-vlan-configuration`
[all …]
|
| /Documentation/driver-api/firmware/ |
| D | fw_search_path.rst | 5 The following search paths are used to look for firmware on your
8 * fw_path_para - module parameter - default is empty so this is ignored
14 The module parameter ''path'' can be passed to the firmware_class module
15 to activate the first optional custom fw_path_para. The custom path can
16 only be up to 256 characters long. The kernel parameter passed would be:
20 There is an alternative to customize the path at run time after bootup, you
27 and may not produce the intended effects. For instance you might want to use:
29 echo -n /path/to/script > /sys/module/firmware_class/parameters/path
31 to ensure that your script is being used.
|
| /Documentation/misc-devices/ |
| D | xilinx_sdfec.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
4 Xilinx SD-FEC Driver
10 This driver supports SD-FEC Integrated Block for Zynq |Ultrascale+ (TM)| RFSoCs.
15 …f SD-FEC core features, see the `SD-FEC Product Guide (PG256) <https://www.xilinx.com/cgi-bin/docs…
19 - Retrieval of the Integrated Block configuration and status information
20 - Configuration of LDPC codes
21 - Configuration of Turbo decoding
22 - Monitoring errors
24 Missing features, known issues, and limitations of the SD-FEC driver are as
27 - Only allows a single open file handler to any instance of the driver at any time
[all …]
|
| /Documentation/arch/x86/ |
| D | amd-memory-encryption.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 SME provides the ability to mark individual pages of memory as encrypted using
12 automatically decrypted when read from DRAM and encrypted when written to
13 DRAM. SME can therefore be used to protect the contents of DRAM from physical
19 memory. Private memory is encrypted with the guest-specific key, while shared
24 below on how to determine its position). The encryption bit can also be
25 specified in the cr3 register, allowing the PGD table to be encrypted. Each
27 bit in the page table entry that points to the next table. This allows the full
28 page table hierarchy to be encrypted. Note, this means that just because the
30 Each page table entry in the hierarchy needs to have the encryption bit set to
[all …]
|
| /Documentation/userspace-api/media/rc/ |
| D | rc-tables.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
9 Unfortunately, for several years, there was no effort to create uniform
10 IR keycodes for different devices. This caused the same IR keyname to be
12 that the same IR keyname to be mapped completely different on different
13 IR's. Due to that, V4L2 API now specifies a standard for mapping Media
22 devices (CONFIG_INPUT_EVDEV) it is possible for applications to access
30 .. flat-table:: IR default keymapping
31 :header-rows: 0
32 :stub-columns: 0
36 - .. row 1
[all …]
|
| /Documentation/devicetree/bindings/iio/light/ |
| D | capella,cm3605.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Linus Walleij <linus.walleij@linaro.org>
12 - Kevin Tsai <ktsai@capellamicro.com>
16 software logic to interface a host operating system.
26 aset-gpios:
29 ASET line (drive low to activate the ALS, should be flagged
35 Connected to the POUT (proximity sensor out) line. The edge
36 detection must be set to IRQ_TYPE_EDGE_BOTH so as to detect
[all …]
|
| /Documentation/translations/zh_CN/doc-guide/ |
| D | sphinx.rst | 1 .. include:: ../disclaimer-zh_CN.rst
3 :Original: Documentation/doc-guide/sphinx.rst
12 Linux内核使用 `Sphinx <http://www.sphinx-doc.org/>`_ 来把 ``Documentation``
17 reStructuredText文件可能包含包含来自源文件的结构化文档注释或kernel-doc注释。
18 通常它们用于描述代码的功能、类型和设计。kernel-doc注释有一些特殊的结构和
32 :ref:`sphinx-pre-install_zh` 。
38 ``virtualenv-3`` 或 ``virtualenv`` 在虚拟环境中安装Sphinx，具体取决于发行版
52 $ . sphinx_2.4.4/bin/activate
53 (sphinx_2.4.4) $ pip install -r Documentation/sphinx/requirements.txt
55 在运行 ``. sphinx_2.4.4/bin/activate`` 之后，提示符将变化，以指示您正在使用新
[all …]
|
| /Documentation/driver-api/tty/ |
| D | tty_port.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 The TTY drivers are advised to use struct tty_port helpers as much as possible.
10 If the drivers implement :c:member:`tty_port.ops.activate()` and
22 --------------
24 .. kernel-doc:: drivers/tty/tty_port.c
29 -------------------------
31 .. kernel-doc:: drivers/tty/tty_port.c
37 ---------------
39 .. kernel-doc:: drivers/tty/tty_port.c
43 -----------
[all …]
|
| /Documentation/hwmon/ |
| D | oxp-sensors.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
3 Kernel driver oxp-sensors
7 - Derek John Clark <derekjohn.clark@gmail.com>
8 - Joaquín Ignacio Aramendía <samsagax@gmail.com>
11 ------------
27 -----------------
31 - AOKZOE A1
32 - AOKZOE A1 PRO
33 - AYANEO 2
34 - AYANEO 2S
[all …]
|
| /Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| D | switchdev.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR Linux-OpenIB
17 representor is attached to bridge.
19 - Change device to switchdev mode::
23 - Attach mlx5 switchdev representor 'enp8s0f0' to bridge netdev 'bridge1'::
28 -----
32 - VLAN filtering (including multiple VLANs per port)::
35 $ bridge vlan add dev enp8s0f0 vid 2-3
37 - VLAN push on bridge ingress::
41 - VLAN pop on bridge egress::
48 Subfunction which are spawned over the E-switch are created only with devlink
[all …]
|
| /Documentation/input/devices/ |
| D | appletouch.rst | 3 ----------------------------------
5 ----------------------------------
17 to have touchpad acceleration, scrolling, etc.
19 Credits go to Johannes Berg for reverse-engineering the touchpad protocol,
25 -----
27 In order to use the touchpad in the basic mode, compile the driver and load
28 the module. A new input device will be detected and you will be able to read
31 In X11, you can configure the touchpad to use the synaptics X11 driver, which
34 emulation, etc. In order to do this, make sure you're using a recent version of
44 Option "Protocol" "auto-dev"
[all …]
|
| /Documentation/admin-guide/media/ |
| D | technisat.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 How to set up the Technisat/B2C2 Flexcop devices
13 -----------------------------
19 .. code-block:: none
21 lspci -vvv for a PCI device (lsusb -vvv for an USB device) will show you for example:
29 -------------------
34 ``Multimedia support`` => ``Customise analog and hybrid tuner modules to build``
37 (except ``Simple tuner support`` for ATSC 3rd generation only -> see case 9 please).
39 Then please activate:
41 - Main module part:
[all …]
|
1234