From: Szymon Janc <szymon.janc@tieto.com>
To: Prabhu Chawandi <foss.chaws@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: android/handsfree.c | Possible Fix | Review
Date: Wed, 01 Apr 2015 16:11:47 +0200 [thread overview]
Message-ID: <1749491.DZ1N48qHzk@leonov> (raw)
In-Reply-To: <CAKafyqoaN+fQBH5hjqv6_+ZMt6_b7hGfF_2a6mKAngLF+PR_0w@mail.gmail.com>
Hi Prabhu,
On Wednesday 01 of April 2015 18:40:52 Prabhu Chawandi wrote:
> Hi,
>
> When we were testing handsfree we were seeing command is not being
> identified and when looked size was sent zero when we set it as below
> it started working.
>
> static const struct ipc_handler sco_handlers[] = {
> /* SCO_OP_GET_FD */
> - { bt_sco_get_fd, false, 0 }
> };
>
>
> static const struct ipc_handler sco_handlers[] = {
> /* SCO_OP_GET_FD */
> + { bt_sco_get_fd, false, sizeof(struct sco_cmd_get_fd) }
> };
Yes, the fix is correct. Could you send a proper patch for it?
> one request - have you documented anywhere the sequence of commands
> to test each profiles supported till now. if we get the the proper
> sequences we can validate much faster stabilising the code. Else we
> need to spend time in identifying the sequences.
>
> So, if you have documented anywhere request you to share,
Those sequences are defined by android code (framework or multimedia) and are
not really documented. You could find some suggestion if you look at our PTS
testing documentation (android/pts-*.txt) where we do use haltest for tests.
Note that if possible we prefer to use Android Framework for validation
instead of haltest (which is mostly development tool).
--
BR
Szymon Janc
next prev parent reply other threads:[~2015-04-01 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 13:10 android/handsfree.c | Possible Fix | Review Prabhu Chawandi
2015-04-01 14:11 ` Szymon Janc [this message]
2015-04-01 14:59 ` Prabhu Chawandi
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=1749491.DZ1N48qHzk@leonov \
--to=szymon.janc@tieto.com \
--cc=foss.chaws@gmail.com \
--cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox