| /linux/drivers/usb/typec/ |
| H A D | class.c | 64 struct typec_partner *partner = to_typec_partner(dev); in get_pd_identity() local
66 return partner->identity; in get_pd_identity()
249 struct altmode *partner; in typec_altmode_set_partner() local
256 /* Bind the port alt mode to the partner/plug alt mode. */ in typec_altmode_set_partner()
257 partner = to_altmode(to_typec_altmode(dev)); in typec_altmode_set_partner()
258 altmode->partner = partner; in typec_altmode_set_partner()
260 /* Bind the partner/plug alt mode to the port alt mode. */ in typec_altmode_set_partner()
264 partner->plug[plug->index] = altmode; in typec_altmode_set_partner()
266 partner->partner = altmode; in typec_altmode_set_partner()
272 struct altmode *partner = altmode->partner; in typec_altmode_put_partner() local
[all …]
|
| H A D | mode_selection.c | 34 * @partner: Handle to the Type-C partner device
44 struct typec_partner *partner; member
96 device_for_each_child(&sel->partner->dev, &order, activate_altmode); in mode_selection_activate()
145 dev_dbg(&sel->partner->dev, "%x altmode is active\n", ms->svid); in mode_selection_work_fn()
154 dev_err(&sel->partner->dev, "%x: entry error %pe\n", in mode_selection_work_fn()
162 dev_err(&sel->partner->dev, "%x: activation error %pe\n", in mode_selection_work_fn()
176 void typec_altmode_state_update(struct typec_partner *partner, const u16 svid, in typec_altmode_state_update() argument
179 struct mode_selection *sel = partner->sel; in typec_altmode_state_update()
231 int typec_mode_selection_start(struct typec_partner *partner, in typec_mode_selection_start() argument
237 if (partner->usb_mode == USB_MODE_USB4) in typec_mode_selection_start()
[all …]
|
| H A D | wusb3801.c | 89 struct typec_partner *partner; member
272 if (wusb3801->partner) { in wusb3801_hw_update()
273 typec_unregister_partner(wusb3801->partner); in wusb3801_hw_update()
274 wusb3801->partner = NULL; in wusb3801_hw_update()
278 wusb3801->partner = typec_register_partner(port, &desc); in wusb3801_hw_update()
279 if (IS_ERR(wusb3801->partner)) in wusb3801_hw_update()
280 dev_err(dev, "Failed to register partner: %ld\n", in wusb3801_hw_update()
281 PTR_ERR(wusb3801->partner)); in wusb3801_hw_update()
408 if (wusb3801->partner) in wusb3801_remove()
409 typec_unregister_partner(wusb3801->partner); in wusb3801_remove()
|
| /linux/include/linux/ |
| H A D | pci-ide.h | 18 * In addition to the resources in each partner port the
28 * @rid_start: Partner Port Requester ID range start
29 * @rid_end: Partner Port Requester ID range end (inclusive)
31 * @mem_assoc: PCI bus memory address association for targeting peer partner
33 * targeting peer partner
37 * partner slot
38 * @enable: flag whether to run pci_ide_stream_disable() for this partner slot
81 * @partner: per-partner settings
83 * @stream_id: unique Stream ID (within Partner Port pairing)
92 struct pci_ide_partner partner[PCI_IDE_PARTNER_MAX]; member
|
| /linux/Documentation/driver-api/usb/ |
| H A D | typec_bus.rst | 8 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 …]
|
| H A D | typec.rst | 33 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/arch/powerpc/platforms/pseries/ |
| H A D | hvcserver.c | 56 * @head: list_head pointer for an allocated list of partner info structs to
59 * This function is used to free the partner info list that was returned by
95 * hvcs_get_partner_info - Get all of the partner info for a vty-server adapter
97 * function is fetching partner info.
99 * list of partner info fetched from the hypervisor to the caller.
102 * of the partner info retrieval.
104 * This function returns non-zero on success, or if there is no partner info.
110 * The first long of this buffer is used to store a partner unit address. The
111 * second long is used to store a partner partition ID and starting at
168 " allocate partner info struct.\n"); in hvcs_get_partner_info()
[all …]
|
| /linux/arch/powerpc/include/asm/ |
| H A D | hvcserver.h | 19 * hvcs_partner_info - an element in a list of partner info
21 * partner info.
22 * @unit_address: The partner unit address of this entry.
23 * @partition_ID: The partner partition ID of this entry.
27 * This structure outlines the format that partner info is presented to a caller
28 * of the hvcs partner info fetching functions. These are strung together into
|
| /linux/Documentation/ABI/obsolete/ |
| H A D | sysfs-class-typec | 4 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/tools/testing/selftests/drivers/net/hw/ |
| H A D | ethtool_extended_state.sh | 55 "Autoneg" "No partner detected")
58 log_test "Autoneg, No partner detected"
80 "Autoneg" "No partner detected during force mode")
84 "Autoneg" "No partner detected during force mode")
87 log_test "Autoneg, No partner detected during force mode"
|
| /linux/tools/testing/selftests/drivers/net/hw/lib/py/ |
| H A D | linkconfig.py | |
| /linux/drivers/tty/hvc/ |
| H A D | hvcs.c | 36 * partner possibilities.
38 * Firmware does not provide notification of vty partner changes to this
39 * driver. This means that an HMC Super Admin may add or remove partner vtys
40 * from a vty-server's partner list but the changes will not be signaled to
44 * rescanning partner information upon a user's request.
133 * tty_device pointers when the number of vty-server & vty partner connections
143 * vty-server & vty partner connections.
202 /* Status of partner info rescan triggered via sysfs. */
242 * partner info.
284 uint32_t p_unit_address; /* partner unit address */
[all …]
|
| /linux/drivers/net/phy/ |
| H A D | linkmode.c | 7 * @partner_adv: partner advertisement in ethtool format
15 * Local device Link partner
67 * Local device Link partner
75 * Local device Link partner
|
| /linux/arch/sh/include/mach-kfr2r09/mach/ |
| H A D | romimage.h | 5 * converts the "partner-jet-script.txt" script into assembly
10 #include <mach/partner-jet-setup.txt>
|
| H A D | partner-jet-setup.txt | 2 LIST "partner-jet-setup.txt - 20090729 Magnus Damm"
7 LIST "> < partner-jet-setup.txt"
|
| /linux/drivers/net/ethernet/intel/igc/ |
| H A D | igc_mac.c | 115 * function. Assuming the adapter has a valid link partner, a valid link
398 * different link partner. in igc_check_for_copper_link()
442 * partner.
464 * and if so, how the PHY and link partner has flow control in igc_config_fc_after_link_up()
503 * for both the PHY and the link partner. The following in igc_config_fc_after_link_up()
509 * LOCAL DEVICE | LINK PARTNER in igc_config_fc_after_link_up()
527 * LOCAL DEVICE | LINK PARTNER in igc_config_fc_after_link_up()
552 * LOCAL DEVICE | LINK PARTNER in igc_config_fc_after_link_up()
566 * LOCAL DEVICE | LINK PARTNER in igc_config_fc_after_link_up()
582 * partner. So if we advertised no flow control, that is in igc_config_fc_after_link_up()
[all …]
|
| /linux/arch/sh/include/mach-ecovec24/mach/ |
| H A D | romimage.h | 5 * converts the "partner-jet-script.txt" script into assembly
10 #include <mach/partner-jet-setup.txt>
|
| H A D | partner-jet-setup.txt | 2 LIST "partner-jet-setup.txt"
8 LIST "> < partner-jet-setup.txt"
|
| /linux/drivers/net/ethernet/intel/e1000e/ |
| H A D | mac.c | 450 * different link partner. in e1000e_check_for_copper_link()
482 /* If we don't have link (auto-negotiation failed or link partner in e1000e_check_for_fiber_link()
484 * and our link partner is not trying to auto-negotiate with us (we in e1000e_check_for_fiber_link()
516 * in an attempt to auto-negotiate with our link partner. in e1000e_check_for_fiber_link()
547 /* If we don't have link (auto-negotiation failed or link partner in e1000e_check_for_serdes_link()
548 * cannot auto-negotiate), and our link partner is not trying to in e1000e_check_for_serdes_link()
579 * in an attempt to auto-negotiate with our link partner. in e1000e_check_for_serdes_link()
675 * function. Assuming the adapter has a valid link partner, a valid link
699 * on the link partner's capabilities, we may or may not use this mode. in e1000e_setup_link_generic()
1010 * partner.
[all …]
|
| /linux/Documentation/arch/powerpc/ |
| H A D | hvcs.rst | 335 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/drivers/net/ethernet/dec/tulip/ |
| H A D | pnic2.c | 50 * Bit 25 - Partner can do T4
51 * Bit 24 - Partner can do 100baseTx-FD
52 * Bit 23 - Partner can do 100baseTx-HD
53 * Bit 22 - Partner can do 10baseT-FD
54 * Bit 21 - Partner can do 10baseT-HD
184 /* If NWay finished and we have a negotiated partner capability. in pnic2_lnk_change()
|
| /linux/drivers/s390/net/ |
| H A D | ctcm_fsms.h | 283 have been received from partner.
291 have been received from partner.
309 have been received from partner.
317 have been received from partner.
|
| /linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | e1000.rst | 74 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.
354 negotiation is disabled, and the AutoNeg parameter is ignored. Partner
387 If the link partner is forced to a specific speed and duplex, then this
|
| H A D | e1000e.rst | 330 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
|
| /linux/drivers/usb/typec/tcpm/ |
| H A D | tcpm.c | 289 * @req_min_volt: Requested min voltage to the port partner
291 * @req_max_volt: Requested max voltage to the port partner
293 * @req_max_curr: Requested max current of the port partner
294 * @req_out_volt: Requested output voltage to the port partner
295 * @req_op_curr: Requested operating current to the port partner
330 * @req_op_curr_ma: Requested operating current to the port partner acting as source
331 * @req_out_volt_mv: Requested output voltage to the port partner acting as source
332 * @max_out_volt_mv: Max SPR voltage supported by the port and the port partner
333 * @max_current_ma; MAX SPR current supported by the port and the port partner
334 * @port_partner_src_status: SPR AVS status of port partner acting as source
[all …]
|