linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tedd Ho-Jeong An <tedd.an@linux.intel.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Linux Bluetooth Mailing List <linux-bluetooth@vger.kernel.org>
Subject: Re: [BlueZ PATCH V2] btp: Update connect event structure
Date: Fri, 26 Jun 2020 10:33:53 -0700	[thread overview]
Message-ID: <01396c1298c1d34127aa6a164f59adc15aa3b7af.camel@linux.intel.com> (raw)
In-Reply-To: <CABBYNZJ34-f3_2vZStRaghc8jn9YPPc+Av93bBOuU1Jek7Fprg@mail.gmail.com>

Hi Luiz

On Fri, 2020-06-26 at 09:58 -0700, Luiz Augusto von Dentz wrote:
> Hi Tedd,
> 
> On Thu, Jun 25, 2020 at 5:10 PM Tedd Ho-Jeong An
> <tedd.an@linux.intel.com> wrote:
> > From: Tedd Ho-Jeong An <tedd.an@intel.com>
> > 
> > This patch updates the connect event struct to align withe the btp spec.
> > 
> >  Opcode 0x82 - Device Connected event
> >     Controller Index:   <controller id>
> >     Event parameters:   Address_Type (1 octet)
> >                         Address (6 octets)
> >                         Connection Interval (2 octets)
> >                         Connection Latency (2 octets)
> >                         Supervision Timeout (2 octets)
> > ---
> >  src/shared/btp.h | 3 +++
> >  1 file changed, 3 insertions(+)
> > 
> > diff --git a/src/shared/btp.h b/src/shared/btp.h
> > index f0ac3a1ee..cc71a71df 100644
> > --- a/src/shared/btp.h
> > +++ b/src/shared/btp.h
> > @@ -259,6 +259,9 @@ struct btp_device_found_ev {
> >  struct btp_gap_device_connected_ev {
> >         uint8_t address_type;
> >         bdaddr_t address;
> > +       uint16_t connection_interval;
> > +       uint16_t connection_latency;
> > +       uint16_t supervision_timeout;
> >  } __packed;
> 
> This appears to be an API break, or we don't for BTP to be stable?

It was old change and this patch was to align the change for BlueZ.
All other projects using BTP such as Zephyr and Mynewt are already using new
change.

> 
> >  #define BTP_EV_GAP_DEVICE_DISCONNECTED         0x83
> > --
> > 2.17.1
> > 
> > 
> 
> 


      reply	other threads:[~2020-06-26 17:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26  0:02 [BlueZ PATCH V2] btp: Update connect event structure Tedd Ho-Jeong An
2020-06-26 16:58 ` Luiz Augusto von Dentz
2020-06-26 17:33   ` Tedd Ho-Jeong An [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=01396c1298c1d34127aa6a164f59adc15aa3b7af.camel@linux.intel.com \
    --to=tedd.an@linux.intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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;
as well as URLs for NNTP newsgroup(s).