From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: jeff_chang <jeff_chang@richtek.com>,
Jeff Chang <richtek.jeff.chang@gmail.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"perex@perex.cz" <perex@perex.cz>,
"tiwai@suse.com" <tiwai@suse.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6] ASoC: Add MediaTek MT6660 Speaker Amp Driver
Date: Tue, 14 Jan 2020 14:49:45 +0000 [thread overview]
Message-ID: <20200114144945.GU3897@sirena.org.uk> (raw)
In-Reply-To: <s5hwo9uqrbu.wl-tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 495 bytes --]
On Tue, Jan 14, 2020 at 11:12:53AM +0100, Takashi Iwai wrote:
> So, for the codec, it doesn't matter at all about the signedness and
> the alingment of 32bit / 24bit of the incoming signals, but magically
> handled as is? Interesting...
On the playback side CODECs sometimes don't care that much, they
clock data in and if it stops early they just go on to the next
sample with the width being used to configure filters or
something.
The signedness is a bit more surprising I have to say :/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tiwai@suse.com" <tiwai@suse.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
Jeff Chang <richtek.jeff.chang@gmail.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
jeff_chang <jeff_chang@richtek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [alsa-devel] [PATCH v6] ASoC: Add MediaTek MT6660 Speaker Amp Driver
Date: Tue, 14 Jan 2020 14:49:45 +0000 [thread overview]
Message-ID: <20200114144945.GU3897@sirena.org.uk> (raw)
In-Reply-To: <s5hwo9uqrbu.wl-tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 495 bytes --]
On Tue, Jan 14, 2020 at 11:12:53AM +0100, Takashi Iwai wrote:
> So, for the codec, it doesn't matter at all about the signedness and
> the alingment of 32bit / 24bit of the incoming signals, but magically
> handled as is? Interesting...
On the playback side CODECs sometimes don't care that much, they
clock data in and if it stops early they just go on to the next
sample with the width being used to configure filters or
something.
The signedness is a bit more surprising I have to say :/
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tiwai@suse.com" <tiwai@suse.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
Jeff Chang <richtek.jeff.chang@gmail.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
jeff_chang <jeff_chang@richtek.com>,
"perex@perex.cz" <perex@perex.cz>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v6] ASoC: Add MediaTek MT6660 Speaker Amp Driver
Date: Tue, 14 Jan 2020 14:49:45 +0000 [thread overview]
Message-ID: <20200114144945.GU3897@sirena.org.uk> (raw)
In-Reply-To: <s5hwo9uqrbu.wl-tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 495 bytes --]
On Tue, Jan 14, 2020 at 11:12:53AM +0100, Takashi Iwai wrote:
> So, for the codec, it doesn't matter at all about the signedness and
> the alingment of 32bit / 24bit of the incoming signals, but magically
> handled as is? Interesting...
On the playback side CODECs sometimes don't care that much, they
clock data in and if it stops early they just go on to the next
sample with the width being used to configure filters or
something.
The signedness is a bit more surprising I have to say :/
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-01-14 14:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 2:22 [PATCH v6] ASoC: Add MediaTek MT6660 Speaker Amp Driver Jeff Chang
2020-01-14 2:22 ` Jeff Chang
2020-01-14 2:22 ` [alsa-devel] " Jeff Chang
2020-01-14 7:44 ` Takashi Iwai
2020-01-14 7:44 ` Takashi Iwai
2020-01-14 7:44 ` [alsa-devel] " Takashi Iwai
2020-01-14 9:48 ` jeff_chang(張世佳)
2020-01-14 10:12 ` Takashi Iwai
2020-01-14 10:12 ` Takashi Iwai
2020-01-14 10:12 ` [alsa-devel] " Takashi Iwai
2020-01-14 14:49 ` Mark Brown [this message]
2020-01-14 14:49 ` Mark Brown
2020-01-14 14:49 ` [alsa-devel] " Mark Brown
2020-01-14 12:47 ` Mark Brown
2020-01-14 12:47 ` Mark Brown
2020-01-14 12:47 ` [alsa-devel] " Mark Brown
2020-01-14 13:27 ` Takashi Iwai
2020-01-14 13:27 ` Takashi Iwai
2020-01-14 13:27 ` [alsa-devel] " Takashi Iwai
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=20200114144945.GU3897@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jeff_chang@richtek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=perex@perex.cz \
--cc=richtek.jeff.chang@gmail.com \
--cc=tiwai@suse.com \
--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.