Home
last modified time | relevance | path

Searched full:companion (Results 1 – 25 of 203) sorted by relevance

123456789

/linux/Documentation/ABI/testing/
H A Dsysfs-bus-pci-drivers-ehci_hcd1 What: /sys/bus/pci/drivers/ehci_hcd/.../companion
2 /sys/bus/usb/devices/usbN/../companion
9 "companion" full/low-speed USB-1.1 controllers. When a
12 is plugged in, the connection is routed to the companion
17 connection to be routed to the companion controller.
20 companion controller, and writing the negative of a port
26 echo 4 >/sys/bus/usb/devices/usb2/../companion
30 echo -4 >/sys/bus/usb/devices/usb2/../companion
33 to the companion controller.
/linux/drivers/usb/host/
H A Dehci-sysfs.c9 /* Display the ports dedicated to the companion controller */
33 * Dedicate or undedicate a port to the companion controller.
45 new_owner = PORT_OWNER; /* Owned by companion */ in companion_store()
62 static DEVICE_ATTR_RW(companion);
154 /* with integrated TT there is no companion! */ in create_sysfs_files()
169 /* with integrated TT there is no companion! */ in remove_sysfs_files()
H A Dehci-hub.c30 /* After a power loss, ports that were owned by the companion must be
31 * reset so that the companion can still own them.
46 * suspends. If we ensure that none of our companion's devices have in ehci_handover_companion_ports()
75 /* Port already owned by companion? */ in ehci_handover_companion_ports()
105 /* The companion should now own the port, in ehci_handover_companion_ports()
590 ehci_dbg (ehci, "port %d full speed --> companion\n", in check_reset_complete()
671 * high-speed device is switched over to the companion in ehci_hub_status_data()
787 * companion controller, hub_wq needs to be able to clear in ehci_hub_control()
968 /* transfer dedicated ports to the companion hc */ in ehci_hub_control()
974 ehci_dbg(ehci, "port %d --> companion\n", wIndex + 1); in ehci_hub_control()
[all …]
/linux/drivers/clk/ti/
H A Dclkt_dflt.c30 * CM module register offsets, used for calculating the companion
114 * omap2_clk_dflt_find_companion - find companion clock to @clk
115 * @clk: struct clk * to find the companion clock of
116 * @other_reg: void __iomem ** to return the companion clock CM_*CLKEN va in
117 * @other_bit: u8 ** to return the companion clock bit shift in
126 * Some clocks don't have companion clocks. For example, modules with
127 * only an interface clock (such as MAILBOXES) don't have a companion
129 * in the correct companion register that indicates that the
130 * nonexistent 'companion clock' is active. Future patches will
H A Dclk-3xxx.c158 * am35xx_clk_find_companion - find companion clock to @clk
159 * @clk: struct clk * to find the companion clock of
160 * @other_reg: void __iomem ** to return the companion clock CM_*CLKEN va in
161 * @other_bit: u8 ** to return the companion clock bit shift in
163 * Some clocks don't have companion clocks. For example, modules with
164 * only an interface clock (such as HECC) don't have a companion
166 * in the correct companion register that indicates that the
167 * nonexistent 'companion clock' is active. Future patches will
/linux/drivers/mfd/
H A D88pm80x.c102 * second chip is probed, just point to the companion to each in pm80x_init()
109 chip->companion = g_pm80x_chip->client; in pm80x_init()
110 g_pm80x_chip->companion = chip->client; in pm80x_init()
123 if (g_pm80x_chip->companion) in pm80x_deinit()
124 g_pm80x_chip->companion = NULL; in pm80x_deinit()
H A D88pm860x-core.c470 i2c = (chip->id == CHIP_PM8607) ? chip->client : chip->companion; in pm860x_irq()
499 i2c = (chip->id == CHIP_PM8607) ? chip->client : chip->companion; in pm860x_irq_sync_unlock()
571 chip->client : chip->companion; in device_irq_init()
656 chip->client : chip->companion; in pm8606_osc_enable()
697 chip->client : chip->companion; in pm8606_osc_disable()
1068 if (chip->companion) { in pm860x_device_init()
1071 device_8606_init(chip, chip->companion, pdata); in pm860x_device_init()
1074 device_8607_init(chip, chip->companion, pdata); in pm860x_device_init()
1171 * Both client and companion client shares same platform driver. in pm860x_probe()
1173 * pdata->companion_addr is only assigned if companion chip exists. in pm860x_probe()
[all …]
/linux/arch/sh/cchips/
H A DKconfig2 menu "Companion Chips"
13 bool "Hitachi HD64461 companion chip support"
43 via the HD64461 companion chip.
/linux/drivers/input/mouse/
H A Dpsmouse-smbus.c75 "Marking SMBus companion %s as gone\n", in psmouse_smbus_detach_i2c_client()
137 dev_dbg(&rwork->client->dev, "destroying SMBus companion device\n"); in psmouse_smbus_remove_i2c_device()
144 * This schedules removal of SMBus companion device. We have to do
180 "posting removal request for SMBus companion %s\n", in psmouse_smbus_disconnect()
270 /* We have our companion device */ in psmouse_smbus_init()
275 "failed to set up link with iSMBus companion %s\n", in psmouse_smbus_init()
/linux/Documentation/devicetree/bindings/display/bridge/
H A Drenesas,lvds.yaml71 renesas,companion:
74 phandle to the companion LVDS encoder. This property is mandatory
76 point to the second encoder to be used as a companion in dual-link mode.
136 renesas,companion: false
185 renesas,companion = <&lvds1>;
H A Dfsl,imx8qxp-ldb.yaml63 fsl,companion-ldb:
66 A phandle which points to companion LDB which is used in LDB split mode.
126 fsl,companion-ldb: false
H A Dfsl,imx8qxp-pxl2dpi.yaml34 fsl,companion-pxl2dpi:
37 A phandle which points to companion PXL2DPI which is used by downstream
/linux/include/linux/usb/
H A Dphy_companion.h3 * phy-companion.h -- phy companion to indicate the comparator part of PHY
/linux/Documentation/devicetree/bindings/mfd/
H A Dmaxim,max14577.yaml7 title: Maxim MAX14577/MAX77836 MicroUSB and Companion Power Management IC
16 The Maxim MAX14577 is a MicroUSB and Companion Power Management IC which
19 The Maxim MAX77836 is a MicroUSB and Companion Power Management IC which
H A Dmaxim,max77843.yaml7 title: Maxim MAX77843 MicroUSB and Companion Power Management IC
16 The Maxim MAX77843 is a MicroUSB and Companion Power Management IC which
/linux/Documentation/devicetree/bindings/phy/
H A Dnvidia,tegra194-xusb-padctl.yaml40 for the USB signal, the VBUS power supply, the USB 2.0 companion port for
397 nvidia,usb2-companion:
430 nvidia,usb2-companion:
463 nvidia,usb2-companion:
496 nvidia,usb2-companion:
615 nvidia,usb2-companion = <1>;
629 nvidia,usb2-companion = <3>;
H A Dnvidia,tegra210-xusb-padctl.yaml40 for the USB signal, the VBUS power supply, the USB 2.0 companion port for
529 nvidia,usb2-companion:
550 nvidia,usb2-companion:
571 nvidia,usb2-companion:
592 nvidia,usb2-companion:
771 nvidia,usb2-companion = <1>;
775 nvidia,usb2-companion = <2>;
H A Dnvidia,tegra186-xusb-padctl.yaml40 for the USB signal, the VBUS power supply, the USB 2.0 companion port for
360 nvidia,usb2-companion:
381 nvidia,usb2-companion:
402 nvidia,usb2-companion:
533 nvidia,usb2-companion = <1>;
H A Dnvidia,tegra124-xusb-padctl.yaml40 for the USB signal, the VBUS power supply, the USB 2.0 companion port for
474 nvidia,usb2-companion:
495 nvidia,usb2-companion:
647 nvidia,usb2-companion = <2>;
/linux/Documentation/devicetree/bindings/usb/
H A Dusb-hcd.yaml16 companion:
17 description: Phandle of a companion device
/linux/drivers/acpi/
H A Dbus.c717 * @adev: ACPI companion device
721 * the ACPI companion device. This distinction is needed in some cases
722 * where the same companion device is shared between many physical devices.
733 * acpi_companion_match() - Can we match via ACPI companion device
736 * Check if the given device has an ACPI companion and if that companion has
738 * device associated with it. Return the companion pointer if that's the case
741 * If multiple physical devices are attached to a single ACPI companion, we need
744 * companion. A typical case is an MFD device where all the sub-devices share
745 * the parent's ACPI companion. In such cases we can only allow the primary
746 * (first) physical device to be matched with the help of the companion's PNP
[all …]
/linux/Documentation/usb/
H A Dehci.rst19 into an EHCI controller, they are given to a USB 1.1 "companion"
79 The EHCI root hub code hands off USB 1.1 devices to its companion
105 You should also have a driver for a "companion controller", such as
107 remove its module and then the driver for that companion controller will
/linux/arch/x86/include/asm/
H A Dpci.h18 struct acpi_device *companion; /* ACPI companion device */ member
/linux/drivers/usb/gadget/
H A Depautoconf.c21 * descriptor and ep companion descriptor
27 * @ep_comp: Endpoint companion descriptor, with the required
55 * the bmAttribute field in the ep companion descriptor is
/linux/drivers/usb/core/
H A Dconfig.c53 * The SuperSpeedPlus Isoc endpoint companion descriptor immediately in usb_parse_ssp_isoc_endpoint_companion()
54 * follows the SuperSpeed Endpoint Companion descriptor in usb_parse_ssp_isoc_endpoint_companion()
59 dev_notice(ddev, "Invalid SuperSpeedPlus isoc endpoint companion" in usb_parse_ssp_isoc_endpoint_companion()
75 * eUSB2 isochronous endpoint companion descriptor for this endpoint in usb_parse_eusb2_isoc_endpoint_companion()
94 dev_notice(ddev, "No eUSB2 isoc ep %d companion for config %d interface %d altsetting %d\n", in usb_parse_eusb2_isoc_endpoint_companion()
105 /* The SuperSpeed endpoint companion descriptor is supposed to in usb_parse_ss_endpoint_companion()
112 dev_notice(ddev, "No SuperSpeed endpoint companion for config %d " in usb_parse_ss_endpoint_companion()
198 /* Parse a possible SuperSpeedPlus isoc ep companion descriptor */ in usb_parse_ss_endpoint_companion()
503 /* Parse a possible eUSB2 periodic endpoint companion descriptor */ in usb_parse_endpoint()
509 /* Parse a possible SuperSpeed endpoint companion descriptor */ in usb_parse_endpoint()

123456789