Lines Matching refs:slave
293 * this is different from @dev->link only when @dev is on slave
357 * controller has slave link, device number 16 points to it.
2714 the slave device */
3509 * only on the master and it will handle both master and slave.
4376 * - in many setups only the one drive (slave if present) will
5251 * ata_phys_link_online() when there's no slave link. When
5252 * there's a slave link, this function should only be called on
5264 struct ata_link *slave = link->ap->slave_link;
5266 WARN_ON(link == slave); /* shouldn't be called on slave link */
5269 (slave && ata_phys_link_online(slave));
5277 * ata_phys_link_offline() when there's no slave link. When
5278 * there's a slave link, this function should only be called on
5290 struct ata_link *slave = link->ap->slave_link;
5292 WARN_ON(link == slave); /* shouldn't be called on slave link */
5295 (!slave || ata_phys_link_offline(slave));
5715 * ata_slave_link_init - initialize slave link
5716 * @ap: port to initialize slave link for
5718 * Create and initialize slave link for @ap. This enables slave
5726 * and slave.
5730 * interface with both master and slave devices but also have
5740 * link is used for both master and slave. For physical link
5744 * called once more for the slave link, so the reset sequence