All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tyszkowski Jakub <jakub.tyszkowski@tieto.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFCv2 2/2] android/gatt: Add test command for database dump
Date: Tue, 03 Jun 2014 09:58:45 +0200	[thread overview]
Message-ID: <538D8035.5040801@tieto.com> (raw)
In-Reply-To: <C088D1E3-5FAD-49FA-8255-B63ADB999622@holtmann.org>

Hi Marcel,

> Hi Jakub,
>
>> With this we can check all attributes handles, uuids, permissions etc.
>> on demand without adding to much logs. This will help to execute and
>> verify some PTS test cases and debug.
>> ---
>> android/gatt.c    | 4 ++++
>> android/hal-msg.h | 1 +
>> 2 files changed, 5 insertions(+)
>>
>> diff --git a/android/gatt.c b/android/gatt.c
>> index 429181f..83a051b 100644
>> --- a/android/gatt.c
>> +++ b/android/gatt.c
>> @@ -3543,6 +3543,10 @@ static void handle_client_test_command(const void *buf, uint16_t len)
>> 		status = test_read_write(&bdaddr, &uuid, cmd->u1, cmd->u2,
>> 						cmd->u3, cmd->u4, cmd->u5);
>> 		break;
>> +	case GATT_CLIENT_TEST_CMD_DB_DUMP:
>> +		gatt_db_dump(gatt_db);
>> +		status = HAL_STATUS_SUCCESS;
>> +		break;
>> 	case GATT_CLIENT_TEST_CMD_PAIRING_CONFIG:
>> 	default:
>> 		status = HAL_STATUS_FAILED;
>> diff --git a/android/hal-msg.h b/android/hal-msg.h
>> index 5da62f3..ce86304 100644
>> --- a/android/hal-msg.h
>> +++ b/android/hal-msg.h
>> @@ -753,6 +753,7 @@ struct hal_cmd_gatt_client_set_adv_data {
>> #define GATT_CLIENT_TEST_CMD_DISCOVER		0x04
>> #define GATT_CLIENT_TEST_CMD_READ		0xe0
>> #define GATT_CLIENT_TEST_CMD_WRITE		0xe1
>> +#define GATT_CLIENT_TEST_CMD_DB_DUMP		0xe2
>> #define GATT_CLIENT_TEST_CMD_PAIRING_CONFIG	0xf0
>
> are these all defined by Bluedroid and Android Bluetooth Service or are some of these BlueZ specific? If so we need to comment that.

Some are defined by Android, but we added our own starting from 0xe0. I 
wonder if README entry wouldn't be better to actually comment that and 
describe parameters for commands we added, so they can be used in 
haltest without searching through the implementation.

>
> Regards
>
> Marcel
>

Regards,
Jakub

  reply	other threads:[~2014-06-03  7:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02 13:19 [RFCv2 0/2] Attribute database dump Jakub Tyszkowski
2014-06-02 13:19 ` [RFCv2 1/2] shared/gatt-db: Add databse dump Jakub Tyszkowski
2014-06-02 13:19 ` [RFCv2 2/2] android/gatt: Add test command for database dump Jakub Tyszkowski
2014-06-02 15:05   ` Marcel Holtmann
2014-06-03  7:58     ` Tyszkowski Jakub [this message]
2014-06-03  9:24       ` Marcel Holtmann

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=538D8035.5040801@tieto.com \
    --to=jakub.tyszkowski@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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.