All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harish Bandi <c-hbandi@codeaurora.org>
To: marcel@holtmann.org, johan.hedberg@gmail.com
Cc: mka@chromium.org, linux-kernel@vger.kernel.org,
	linux-bluetooth@vger.kernel.org, hemantg@codeaurora.org,
	linux-arm-msm@vger.kernel.org, bgodavar@codeaurora.org,
	anubhavg@codeaurora.org, Harish Bandi <c-hbandi@codeaurora.org>
Subject: [PATCH v1 0/2] Enable Bluetooth functionality for wcn3998.
Date: Thu,  7 Mar 2019 17:46:50 +0530	[thread overview]
Message-ID: <1551961012-23898-1-git-send-email-c-hbandi@codeaurora.org> (raw)

This patch series we add support for wcn3998 BT chip set. This new chipset
is based from the wcn3990 with minimal power numbers. So here in this patch
The major difference between wcn3990 and wcn3998 is only power numbers. where
as init process and fw download is same with wcn3990.So we are leveraging the 
existing code of wcn3990 along with readiing the voltages from the dts file. 


Harish Bandi (2):
  Bluetooth: hci_qca: Added support to read the regulator values from
    DTS
  dt-bindings: net: bluetooth: Add device tree bindings for QTI chip
    wcn3990

 .../devicetree/bindings/net/qualcomm-bluetooth.txt | 12 ++++
 drivers/bluetooth/hci_qca.c                        | 76 +++++++++++++++++++---
 2 files changed, 80 insertions(+), 8 deletions(-)

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

             reply	other threads:[~2019-03-07 12:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 12:16 Harish Bandi [this message]
2019-03-07 12:16 ` [PATCH v1 1/2] Bluetooth: hci_qca: Added support to read the regulator values from DTS Harish Bandi
2019-03-07 12:16 ` [PATCH v1 2/2] dt-bindings: net: bluetooth: Add device tree bindings for QTI chip wcn3990 Harish Bandi
2019-03-07 19:18 ` [PATCH v1 0/2] Enable Bluetooth functionality for wcn3998 Matthias Kaehlcke
2019-03-08  6:39   ` c-hbandi

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=1551961012-23898-1-git-send-email-c-hbandi@codeaurora.org \
    --to=c-hbandi@codeaurora.org \
    --cc=anubhavg@codeaurora.org \
    --cc=bgodavar@codeaurora.org \
    --cc=hemantg@codeaurora.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mka@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.