public inbox for linux-mediatek@lists.infradead.org
 help / color / mirror / Atom feed
From: KaiChieh Chuang <kaichieh.chuang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
To: broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
	garlic.tseng-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
	linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	wsd_upstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
	kaichieh.chuang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org
Subject: [RFC PATCH 0/2] ASoC: mediatek: add btcvsd driver
Date: Thu, 24 Jan 2019 16:58:40 +0800	[thread overview]
Message-ID: <20190124085842.24073-1-kaichieh.chuang@mediatek.com> (raw)

The driver function for transferring/receiving
BT encoded data to/from BT hardware.

KaiChieh Chuang (2):
  ASoC: mediatek: add btcvsd driver
  ASoC: mediatek: add documents for btcvsd driver

 .../bindings/sound/mtk-btcvsd-snd.txt         |   24 +
 sound/soc/mediatek/Kconfig                    |    9 +
 sound/soc/mediatek/common/Makefile            |    2 +
 sound/soc/mediatek/common/mtk-btcvsd.c        | 1376 +++++++++++++++++
 4 files changed, 1411 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/sound/mtk-btcvsd-snd.txt
 create mode 100644 sound/soc/mediatek/common/mtk-btcvsd.c

-- 
2.18.0

             reply	other threads:[~2019-01-24  8:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24  8:58 KaiChieh Chuang [this message]
     [not found] ` <20190124085842.24073-1-kaichieh.chuang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-01-24  8:58   ` [RFC PATCH 1/2] ASoC: mediatek: add btcvsd driver KaiChieh Chuang
2019-01-24 19:25     ` Mark Brown
2019-01-28  8:22       ` KaiChieh Chuang
2019-01-24  8:58   ` [RFC PATCH 2/2] ASoC: mediatek: add documents for " KaiChieh Chuang

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=20190124085842.24073-1-kaichieh.chuang@mediatek.com \
    --to=kaichieh.chuang-nus5lvnupcjwk0htik3j/w@public.gmane.org \
    --cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=garlic.tseng-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
    --cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=wsd_upstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.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