From: "Heiko Stübner" <heiko@sntech.de>
To: Vasily Khoruzhick <anarsoul@gmail.com>
Cc: Tomasz Figa <t.figa@samsung.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
alsa-devel@alsa-project.org, Kukjin Kim <kgene.kim@samsung.com>,
Sangbeom Kim <sbkim73@samsung.com>,
Lars-Peter Clausen <lars@metafoo.de>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>
Subject: Re: [alsa-devel] [PATCH v2 1/2] ASoC: samsung: s3c24{xx, 12}-i2s: port to use generic dmaengine API
Date: Wed, 21 May 2014 18:24:32 +0200 [thread overview]
Message-ID: <1736816.ReELmLitPm@phil> (raw)
In-Reply-To: <CA+E=qVdnNPyR8NL2gxrt_rptjxB3RROYjSRe3rkHH-JLq==oFg@mail.gmail.com>
Am Mittwoch, 21. Mai 2014, 19:09:19 schrieb Vasily Khoruzhick:
> On Wed, May 21, 2014 at 6:56 PM, Heiko Stübner <heiko@sntech.de> wrote:
> > Openmoko Freerunner (S3C2440) where there may be sound reachable someway
> > and a "Oyo" ebook-reader (S3C2416) whose i2s is I think compatible with
> > the s3c64xx instead of the s3c24xx ones and with a completely unsupported
> > codec.
> Freerunner is s3c2442, and actually I can test s3c2442 on my iPAQ rx1950.
> s3c2416 may be supported by s3c2412-i2s, I have no spec at the hand,
> so I can't check.
I'm quite sure, s3c2416 shares the s3c64xx i2s ... at some point I matched the
registers and it also shares the hsspi, sdhci and fb drivers with the newer
generations (s3c64xx onward).
Heiko
prev parent reply other threads:[~2014-05-21 16:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 20:26 [PATCH v2 1/2] ASoC: samsung: s3c24{xx, 12}-i2s: port to use generic dmaengine API Vasily Khoruzhick
2014-05-20 20:26 ` [PATCH v2 2/2] ASoC: samsung: drop support for legacy S3C24XX DMA API Vasily Khoruzhick
2014-05-20 22:19 ` [PATCH v2 1/2] ASoC: samsung: s3c24{xx, 12}-i2s: port to use generic dmaengine API Mark Brown
2014-05-21 6:42 ` Vasily Khoruzhick
2014-05-21 10:49 ` Mark Brown
2014-05-21 10:53 ` Vasily Khoruzhick
2014-05-21 13:28 ` [alsa-devel] " Tomasz Figa
2014-05-21 14:53 ` Vasily Khoruzhick
2014-05-21 15:07 ` Tomasz Figa
2014-05-21 15:20 ` Vasily Khoruzhick
2014-05-21 15:29 ` Heiko Stübner
2014-05-21 15:39 ` Vasily Khoruzhick
2014-05-21 15:56 ` Heiko Stübner
2014-05-21 16:09 ` Vasily Khoruzhick
2014-05-21 16:20 ` Mark Brown
2014-05-21 16:24 ` Heiko Stübner [this message]
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=1736816.ReELmLitPm@phil \
--to=heiko@sntech.de \
--cc=alsa-devel@alsa-project.org \
--cc=anarsoul@gmail.com \
--cc=broonie@kernel.org \
--cc=kgene.kim@samsung.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sbkim73@samsung.com \
--cc=t.figa@samsung.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 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.