Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Lukasz Rymanowski <lukasz.rymanowski@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] android/gatt: Fix handling write request
Date: Thu, 22 May 2014 13:15:27 +0200	[thread overview]
Message-ID: <10153799.ryd9BIo34z@uw000953> (raw)
In-Reply-To: <1400675539-12592-1-git-send-email-lukasz.rymanowski@tieto.com>

Hi Łukasz,

On Wednesday 21 of May 2014 14:32:19 Lukasz Rymanowski wrote:
> This patch adds write request to Android framework and uses buffor on
> the stack for the request event.
> ---
>  android/gatt.c | 26 +++++++++++++++-----------
>  1 file changed, 15 insertions(+), 11 deletions(-)
> 
> diff --git a/android/gatt.c b/android/gatt.c
> index 89da60d..42bf2ec 100644
> --- a/android/gatt.c
> +++ b/android/gatt.c
> @@ -3891,7 +3891,8 @@ static void write_cb(uint16_t handle, uint16_t offset,
>  					uint8_t att_opcode, bdaddr_t *bdaddr,
>  					void *user_data)
>  {
> -	struct hal_ev_gatt_server_request_write ev;
> +	uint8_t buf[IPC_MTU];
> +	struct hal_ev_gatt_server_request_write *ev = (void *) buf;
>  	struct gatt_app *app;
>  	int32_t id = PTR_TO_INT(user_data);
>  	static int32_t trans_id = 1;
> @@ -3916,21 +3917,24 @@ static void write_cb(uint16_t handle, uint16_t offset,
>  	if (att_opcode == ATT_OP_EXEC_WRITE_REQ)
>  		goto failed;
>  
> -	memset(&ev, 0, sizeof(ev));
> +	memset(ev, 0, sizeof(*ev));
>  
> -	bdaddr2android(bdaddr, ev.bdaddr);
> -	ev.attr_handle = handle;
> -	ev.offset = offset;
> +	bdaddr2android(bdaddr, &ev->bdaddr);
> +	ev->attr_handle = handle;
> +	ev->offset = offset;
>  
> -	ev.conn_id = conn->id;
> -	ev.trans_id = app->trans_id.id;
> +	ev->conn_id = conn->id;
> +	ev->trans_id = app->trans_id.id;
>  
> -	ev.is_prep = att_opcode == ATT_OP_PREP_WRITE_REQ;
> -	ev.need_rsp = att_opcode == ATT_OP_WRITE_REQ;
> +	ev->is_prep = att_opcode == ATT_OP_PREP_WRITE_REQ;
> +	ev->need_rsp = att_opcode == ATT_OP_WRITE_REQ;
>  
> -	ev.length = len;
> -	memcpy(&ev.value, value, len);
> +	ev->length = len;
> +	memcpy(ev->value, value, len);
>  
> +	ipc_send_notif(hal_ipc, HAL_SERVICE_ID_GATT,
> +			HAL_EV_GATT_SERVER_REQUEST_WRITE,
> +						sizeof(*ev) + ev->length , ev);
>  	return;
>  
>  failed:
> 

Patch applied, thanks.

-- 
Best regards, 
Szymon Janc

      reply	other threads:[~2014-05-22 11:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 12:32 [PATCH] android/gatt: Fix handling write request Lukasz Rymanowski
2014-05-22 11:15 ` Szymon Janc [this message]

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=10153799.ryd9BIo34z@uw000953 \
    --to=szymon.janc@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=lukasz.rymanowski@tieto.com \
    /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