From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Geoffrey Wossum <geoffrey@pager.net>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org,
Brett Saunders <breton.saunders@ntlworld.com>
Subject: Re: [PATCH 1/3] ASoC: Add WM8510 driver
Date: Thu, 5 Jun 2008 15:46:55 +0100 [thread overview]
Message-ID: <20080605144655.GA24582@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <200806050917.23252.geoffrey@pager.net>
On Thu, Jun 05, 2008 at 09:17:23AM -0500, Geoffrey Wossum wrote:
> On Thursday 05 June 2008 07:49:32 am Mark Brown wrote:
> > + case SNDRV_PCM_FORMAT_S32_LE:
> > + iface |= 0x0060;
> > + break;
> > + }
> This should either be changed to use SNDRV_PCM_FORMAT_S16 and friends, which I
> think will automagically use the correct endian for the selected
> architecture, or explicitly list both _LE and _BE formats. Not an issue,
It should list both. The codec really doesn't care how the data is laid
out in memory, it's up to the other end of the link to format it into
the appropriate format for the bus and there's no reason why controllers
wouldn't be able to offer byteswapping.
> unless you're using a correct endian, I mean big endian, processor like I
> am :) I would think this would need to be propagated to other CODEC drivers.
Yes - I've got a change queued up to do this which applies it uniformly
over all codec drivers (as part of some other cross-driver cleanup
work I'm still working on). For clarity it's a change which should be
applied uniformly to all codec drivers rather than over some of them
(creating confusion) so for the minute this driver does the same as all
the rest.
> Mark, were able to verify that the default value SPKMIX differs from the
> datasheet? Is this a datasheet mistake, or an issue in the WM8510 part I
> have? The full markings on the part are "WM8510G / 63AETV9", and the
> datasheet is "February 2008, Rev 4.4".
It's most likely a typo in the datasheet; I should have confirmed this
by tomorrow.
next prev parent reply other threads:[~2008-06-05 14:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 12:49 [PATCH 1/3] ASoC: Add WM8510 driver Mark Brown
[not found] ` <1212670174-19810-2-git-send-email-broonie@opensource.wolfsonmicro.com>
2008-06-05 12:49 ` [PATCH 3/3] Revised AT32 ASoC Patch Mark Brown
2008-06-05 14:17 ` [PATCH 1/3] ASoC: Add WM8510 driver Geoffrey Wossum
2008-06-05 14:46 ` Mark Brown [this message]
2008-06-06 16:12 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2008-06-05 8:54 Mark Brown
2008-06-06 10:36 ` Takashi Iwai
2008-06-04 16:33 Mark Brown
2008-06-04 16:50 ` Takashi Iwai
2008-06-04 19:24 ` Mark Brown
2008-06-04 21:38 ` Takashi Iwai
2008-06-05 8:47 ` 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=20080605144655.GA24582@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=breton.saunders@ntlworld.com \
--cc=geoffrey@pager.net \
--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 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.