Home
last modified time | relevance | path

Searched refs:naming (Results 1 – 25 of 116) sorted by relevance

12345

/linux-6.15/Documentation/devicetree/bindings/arm/samsung/
H A Dsamsung-soc.yaml7 title: Samsung S3C, S5P and Exynos SoC compatibles naming convention
30 - description: Preferred naming style for compatibles of SoC components
/linux-6.15/Documentation/devicetree/bindings/soc/renesas/
H A Drenesas-soc.yaml7 title: Renesas SoC compatibles naming convention
38 # Preferred naming style for compatibles of SoC components
/linux-6.15/drivers/comedi/drivers/ni_routing/
H A DREADME100 easier, the naming conventions used in the [board-name].c file are
101 similar to the naming conventions as presented by NI-MAX.
171 Various naming conventions and relations:
173 These are various notes that help to relate the naming conventions used in the
174 NI-STC with those naming conventions used here.
177 Signal sources for most signals-destinations are given a specific naming
/linux-6.15/Documentation/devicetree/bindings/arm/
H A Dqcom-soc.yaml7 title: Qualcomm SoC compatibles naming convention
33 # Preferred naming style for compatibles of SoC components:
/linux-6.15/Documentation/ABI/removed/
H A Ddevfs6 races, contains a naming policy within the kernel that is
/linux-6.15/Documentation/driver-api/tty/
H A Dmoxa-smartio.rst14 3.2 Device naming convention
105 3.2 Device naming convention
110 Device naming when more than 2 boards installed
/linux-6.15/Documentation/filesystems/
H A Dadfs.rst101 file type information, a file naming convention was devised (initially
104 naming convention is now also used by RISC OS emulators such as RPCEmu.
/linux-6.15/Documentation/bpf/libbpf/
H A Dlibbpf_naming_convention.rst3 API naming convention
7 functions and types. Every group has its own naming convention
68 API documentation above. See API naming convention to choose the right
/linux-6.15/fs/sysfs/
H A DKconfig18 delegating policy decisions, like persistently naming devices.
/linux-6.15/Documentation/hwmon/
H A Dpowr1220.rst32 The input naming convention is as follows:
/linux-6.15/Documentation/networking/
H A Dalias.rst19 Alias creation is done by 'magic' interface naming: eg. to create a
/linux-6.15/drivers/gpu/drm/ttm/tests/
H A DTODO11 - Agree on the naming convention
/linux-6.15/Documentation/leds/
H A Duleds.rst23 any valid sysfs device node name, but consider using the LED class naming
/linux-6.15/Documentation/userspace-api/netlink/
H A Dc-code-gen.rst10 to control the naming.
69 If naming is desired ``enum-name`` can be used to specify the name.
/linux-6.15/Documentation/admin-guide/
H A Ddevices.rst36 and can use ``sysfs`` and ``udev`` (``systemd``) to handle the naming needs.
171 naming and use of the various types of TTYs. Note that the naming
262 the System V/Unix98 naming scheme for PTYs, which assigns a common
/linux-6.15/Documentation/devicetree/bindings/mmc/
H A Dsdhci-omap.txt28 DMA specifiers listed in dmas. The string naming is to be "tx"
/linux-6.15/Documentation/virt/coco/
H A Dtdx-guest.rst42 a new IOCTL CMD will be created to handle it. To keep the IOCTL naming
/linux-6.15/Documentation/translations/zh_CN/rust/
H A Dcoding-guidelines.rst178 https://rust-lang.github.io/api-guidelines/naming.html
/linux-6.15/arch/arm64/boot/dts/actions/
H A Ds900-bubblegum-96.dts82 * When the 96Boards naming of a line and the schematic name of
87 * naming has been preferred. This is only for the informational
/linux-6.15/Documentation/arch/x86/
H A Dcpuinfo.rst133 resulting x86_cap/bug_flags[] are used to populate /proc/cpuinfo. The naming
155 constant. If, for some reason, the naming of X86_FEATURE_<name> changes, one
156 shall override the new naming with the name already used in /proc/cpuinfo.
/linux-6.15/Documentation/devicetree/bindings/interrupt-controller/
H A Dbrcm,bcm2835-armctrl-ic.txt6 as "armctrl" in the SoC documentation, hence naming of this binding.
/linux-6.15/drivers/staging/iio/Documentation/
H A Dinkernel.txt56 iio_hwmon where the number and naming of channels is not known by the
/linux-6.15/Documentation/devicetree/bindings/timer/
H A Darm,sp804.yaml69 # consistent naming used in the existing DTs. The primecell binding
/linux-6.15/arch/arm/boot/dts/aspeed/
H A Daspeed-bmc-tyan-s8036.dts376 /* We're following the GPIO naming as defined at
377 * https://github.com/openbmc/docs/blob/master/designs/device-tree-gpio-naming.md.
/linux-6.15/tools/testing/selftests/futex/
H A DREADME53 o FIXME: decide on a sane test naming scheme. Currently the tests are named

12345