Lines Matching full:via
41 differentiate between devices that are presented to the system via one of
42 the conventional ways, e.g. as platform devices via ACPI, and devices that
50 All communication with the SAM EC is handled via the |ssam_controller|
53 connection/relation to that controller. This can be done via the
56 client device and controller (this can also be done separate via
80 The controller may be separately obtained via |ssam_get_controller| and its
81 lifetime be guaranteed via |ssam_controller_get| and |ssam_controller_put|.
91 If a device does not already exist/is not already provided via conventional
92 means, it should be provided as |ssam_device| via the SSAM client device
94 corresponding registry. SSAM devices can also be manually allocated via
95 |ssam_device_alloc|, subsequently to which they have to be added via
96 |ssam_device_add| and eventually removed via |ssam_device_remove|. By
108 via |ssam_client_link|, causing it to unbind before the controller driver
119 driver types. They are represented via |ssam_device_driver| and bind to a
120 |ssam_device| via its UID (:c:type:`struct ssam_device.uid <ssam_device>`)
131 be accessed via the Surface Serial Hub, and virtual ones
140 A driver instance can be registered via |ssam_device_driver_register| and
141 unregistered via |ssam_device_driver_unregister|. For convenience, the
218 * on the stack as opposed to allocation via kzalloc().
236 one of the generator macros, for example via:
254 said function. In this example, the argument is provided via the ``arg``
256 the stack. Thus, if the argument provided via the request is large, these
313 the desired event via |ssam_notifier_register|. The notifier must be
314 unregistered via |ssam_notifier_unregister| once it is not required any
336 Surface Laptop 1 and 2, which are enabled via a registry with target ID 1,