| /linux-6.6.21/drivers/power/supply/ |
| D | surface_charger.c | 47 struct ssam_event_registry registry; member
175 struct ssam_event_registry registry, const char *name) in spwr_ac_init() argument
184 ac->notif.event.reg = registry; in spwr_ac_init()
244 spwr_ac_init(ac, sdev, p->registry, p->name); in surface_ac_probe()
259 .registry = SSAM_EVENT_REGISTRY_SAM,
|
| D | surface_battery.c | 116 struct ssam_event_registry registry; member
722 struct ssam_event_registry registry, const char *name) in spwr_battery_init() argument
731 bat->notif.event.reg = registry; in spwr_battery_init()
830 spwr_battery_init(bat, sdev, p->registry, p->name); in surface_battery_probe()
846 .registry = SSAM_EVENT_REGISTRY_SAM,
851 .registry = SSAM_EVENT_REGISTRY_KIP,
|
| /linux-6.6.21/Documentation/driver-api/surface_aggregator/ |
| D | client.rst | 96 corresponding registry. SSAM devices can also be manually allocated via
322 in case an event has been received, the registry specifying how the event
324 optionally and depending on the registry used, for which instance ID events
326 events. If the specific registry does not enable events by instance ID, the
335 notifier IDs (in case of target ID, the target ID of the registry), by
338 In general, the target ID of the registry is also the target ID of the
340 Surface Laptop 1 and 2, which are enabled via a registry with target ID 1,
368 /* Specify event registry, i.e. how events get enabled/disabled. */
391 specific event (combination of registry, event target category, and event
|
| D | internal.rst | 484 event registry, i.e. the governing authority of this event (so to speak),
486 target category and, depending on the event registry, instance ID of the
488 zero if the registry does not use it. Together, target category and instance
490 registry and event ID, are required to uniquely identify a respective class
506 registry and ID as key (there is no known list of valid event registry and
526 event registry and event ID to the command data (target ID, target category,
534 target ID (provided via the event registry) and instance ID (provided via
|
| D | overview.rst | 40 harder to discover and requiring us to hard-code a sort of device registry.
|
| /linux-6.6.21/drivers/platform/surface/ |
| D | Kconfig | 109 Device-registry for Surface System Aggregator Module (SSAM) devices.
111 Provides a module and driver which act as a device-registry for SSAM
113 Such devices are instead provided and managed via this registry.
115 Devices provided via this registry are:
|
| /linux-6.6.21/drivers/net/ethernet/broadcom/bnx2x/ |
| D | bnx2x_sp.c | 2782 if (o->registry.aprox_match.vec[i]) in bnx2x_mcast_get_next_bin()
2785 if (BIT_VEC64_TEST_BIT(o->registry.aprox_match. in bnx2x_mcast_get_next_bin()
2809 BIT_VEC64_CLEAR_BIT(o->registry.aprox_match.vec, cur_bit); in bnx2x_mcast_clear_first_bin()
2852 BIT_VEC64_SET_BIT(o->registry.aprox_match.vec, bin); in bnx2x_mcast_set_one_rule_e2()
2871 BIT_VEC64_SET_BIT(o->registry.aprox_match.vec, bin); in bnx2x_mcast_set_one_rule_e2()
2876 BIT_VEC64_CLEAR_BIT(o->registry.aprox_match.vec, bin); in bnx2x_mcast_set_one_rule_e2()
3026 memcpy(cur, o->registry.aprox_match.vec, in bnx2x_mcast_hdl_pending_set_e2_convert()
3363 elem = o->registry.aprox_match.vec[i]; in bnx2x_mcast_refresh_registry_e2()
3504 BIT_VEC64_SET_BIT(o->registry.aprox_match.vec, in bnx2x_mcast_hdl_add_e1h()
3554 memset(o->registry.aprox_match.vec, 0, in bnx2x_mcast_setup_e1h()
[all …]
|
| D | bnx2x_sp.h | 572 } registry; member
|
| /linux-6.6.21/Documentation/usb/ |
| D | linux.inf | 50 ; Optional registry settings. You can modify as needed.
|
| /linux-6.6.21/Documentation/gpu/rfc/ |
| D | i915_scheduler.rst | 85 * https://www.khronos.org/registry/EGL/extensions/IMG/EGL_IMG_context_priority.txt
86 * https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap5.html#devsandqueues-priori…
|
| /linux-6.6.21/Documentation/process/ |
| D | magic-number.rst | 6 This file is a registry of magic numbers which are in use. When you
|
| D | email-clients.rst | 323 to bring up the thunderbird's registry editor.
|
| /linux-6.6.21/Documentation/scsi/ |
| D | megaraid.rst | 60 module acts as a registry for low level hba drivers. The low level drivers
|
| /linux-6.6.21/Documentation/arch/arm64/ |
| D | silicon-errata.rst | 45 file acts as a registry of software workarounds in the Linux Kernel and
|
| D | arm-acpi.rst | 309 wide registry that maintains a list of names, minimizing re-use; (3)
310 there is also no registry for the definition of property values ("value0"),
353 within the registry. This may require iteration. The UEFI Forum, though,
|
| /linux-6.6.21/drivers/staging/rtl8723bs/core/ |
| D | rtw_xmit.c | 1992 struct registry_priv *registry = &adapter->registrypriv; in xmitframe_hiq_filter() local
1994 if (registry->hiq_filter == RTW_HIQ_FILTER_ALLOW_SPECIAL) { in xmitframe_hiq_filter()
2003 } else if (registry->hiq_filter == RTW_HIQ_FILTER_ALLOW_ALL) in xmitframe_hiq_filter()
2005 else if (registry->hiq_filter == RTW_HIQ_FILTER_DENY_ALL) { in xmitframe_hiq_filter()
|
| /linux-6.6.21/Documentation/admin-guide/ |
| D | unicode.rst | 175 Since the assignment of the Klingon Linux Unicode block, a registry of
|
| D | devices.rst | 6 This list is the Linux Device List, the official registry of allocated
|
| /linux-6.6.21/Documentation/admin-guide/blockdev/ |
| D | paride.rst | 57 to kernel libata subsystem, registry and some common methods for accessing
|
| /linux-6.6.21/lib/ |
| D | Kconfig | 646 Enable fast lookup object identifier registry.
|
| /linux-6.6.21/Documentation/gpu/ |
| D | drm-uapi.rst | 266 .. _GL_KHR_robustness: https://www.khronos.org/registry/OpenGL/extensions/KHR/KHR_robustness.txt
|
| /linux-6.6.21/Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 278 .. kernel-figure:: TreeRCU-callback-registry.svg
|
| /linux-6.6.21/Documentation/admin-guide/cifs/ |
| D | usage.rst | 264 the Server's registry. Samba starting with version 3.10 will allow such
|