From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ASoC: sun4i-spdif: Add quirks to the spdif driver
Date: Tue, 20 Dec 2016 20:12:46 +0100 [thread overview]
Message-ID: <20161220191246.7fcvfovvvttdntn3@lukather> (raw)
In-Reply-To: <20161220144914.30945-3-codekipper@gmail.com>
On Tue, Dec 20, 2016 at 03:49:14PM +0100, codekipper at gmail.com wrote:
> From: Marcus Cooper <codekipper@gmail.com>
>
> It has been seen that some newer SoCs have a different TX FIFO
> address and we already have the difference with the A31 requiring
> a reset. Add a quirks structure so that these can be managed
> easily.
>
> Signed-off-by: Marcus Cooper <codekipper@gmail.com>
Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161220/f7369346/attachment.sig>
next prev parent reply other threads:[~2016-12-20 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 14:49 [PATCH 0/2] ASoC: sun4i-spdif: Changes in preparation of supporting new SoCs codekipper at gmail.com
2016-12-20 14:49 ` [PATCH 1/2] ASoC: sun4i-spdif: remove legacy dapm components codekipper at gmail.com
2016-12-20 19:11 ` Maxime Ripard
2016-12-31 19:19 ` Applied "ASoC: sun4i-spdif: remove legacy dapm components" to the asoc tree Mark Brown
2016-12-20 14:49 ` [PATCH 2/2] ASoC: sun4i-spdif: Add quirks to the spdif driver codekipper at gmail.com
2016-12-20 19:12 ` Maxime Ripard [this message]
2016-12-31 19:19 ` Applied "ASoC: sun4i-spdif: Add quirks to the spdif driver" 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=20161220191246.7fcvfovvvttdntn3@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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