devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Baluta <daniel.baluta@nxp.com>
To: "broonie@kernel.org" <broonie@kernel.org>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Cc: Cosmin Samoila <cosmin.samoila@nxp.com>,
	Daniel Baluta <daniel.baluta@nxp.com>,
	Viorel Suman <viorel.suman@nxp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"S.j. Wang" <shengjiu.wang@nxp.com>,
	dl-linux-imx <linux-imx@nxp.com>,
	"daniel.baluta@gmail.com" <daniel.baluta@gmail.com>
Subject: [PATCH 0/2]  Add support for AK4497 codec
Date: Fri, 4 Jan 2019 16:27:03 +0000	[thread overview]
Message-ID: <20190104162649.13103-1-daniel.baluta@nxp.com> (raw)

AK4497 is almost register compatible with AK4458. Almost means that
AK4497 has an extra "debug" register that we currently do not use.

Daniel Baluta (2):
  ASoC: ak4458: Add support for AK4497
  ASoC: dt-bindings: Document support for ak4497

 .../devicetree/bindings/sound/ak4458.txt      |  2 +-
 sound/soc/codecs/ak4458.c                     | 79 ++++++++++++++++++-
 2 files changed, 77 insertions(+), 4 deletions(-)

-- 
2.17.1

             reply	other threads:[~2019-01-04 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 16:27 Daniel Baluta [this message]
2019-01-04 16:27 ` [PATCH 1/2] ASoC: ak4458: Add support for AK4497 Daniel Baluta
2019-01-07 18:58   ` Applied "ASoC: ak4458: Add support for AK4497" to the asoc tree Mark Brown
2019-01-04 16:27 ` [PATCH 2/2] ASoC: dt-bindings: Document support for ak4497 Daniel Baluta
2019-01-07 18:58   ` Applied "ASoC: dt-bindings: Document support for ak4497" to the asoc tree Mark Brown

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=20190104162649.13103-1-daniel.baluta@nxp.com \
    --to=daniel.baluta@nxp.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cosmin.samoila@nxp.com \
    --cc=daniel.baluta@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=shengjiu.wang@nxp.com \
    --cc=viorel.suman@nxp.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).