Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20201022082435.31831-1-sathish.narasimman@intel.com>
In-Reply-To: <20201022082435.31831-1-sathish.narasimman@intel.com>
From:   Sathish Narasimman <nsathish41@gmail.com>
Date:   Wed, 28 Oct 2020 10:56:20 +0530
Message-ID: <CAOVXEJ+NZ-=y4xcGBOsdmjumw53ZpSjfXnPMSSyjaPzDV0ExAg@mail.gmail.com>
Subject: Re: [PATCH 0/3] Bluetooth:btintel parse TLV structure
To:     Bluez mailing list <linux-bluetooth@vger.kernel.org>
Cc:     Chethan T N <chethan.tumkur.narayan@intel.com>,
        ravishankar.srivatsa@intel.com, kiran.k@intel.com,
        Sathish Narasimman <sathish.narasimman@intel.com>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

hi
gentle reminder

On Thu, Oct 22, 2020 at 1:49 PM Sathish Narasimman <nsathish41@gmail.com> wrote:
>
> Latest intel firmware supports TLV structure in operational mode for intel
> read version. so made changes accordingly to support both bootloader
> and operational mode . These changes are only to specific intel bluetooth
> controller for example ThP, CcP.
>
> Sathish Narasimman (3):
>   Bluetooth: btintel: seperated TLV parsing as new function
>   Bluetooth: btintel: Introducing new btintel read version
>   Bluetooth: btusb: Use the new btintel read version
>
>  drivers/bluetooth/btintel.c | 105 +++++++++++++++++++++++++++---------
>  drivers/bluetooth/btintel.h |  16 ++++++
>  drivers/bluetooth/btusb.c   |  41 ++++++++++----
>  3 files changed, 129 insertions(+), 33 deletions(-)
>
> --
> 2.17.1
>