Lines Matching full:via

43 differentiate between devices that are presented to the system via one of
44 the conventional ways, e.g. as platform devices via ACPI, and devices that
52 All communication with the SAM EC is handled via the |ssam_controller|
55 connection/relation to that controller. This can be done via the
58 client device and controller (this can also be done separate via
82 The controller may be separately obtained via |ssam_get_controller| and its
83 lifetime be guaranteed via |ssam_controller_get| and |ssam_controller_put|.
93 If a device does not already exist/is not already provided via conventional
94 means, it should be provided as |ssam_device| via the SSAM client device
96 corresponding registry. SSAM devices can also be manually allocated via
97 |ssam_device_alloc|, subsequently to which they have to be added via
98 |ssam_device_add| and eventually removed via |ssam_device_remove|. By
110 via |ssam_client_link|, causing it to unbind before the controller driver
121 driver types. They are represented via |ssam_device_driver| and bind to a
122 |ssam_device| via its UID (:c:type:`struct ssam_device.uid <ssam_device>`)
133 be accessed via the Surface Serial Hub, and virtual ones
142 A driver instance can be registered via |ssam_device_driver_register| and
143 unregistered via |ssam_device_driver_unregister|. For convenience, the
220             * on the stack as opposed to allocation via kzalloc().
238 one of the generator macros, for example via:
256 said function. In this example, the argument is provided via the ``arg``
258 the stack. Thus, if the argument provided via the request is large, these
315 the desired event via |ssam_notifier_register|. The notifier must be
316 unregistered via |ssam_notifier_unregister| once it is not required any
340 Surface Laptop 1 and 2, which are enabled via a registry with target ID 1,