| /linux-6.6.21/drivers/pinctrl/intel/ |
| D | pinctrl-tangier.c | 74 family = &tp->families[i]; in tng_get_family()
527 struct tng_family *families; in tng_pinctrl_probe() local
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()
|
| D | pinctrl-tangier.h | 80 const struct tng_family *families; member
|
| /linux-6.6.21/Documentation/userspace-api/netlink/ |
| D | netlink-raw.rst | 4 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
|
| D | genetlink-legacy.rst | 4 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
|
| D | intro.rst | 249 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
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:
568 happily allocate to one of its families as well).
594 This is no longer the case for new Generic Netlink families and those opting
[all …]
|
| D | specs.rst | 35 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-6.6.21/Documentation/core-api/ |
| D | netlink.rst | 15 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-6.6.21/tools/testing/selftests/bpf/prog_tests/ |
| D | cls_redirect.c | 372 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-6.6.21/Documentation/devicetree/bindings/interrupt-controller/ |
| D | intel,ixp4xx-interrupt.yaml | 19 The distinct IXP4xx families with different interrupt controller
21 families were the only ones to reach the developer and consumer
|
| D | aspeed,ast2400-vic.txt | 4 AST2500 SoC families include a legacy register layout before a re-designed
|
| /linux-6.6.21/Documentation/arch/sh/ |
| D | register-banks.rst | 10 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-6.6.21/Documentation/devicetree/bindings/net/ |
| D | micrel-ks8995.txt | 1 Micrel KS8995 SPI controlled Ethernet Switch families
|
| /linux-6.6.21/Documentation/devicetree/bindings/arm/marvell/ |
| D | armada-8kp.txt | 4 Boards using a SoC of the Marvell Armada 8KP families must carry
|
| D | 98dx3236.txt | 4 Boards with a SoC of the Marvell 98DX3236, 98DX3336 and 98DX4251 families
|
| D | armada-370-xp.txt | 4 Boards with a SoC of the Marvell Armada 370 and Armada XP families
|
| /linux-6.6.21/arch/arm/mach-mstar/ |
| D | Kconfig | 11 Support for newer MStar/Sigmastar SoC families that are
|
| /linux-6.6.21/Documentation/devicetree/bindings/iio/dac/ |
| D | adi,ad5764.yaml | 7 title: Analog Devices AD5744 and AD5764 DAC families
|
| /linux-6.6.21/Documentation/arch/arm/sti/ |
| D | overview.rst | 21 All the files for multiple machine families (STiH407, STiH410, and STiH418)
|
| /linux-6.6.21/Documentation/arch/arm/stm32/ |
| D | overview.rst | 23 All the files for multiple machine families are located in the platform code
|
| /linux-6.6.21/drivers/nfc/nxp-nci/ |
| D | Kconfig | 7 NPC300 (PN548) or PN7150 families.
|
| /linux-6.6.21/drivers/mtd/lpddr/ |
| D | Kconfig | 19 families of devices. This serves similar purpose of CFI on legacy
|
| /linux-6.6.21/Documentation/devicetree/bindings/arm/keystone/ |
| D | keystone.txt | 12 SoC families:
|
| /linux-6.6.21/drivers/net/ethernet/smsc/ |
| D | Kconfig | 79 tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
85 Say Y here if you want support for SMSC LAN911x and LAN921x families
|
| /linux-6.6.21/drivers/net/wireless/ti/wlcore/ |
| D | Kconfig | 8 hardware-specific differences among different chipset families.
|
| /linux-6.6.21/Documentation/devicetree/bindings/memory-controllers/ |
| D | qca,ath79-ddr-controller.yaml | 13 The DDR controller of the AR7xxx and AR9xxx families provides an interface to
|