Home
last modified time | relevance | path

Searched refs:partner (Results 1 – 25 of 50) sorted by relevance

12

/Linux-v5.10/drivers/usb/typec/
Dbus.c34 port_altmode = is_port ? to_altmode(adev) : to_altmode(adev)->partner; in typec_altmode_set_state()
60 struct altmode *partner; in typec_altmode_notify() local
68 if (!altmode->partner) in typec_altmode_notify()
72 partner = altmode->partner; in typec_altmode_notify()
74 ret = typec_altmode_set_mux(is_port ? altmode : partner, conf, data); in typec_altmode_notify()
78 if (partner->adev.ops && partner->adev.ops->notify) in typec_altmode_notify()
79 return partner->adev.ops->notify(&partner->adev, conf, data); in typec_altmode_notify()
97 struct altmode *partner = to_altmode(adev)->partner; in typec_altmode_enter() local
98 struct typec_altmode *pdev = &partner->adev; in typec_altmode_enter()
128 struct altmode *partner = to_altmode(adev)->partner; in typec_altmode_exit() local
[all …]
Dclass.c87 struct typec_partner *partner = to_typec_partner(dev); in get_pd_identity() local
89 return partner->identity; in get_pd_identity()
168 struct altmode *partner; in typec_altmode_set_partner() local
176 partner = to_altmode(to_typec_altmode(dev)); in typec_altmode_set_partner()
177 altmode->partner = partner; in typec_altmode_set_partner()
183 partner->plug[plug->index] = altmode; in typec_altmode_set_partner()
185 partner->partner = altmode; in typec_altmode_set_partner()
191 struct altmode *partner = altmode->partner; in typec_altmode_put_partner() local
194 if (!partner) in typec_altmode_put_partner()
197 adev = &partner->adev; in typec_altmode_put_partner()
[all …]
Dstusb160x.c157 struct typec_partner *partner; member
364 chip->partner = typec_register_partner(chip->port, &desc); in stusb160x_attach()
365 if (IS_ERR(chip->partner)) { in stusb160x_attach()
366 ret = PTR_ERR(chip->partner); in stusb160x_attach()
388 typec_unregister_partner(chip->partner); in stusb160x_detach()
389 chip->partner = NULL; in stusb160x_detach()
467 if (chip->partner) { in stusb160x_irq_init()
468 typec_unregister_partner(chip->partner); in stusb160x_irq_init()
469 chip->partner = NULL; in stusb160x_irq_init()
796 if (chip->partner) { in stusb160x_remove()
[all …]
Dtps6598x.c96 struct typec_partner *partner; member
219 if (tps->partner) in tps6598x_connect()
244 tps->partner = typec_register_partner(tps->port, &desc); in tps6598x_connect()
245 if (IS_ERR(tps->partner)) in tps6598x_connect()
246 return PTR_ERR(tps->partner); in tps6598x_connect()
249 typec_partner_set_identity(tps->partner); in tps6598x_connect()
256 if (!IS_ERR(tps->partner)) in tps6598x_disconnect()
257 typec_unregister_partner(tps->partner); in tps6598x_disconnect()
258 tps->partner = NULL; in tps6598x_disconnect()
Dbus.h23 struct altmode *partner; member
/Linux-v5.10/Documentation/driver-api/usb/
Dtypec_bus.rst8 Alternate modes require communication with the partner using Vendor Defined
13 USB Type-C bus allows binding a driver to the discovered partner alternate
17 mode a port supports, and separate device for every alternate mode the partner
18 supports. The drivers for the alternate modes are bound to the partner alternate
22 When a new partner alternate mode device is registered, it is linked to the
23 alternate mode device of the port that the partner is attached to, that has
27 The port alternate mode devices are used as a proxy between the partner and the
29 specific commands from the alternate mode drivers to the partner, and from the
33 drivers need to provide them for the partner alternate mode devices.
47 will be used to deliver all the SVID specific commands from the partner to the
[all …]
Dtypec.rst33 When connected, the partner will be presented also as its own device under
34 /sys/class/typec/. The parent of the partner device will always be the port it
35 is attached to. The partner attached to port "port0" will be named
36 "port0-partner". Full path to the device would be
37 /sys/class/typec/port0/port0-partner/.
46 If the port, partner or cable plug supports Alternate Modes, every supported
50 mode of port0-partner will be presented under /sys/class/typec/port0-partner/.
78 After successful connection of a partner, the port driver needs to register the
79 partner with the class. Details about the partner need to be described in struct
80 typec_partner_desc. The class copies the details of the partner during
[all …]
/Linux-v5.10/Documentation/ABI/obsolete/
Dsysfs-class-typec4 What: /sys/class/typec/<port|partner|cable>/<dev>/svid
11 What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/
20 What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/description
27 What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/vdo
34 What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/active
/Linux-v5.10/drivers/usb/typec/ucsi/
Ducsi.c308 alt = typec_partner_register_altmode(con->partner, desc); in ucsi_register_altmode()
546 struct typec_partner *partner; in ucsi_register_partner() local
548 if (con->partner) in ucsi_register_partner()
566 partner = typec_register_partner(con->port, &desc); in ucsi_register_partner()
567 if (IS_ERR(partner)) { in ucsi_register_partner()
570 PTR_ERR(partner)); in ucsi_register_partner()
571 return PTR_ERR(partner); in ucsi_register_partner()
574 con->partner = partner; in ucsi_register_partner()
581 if (!con->partner) in ucsi_unregister_partner()
585 typec_unregister_partner(con->partner); in ucsi_unregister_partner()
[all …]
/Linux-v5.10/Documentation/ABI/testing/
Dsysfs-class-typec57 when both the port and the partner support USB Power Delivery.
126 USB Type-C partner devices (eg. /sys/class/typec/port0-partner/)
128 What: /sys/class/typec/<port>-partner/accessory_mode
132 Shows the Accessory Mode name when the partner is an Accessory.
135 What: /sys/class/typec/<port>-partner/supports_usb_power_delivery
139 Shows if the partner supports USB Power Delivery communication:
142 What: /sys/class/typec/<port>-partner>/identity/
154 What: /sys/class/typec/<port>-partner/identity/id_header
162 What: /sys/class/typec/<port>-partner/identity/cert_stat
170 What: /sys/class/typec/<port>-partner/identity/product
Dsysfs-bus-pci-devices-aer_stats7 counters may increment at its link partner (e.g. root port) because the
8 errors may be "seen" / reported by the link partner and not the
/Linux-v5.10/drivers/platform/chrome/
Dcros_ec_typec.c38 struct typec_partner *partner; member
160 port->partner = typec_register_partner(port->port, &p_desc); in cros_typec_add_partner()
161 if (IS_ERR(port->partner)) { in cros_typec_add_partner()
162 ret = PTR_ERR(port->partner); in cros_typec_add_partner()
163 port->partner = NULL; in cros_typec_add_partner()
182 typec_unregister_partner(port->partner); in cros_typec_remove_partner()
183 port->partner = NULL; in cros_typec_remove_partner()
373 if (typec->ports[port_num]->partner) in cros_typec_set_port_params_v1()
383 if (!typec->ports[port_num]->partner) in cros_typec_set_port_params_v1()
536 if (!port->partner) in cros_typec_configure_mux()
/Linux-v5.10/include/linux/usb/
Dtypec.h108 int typec_partner_set_identity(struct typec_partner *partner);
130 *typec_partner_register_altmode(struct typec_partner *partner,
245 void typec_unregister_partner(struct typec_partner *partner);
/Linux-v5.10/drivers/net/bonding/
Dbond_3ad.c471 struct port_params *partner = &port->partner_oper; in __record_pdu() local
477 partner->port_number = ntohs(lacpdu->actor_port); in __record_pdu()
478 partner->port_priority = ntohs(lacpdu->actor_port_priority); in __record_pdu()
479 partner->system = lacpdu->actor_system; in __record_pdu()
480 partner->system_priority = ntohs(lacpdu->actor_system_priority); in __record_pdu()
481 partner->key = ntohs(lacpdu->actor_key); in __record_pdu()
482 partner->port_state = lacpdu->actor_state; in __record_pdu()
492 partner->port_state |= LACP_STATE_SYNCHRONIZATION; in __record_pdu()
496 partner->port_state &= ~LACP_STATE_SYNCHRONIZATION; in __record_pdu()
539 const struct port_params *partner = &port->partner_oper; in __update_selected() local
[all …]
/Linux-v5.10/drivers/net/ethernet/3com/
D3c574_cs.c199 u16 advertising, partner; /* NWay media advertisement */ member
866 unsigned short /* cable, */ media, partner; in media_check() local
893 partner = mdio_read(ioaddr, lp->phys, 5); in media_check()
901 lp->partner = 0; in media_check()
904 } else if (partner) { in media_check()
905 partner &= lp->advertising; in media_check()
906 lp->partner = partner; in media_check()
909 (partner & 0x0180) ? 100 : 10, in media_check()
910 (partner & 0x0140) ? 'F' : 'H'); in media_check()
916 outb((partner & 0x0140 ? 0x20 : 0) | in media_check()
/Linux-v5.10/arch/sh/include/mach-ecovec24/mach/
Dpartner-jet-setup.txt2 LIST "partner-jet-setup.txt"
8 LIST "> < partner-jet-setup.txt"
/Linux-v5.10/arch/sh/include/mach-kfr2r09/mach/
Dpartner-jet-setup.txt2 LIST "partner-jet-setup.txt - 20090729 Magnus Damm"
7 LIST "> < partner-jet-setup.txt"
/Linux-v5.10/Documentation/powerpc/
Dhvcs.rst335 partner vty removals but not the addition of partner vtys. Since an HMC
336 Super Admin can add partner info dynamically we have provided the hvcs
338 firmware and update the partner info for all the vty-servers that this
371 provide lists of easily parsed partner vty data: "partner_vtys" and
388 Reading partner_vtys returns a list of partner vtys. Vty unit address
394 adapter. The first vty partner corresponds to the first clc item, the
395 second vty partner to the second clc item, etc.
398 "current_vty" prints the clc of the currently selected partner vty when
401 The current_vty can be changed by writing a valid partner clc to the entry
/Linux-v5.10/arch/arm/boot/dts/
Ds5pv210-smdkc110.dts7 * Mateusz Krawczuk <m.krawczuk@partner.samsung.com>
Ds5pv210-torbreck.dts7 * Mateusz Krawczuk <m.krawczuk@partner.samsung.com>
Ds5pv210-smdkv210.dts7 * Mateusz Krawczuk <m.krawczuk@partner.samsung.com>
/Linux-v5.10/Documentation/networking/device_drivers/ethernet/intel/
De1000e.rst330 connections will attempt to auto-negotiate with its link partner to determine
331 the best setting. If the adapter cannot establish link with the link partner
333 partner to identical settings to establish link and pass packets. This should
336 duplex mode. Your link partner must match the setting you choose. 1 Gbps speeds
350 will not attempt to auto-negotiate with its link partner since those adapters
De1000.rst74 either one or two-directional. If both Duplex and the link partner are
76 link partner is forced (either full or half), Duplex defaults to half-
253 partner is set to auto-negotiate, the board will auto-detect the correct
348 common speed and duplex mode IF the link partner is set to auto-negotiate.
387 If the link partner is forced to a specific speed and duplex, then this
/Linux-v5.10/Documentation/misc-devices/
Dibmvmc.rst84 communicate capabilities to their partner. HMC Interface messages are used
96 client or from the server to its partner partition. DMA refers
101 between partner partitions. Transport events which are signaled
/Linux-v5.10/Documentation/networking/device_drivers/ethernet/3com/
D3c509.rst81 (c) Most importantly, your 3c509B must be connected to a link partner that is
97 auto-negotiate a full-duplex connection with its link partner under any
99 of the 3c509B is enabled, its link partner will very likely need to be

12