'\" t
.\"     Title: ata_force_cbl
.\"    Author: 
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\"      Date: June 2017
.\"    Manual: libata Core Internals
.\"    Source: Kernel Hackers Manual 4.11.3
.\"  Language: English
.\"
.TH "ATA_FORCE_CBL" "9" "June 2017" "Kernel Hackers Manual 4\&.11\&" "libata Core Internals"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
ata_force_cbl \- force cable type according to libata\&.force
.SH "SYNOPSIS"
.HP \w'void\ ata_force_cbl('u
.BI "void ata_force_cbl(struct\ ata_port\ *\ " "ap" ");"
.SH "ARGUMENTS"
.PP
\fIstruct ata_port * ap\fR
.RS 4
ATA port of interest
.RE
.SH "DESCRIPTION"
.PP
Force cable type according to libata\&.force and whine about it\&. The last entry which has matching port number is used, so it can be specified as part of device force parameters\&. For example, both
\(lqa:40c,1\&.00:udma4\(rq
and
\(lq1\&.00:40c,udma4\(rq
have the same effect\&.
.PP
LOCKING: EH context\&.
.SH "AUTHOR"
.PP
\fBJeff Garzik\fR
.RS 4
Author.
.RE
.SH "COPYRIGHT"
.br