Searched full:model (Results 1 – 25 of 325) sorted by relevance
12345678910>>...13
| /Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,bcm2835.txt | 4 Raspberry Pi Model A
6 compatible = "raspberrypi,model-a", "brcm,bcm2835";
8 Raspberry Pi Model A+
10 compatible = "raspberrypi,model-a-plus", "brcm,bcm2835";
12 Raspberry Pi Model B
14 compatible = "raspberrypi,model-b", "brcm,bcm2835";
16 Raspberry Pi Model B (no P5)
17 early model B with I2C0 rather than I2C1 routed to the expansion header
19 compatible = "raspberrypi,model-b-i2c0", "brcm,bcm2835";
21 Raspberry Pi Model B rev2
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | nspire-clock.txt | 5 "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/ |
| D | sysfs-bus-media | 1 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.
|
| D | sysfs-bus-mcb | 19 What: /sys/bus/mcb/devices/mcb:X/model
23 Description: The FPGA's model number
|
| /Documentation/devicetree/bindings/c6x/ |
| D | soc.txt | 13 - model: specific SoC model
22 model = "tms320c6455";
|
| /Documentation/vm/ |
| D | memory-model.rst | 6 Physical Memory Model
19 memory models it supports, what the default memory model is and
29 Regardless of the selected memory model, there exists one-to-one
33 Each memory model defines :c:func:`pfn_to_page` and :c:func:`page_to_pfn`
40 The simplest memory model is FLATMEM. This model is suitable for
44 In the FLATMEM memory model, there is a global `mem_map` array that
71 The DISCONTIGMEM model treats the physical memory as a collection of
91 DISCONTIGMEM model became slightly more complex as it has to determine
108 SPARSEMEM is the most versatile memory model available in Linux and it
109 is the only memory model that supports several advanced features such
[all …]
|
| /Documentation/driver-api/driver-model/ |
| D | overview.rst | 2 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,
|
| D | porting.rst | 2 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/sound/ |
| D | qcom,apq8096.txt | 53 - model:
89 qcom,model: String for soundcard name (Use model instead)
97 model = "DB820c";
|
| D | storm.txt | 14 - qcom,model : The user-visible name of this sound card.
20 qcom,model = "ipq806x-storm";
|
| D | rockchip-rt5645.txt | 5 - rockchip,model: The user-visible name of this sound complex
14 rockchip,model = "ROCKCHIP-I2S";
|
| D | rockchip-max98090.txt | 5 - rockchip,model: The user-visible name of this sound complex
15 rockchip,model = "ROCKCHIP-I2S";
|
| D | eukrea-tlv320.txt | 7 - eukrea,model : The user-visible name of this sound complex.
22 eukrea,model = "imx51-eukrea-tlv320aic23";
|
| D | mikroe,mikroe-proto.txt | 9 - model: The user-visible name of this sound complex.
18 model = "wm8731 @ sama5d2_xplained";
|
| D | atmel-at91sam9g20ek-wm8731-audio.txt | 5 - atmel,model: The user-visible name of this sound complex.
18 atmel,model = "wm8731 @ AT91SAMG20EK";
|
| D | imx-audio-spdif.txt | 7 - model : The user-visible name of this sound complex
32 model = "imx-spdif";
|
| D | snow.txt | 21 - samsung,model: The name of the sound-card
28 samsung,model = "Snow-I2S-MAX98095";
|
| D | atmel-sam9x5-wm8731-audio.txt | 5 - atmel,model: The user-visible name of this sound complex.
25 atmel,model = "wm8731 @ AT91SAM9X5EK";
|
| D | mxs-audio-sgtl5000.txt | 5 - model : The user-visible name of this sound complex
35 model = "imx28-evk-sgtl5000";
|
| /Documentation/devicetree/bindings/arm/ |
| D | vexpress.txt | 20 compatible = "arm,vexpress,<model>", "arm,vexpress";
21 where <model> is the full tile model name (as used in the tile's
29 compatible = "arm,vexpress,<model>,<variant>", \
30 "arm,vexpress,<model>", "arm,vexpress";
40 - tile model name (use name from the tile's Technical Reference
42 model = "<model>";
43 - tile's HBI number (unique ARM's board model ID, visible on the
170 model = "V2P-CA5s";
|
| D | vexpress-scc.txt | 15 - compatible value: "arm,vexpress-scc,<model>", "arm,vexpress-scc";
16 where <model> is the full tile model name (as used
|
| /Documentation/devicetree/bindings/eeprom/ |
| D | at24.txt | 5 - compatible: Must be a "<manufacturer>,<model>" pair. The following <model>
33 with the same <model> and "atmel" as manufacturer.
48 Some vendors use different model names for chips which are just
|
| /Documentation/driver-api/thermal/ |
| D | cpu-cooling-api.rst | 61 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/driver-api/ |
| D | isa.rst | 12 through the driver model. In the course of that, I suggested a separate
21 As another difference: these devices only exist in the driver model due
25 The usage model this provides is nice, and has been acked from the ALSA
67 the model from saner buses more closely, wants to load when a later bind
71 the nicest model.
|
| D | spi.rst | 17 Linux driver model, and perform input/output operations. At this time,
35 spi_device using normal driver model calls.
37 The I/O model is a set of queued messages. Protocol drivers submit one
|
12345678910>>...13