Home
last modified time | relevance | path

Searched refs:SAM (Results 1 – 25 of 26) sorted by relevance

12

/openbmc/linux/Documentation/driver-api/surface_aggregator/
H A Doverview.rst7 The Surface/System Aggregator Module (SAM, SSAM) is an (arguably *the*)
17 Not much is currently known about SAM on 4th generation devices (Surface Pro
20 Book 2, Surface Laptop 1) and later generation devices, SAM is responsible
36 SAN), translating ACPI generic serial bus write-/read-accesses to SAM
38 devices require a driver hooking directly into the SAM interface. Equally,
54 needed, we differentiate between both types of SAM by referring to them as
55 SAM-over-SSH and SAM-over-HID.
57 Currently, this subsystem only supports SAM-over-SSH. The SSH communication
67 communication interface for SAM on 5th- and all later-generation Surface
H A Dclient.rst52 All communication with the SAM EC is handled via the |ssam_controller|
131 differentiate between physical SAM devices
135 hubs, that have no real representation on the SAM EC and are solely used on
138 used to access the physical SAM device. In addition, ``function`` references
139 a specific device functionality, but has no meaning to the SAM EC. The
165 that the caller provides an argument to the SAM EC and receives a response.
169 Care must be taken to ensure that any command payload data passed to the SAM
191 * they do not correspond to an actual SAM/EC request.
314 To receive events from the SAM EC, an event notifier must be registered for
H A Dssh.rst26 embedded Surface Aggregator Module controller (SAM or EC), found on newer
28 SAM-over-SSH, as opposed to SAM-over-HID for the older generations.
30 On Surface devices with SAM-over-SSH, SAM is connected to the host via UART
32 significant functionality is provided via SAM, including access to battery
35 through SAM, on the Surface Laptop 3 and Surface Book 3 this also includes
H A Dinternal.rst81 ``RQID``). This layer basically provides a fundamental interface to the SAM
/openbmc/linux/drivers/platform/surface/aggregator/
H A DKconfig10 The Surface System Aggregator Module (Surface SAM or SSAM) is an
24 This option controls whether the Surface SAM subsystem core will be
34 Note: While 4th-generation Surface devices also make use of a SAM EC,
37 devices using SAM-over-SSH are supported, whereas devices using
38 SAM-over-HID, which is used on the 4th generation, are currently not
41 Choose m if you want to build the SAM subsystem core and SSH driver as
/openbmc/linux/Documentation/ABI/stable/
H A Dsysfs-bus-firewire123 in SAM-2...SAM-4 annex A. They are persistent and world-wide
134 a somewhat shorter format which was not as close to SAM.
/openbmc/linux/drivers/platform/surface/
H A Dsurface_aggregator_hub.c351 { SSAM_VDEV(HUB, SAM, SSAM_SSH_TC_KIP, 0x00), (unsigned long)&kip_hub },
352 { SSAM_VDEV(HUB, SAM, SSAM_SSH_TC_BAS, 0x00), (unsigned long)&base_hub },
H A Dsurface_platform_profile.c171 { SSAM_SDEV(TMP, SAM, 0x00, 0x01) },
H A Dsurface_aggregator_tabletsw.c625 { SSAM_SDEV(KIP, SAM, 0x00, 0x01), (unsigned long)&ssam_kip_sw_desc },
626 { SSAM_SDEV(POS, SAM, 0x00, 0x01), (unsigned long)&ssam_pos_sw_desc },
H A DKconfig213 (SSAM) connected via the Surface Serial Hub (SSH / SAM-over-SSH). In
H A Dsurface_dtx.c1217 { SSAM_SDEV(BAS, SAM, 0x00, 0x00) },
/openbmc/openbmc/poky/meta/files/common-licenses/
H A Dlibtiff8 IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT O…
/openbmc/linux/Documentation/driver-api/surface_aggregator/clients/
H A Dcdev.rst13 the SAM EC. It is intended to be used for development and debugging, and
79 - Perform synchronous SAM request.
111 Executes a synchronous SAM request. The request specification is passed in
H A Dsan.rst12 SAM controller. Specifically, ACPI code can execute requests and handle
/openbmc/u-boot/doc/
H A DREADME.atmel_pmecc34 The usual way to program SPL into NAND flash is to use the SAM-BA Atmel tool.
H A DREADME.console4 * Paolo Scaffardi, AIRVENT SAM s.p.a - RIMINI(ITALY), arsenio@tin.it
H A DREADME.video4 * Paolo Scaffardi, AIRVENT SAM s.p.a - RIMINI(ITALY), arsenio@tin.it
/openbmc/linux/drivers/power/supply/
H A Dsurface_charger.c263 { SSAM_SDEV(BAT, SAM, 0x01, 0x01), (unsigned long)&spwr_psy_props_adp1 },
H A Dsurface_battery.c855 { SSAM_SDEV(BAT, SAM, 0x01, 0x00), (unsigned long)&spwr_psy_props_bat1 },
/openbmc/linux/Documentation/devicetree/bindings/mips/cavium/
H A Dbootbus.txt64 - cavium,sam-mode: Optional. If present, SAM mode is selected.
/openbmc/linux/Documentation/scsi/
H A Dlibsas.rst10 SAM/SPC issues, and a SAS LLDD+sequencer is concerned with
205 Management Functions (TMFs) described in SAM::
215 For more information please read SAM from T10.org.
H A Dufs.rst56 SAM-5 architectural model.
H A Dscsi_mid_low_api.rst14 (SCSI terminology, see SAM-3 at http://www.t10.org) sends SCSI commands
1240 Autosense (or auto-sense) is defined in the SAM-2 document as "the
/openbmc/linux/arch/arm/mach-at91/
H A DKconfig14 bool "SAM Cortex-M7 family" if ARM_SINGLE_ARMV7M
/openbmc/linux/Documentation/arch/arm/
H A Dmicrochip.rst196 …http://ww1.microchip.com/downloads/en/DeviceDoc/SAM-E70-S70-V70-V71-Family-Data-Sheet-DS60001527D.…

12