From: Tedd Ho-Jeong An <tedd.an@intel.com>
To: BlueZ development <linux-bluetooth@vger.kernel.org>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [PATCH] Bluetooth: btusb: Apply Intel device configuration routine
Date: Sat, 9 May 2015 04:17:16 -0700 [thread overview]
Message-ID: <20150509041716.6e10056c@tedd-fedora-vm> (raw)
In-Reply-To: <20150508035946.0039963d@intel.com>
Hi Marcel,
I just wonder if you had a chance to review this pacth.
Let me know if you have any comments.
Regards,
Tedd
On Fri, 8 May 2015 03:59:46 -0700
Tedd Ho-Jeong An <tedd.an@intel.com> wrote:
> From: Tedd Ho-Jeong An <tedd.an@intel.com>
>
> This patch adds support to apply the device configuration parameters
> (DDC) after firwmare downloading on Intel 8265 device.
>
> This is optional configuration parameters and good to have.
> So, even if it fails to apply it, it is not necessary to fail the
> setup.
>
> The file format is same as previous firmware patch (.bseq) and
> this is only applicable to Intel 8265 device.
>
> Signed-off-by: Tedd Ho-Jeong An <tedd.an@intel.com>
> ---
> drivers/bluetooth/btusb.c | 34 ++++++++++++++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index d21f3b4..27cd2bf 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -2644,6 +2644,40 @@ done:
>
> clear_bit(BTUSB_BOOTLOADER, &data->flags);
>
> + /* Once the device is running in operational mode, it needs to apply
> + * the configuration parameters to the device.
> + */
> + snprintf(fwname, sizeof(fwname), "intel/ibt-11.bseq");
> +
> + /* Device can work without this configuration so even if it fails
> + * to load the file, no need to fail the setup
> + */
> + err = request_firmware_direct(&fw, fwname, &hdev->dev);
> + if (err < 0) {
> + BT_INFO("%s: WARNING: unable to load configuration file (%d)",
> + hdev->name, err);
> + return 0;
> + }
> +
> + BT_INFO("%s: Found device configuration file: %s", hdev->name, fwname);
> +
> + fw_ptr = fw->data;
> + while (fw->size > fw_ptr - fw->data) {
> + int ignore;
> +
> + err = btusb_setup_intel_patching(hdev, fw, &fw_ptr,
> + &ignore);
> + if (err < 0) {
> + BT_INFO("%s: WARNING: failed to send configuration(%d)",
> + hdev->name, err);
> + release_firmware(fw);
> + return 0;
> + }
> + }
> + release_firmware(fw);
> +
> + BT_INFO("%s: Device configuration completed", hdev->name);
> +
> return 0;
> }
>
next prev parent reply other threads:[~2015-05-09 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 10:59 [PATCH] Bluetooth: btusb: Apply Intel device configuration routine Tedd Ho-Jeong An
2015-05-09 11:17 ` Tedd Ho-Jeong An [this message]
2015-05-12 15:05 ` Marcel Holtmann
2015-05-09 13:50 ` Tedd Ho-Jeong An
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=20150509041716.6e10056c@tedd-fedora-vm \
--to=tedd.an@intel.com \
--cc=johan.hedberg@gmail.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 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).