linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ken Clark <kenidevices@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Long Characteristic Reads
Date: Thu, 5 Apr 2018 13:53:12 -0400	[thread overview]
Message-ID: <CANB6vTsVX7Wc2kcxYHFBTK-TCxn2S_J2TzmB+NN=m7H76pXe8w@mail.gmail.com> (raw)

Trying to determine how to respond to long characteristic reads over d-bus.
My application is based on client/bluetoothctl
When I read a characteristic of > MTU size, I get multiple callbacks
to chrc_read_value, with the different offsets that need to be send in
the next transaction.

However I do not see a path in gatt.c to get the MTU for the current
connection, so I know how much data to send.
When I hardcode MTU everything works, but MTU is going to be dynamic
in our application.

Is there a way to access the connections MTU, or is there another
method for handling long reads requests?

Thanks,
Ken

                 reply	other threads:[~2018-04-05 17:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CANB6vTsVX7Wc2kcxYHFBTK-TCxn2S_J2TzmB+NN=m7H76pXe8w@mail.gmail.com' \
    --to=kenidevices@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;
as well as URLs for NNTP newsgroup(s).