From: Jianqun <jay.xu@rock-chips.com>
To: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
heiko@sntech.de, lgirdwood@gmail.com, broonie@kernel.org,
perex@perex.cz, tiwai@suse.de, grant.likely@linaro.org,
jay.xu@rock-chips.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: huangtao@rock-chips.com, cf@rock-chips.com
Subject: [PATCH 0/2] rockchip-max98090: add driver for rockchip board with max98090
Date: Fri, 12 Sep 2014 15:26:46 +0800 [thread overview]
Message-ID: <1410506806-15327-1-git-send-email-jay.xu@rock-chips.com> (raw)
This patch to add driver for rockchip board using a max98090.
Tested on RK3288 using a max98090.
Jianqun (2):
ASoC: rockchip-max98090: add documentation for rockchip-max98090
driver
ASoC: rockchip-max98090: add driver for rockchip board using a
max98090
.../sound/rockchip,rockchip-audio-max98090.txt | 23 ++
sound/soc/rockchip/Kconfig | 9 +
sound/soc/rockchip/Makefile | 5 +-
sound/soc/rockchip/rockchip_max98090.c | 308 +++++++++++++++++++++
4 files changed, 344 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/sound/rockchip,rockchip-audio-max98090.txt
create mode 100644 sound/soc/rockchip/rockchip_max98090.c
--
1.9.1
next reply other threads:[~2014-09-12 7:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 7:26 Jianqun [this message]
2014-09-12 7:32 ` [PATCH 2/2] ASoC: rockchip-max98090: add driver for rockchip board using a max98090 Jianqun
[not found] ` <1410506806-15327-1-git-send-email-jay.xu-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-09-12 7:30 ` [PATCH 1/2] ASoC: rockchip-max98090: add documentation for rockchip-max98090 driver Jianqun
2014-09-12 9:10 ` Jianqun
[not found] ` <1410513055-17775-1-git-send-email-jay.xu-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-09-12 10:04 ` Heiko Stübner
2014-09-12 10:12 ` Jianqun
2014-09-12 13:44 ` Mark Brown
2014-09-28 0:54 ` Jianqun
[not found] ` <54275C43.8010205-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-09-28 10:48 ` Mark Brown
2014-09-28 11:05 ` Jianqun
2014-09-12 7:39 ` [PATCH] ASoC: rockchip-max98090: add driver for rockchip board using a max98090 Jianqun
2014-09-12 13:52 ` Mark Brown
[not found] ` <20140912135247.GU7960-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-10-02 8:06 ` Jianqun
2014-09-12 7:43 ` [PATCH 2/2] " Jianqun
[not found] ` <1410507807-15795-1-git-send-email-jay.xu-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-10-02 8:36 ` [PATCH v2 " Jianqun
[not found] ` <1412238960-4220-1-git-send-email-jay.xu-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-10-02 10:22 ` Mark Brown
2014-09-12 13:42 ` [PATCH 0/2] rockchip-max98090: add driver for rockchip board with max98090 Mark Brown
2014-09-14 3:00 ` Jianqun
-- strict thread matches above, loose matches on Subject: below --
2014-10-07 1:43 Jianqun
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=1410506806-15327-1-git-send-email-jay.xu@rock-chips.com \
--to=jay.xu@rock-chips.com \
--cc=broonie@kernel.org \
--cc=cf@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.de \
/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).