Lines Matching full:expander
3 * Serial Attached SCSI (SAS) Expander discovery and configuration
344 /* check if we have an existing attached ata device on this expander phy */
1089 pr_debug("second fanout expander %016llx phy%02d attached to ex %016llx phy%02d\n", in sas_ex_discover_dev()
1167 * sas_ex_discover_devices - discover devices attached to this expander
1168 * @dev: pointer to the expander domain device
1171 * Configure this expander for use with its devices and register the
1172 * devices of this expander.
1517 * @parent: parent expander
1518 * @child: child expander
1520 * @include: whether or not to include @child in the expander routing table
1560 * @dev: expander device
1561 * @sas_addr: port identifier of device directly attached to the expander device
1578 * sas_discover_expander - expander discovery
1579 * @dev: pointer to expander domain device
1600 pr_warn("expander %016llx discovery failed(0x%x)\n", in sas_discover_expander()
1814 * Add self-configuration expander support. Suppose two expander cascading,
1815 * when the first level expander is self-configuring, hotplug the disks in
1816 * second level expander, BROADCAST(CHANGE) will not only be originated
1817 * in the second level expander, but also be originated in the first level
1818 * expander (see SAS protocol SAS 2r-14, 7.11 for detail), it is to say,
1819 * expander changed count in two level expanders will all increment at least
1837 /* Just detect if this expander phys phy change count changed, in sas_find_bcast_dev()
1838 * in order to determine if this expander originate BROADCAST, in sas_find_bcast_dev()