Home
last modified time | relevance | path

Searched +full:host +full:- +full:only (Results 1 – 25 of 641) sorted by relevance

12345678910>>...26

/Documentation/virt/kvm/arm/
Dpkvm.rst1 .. SPDX-License-Identifier: GPL-2.0
7 ------------
9 Protected KVM (pKVM) is a KVM/arm64 extension which uses the two-stage
10 translation capability of the Armv8 MMU to isolate guest memory from the host
12 without relying on whizz-bang features in hardware, but still allowing room for
13 complementary technologies such as memory encryption and hardware-backed
18 of the host kernel running at EL1 and therefore additional hypercalls are
19 introduced to manage manipulation of guest stage-2 page tables, creation of VM
21 of this change is that the host itself runs with an identity mapping enabled
22 at stage-2, providing the hypervisor code with a mechanism to restrict host
[all …]
/Documentation/devicetree/bindings/display/
Dmipi-dsi-bus.txt5 communication between a host and up to four peripherals. This document will
8 This document describes DSI bus-specific properties only or defines existing
11 Each DSI host provides a DSI bus. The DSI host controller's node contains a
15 The following assumes that only a single peripheral is connected to a DSI
16 host. Experience shows that this is true for the large majority of setups.
18 DSI host
22 a DSI host, the following properties apply to a node representing a DSI host.
25 - #address-cells: The number of cells required to represent an address on the
26 bus. DSI peripherals are addressed using a 2-bit virtual channel number, so
29 - #size-cells: Should be 0. There are cases where it makes sense to use a
[all …]
/Documentation/i2c/busses/
Di2c-sis630.rst2 Kernel driver i2c-sis630
7 630 chipset (Datasheet: available at http://www.sfr-fresh.com/linux)
13 - Alexander Malysh <amalysh@web.de>
14 - Amaury Decrême <amaury.decreme@gmail.com> - SiS964 support
17 -----------------
25 high_clock = [1|0] Forcibly set Host Master Clock to 56KHz (default,
28 SIS630/730 chip only.
33 -----------
35 This SMBus only driver is known to work on motherboards with the above
40 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 630 Host (rev 31)
[all …]
/Documentation/accel/qaic/
Daic100.rst1 .. SPDX-License-Identifier: GPL-2.0-only
10 The Qualcomm Cloud AI 100/AIC100 family of products (including SA9000P - part of
20 performance. AIC100 cards are multi-user capable and able to execute workloads
26 An AIC100 card consists of an AIC100 SoC, on-card DDR, and a set of misc
30 or a Dual M.2 card. Both use PCIe to connect to the host system.
33 DeviceID(DID) combination to uniquely identify itself to the host. AIC100
39 AIC100 implements MSI but does not implement MSI-X. AIC100 prefers 17 MSIs to
43 As a PCIe device, AIC100 utilizes BARs to provide host interfaces to the device
44 hardware. AIC100 provides 3, 64-bit BARs.
46 * The first BAR is 4K in size, and exposes the MHI interface to the host.
[all …]
/Documentation/nvme/
Dfeature-and-quirk-policy.rst1 .. SPDX-License-Identifier: GPL-2.0
16 The Linux NVMe host driver in drivers/nvme/host/ supports devices
20 - the NVMe Base specification
21 - various Command Set specifications (e.g. NVM Command Set)
22 - various Transport specifications (e.g. PCIe, Fibre Channel, RDMA, TCP)
23 - the NVMe Management Interface specification
31 NVMe is a large suite of specifications, and contains features that are only
32 useful or suitable for specific use-cases. It is important to note that Linux
36 maintainability of the NVMe host driver.
38 Any feature implemented in the Linux NVMe host driver must support the
[all …]
/Documentation/devicetree/bindings/mmc/
Dsocionext,uniphier-sd.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mmc/socionext,uniphier-sd.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Masahiro Yamada <yamada.masahiro@socionext.com>
16 - socionext,uniphier-sd-v2.91
17 - socionext,uniphier-sd-v3.1
18 - socionext,uniphier-sd-v3.1.1
32 dma-names:
33 const: rx-tx
[all …]
/Documentation/ABI/testing/
Dsysfs-bus-pci-drivers-xhci_hcd5 xHCI compatible USB host controllers (i.e. super-speed
9 the equivalent of a very high performance full-duplex
12 The DbC debug device shares a root port with xHCI host.
34 Value can only be changed while debug capability (DbC) is in
36 connected to a USB host.
38 It can be any 16-bit integer.
47 Value can only be changed while debug capability (DbC) is in
49 connected to a USB host.
50 The default value is 0x0010. It can be any 16-bit integer.
59 Value can only be changed while debug capability (DbC) is in
[all …]
/Documentation/driver-api/
Dxillybus.rst10 - Introduction
11 -- Background
12 -- Xillybus Overview
14 - Usage
15 -- User interface
16 -- Synchronization
17 -- Seekable pipes
19 - Internals
20 -- Source code organization
21 -- Pipe attributes
[all …]
/Documentation/scsi/
Dtcm_qla2xxx.rst1 .. SPDX-License-Identifier: GPL-2.0
8 ------------------------------
14 This attribute and accompanying code is only included if the
20 selected host.
25 Setting a boolean of 1 for the jam_host attribute for a particular host
26 will discard the commands for that host.
30 Enable host 4 to be jammed::
34 Disable jamming on host 4::
DBusLogic.rst1 .. SPDX-License-Identifier: GPL-2.0
21 Copyright 1995-1998 by Leonard N. Zubkoff <lnz@dandelion.com>
28 host adapters which share a common programming interface across a diverse
34 This driver supports all present BusLogic MultiMaster Host Adapters, and should
36 recently, BusLogic introduced the FlashPoint Host Adapters, which are less
37 costly and rely on the host CPU, rather than including an onboard processor.
38 Despite not having an onboard CPU, the FlashPoint Host Adapters perform very
42 is the library of code that runs on the host CPU and performs functions
43 analogous to the firmware on the MultiMaster Host Adapters. Thanks to their
44 having provided the SCCB Manager, this driver now supports the FlashPoint Host
[all …]
Dhpsa.rst1 .. SPDX-License-Identifier: GPL-2.0
4 HPSA - Hewlett Packard Smart Array driver
12 "split-brained" design of the cciss driver is a source of excess
19 - Smart Array P212
20 - Smart Array P410
21 - Smart Array P410i
22 - Smart Array P411
23 - Smart Array P812
24 - Smart Array P712m
25 - Smart Array P711m
[all …]
DFlashPoint.rst1 .. SPDX-License-Identifier: GPL-2.0
7 The BusLogic FlashPoint SCSI Host Adapters are now fully supported on Linux.
14 BUSLOGIC FLASHPOINT LINE OF SCSI HOST ADAPTERS
17 FREMONT, CA, -- October 8, 1996 -- Mylex Corporation has expanded Linux
19 host adapters. All of BusLogic's other SCSI host adapters, including the
26 development and provided technical support for our host adapters for several
33 Linux is a freely-distributed implementation of UNIX for Intel x86, Sun
39 FlashPoint Host Adapters
42 The FlashPoint family of Ultra SCSI host adapters, designed for workstation
56 BusLogic line of Ultra SCSI host adapter products, Mylex provides enabling
[all …]
/Documentation/devicetree/bindings/w1/
Damd,axi-1wire-host.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/w1/amd,axi-1wire-host.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: AMD AXI 1-wire bus host for programmable logic
10 - Kris Chaplin <kris.chaplin@amd.com>
14 const: amd,axi-1wire-host
26 - compatible
27 - reg
28 - clocks
[all …]
/Documentation/driver-api/cxl/
Dmemory-devices.rst1 .. SPDX-License-Identifier: GPL-2.0
12 Address space is handled via HDM (Host Managed Device Memory) decoders
14 range across multiple devices underneath a host-bridge or interleaved
15 across host-bridges.
25 multiple Host Bridges and endpoints while another may opt for fault tolerance
30 dictates which endpoints can participate in which Host Bridge decode regimes.
33 given range only decodes to 1 one Host Bridge, but that Host Bridge may in turn
39 module generates an emulated CXL topology of 2 Host Bridges each with 2 Root
40 Ports. Each of those Root Ports are connected to 2-way switches with endpoints
43 # cxl list -BEMPu -b cxl_test
[all …]
/Documentation/driver-api/usb/
Dgadget.rst11 This document presents a Linux-USB "Gadget" kernel mode API, for use
17 - Supports USB 2.0, for high speed devices which can stream data at
20 - Handles devices with dozens of endpoints just as well as ones with
21 just two fixed-function ones. Gadget drivers can be written so
24 - Flexible enough to expose more complex USB device capabilities such
28 - USB "On-The-Go" (OTG) support, in conjunction with updates to the
29 Linux-USB host side.
31 - Sharing data structures and API models with the Linux-USB host side
32 API. This helps the OTG support, and looks forward to more-symmetric
33 frameworks (where the same I/O model is used by both host and device
[all …]
/Documentation/PCI/
Dacpi-info.rst1 .. SPDX-License-Identifier: GPL-2.0
4 ACPI considerations for PCI host bridges
11 host bridges, so the ACPI namespace must describe each host bridge, the
13 the host bridge forwards to PCI (using _CRS), and the routing of legacy
16 PCI devices, which are below the host bridge, generally do not need to be
39 If the OS is expected to manage a non-discoverable device described via
44 PCI host bridges are PNP0A03 or PNP0A08 devices. Their _CRS should
46 they forward down to the PCI bus, as well as registers of the host bridge
47 itself that are not forwarded to PCI. The host bridge registers include
50 These are all device-specific, non-architected things, so the only way a
[all …]
/Documentation/devicetree/bindings/phy/
Dmarvell,armada-3700-utmi-phy.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/phy/marvell,armada-3700-utmi-phy.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Miquel Raynal <miquel.raynal@bootlin.com>
16 compliant and only supports host mode. Both of these controllers come with
22 - marvell,a3700-utmi-host-phy
23 - marvell,a3700-utmi-otg-phy
27 "#phy-cells":
30 marvell,usb-misc-reg:
[all …]
/Documentation/devicetree/bindings/pci/
Dhost-generic-pci.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/host-generic-pci.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic PCI host controller
10 - Will Deacon <will@kernel.org>
13 Firmware-initialised PCI host controllers and PCI emulations, such as the
14 virtio-pci implementations found in kvmtool and other para-virtualised
21 Configuration Space is assumed to be memory-mapped (as opposed to being
26 For CAM, this 24-bit offset is:
[all …]
Dpci.txt3 PCI Bus Binding to: IEEE Std 1275-1994
4 https://www.devicetree.org/open-firmware/bindings/pci/pci2_1.pdf
9 https://www.devicetree.org/open-firmware/practice/imap/imap0_9d.pdf
11 Additionally to the properties specified in the above standards a host bridge
14 - linux,pci-domain:
15 If present this property assigns a fixed PCI domain number to a host bridge,
18 host bridges in the system, otherwise potentially conflicting domain numbers
19 may be assigned to root buses behind different host bridges. The domain
20 number for each host bridge in the system must be unique.
21 - max-link-speed:
[all …]
Dti,j721e-pci-host.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
2 # Copyright (C) 2019 Texas Instruments Incorporated - http://www.ti.com/
4 ---
5 $id: http://devicetree.org/schemas/pci/ti,j721e-pci-host.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: TI J721E PCI Host (PCIe Wrapper)
11 - Kishon Vijay Abraham I <kishon@ti.com>
16 - const: ti,j721e-pcie-host
17 - const: ti,j784s4-pcie-host
18 - description: PCIe controller in AM64
[all …]
Dplda,xpressrich3-axi-common.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/plda,xpressrich3-axi-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: PLDA XpressRICH PCIe host common properties
10 - Daire McNamara <daire.mcnamara@microchip.com>
11 - Kevin Xie <kevin.xie@starfivetech.com>
14 Generic PLDA XpressRICH PCIe host common properties.
17 - $ref: /schemas/pci/pci-host-bridge.yaml#
23 reg-names:
[all …]
/Documentation/mhi/
Dmhi.rst1 .. SPDX-License-Identifier: GPL-2.0
4 MHI (Modem Host Interface)
13 by the host processors to control and communicate with modem devices over high
26 ----
29 which are mapped to the host memory space by the peripheral buses like PCIe.
34 MHI BHI registers: BHI (Boot Host Interface) registers are used by the host
37 Channel Doorbell array: Channel Doorbell (DB) registers used by the host to
41 (DB) registers are used by the host to notify the device when new events are
45 debugging information like performance, functional, and stability to the host.
48 ---------------
[all …]
/Documentation/devicetree/bindings/usb/
Dnxp,isp1760.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Siewior <bigeasy@linutronix.de>
11 - Laurent Pinchart <laurent.pinchart@ideasonboard.com>
20 - nxp,usb-isp1760
21 - nxp,usb-isp1761
22 - nxp,usb-isp1763
29 - description: Host controller interrupt
30 - description: Device controller interrupt in isp1761
[all …]
/Documentation/virt/hyperv/
Dvmbus.rst1 .. SPDX-License-Identifier: GPL-2.0
5 VMBus is a software construct provided by Hyper-V to guest VMs. It
7 devices that Hyper-V presents to guest VMs. The control path is
11 and the synthetic device implementation that is part of Hyper-V, and
12 signaling primitives to allow Hyper-V and the guest to interrupt
17 establishes the VMBus control path with the Hyper-V host, then
21 Most synthetic devices offered by Hyper-V have a corresponding Linux
29 * PCI device pass-thru
34 * Key/Value Pair (KVP) exchange with Hyper-V
35 * Hyper-V online backup (a.k.a. VSS)
[all …]
/Documentation/admin-guide/
Dthunderbolt.rst1 .. SPDX-License-Identifier: GPL-2.0
8 manager is an entity running on the host router (host controller)
21 the software connection manager only supports ``user`` security level and
25 -----------------------------------
27 should be a userspace tool that handles all the low-level details, keeps
31 found in ``Documentation/ABI/testing/sysfs-bus-thunderbolt``.
35 ``/etc/udev/rules.d/99-local.rules``::
46 be DMA masters and thus read contents of the host memory without CPU and OS
76 typically called *Display Port Only*.
89 the Thunderbolt domain the host controller manages. There is typically
[all …]

12345678910>>...26