From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 2/2] android/tester: Enable bthost after device is enabled
Date: Tue, 17 Dec 2013 10:04:09 +0200 [thread overview]
Message-ID: <20131217080214.GA3209@aemeltch-MOBL1> (raw)
In-Reply-To: <20131217075057.GA19701@x220.p-661hnu-f1>
Hi Johan,
On Tue, Dec 17, 2013 at 09:50:57AM +0200, Johan Hedberg wrote:
> Hi Andrei,
>
> On Mon, Dec 16, 2013, Andrei Emeltchenko wrote:
> > +static void client_connectable_complete(uint16_t opcode, uint8_t status,
> > + const void *param, uint8_t len,
> > + void *user_data)
> > +{
> > + switch (opcode) {
> > + case BT_HCI_CMD_WRITE_SCAN_ENABLE:
> > + case BT_HCI_CMD_LE_SET_ADV_ENABLE:
> > + break;
> > + default:
> > + return;
> > + }
> > +
> > + tester_print("Client set connectable status 0x%02x", status);
> > +
> > + if (status)
> > + tester_setup_failed();
> > + else
> > + tester_setup_complete();
> > +}
> > +
> > +static void setup_powered_client(void)
> > +{
> > + struct test_data *data = tester_get_data();
> > + struct bthost *bthost;
> > +
> > + tester_print("Controller powered on");
> > +
> > + bthost = hciemu_client_get_host(data->hciemu);
> > + bthost_set_cmd_complete_cb(bthost, client_connectable_complete, data);
> > +
> > + if (data->hciemu_type == HCIEMU_TYPE_LE)
> > + bthost_set_adv_enable(bthost, 0x01);
> > + else
> > + bthost_write_scan_enable(bthost, 0x03);
> > +}
> > +
> > static void adapter_state_changed_cb(bt_state_t state)
> > {
> > enum hal_bluetooth_callbacks_id hal_cb;
> > @@ -484,7 +525,7 @@ static void adapter_state_changed_cb(bt_state_t state)
> > break;
> > case adapter_test_setup_mode:
> > if (state == BT_STATE_ON)
> > - tester_setup_complete();
> > + setup_powered_client();
> > else
> > tester_setup_failed();
> > break;
>
> You seem to have copied this from l2cap-tester without understanding why
> the naming of these functions are as they are. The "client" in the names
> are for testing client sockets (as opposed to server ones). However,
> you're calling these for every test case, including the server tests
> (the ones with _listen in them), which doesn't seem right. If you're the
> server you don't need to make the bthost side connectable.
So what is appropriate way of setting emulated remote device connectible?
This actually does not hurt in every case.
Best regards
Andrei Emeltchenko
next prev parent reply other threads:[~2013-12-17 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 14:52 [PATCH 1/2] android/tester: Add missing break Andrei Emeltchenko
2013-12-16 14:52 ` [PATCH 2/2] android/tester: Enable bthost after device is enabled Andrei Emeltchenko
2013-12-17 7:50 ` Johan Hedberg
2013-12-17 8:04 ` Andrei Emeltchenko [this message]
2013-12-17 8:20 ` Johan Hedberg
2013-12-17 7:51 ` [PATCH 1/2] android/tester: Add missing break Johan Hedberg
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=20131217080214.GA3209@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@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