Searched +full:bool +full:- +full:property (Results 1 – 13 of 13) sorted by relevance
| /Documentation/devicetree/bindings/ |
| D | example-schema.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 4 --- 5 # All the top-level keys are standard json-schema keywords except for 10 $id: http://devicetree.org/schemas/example-schema.yaml# 11 # $schema is the meta-schema this schema should be validated with. 12 $schema: http://devicetree.org/meta-schemas/core.yaml# 17 - Rob Herring <robh@kernel.org> 20 A more detailed multi-line description of the binding. 44 - items: 45 # items is a list of possible values for the property. The number of [all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | stih407-c8sectpfe.txt | 14 - compatible : Should be "stih407-c8sectpfe" 16 - reg : Address and length of register sets for each device in 17 "reg-names" 19 - reg-names : The names of the register addresses corresponding to the 21 - c8sectpfe: c8sectpfe registers 22 - c8sectpfe-ram: c8sectpfe internal sram 24 - clocks : phandle list of c8sectpfe clocks 25 - clock-names : should be "c8sectpfe" 26 See: Documentation/devicetree/bindings/clock/clock-bindings.txt 28 - pinctrl-names : a pinctrl state named tsin%d-serial or tsin%d-parallel (where %d is tsin-num) [all …]
|
| /Documentation/devicetree/bindings/phy/ |
| D | phy-miphy365x.txt | 8 - compatible : Should be "st,miphy365x-phy" 9 - st,syscfg : Phandle / integer array property. Phandle of sysconfig group 11 an entry for each port sub-node, specifying the control 14 Required nodes : A sub-node is required for each channel the controller 16 'reg' and 'reg-names' properties are used inside these 21 - #phy-cells : Should be 1 (See second example) 23 - PHY_TYPE_SATA 24 - PHY_TYPE_PCI 25 - reg : Address and length of register sets for each device in 26 "reg-names" [all …]
|
| /Documentation/devicetree/bindings/misc/ |
| D | atmel-ssc.txt | 4 - compatible: "atmel,at91rm9200-ssc" or "atmel,at91sam9g45-ssc" 5 - atmel,at91rm9200-ssc: support pdc transfer 6 - atmel,at91sam9g45-ssc: support dma transfer 7 - reg: Should contain SSC registers location and length 8 - interrupts: Should contain SSC interrupt 9 - clock-names: tuple listing input clock names. 11 - clocks: phandles to input clocks. 14 Required properties for devices compatible with "atmel,at91sam9g45-ssc": 15 - dmas: DMA specifier, consisting of a phandle to DMA controller node, 17 See Documentation/devicetree/bindings/dma/atmel-dma.txt for details. [all …]
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | lltc,ltc4286.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Delphine CC Chiu <Delphine_CC_Chiu@Wiwynn.com> 15 - lltc,ltc4286 16 - lltc,ltc4287 21 adi,vrange-low-enable: 23 This property is a bool parameter to represent the 29 - compatible 30 - reg [all …]
|
| /Documentation/admin-guide/media/ |
| D | si4713.rst | 1 .. SPDX-License-Identifier: GPL-2.0 14 ---------------------------- 29 ------------------------- 34 The I2C device driver exports a v4l2-subdev interface to the kernel. 36 using the v4l2-subdev calls (g_ext_ctrls, s_ext_ctrls). 45 When the v4l2 mute property is set to 1 (true), the driver will turn the chip off. 48 ---------------------- 51 Here is an output from v4l2-ctl util: 53 .. code-block:: none 55 / # v4l2-ctl -d /dev/radio0 --all -L [all …]
|
| /Documentation/driver-api/phy/ |
| D | samsung-usb2.rst | 6 -------------- 18 -------------------- 20 - phy-samsung-usb2.c 30 - phy-samsung-usb2.h 36 ------------------ 46 bool has_mode_switch; 51 property is a boolean flag that determines whether the SoC has USB host 65 - `int (*rate_to_clk)(unsigned long, u32 *)` 101 - `int (*power_on)(struct samsung_usb2_phy_instance *);` 108 phy-samsung-usb2.c file. In case of Exynos 4210 the following lines were [all …]
|
| /Documentation/driver-api/ |
| D | mailbox.rst | 11 proprietary and implement non-standard protocol. So even if two 34 The method in order of preference is IRQ -> Poll -> None, which 44 send a message through before returning) or non-blocking/async mode (submit 53 bool async; 64 if (dc->async) { 80 complete(&dc->c); 93 /* Populate non-blocking mode client */ 94 dc_async->cl.dev = &pdev->dev; 95 dc_async->cl.rx_callback = message_from_remote; 96 dc_async->cl.tx_done = sample_sent; [all …]
|
| D | pwm.rst | 15 ---------------- 24 PWM_LOOKUP("tegra-pwm", 0, "pwm-backlight", NULL, 36 ---------- 52 bool pwm_might_sleep(struct pwm_device *pwm); 82 PWM arguments are usually platform-specific and allows the PWM user to only 93 ----------------------------------- 102 The number of PWM channels this chip supports (read-only). 105 Exports a PWM channel for use with sysfs (write-only). 108 Unexports a PWM channel from sysfs (write-only). 110 The PWM channels are numbered using a per-chip index from 0 to npwm-1. [all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | enumeration.rst | 1 .. SPDX-License-Identifier: GPL-2.0 13 that are accessed through memory-mapped registers. 15 In order to support this and re-use the existing drivers as much as 18 - Devices that have no bus connector resource are represented as 21 - Devices behind real busses where there is a connector resource 34 This means that when ACPI_HANDLE(dev) returns non-NULL the device was 36 device-specific configuration. There is an example of this below. 43 for the device and add supported ACPI IDs. If this same IP-block is used on 44 some other non-ACPI platform, the driver might work out of the box or needs 133 static bool filter_func(struct dma_chan *chan, void *param) [all …]
|
| /Documentation/power/ |
| D | energy-model.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 ----------- 12 subsystems willing to use that information to make energy-aware decisions. 18 each and every client subsystem to re-implement support for each and every 23 The power values might be expressed in micro-Watts or in an 'abstract scale'. 26 can be found in the Energy-Aware Scheduler documentation 27 Documentation/scheduler/sched-energy.rst. For some subsystems like thermal or 30 thus the real micro-Watts might be needed. An example of these requirements can 32 Documentation/driver-api/thermal/power_allocator.rst. 36 an 'abstract scale' deriving real energy in micro-Joules would not be possible. [all …]
|
| /Documentation/admin-guide/ |
| D | kernel-parameters.txt | 16 force -- enable ACPI if default was off 17 on -- enable ACPI but allow fallback to DT [arm64,riscv64] 18 off -- disable ACPI if default was on 19 noirq -- do not use ACPI for IRQ routing 20 strict -- Be less tolerant of platforms that are not 22 rsdt -- prefer RSDT over (default) XSDT 23 copy_dsdt -- copy DSDT to memory 24 nospcr -- disable console in ACPI SPCR table as 41 If set to vendor, prefer vendor-specific driver 73 Documentation/firmware-guide/acpi/debug.rst for more information about [all …]
|
| /Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 16 ------------ 18 Read-copy update (RCU) is a synchronization mechanism that is often used 19 as a replacement for reader-writer locking. RCU is unusual in that 20 updaters do not block readers, which means that RCU's read-side 28 thought of as an informal, high-level specification for RCU. It is 40 #. `Fundamental Non-Requirements`_ 42 #. `Quality-of-Implementation Requirements`_ 44 #. `Software-Engineering Requirements`_ 53 ------------------------ 58 #. `Grace-Period Guarantee`_ [all …]
|