Re: [PATCHv2 10/19] Bluetooth: Add logical link confirm

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Wed, Oct 17, 2012 at 10:22:09AM -0700, Marcel Holtmann wrote:
> Hi Mat,
> 
> > The logical link confirm callback is executed when the AMP controller
> > completes its logical link setup.  During a channel move, a newly
> > formed logical link allows a move responder to send a move channel
> > response.  A move initiator will send a move channel confirm.  A
> > failed logical link will end the channel move and send an appropriate
> > response or confirm command indicating a failure.
> > 
> > If the channel is being created on an AMP controller, L2CAP
> > configuration is started after the logical link is set up.
> > 
> > Signed-off-by: Mat Martineau <mathewm@xxxxxxxxxxxxxx>
> > ---
> >  net/bluetooth/l2cap_core.c | 114 ++++++++++++++++++++++++++++++++++++++++++++-
> >  1 file changed, 112 insertions(+), 2 deletions(-)
> > 
> > diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
> > index 5e4796c..ddd8c72 100644
> > --- a/net/bluetooth/l2cap_core.c
> > +++ b/net/bluetooth/l2cap_core.c
> > @@ -3799,6 +3799,7 @@ static inline int l2cap_config_req(struct l2cap_conn *conn,
> >  		goto unlock;
> >  	}
> >  
> > +	chan->ident = cmd->ident;
> >  	l2cap_send_cmd(conn, cmd->ident, L2CAP_CONF_RSP, len, rsp);
> >  	chan->num_conf_rsp++;
> >  
> > @@ -4241,11 +4242,120 @@ static void l2cap_send_move_chan_cfm_rsp(struct l2cap_conn *conn, u8 ident,
> >  	l2cap_send_cmd(conn, ident, L2CAP_MOVE_CHAN_CFM_RSP, sizeof(rsp), &rsp);
> >  }
> >  
> > +/* Call with chan locked */
> >  static void l2cap_logical_cfm(struct l2cap_chan *chan, struct hci_chan *hchan,
> >  			      u8 status)
> >  {
> > -	/* Placeholder */
> > -	return;
> > +	BT_DBG("chan %p, hchan %p, status %d", chan, hchan, status);
> > +
> > +	if (status) {
> > +		/* Logical link setup failed */
> > +		if (chan->state != BT_CONNECTED) {
> > +			/* Create channel failure, disconnect */
> > +			l2cap_send_disconn_req(chan->conn, chan, ECONNRESET);
> > +		} else if (chan->move_role == L2CAP_MOVE_ROLE_RESPONDER) {
> > +			l2cap_move_revert(chan);
> > +			chan->move_role = L2CAP_MOVE_ROLE_NONE;
> > +			chan->move_state = L2CAP_MOVE_STABLE;
> > +			l2cap_send_move_chan_rsp(chan->conn, chan->ident,
> > +						 chan->dcid, L2CAP_MR_NOT_SUPP);
> > +		} else if (chan->move_role == L2CAP_MOVE_ROLE_INITIATOR) {
> > +			if (chan->move_state == L2CAP_MOVE_WAIT_LOGICAL_COMP ||
> > +			    chan->move_state == L2CAP_MOVE_WAIT_LOGICAL_CFM) {
> > +				/* Remote has only sent pending or
> > +				 * success responses, clean up
> > +				 */
> > +				l2cap_move_revert(chan);
> > +				chan->move_role = L2CAP_MOVE_ROLE_NONE;
> > +				chan->move_state = L2CAP_MOVE_STABLE;
> > +			}
> > +
> > +			/* Other amp move states imply that the move
> > +			 * has already aborted
> > +			 */
> > +			l2cap_send_move_chan_cfm(chan->conn, chan, chan->scid,
> > +						 L2CAP_MC_UNCONFIRMED);
> > +			__set_chan_timer(chan, L2CAP_MOVE_TIMEOUT);
> > +		}
> > +
> > +		chan->hs_hchan = NULL;
> > +		chan->hs_hcon = NULL;
> > +
> > +		/* Placeholder - free logical link */
> > +
> > +	} else if (chan->state != BT_CONNECTED) {
> > +		struct l2cap_conf_rsp rsp;
> > +		u8 code;
> > +
> > +		/* Create channel complete */
> > +
> > +		/* Ignore logical link if channel is on BR/EDR */
> > +		if (!chan->local_amp_id)
> > +			return;
> > +
> > +		chan->hs_hcon = hchan->conn;

I was thinking that hs_hcon might be assigned when physical link is
completed. Isn't this assignment a bit late?

> > +		chan->hs_hcon->l2cap_data = chan->conn;
> > +
> > +		code = l2cap_build_conf_rsp(chan, &rsp,
> > +					    L2CAP_CONF_SUCCESS, 0);
> > +		l2cap_send_cmd(chan->conn, chan->ident, L2CAP_CONF_RSP, code,
> > +			       &rsp);
> > +		set_bit(CONF_OUTPUT_DONE, &chan->conf_state);
> > +
> > +		if (test_bit(CONF_INPUT_DONE, &chan->conf_state)) {
> > +			int err = 0;
> > +
> > +			set_default_fcs(chan);
> > +
> > +			err = l2cap_ertm_init(chan);
> > +			if (err < 0)
> > +				l2cap_send_disconn_req(chan->conn, chan, -err);
> > +			else
> > +				l2cap_chan_ready(chan);
> > +		}
> > +	} else {
> > +		/* Channel move */
> > +		chan->hs_hcon = hchan->conn;
> > +		chan->hs_hcon->l2cap_data = chan->conn;
> > +
> > +		BT_DBG("move_state %d", chan->move_state);
> > +
> > +		switch (chan->move_state) {
> > +		case L2CAP_MOVE_WAIT_LOGICAL_COMP:
> > +			/* Move confirm will be sent after a success
> > +			 * response is received
> > +			 */
> > +			chan->move_state = L2CAP_MOVE_WAIT_RSP_SUCCESS;
> > +			break;
> > +		case L2CAP_MOVE_WAIT_LOGICAL_CFM:
> > +			if (test_bit(CONN_LOCAL_BUSY, &chan->conn_state)) {
> > +				chan->move_state = L2CAP_MOVE_WAIT_LOCAL_BUSY;
> > +			} else if (chan->move_role ==
> > +				   L2CAP_MOVE_ROLE_INITIATOR) {
> > +				chan->move_state = L2CAP_MOVE_WAIT_CONFIRM_RSP;
> > +				l2cap_send_move_chan_cfm(chan->conn, chan,
> > +							 chan->scid,
> > +							 L2CAP_MR_SUCCESS);
> > +				__set_chan_timer(chan, L2CAP_MOVE_TIMEOUT);
> > +			} else if (chan->move_role ==
> > +				   L2CAP_MOVE_ROLE_RESPONDER) {
> > +				chan->move_state = L2CAP_MOVE_WAIT_CONFIRM;
> > +				l2cap_send_move_chan_rsp(chan->conn,
> > +							 chan->ident,
> > +							 chan->dcid,
> > +							 L2CAP_MR_SUCCESS);
> > +			}
> > +			break;
> > +		default:
> > +			/* Move was not in expected state, free the channel */
> > +			chan->hs_hchan = NULL;
> > +			chan->hs_hcon = NULL;
> > +
> > +			/* Placeholder - free the logical link */
> > +
> > +			chan->move_state = L2CAP_MOVE_STABLE;
> > +		}
> > +	}
> >  }
> >  
> 
> I find this this function still a little bit too complex. Any chance we
> can split into more logical pieces. It is fine if not, but we should at
> least give it another try.

IMO this would be much cleaner if you would handle (status) case first
then channel create and then channel move without "if else", maybe
splitting to functions would be better.

Best regards 
Andrei Emeltchenko 

--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux