Home
last modified time | relevance | path

Searched full:families (Results 1 – 25 of 197) sorted by relevance

12345678

/Linux-v6.6/Documentation/userspace-api/netlink/
Dgenetlink-legacy.rst4 Netlink specification support for legacy Generic Netlink families
8 required to describe older Generic Netlink families which form
17 New Netlink families should use ``multi-attr`` to define arrays.
18 Older families (e.g. ``genetlink`` control family) attempted to
71 Netlink families should have instead defined this as a flat structure,
83 Modern families use the ``unified`` message ID model, which uses
162 Legacy families can define C structures both to be used as the contents of
248 Legacy families also use ``binary`` attributes to encapsulate C arrays. The
262 New Netlink families should never respond to a DO operation with multiple
Dintro.rst249 about other families (``CTRL_CMD_GETFAMILY``).
255 call would make the kernel respond with information about *all* the families
348 families, selecting the recipient family on message-by-message basis using
443 notifications about registered families. When a new family is added the
527 families may, however, require a larger buffer. 32kB buffer is recommended
549 Families section in Classic Netlink
552 Netlink refers to subsystems as families. This is a remnant of using
553 sockets and the concept of protocol families, which are part of message
557 as "families" making the term very confusing:
563 struct nlmsghdr), yet it also calls its users "Families".
[all …]
Dnetlink-raw.rst4 Netlink specification support for raw Netlink families
8 families such as ``NETLINK_ROUTE`` which use the ``netlink-raw`` protocol
16 multicast IDs used by raw netlink families. See :ref:`classic_netlink` for more
Dspecs.rst35 by new families to the most complex covering all the quirks of the old ones.
40 - ``genetlink`` - most streamlined, should be used by all new families
46 all old genetlink families, strange attribute formats, binary structures etc.
98 allowed for new ``genetlink`` families.
144 In case the definition is shared by multiple families (e.g. ``IFNAMSIZ``)
152 All families have at least one attribute set, most have multiple.
266 Legacy families have special ways of expressing arrays. ``sub-type`` can be
/Linux-v6.6/Documentation/core-api/
Dnetlink.rst15 Older families often define "null" attributes and commands with value
17 but should be avoided in new families. The ``unspec`` enum values are
33 Older families do not reply to all of the commands, especially NEW / ADD
73 New families should use ``per-op`` (default) to be able to narrow down the
84 Accept strings without the null-termination (for legacy families only).
/Linux-v6.6/drivers/pinctrl/intel/
Dpinctrl-tangier.h64 * @families: Array of families this pinctrl handles
65 * @nfamilies: Number of families in the array
80 const struct tng_family *families; member
Dpinctrl-tangier.c74 family = &tp->families[i]; in tng_get_family()
527 struct tng_family *families; in tng_pinctrl_probe() local
545 * Make a copy of the families which we can use to hold pointers in tng_pinctrl_probe()
548 families_len = size_mul(sizeof(*families), tp->nfamilies); in tng_pinctrl_probe()
549 families = devm_kmemdup(dev, tp->families, families_len, GFP_KERNEL); in tng_pinctrl_probe()
550 if (!families) in tng_pinctrl_probe()
555 struct tng_family *family = &families[i]; in tng_pinctrl_probe()
560 tp->families = families; in tng_pinctrl_probe()
/Linux-v6.6/tools/testing/selftests/bpf/prog_tests/
Dcls_redirect.c372 int families[] = { AF_INET, AF_INET6 }; in test_cls_redirect_common() local
377 int servers[__NR_KIND][ARRAY_SIZE(families)] = {}; in test_cls_redirect_common()
378 int conns[__NR_KIND][ARRAY_SIZE(families)] = {}; in test_cls_redirect_common()
379 struct tuple tuples[__NR_KIND][ARRAY_SIZE(families)]; in test_cls_redirect_common()
382 for (i = 0; i < ARRAY_SIZE(families); i++) { in test_cls_redirect_common()
383 slen = prepare_addr(&ss, families[i]); in test_cls_redirect_common()
402 for (j = 0; j < ARRAY_SIZE(families); j++) { in test_cls_redirect_common()
/Linux-v6.6/Documentation/devicetree/bindings/interrupt-controller/
Dintel,ixp4xx-interrupt.yaml19 The distinct IXP4xx families with different interrupt controller
21 families were the only ones to reach the developer and consumer
Daspeed,ast2400-vic.txt4 AST2500 SoC families include a legacy register layout before a re-designed
/Linux-v6.6/Documentation/arch/sh/
Dregister-banks.rst10 The SH-3 and SH-4 CPU families traditionally include a single partial register
11 bank (selected by SR.RB, only r0 ... r7 are banked), whereas other families
/Linux-v6.6/drivers/net/ethernet/smsc/
DKconfig79 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
85 Say Y here if you want support for SMSC LAN911x and LAN921x families
/Linux-v6.6/include/uapi/linux/
Datmbr2684.h51 * This is for the ATM_NEWBACKENDIF call - these are like socket families:
78 * This is for the ATM_SETBACKEND call - these are like socket families:
Datmppp.h16 * This is for the ATM_SETBACKEND call - these are like socket families:
/Linux-v6.6/Documentation/sphinx/
Dkerneldoc-preamble.sty220 due to the lack of suitable font families and/or the texlive-xecjk
223 If you want them, please install ``Noto Sans CJK'' font families
226 Having optional ``Noto Serif CJK'' font families will improve
/Linux-v6.6/net/dsa/
DKconfig96 tristate "Tag driver for Microchip 8795/937x/9477/9893 families of switches"
99 Microchip 8795/937x/9477/9893 families of switches.
/Linux-v6.6/arch/arm/mach-mstar/
DKconfig11 Support for newer MStar/Sigmastar SoC families that are
/Linux-v6.6/arch/arm/mach-ixp4xx/
Dixp4xx-of.c8 * We handle 4 different SoC families. These compatible strings are enough
/Linux-v6.6/Documentation/devicetree/bindings/net/
Dmicrel-ks8995.txt1 Micrel KS8995 SPI controlled Ethernet Switch families
/Linux-v6.6/arch/arm64/
DKconfig.platforms282 bool "Intel's SoCFPGA ARMv8 Families"
284 This enables support for Intel's SoCFPGA ARMv8 families:
/Linux-v6.6/net/atm/
DMakefile3 # Makefile for the ATM Protocol Families.
/Linux-v6.6/Documentation/devicetree/bindings/arm/marvell/
Darmada-8kp.txt4 Boards using a SoC of the Marvell Armada 8KP families must carry
Darmada-370-xp.txt4 Boards with a SoC of the Marvell Armada 370 and Armada XP families
/Linux-v6.6/drivers/nfc/nxp-nci/
DKconfig7 NPC300 (PN548) or PN7150 families.
/Linux-v6.6/drivers/mtd/lpddr/
DKconfig19 families of devices. This serves similar purpose of CFI on legacy

12345678