Home
last modified time | relevance | path

Searched full:model (Results 1 – 25 of 462) sorted by relevance

12345678910>>...19

/Documentation/devicetree/bindings/arm/bcm/
Dbcm2835.yaml23 - raspberrypi,4-model-b
29 - raspberrypi,5-model-b
35 - raspberrypi,model-a
36 - raspberrypi,model-a-plus
37 - raspberrypi,model-b
38 - raspberrypi,model-b-i2c0 # Raspberry Pi Model B (no P5)
39 - raspberrypi,model-b-rev2
40 - raspberrypi,model-b-plus
42 - raspberrypi,model-zero
43 - raspberrypi,model-zero-w
[all …]
/Documentation/trace/rv/
Dda_monitor_instrumentation.rst13 * are translated into model's event.
47 instrumentation section translates *kernel events* into the *model's
54 functions* for each of the three events from the wip model. The developer
64 The preempt_disable event from the model connects directly to the
79 preempt_enable event will be used to synchronize the system to the model.
81 Initially, the *model* is placed in the initial state. However, the *system*
87 and the model are expected to return to the initial state after the
89 system and the model at the initialization of the monitoring section.
142 is used to connect the wip model events to the relative kernel event. dot2k automatically
143 adds "rv_attach_trace_probe()" function call for each model event in the enable phase, as
[all …]
Dda_monitor_synthesis.rst17 functions that glue the monitor to the system reference model, and the
25 | Tracing | -> | Instance(s) | <- | Model |
49 The dot2k utility leverages dot2c by converting an automaton model in
53 For example, it is possible to transform the wip.dot model present in
60 - wip.h: the wip model in C
77 to manipulate the model in a (let's say) non-standard way.
91 the model in C.
93 For example, the wip model with two states and three events can be
120 Using the wip model as example, the events "preempt_disable" and
/Documentation/devicetree/bindings/clock/
Dnspire-clock.txt5 "lsi,nspire-cx-ahb-divider" for the AHB divider in the CX model
6 "lsi,nspire-classic-ahb-divider" for the AHB divider in the older model
7 "lsi,nspire-cx-clock" for the base clock in the CX model
8 "lsi,nspire-classic-clock" for the base clock in the older model
/Documentation/ABI/testing/
Dsysfs-bus-media1 What: /sys/bus/media/devices/.../model
5 Description: Contains the device model name in UTF-8. The device version is
6 is not be appended to the model name.
Dsysfs-driver-input-exc300010 What: /sys/bus/i2c/devices/xxx/model
13 Description: Reports the model identification provided by the touchscreen, for example "Orion_13…
Dsysfs-bus-mcb19 What: /sys/bus/mcb/devices/mcb:X/model
23 Description: The FPGA's model number
/Documentation/devicetree/bindings/sound/
Drockchip-max98090.txt5 - rockchip,model: The user-visible name of this sound complex
20 rockchip,model = "ROCKCHIP-I2S";
29 rockchip,model = "ROCKCHIP-I2S";
37 rockchip,model = "ROCKCHIP-I2S";
Dimx-audio-hdmi.yaml18 model:
43 - model
52 model = "audio-hdmi";
Dloongson,ls-audio-card.yaml21 model:
50 - model
61 model = "loongson-audio";
Dstorm.txt14 - qcom,model : The user-visible name of this sound card.
20 qcom,model = "ipq806x-storm";
Drockchip-rt5645.txt5 - rockchip,model: The user-visible name of this sound complex
14 rockchip,model = "ROCKCHIP-I2S";
Datmel,sam9x5-wm8731-audio.yaml19 atmel,model:
54 - atmel,model
66 atmel,model = "wm8731 @ AT91SAM9X5EK";
Deukrea-tlv320.txt7 - eukrea,model : The user-visible name of this sound complex.
22 eukrea,model = "imx51-eukrea-tlv320aic23";
Datmel,asoc-wm8904.yaml19 atmel,model:
58 - atmel,model
72 atmel,model = "wm8904 @ AT91SAM9N12EK";
Datmel-at91sam9g20ek-wm8731-audio.txt5 - atmel,model: The user-visible name of this sound complex.
18 atmel,model = "wm8731 @ AT91SAMG20EK";
Dmikroe,mikroe-proto.txt9 - model: The user-visible name of this sound complex.
18 model = "wm8731 @ sama5d2_xplained";
/Documentation/admin-guide/RAS/
Derror-decoding.rst18 Also, the user can pass particular family and model to decode the error
21 …n -p --status <STATUS> --ipid <IPID> --smca --family <CPU Family> --model <CPU Model> --bank <BANK…
/Documentation/mm/
Dmemory-model.rst4 Physical Memory Model
17 memory models it supports, what the default memory model is and
23 Regardless of the selected memory model, there exists one-to-one
27 Each memory model defines :c:func:`pfn_to_page` and :c:func:`page_to_pfn`
34 The simplest memory model is FLATMEM. This model is suitable for
38 In the FLATMEM memory model, there is a global `mem_map` array that
63 SPARSEMEM is the most versatile memory model available in Linux and it
64 is the only memory model that supports several advanced features such
69 The SPARSEMEM model presents the physical memory as a collection of
/Documentation/driver-api/driver-model/
Doverview.rst2 The Linux Kernel Device Model
14 The Linux Kernel Driver Model is a unification of all the disparate driver
23 The current driver model provides a common, uniform data model for describing
25 model includes a set of common attributes which all busses carry, and a set
31 management, and hot plug. In particular, the model dictated by Intel and
66 driver model generally do not and should not touch the fields of struct device,
Dporting.rst2 Porting Drivers to the New Driver Model
12 Please refer to `Documentation/driver-api/driver-model/*.rst` for definitions of
15 Most of the work of porting devices drivers to the new model happens
20 In a nutshell, the driver model consists of a set of objects that can
24 The generic objects must be registered with the driver model core. By
138 The driver model maintains an ordered list of devices that it uses
160 The release field is a callback that the driver model core calls
168 with the driver model core by doing::
178 it. It should instead wait for the driver model core to call the
231 of operations that the driver model core may call.
[all …]
/Documentation/devicetree/bindings/arm/
Dvexpress-scc.txt15 - compatible value: "arm,vexpress-scc,<model>", "arm,vexpress-scc";
16 where <model> is the full tile model name (as used
/Documentation/driver-api/thermal/
Dcpu-cooling-api.rst61 The power API registration functions provide a simple power model for
63 supported currently). This power model requires that the operating-points of
83 A high level dynamic power consumption model may then be represented as::
92 in practice, such an on-line model has dependencies on a number of
98 In this simplified representation our model becomes::
/Documentation/arch/loongarch/
Dirq-chip-model.rst4 IRQ chip model (hierarchy) of LoongArch
17 and there are two models of hierarchy (legacy model and extended model).
19 Legacy IRQ model
22 In this model, IPI (Inter-Processor Interrupt) and CPU Local Timer interrupt go
56 Extended IRQ model
59 In this model, IPI (Inter-Processor Interrupt) and CPU Local Timer interrupt go
88 Advanced Extended IRQ model
91 In this model, IPI (Inter-Processor Interrupt) and CPU Local Timer interrupt go
/Documentation/sound/hd-audio/
Dnotes.rst153 Model Option
170 hda_codec: Unknown model for ALC880, trying auto-probe from BIOS...
175 listed in the known preset model (white-)list. But, this doesn't mean
188 The preset model (or recently called as "fix-up") is provided
190 model is found in the white-list, the driver assumes the static
194 re-use the same model. You can pass the ``model`` option to specify the
195 preset model instead of PCI (and codec-) SSID look-up.
197 What ``model`` option values are available depends on the codec chip.
202 and ``model`` options belonging to each codec. For example, for Realtek
203 ALC262 codec chip, pass ``model=ultra`` for devices that are compatible
[all …]

12345678910>>...19