Searched +full:target +full:- +full:module (Results 1 – 25 of 150) sorted by relevance
123456
| /Documentation/devicetree/bindings/bus/ |
| D | ti-sysc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/bus/ti-sysc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Texas Instruments interconnect target module
10 - Tony Lindgren <tony@atomide.com>
13 Texas Instruments SoCs can have a generic interconnect target module
15 using Arteris NoC, and L4 interconnect using Sonics s3220. This module
16 is mostly used for interaction between module and Power, Reset and Clock
20 Each interconnect target module can have one or more devices connected to
[all …]
|
| /Documentation/target/ |
| D | tcm_mod_builder.rst | 2 The TCM v4 fabric module script generator
7 This document is intended to be a mini-HOWTO for using the tcm_mod_builder.py
8 script to generate a brand new functional TCM v4 fabric .ko module of your very own,
13 mkdir -p /sys/kernel/config/target/$TCM_NEW_MOD
15 This script will create a new drivers/target/$TCM_NEW_MOD/, and will do the following
17 1) Generate new API callers for drivers/target/target_core_fabric_configs.c logic
18 ->make_tpg(), ->drop_tpg(), ->make_wwn(), ->drop_wwn(). These are created
20 2) Generate basic infrastructure for loading/unloading LKMs and TCM/ConfigFS fabric module
22 3) Based on user defined T10 Proto_Ident for the new fabric module being built,
23 the TransportID / Initiator and Target WWPN related handlers for
[all …]
|
| /Documentation/kbuild/ |
| D | modules.rst | 5 This document describes how to build an out-of-tree kernel module.
13 both in-tree and out-of-tree is provided. The method for building
15 out-of-tree.
18 in building out-of-tree (or "external") modules. The author of an
19 external module should supply a makefile that hides most of the
20 complexity, so one only has to type "make" to build the module. This is
22 section `Creating a Kbuild File for an External Module`_.
34 An alternative is to use the "make" target "modules_prepare." This will
35 make sure the kernel contains the information required. The target
39 NOTE: "modules_prepare" will not build Module.symvers even if
[all …]
|
| D | makefiles.rst | 22 (the resident kernel image) and modules (any module files).
29 architecture-specific information to the top Makefile.
34 any built-in or modular targets.
80 ----------------
90 obj-y += foo.o
95 If foo.o shall be built as a module, the variable obj-m is used.
100 obj-$(CONFIG_FOO) += foo.o
102 $(CONFIG_FOO) evaluates to either y (for built-in) or m (for module).
106 Built-in object goals - obj-y
107 -----------------------------
[all …]
|
| D | gendwarfksyms.rst | 2 DWARF module versioning
15 details about the final module ABI.
18 -----
23 Usage: gendwarfksyms [options] elf-object-file ... < symbol-list
26 -d, --debug Print debugging information
27 --dump-dies Dump DWARF DIE contents
28 --dump-die-map Print debugging information about die_map changes
29 --dump-types Dump type strings
30 --dump-versions Dump expanded type strings used for symbol versions
31 -s, --stable Support kABI stability features
[all …]
|
| /Documentation/livepatch/ |
| D | callbacks.rst | 5 Livepatch (un)patch-callbacks provide a mechanism for livepatch modules
10 - Safe updates to global data
12 - "Patches" to init and probe functions
14 - Patching otherwise unpatchable code (i.e. assembly)
25 - Module init/exit code doesn't run when disabling and re-enabling a
28 - A module notifier can't stop a to-be-patched module from loading.
32 be patched, irrespective of the target klp_object's current state.
39 * Pre-patch
40 - before a klp_object is patched
42 * Post-patch
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | ti-clkctrl.txt | 4 interconnect target module. The clkctrl clock controller manages functional
5 and interface clocks for each module. Each clkctrl controller can also
6 gate one or more optional functional clocks for a module, and can have one
8 interconnect target module on omap4 and later variants.
16 Documentation/devicetree/bindings/clock/clock-bindings.txt.
19 - compatible : shall be "ti,clkctrl" or a clock domain specific name:
20 "ti,clkctrl-l4-cfg"
21 "ti,clkctrl-l4-per"
22 "ti,clkctrl-l4-secure"
23 "ti,clkctrl-l4-wkup"
[all …]
|
| /Documentation/i2c/ |
| D | i2c-stub.rst | 2 i2c-stub
8 This module is a very simple fake I2C/SMBus driver. It implements six
12 You need to provide chip addresses as a module parameter when loading this
15 No hardware is needed nor associated with this module. It will accept write
21 A pointer register with auto-increment is implemented for all byte
27 module parameter.
33 The typical use-case is like this:
35 1. load this module
36 2. use i2cset (from the i2c-tools project) to pre-load some data
37 3. load the target chip driver module
[all …]
|
| /Documentation/devicetree/bindings/ata/ |
| D | allwinner,sun4i-a10-ahci.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/ata/allwinner,sun4i-a10-ahci.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chen-Yu Tsai <wens@csie.org>
11 - Maxime Ripard <mripard@kernel.org>
15 const: allwinner,sun4i-a10-ahci
22 - description: AHCI Bus Clock
23 - description: AHCI Module Clock
28 target-supply:
[all …]
|
| /Documentation/dev-tools/ |
| D | gdb-kernel-debugging.rst | 6 The kernel debugger kgdb, hypervisors like QEMU or JTAG-based hardware
11 them. It focuses on QEMU/KVM virtual machines as target, but the examples can
16 ------------
18 - gdb 7.2+ (recommended: 7.4+) with python support enabled (typically true
23 -----
25 - Create a virtual Linux machine for QEMU/KVM (see www.linux-kvm.org and
26 www.qemu.org for more details). For cross-development,
30 - Build the kernel with CONFIG_GDB_SCRIPTS enabled, but leave
34 - Install that kernel on the guest, turn off KASLR if necessary by adding
36 Alternatively, QEMU allows to boot the kernel directly using -kernel,
[all …]
|
| D | kgdb.rst | 15 Kdb is simplistic shell-style interface which you can use on a system
22 kernel built-ins or in kernel modules if the code was built with
34 development machine and the other is the target machine. The kernel to
35 be debugged runs on the target machine. The development machine runs an
40 kgdb I/O modules compiled as built-ins or loadable kernel modules in the
46 - In order to enable compilation of kdb, you must first enable kgdb.
48 - The kgdb test compile options are described in the kgdb test suite
52 ------------------------------
55 :menuselection:`Kernel hacking --> Kernel debugging` and select
73 certain regions of the kernel's memory space as read-only. If kgdb
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-init.rst | 5 It is possible to configure a device-mapper device to act as the root device for
11 The second is to create one or more device-mappers using the module parameter
12 "dm-mod.create=" through the kernel boot command line argument.
15 semi-colons, where:
17 - a comma is used to separate fields like name, uuid, flags and table
19 - a semi-colon is used to separate devices.
23 …dm-mod.create=<name>,<uuid>,<minor>,<flags>,<table>[,<table>+][;<name>,<uuid>,<minor>,<flags>,<tab…
28 <uuid> ::= xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx | ""
35 `--concise` argument.
37 Target types
[all …]
|
| D | unstriped.rst | 2 Device-mapper "unstriped" target
8 The device-mapper "unstriped" target provides a transparent mechanism to
9 unstripe a device-mapper "striped" target to access the underlying disks
10 without having to touch the true backing block-device. It can also be
11 used to unstripe a hardware RAID-0 to access backing disks.
30 Why use this module?
33 An example of undoing an existing dm-stripe
34 -------------------------------------------
37 striped target to combine the 4 devices into one. It then will use
38 the unstriped target on top of the striped device to access the
[all …]
|
| /Documentation/gpu/ |
| D | vgaarbiter.rst | 7 implemented on PCI will typically have the same "hard-decoded" addresses as
8 they did on ISA. For more details see "PCI Bus Binding to IEEE Std 1275-1994
12 The Resource Access Control (RAC) module inside the X server [0] existed for
14 than one legacy device co-exists on the same machine. But the problem happens
23 ---------------------------
25 The vgaarb is a module of the Linux Kernel. When it is initially loaded, it
42 Return a string indicating the status of the target like:
51 unplugged, we get "invalid" then for card_ID and an -ENODEV
58 target <card_ID>
59 switch target to card <card_ID> (see below)
[all …]
|
| /Documentation/scsi/ |
| D | BusLogic.rst | 1 .. SPDX-License-Identifier: GPL-2.0
21 Copyright 1995-1998 by Leonard N. Zubkoff <lnz@dandelion.com>
52 line or at module initialization time, allowing individual installations to
57 BT-948/958/958D, will always be available from my Linux Home Page at URL
69 the BT-948 PCI Ultra SCSI Host Adapter, and then again for the BT-958 PCI Wide
90 94555, USA and can be reached at 510/796-6100 or on the World Wide Web at
92 mail at techsup@mylex.com, by Voice at 510/608-2400, or by FAX at 510/745-7715.
101 -----------------------------------
105 requested and negotiated with each target device. AutoSCSI settings for
107 reported for each target device, as well as the status of Tagged Queuing.
[all …]
|
| D | tcm_qla2xxx.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 ------------------------------
9 There is now a new module endpoint attribute called jam_host
32 echo 1 > /sys/kernel/config/target/qla2xxx/21:00:00:24:ff:27:8f:ae/tpgt_1/attrib/jam_host
36 echo 0 > /sys/kernel/config/target/qla2xxx/21:00:00:24:ff:27:8f:ae/tpgt_1/attrib/jam_host
|
| /Documentation/networking/ |
| D | netconsole.rst | 1 .. SPDX-License-Identifier: GPL-2.0
26 This module logs kernel printk messages over UDP allowing debugging of
29 It can be used either built-in or as a module. As a built-in,
41 netconsole=[+][r][src-port]@[src-ip]/[<dev>],[tgt-port]@<tgt-ip>/[tgt-macaddr]
46 src-port source for UDP packets (defaults to 6665)
47 src-ip source IP to use (interface address)
49 tgt-port port for logging agent (6666)
50 tgt-ip IP address for logging agent
51 tgt-macaddr ethernet MAC address for logging agent (broadcast)
71 Built-in netconsole starts immediately after the TCP stack is
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | intel_idle.rst | 1 .. SPDX-License-Identifier: GPL-2.0
24 Documentation/admin-guide/pm/cpuidle.rst if you have not done that yet.]
28 processor's functional blocks into low-power states. That instruction takes two
29 arguments (passed in the ``EAX`` and ``ECX`` registers of the target CPU), the
38 only way to pass early-configuration-time parameters to it is via the kernel
42 .. _intel-idle-enumeration-of-states:
50 as C-states (in the ACPI terminology) or idle states. The list of meaningful
51 ``MWAIT`` hint values and idle states (i.e. low-power configurations of the
56 subsystem (see :ref:`idle-states-representation` in
57 Documentation/admin-guide/pm/cpuidle.rst),
[all …]
|
| /Documentation/admin-guide/hw-vuln/ |
| D | cross-thread-rsb.rst | 2 .. SPDX-License-Identifier: GPL-2.0
4 Cross-Thread Return Address Predictions
7 Certain AMD and Hygon processors are subject to a cross-thread return address
9 transitions out of C0 state, the other sibling thread could use return target
15 transitioning out of C0. This could result in a guest-controlled return target
19 -------------------
23 - AMD Family 17h processors
24 - Hygon Family 18h processors
27 ------------
32 CVE-2022-27672 Cross-Thread Return Address Predictions
[all …]
|
| /Documentation/driver-api/usb/ |
| D | usb3-debug-port.rst | 19 3) have a USB 3.0 super-speed A-to-A debugging cable.
30 super-speed port). The debug device is fully compliant with
32 performance full-duplex serial link between the debug target
41 Other uses include simpler, lockless logging instead of a full-
44 On the debug target system, you need to customize a debugging
58 "usbcore.autosuspend=-1"
60 Before starting the debug target, you should connect the debug
63 should be a USB 3.0 super-speed A-to-A debugging cable.
65 During early boot of the debug target, DbC will be detected and
67 to enumerate the debug device in debug target. The debug host
[all …]
|
| /Documentation/arch/powerpc/ |
| D | hvcs.rst | 24 3.1 Built-in:
25 3.2 Module:
55 major and minor numbers are associated with each vty-server. Directions
68 built into the kernel. If not, the default can be over-ridden by inserting
69 the driver as a module with insmod parameters.
71 3.1 Built-in:
72 -------------
77 Device Drivers --->
78 Character devices --->
83 3.2 Module:
[all …]
|
| /Documentation/admin-guide/aoe/ |
| D | aoe.rst | 11 http://support.coraid.com/support/linux/EtherDrive-2.6-HOWTO.html
16 http://support.coraid.com/support/linux/EtherDrive-2.6-HOWTO-5.html#ss5.19
23 The scripts in this Documentation/admin-guide/aoe directory are intended to
35 There is a udev-install.sh script that shows how to install these
39 /etc/modprobe.d/aoe.conf to ensure that the aoe module is loaded when
40 necessary. Preloading the aoe module is preferable to autoloading,
86 a convenient way. Users with aoetools should use the aoe-stat
89 root@makki root# sh Documentation/admin-guide/aoe/status.sh
111 Use /sys/module/aoe/parameters/aoe_iflist (or better, the driver
114 whitespace-separated list. Unlike the old character device, the
[all …]
|
| /Documentation/core-api/ |
| D | debugging-via-ohci1394.rst | 2 Using physical DMA provided by OHCI-1394 FireWire controllers for debugging
6 ------------
9 to the OHCI-1394 specification which defines the controller to be a PCI
12 PCI-Bus master DMA after applying filters defined by the OHCI-1394 driver.
15 ask the OHCI-1394 controller to perform read and write requests on
28 hardware such as x86, x86-64 and PowerPC.
34 Together with a early initialization of the OHCI-1394 controller for debugging,
41 -------
43 The firewire-ohci driver in drivers/firewire uses filtered physical
47 Because the firewire-ohci driver depends on the PCI enumeration to be
[all …]
|
| /Documentation/driver-api/surface_aggregator/clients/ |
| D | cdev.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
8 User-Space EC Interface (cdev)
11 The ``surface_aggregator_cdev`` module provides a misc-device for the SSAM
12 controller to allow for a (more or less) direct connection from user-space to
15 module is not loaded automatically, but instead must be loaded manually.
18 device-file. All functionality of this interface is provided via IOCTLs.
23 at https://github.com/linux-surface/surface-aggregator-module/tree/master/scripts/ssam.
31 Events can be received by reading from the device-file. The are represented by
37 interface, associated with a specific target category and device-file-instance.
43 notifiers work per-client (i.e. per-device-file-instance), events are enabled
[all …]
|
| /Documentation/hwmon/ |
| D | amc6821.rst | 19 -----------
22 The chip has one on-chip and one remote temperature sensor and one pwm fan
29 temp1_input ro on-chip temperature
51 fan1_target rw Target fan speed, to be used with pwm1_enable
57 combination of the on-chip temperature and
58 remote-sensor temperature,
59 4=fan controlled by target rpm set with
72 temp1_auto_point2_temp rw The low-temperature limit of the proportional
89 temp2_auto_point2_temp rw The low-temperature limit of the proportional
103 Module parameters
[all …]
|
123456