From: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
To: ofono@ofono.org
Subject: Re: [PATCH] handsfree-audio: Add .Connect using the card driver
Date: Wed, 27 Mar 2013 11:45:17 -0300 [thread overview]
Message-ID: <20130327144517.GC2715@samus> (raw)
In-Reply-To: <515302E7.7080100@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2145 bytes --]
Hi Denis,
On 09:32 Wed 27 Mar, Denis Kenzior wrote:
> >
> >Yes. This behaviour is even covered in one of the PTS tests: TP/ACC/BV-03-I
> >(from the description of the test, "To verify the capability of the HF
> >initiating a legacy audio connection with an AG that does not support the
> >Codec Connection setup procedure. The HF should be able to correctly negotiate
> >a working legacy audio connection to the AG.")
> >
>
> Okay, that makes things a little harder since we cannot determine
> the driver to use until the SLC is established.
Yeah.
>
> <snip>
>
> >>>+ if (!driver || !driver->connect)
> >>>+ goto fallback;
> >>>+
> >>>+ err = driver->connect(card, card_connect_reply_cb, card);
> >>>+ if (err == -EINPROGRESS) {
> >>>+ card->msg = dbus_message_ref(msg);
> >>>+ return NULL;
> >>
> >>As mentioned earlier, the driver should not return an int, however,
> >>lets revisit this part. I want to better understand the AT+BCC and
> >>codec negotiation interactions.
> >
> >
> >Of course.
> >
> >Another thing that may make sense to bring up now is the AG case: if we want
> >to have a HFP 1.6 capable AG, we may want to select the codec (send a +BCS)
> >before establishing the SCO connection. I was thinking of setting a specific
> >error code in the callback to signify that the core handsfree-audio may
> >connect the SCO at that point.
> >
>
> I thought of setting error codes in callbacks, but I'm not happy
> with that solution. Perhaps we should make SCO establishment a part
> of the card utility API. e.g. ofono_handsfree_card_connect_sco().
> That way the AG can run the required +BCS transactions and call the
> above function when it comes to making the SCO connection.
Sounds good. This aproach may even make the case that "we" are the AG and we
receive a AT+BCC easier to handle.
>
> For HFP 1.6/1.5, we can either use +BCC or call
> ofono_handsfree_card_connect_sco directly.
>
> Thoughts, other ideas?
Right now, I don't have any. I will give it a try and see how it ends up
looking.
>
> Regards,
> -Denis
Cheers,
--
Vinicius
next prev parent reply other threads:[~2013-03-27 14:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 22:05 [PATCH 1/5] handsfree-audio: Add support for initiating SCO connections Vinicius Costa Gomes
2013-03-25 22:05 ` [PATCH 2/5] handsfree-audio: Add support for sending the SCO socket Vinicius Costa Gomes
2013-03-27 4:42 ` Denis Kenzior
2013-03-25 22:05 ` [PATCH 3/5] handsfree-audio: Reject .Connect() from other senders Vinicius Costa Gomes
2013-03-27 4:42 ` Denis Kenzior
2013-03-25 22:05 ` [PATCH 4/5] hfp_hf_bluez5: Add a card driver for HFP 1.6 Vinicius Costa Gomes
2013-03-27 4:43 ` Denis Kenzior
2013-03-25 22:05 ` [PATCH 5/5] handsfree-audio: Add .Connect using the card driver Vinicius Costa Gomes
2013-03-26 21:21 ` Vinicius Costa Gomes
2013-03-26 21:28 ` [PATCH] " Vinicius Costa Gomes
2013-03-27 4:59 ` Denis Kenzior
2013-03-27 14:22 ` Vinicius Costa Gomes
2013-03-27 14:32 ` Denis Kenzior
2013-03-27 14:45 ` Vinicius Costa Gomes [this message]
2013-03-27 4:41 ` [PATCH 1/5] handsfree-audio: Add support for initiating SCO connections Denis Kenzior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130327144517.GC2715@samus \
--to=vinicius.gomes@openbossa.org \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.