Home
last modified time | relevance | path

Searched +full:line +full:- +full:name (Results 1 – 25 of 457) sorted by relevance

12345678910>>...19

/Documentation/arch/arm/samsung/
Dclksrc-change-registers.awk1 #!/usr/bin/awk -f
3 # Copyright 2010 Ben Dooks <ben-linux@fluff.org>
8 # ./clksrc-change-registers.awk arch/arm/plat-s5pc1xx/include/plat/regs-clock.h < src > dst
14 return substr(s, eqat+2, (comat-eqat)-2)
19 return substr(b, 2, length(b)-2)
69 while (getline line < ARGV[1] > 0) {
70 if (line ~ /\#define.*_MASK/ &&
71 !(line ~ /USB_SIG_MASK/)) {
72 splitdefine(line, fields)
73 name = fields[0]
[all …]
/Documentation/admin-guide/gpio/
Dgpio-sim.rst1 .. SPDX-License-Identifier: GPL-2.0-or-later
6 The configfs GPIO Simulator (gpio-sim) provides a way to create simulated GPIO
12 ------------------------
14 The gpio-sim module registers a configfs subsystem called ``'gpio-sim'``. For
21 **Group:** ``/config/gpio-sim``
23 This is the top directory of the gpio-sim configfs tree.
25 **Group:** ``/config/gpio-sim/gpio-device``
27 **Attribute:** ``/config/gpio-sim/gpio-device/dev_name``
29 **Attribute:** ``/config/gpio-sim/gpio-device/live``
32 attribute is read-only and allows the user-space to read the platform device
[all …]
Dgpio-virtuser.rst1 .. SPDX-License-Identifier: GPL-2.0-only
8 consumer devices can be instantiated from device-tree or over configfs.
10 A virtual consumer uses the driver-facing GPIO APIs and allows to cover it with
11 automated tests driven by user-space. The GPIOs are requested using
15 -----------------------
17 The gpio-consumer module registers a configfs subsystem called
18 ``'gpio-virtuser'``. For details of the configfs filesystem, please refer to
25 **Group:** ``/config/gpio-virtuser``
27 This is the top directory of the gpio-consumer configfs tree.
29 **Group:** ``/config/gpio-consumer/example-name``
[all …]
Dgpio-mockup.rst1 .. SPDX-License-Identifier: GPL-2.0-only
8 This module has been obsoleted by the more flexible gpio-sim.rst.
14 The GPIO Testing Driver (gpio-mockup) provides a way to create simulated GPIO
20 --------------------------------------------
22 When loading the gpio-mockup driver a number of parameters can be passed to the
28 pairs. Each pair defines the base GPIO number (non-negative integer)
30 is -1, the gpiolib will assign it automatically. while the following
33 Example: gpio_mockup_ranges=-1,8,-1,16,405,409
35 The line above creates three chips. The first one will expose 8 lines,
44 The name format is: gpio-mockup-X-Y where X is mockup chip's ID
[all …]
/Documentation/sphinx/
Dmaintainers_include.py2 # SPDX-License-Identifier: GPL-2.0
3 # -*- coding: utf-8; mode: python -*-
7 maintainers-include
10 Implementation of the ``maintainers-include`` reST-directive.
15 The ``maintainers-include`` reST-directive performs extensive parsing
32 app.add_directive("maintainers-include", MaintainersInclude)
40 u"""MaintainersInclude (``maintainers-include``) directive"""
44 """Parse all the MAINTAINERS lines into ReST for human-readability"""
55 # Field letter to field name mapping.
63 for line in open(path):
[all …]
/Documentation/devicetree/bindings/sound/
Dwidgets.txt3 This mainly specifies audio off-codec DAPM widgets.
7 "template-wname", "user-supplied-wname"
9 The "template-wname" being the template widget name and currently includes:
10 "Microphone", "Line", "Headphone" and "Speaker".
12 The "user-supplied-wname" being the user specified widget name.
15 simple-audio-widgets =
17 "Line", "Line In Jack",
18 "Line", "Line Out Jack",
Dmt2701-cs42448.txt4 - compatible: "mediatek,mt2701-cs42448-machine"
5 - mediatek,platform: the phandle of MT2701 ASoC platform
6 - audio-routing: a list of the connections between audio
7 - mediatek,audio-codec: the phandles of cs42448 codec
8 - mediatek,audio-codec-bt-mrg the phandles of bt-sco dummy codec
9 - pinctrl-names: Should contain only one value - "default"
10 - pinctrl-0: Should specify pin control groups used for this controller.
11 - i2s1-in-sel-gpio1, i2s1-in-sel-gpio2: Should specify two gpio pins to
12 control I2S1-in mux.
17 compatible = "mediatek,mt2701-cs42448-machine";
[all …]
Ddavinci-evm-audio.txt4 - compatible : "ti,da830-evm-audio" : forDM365/DA8xx/OMAPL1x/AM33xx
5 - ti,model : The user-visible name of this sound complex.
6 - ti,audio-codec : The phandle of the TLV320AIC3x audio codec
7 - ti,mcasp-controller : The phandle of the McASP controller
8 - ti,audio-routing : A list of the connections between audio components.
14 - ti,codec-clock-rate : The Codec Clock rate (in Hz) applied to the Codec.
15 - clocks : Reference to the master clock
16 - clock-names : The clock should be named "mclk"
17 - Either codec-clock-rate or the codec-clock reference has to be defined. If
24 * Line Out
[all …]
Dsimple-audio-mux.yaml1 # SPDX-License-Identifier: (GPL-2.0+ OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/simple-audio-mux.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Alexandre Belloni <aleandre.belloni@bootlin.com>
14 their input line is connected to the output line.
17 - $ref: dai-common.yaml#
21 const: simple-audio-mux
23 mux-gpios:
25 GPIOs used to select the input line.
[all …]
/Documentation/block/
Dcmdline-partition.rst2 Embedded device command line partition parsing
5 The "blkdevparts" command line option adds support for reading the
6 block device partition table from the kernel command line.
13 The format for the command line is just like mtdparts:
15 blkdevparts=<blkdev-def>[;<blkdev-def>]
16 <blkdev-def> := <blkdev-id>:<partdef>[,<partdef>]
17 <partdef> := <size>[@<offset>](part-name)
19 <blkdev-id>
20 block device disk name. Embedded device uses fixed block device.
21 Its disk name is also fixed, such as: mmcblk0, mmcblk1, mmcblk0boot0.
[all …]
/Documentation/networking/devlink/
Dmlxsw.rst1 .. SPDX-License-Identifier: GPL-2.0
13 .. list-table:: Generic parameters implemented
15 * - Name
16 - Mode
17 * - ``fw_load_policy``
18 - driverinit
20 The ``mlxsw`` driver also implements the following driver-specific
23 .. list-table:: Driver-specific parameters implemented
26 * - Name
27 - Type
[all …]
/Documentation/admin-guide/
Ddynamic-debug-howto.rst9 debug-print code to obtain additional kernel information.
22 - source filename
23 - function name
24 - line number (including ranges of line numbers)
25 - module name
26 - format string
27 - class name (as known/declared by each module)
29 NOTE: To actually get the debug-print output on the console, you may
32 Documentation/admin-guide/kernel-parameters.rst.
39 :#> head -n7 /proc/dynamic_debug/control
[all …]
/Documentation/firmware-guide/acpi/
Dgpio-properties.rst1 .. SPDX-License-Identifier: GPL-2.0
13 With _DSD we can now query GPIOs using a name instead of an integer
19 Name (_HID, ...)
21 Name (_CRS, ResourceTemplate ()
29 Name (_DSD, Package ()
31 ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
34 Package () { "reset-gpios", Package () { ^BTH, 1, 1, 0 } },
35 Package () { "shutdown-gpios", Package () { ^BTH, 0, 0, 0 } },
42 Package () { "name", Package () { ref, index, pin, active_low }}
61 In our Bluetooth example the "reset-gpios" refers to the second GpioIo()
[all …]
/Documentation/devicetree/bindings/gpio/
Dgpio.txt5 -----------------
7 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
8 of this GPIO for the device. While a non-existent <name> is considered valid
10 for new bindings. Also, GPIO properties named "[<name>-]gpio" are valid and old
17 meaningful name. The only case where an array of GPIOs is accepted is when
18 several GPIOs serve the same function (e.g. a parallel data line).
24 and bit-banged data signals:
27 gpio-controller;
28 #gpio-cells = <2>;
32 data-gpios = <&gpio1 12 0>,
[all …]
/Documentation/ABI/testing/
Dsysfs-ocfs23 Contact: ocfs2-devel@lists.linux.dev
6 ocfs2-tools to interact with the filesystem.
10 Contact: ocfs2-devel@lists.linux.dev
19 major number and an overlapping minor number - thus,
23 Reading from this file returns a single line, the major
26 This file is read-only. The value is compiled into the
31 Contact: ocfs2-devel@lists.linux.dev
38 * 'o2cb' - The classic o2cb cluster stack that ocfs2 has
40 * 'user' - A plugin supporting userspace cluster software
44 plugins, one per line.
[all …]
/Documentation/devicetree/bindings/regulator/
Dqcom,qca6390-pmu.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/regulator/qcom,qca6390-pmu.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
20 - qcom,qca6390-pmu
21 - qcom,wcn6855-pmu
22 - qcom,wcn7850-pmu
24 vdd-supply:
27 vddaon-supply:
[all …]
/Documentation/admin-guide/nfs/
Dnfsroot.rst10 Updated 2006 by Nico Schottelius <nico-kernel-nfsroot@schottelius.org>
18 In order to use a diskless system, such as an X-terminal or printer server for
19 example, it is necessary for the root filesystem to be present on a non-disk
21 Documentation/filesystems/ramfs-rootfs-initramfs.rst), a ramdisk (see
22 Documentation/admin-guide/initrd.rst) or a filesystem mounted via NFS. The
34 built-in during configuration. Once this has been selected, the nfsroot
44 Kernel command line
49 both the server and the name of the directory on the server to mount as root.
50 This can be established using the following kernel command line parameters:
54 This is necessary to enable the pseudo-NFS-device. Note that it's not a
[all …]
/Documentation/kernel-hacking/
Dfalse-sharing.rst1 .. SPDX-License-Identifier: GPL-2.0
10 coherence of one cache line stored in multiple CPU's caches; then
17 char name[16];
20 Member 'refcount'(A) and 'name'(B) _share_ one cache line like below::
22 +-----------+ +-----------+
24 +-----------+ +-----------+
28 +----------------------+ +----------------------+
30 +----------------------+ +----------------------+
32 ---------------------------+------------------+-----------------------------
34 +----------------------+
[all …]
/Documentation/userspace-api/gpio/
Dgpio-v2-get-lineinfo-ioctl.rst1 .. SPDX-License-Identifier: GPL-2.0
9 Name chapter
12 GPIO_V2_GET_LINEINFO_IOCTL - Get the publicly available information for a line.
29 ``offset`` field set to indicate the line to be collected.
34 Get the publicly available information for a line.
36 This information is available independent of whether the line is in use.
39 The line info does not include the line value.
41 The line must be requested using gpio-v2-get-line-ioctl.rst to access its
49 On error -1 and the ``errno`` variable is set appropriately.
50 Common error codes are described in error-codes.rst.
Dgpio-v2-get-lineinfo-watch-ioctl.rst1 .. SPDX-License-Identifier: GPL-2.0
9 Name chapter
12 GPIO_V2_GET_LINEINFO_WATCH_IOCTL - Enable watching a line for changes to its
30 the ``offset`` set to indicate the line to watch
35 Enable watching a line for changes to its request state and configuration
36 information. Changes to line info include a line being requested, released
40 Watching line info is not generally required, and would typically only be
43 The line info does NOT include the line value.
44 The line must be requested using gpio-v2-get-line-ioctl.rst to access
45 its value, and the line request can monitor a line for events using
[all …]
Dgpio-get-lineinfo-ioctl.rst1 .. SPDX-License-Identifier: GPL-2.0
11 gpio-v2-get-lineinfo-ioctl.rst.
13 Name chapter
16 GPIO_GET_LINEINFO_IOCTL - Get the publicly available information for a line.
33 ``offset`` field set to indicate the line to be collected.
38 Get the publicly available information for a line.
40 This information is available independent of whether the line is in use.
43 The line info does not include the line value.
45 The line must be requested using gpio-get-linehandle-ioctl.rst or
46 gpio-get-lineevent-ioctl.rst to access its value.
[all …]
Dgpio-get-lineinfo-watch-ioctl.rst1 .. SPDX-License-Identifier: GPL-2.0
11 gpio-v2-get-lineinfo-watch-ioctl.rst.
13 Name chapter
16 GPIO_GET_LINEINFO_WATCH_IOCTL - Enable watching a line for changes to its
34 the ``offset`` set to indicate the line to watch
39 Enable watching a line for changes to its request state and configuration
40 information. Changes to line info include a line being requested, released
44 Watching line info is not generally required, and would typically only be
47 The line info does NOT include the line value.
49 The line must be requested using gpio-get-linehandle-ioctl.rst or
[all …]
/Documentation/driver-api/usb/
Dwriting_musb_glue_layer.rst15 Instead, these embedded UDC rely on the USB On-the-Go (OTG)
18 Dual-Role Controller (MUSB HDRC) found in the Mentor Graphics Inventra™
21 As a self-taught exercise I have written an MUSB glue layer for the
28 .. _musb-basics:
33 To get started on the topic, please read USB On-the-Go Basics (see
46 ------------------------
47 | | <------- drivers/usb/gadget
48 | Linux USB Core Stack | <------- drivers/usb/host
49 | | <------- drivers/usb/core
50 ------------------------
[all …]
/Documentation/devicetree/bindings/gnss/
Dbrcm,bcm4751.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Johan Hovold <johan@kernel.org>
11 - Linus Walleij <linus.walleij@linaro.org>
20 - $ref: gnss-common.yaml#
21 - $ref: /schemas/serial/serial-peripheral-props.yaml#
26 - brcm,bcm4751
27 - brcm,bcm4752
28 - brcm,bcm4753
[all …]
/Documentation/driver-api/gpio/
Dboard.rst14 -----------
20 <function>-gpios, where <function> is the function the driver will request
26 led-gpios = <&gpio 15 GPIO_ACTIVE_HIGH>, /* red */
30 power-gpios = <&gpio 1 GPIO_ACTIVE_LOW>;
33 Properties named <function>-gpio are also considered valid and old bindings use
52 the <function>-prefix of the GPIO suffixes ("gpios" or "gpio", automatically
54 "led-gpios" example, use the prefix without the "-" as con_id parameter: "led".
58 (``snprintf(... "%s-%s", con_id, gpio_suffixes[]``).
61 ----
67 Name (_CRS, ResourceTemplate () {
[all …]

12345678910>>...19