alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Jon Hunter <jonathanh@nvidia.com>,
	Dmitry Osipenko <digetx@gmail.com>,
	linux-tegra@vger.kernel.org, alsa-devel@alsa-project.org,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Thierry Reding <thierry.reding@gmail.com>
Cc: linux-kernel@lists.codethink.co.uk,
	Edward Cragg <edward.cragg@codethink.co.uk>
Subject: Re: [alsa-devel] [PATCH v4 3/7] ASoC: tegra: i2s: Add support for more than 2 channels
Date: Tue, 5 Nov 2019 11:58:06 +0000	[thread overview]
Message-ID: <5d069991-f5c3-ae14-da9c-9b20555be4f6@codethink.co.uk> (raw)
In-Reply-To: <d03a8fa0-3c62-1e32-9ca6-06d1996da11b@nvidia.com>

On 24/10/2019 17:11, Jon Hunter wrote:
> 
> On 17/10/2019 18:38, Dmitry Osipenko wrote:
>> 17.10.2019 19:23, Ben Dooks пишет:
>>> On 08/10/2019 16:29, Dmitry Osipenko wrote:
>>>> Hello Ben,
>> Take a look here for example:
>>
>> https://nv-tegra.nvidia.com/gitweb/?p=linux-3.10.git;a=commit;h=49834eef9d51a6eff950e0f52ddc5343d960652e
> 
> That version of the driver is known to be buggy/incorrect. I don't think
> we want to do that. We want to set the polarity based upon the format
> passed and not the mode ...
> 
> https://nv-tegra.nvidia.com/gitweb/?p=linux-nvidia.git;a=blob;f=sound/soc/tegra-alt/tegra210_i2s_alt.c;h=24cf3b55326f687aded22b91182df41c5ae188ac;hb=703aa948d2c92b87fd84f367f43a07778ed098b5#l333

Ok, thanks.

PS the security certificate on that site is still invalid :/


-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

https://www.codethink.co.uk/privacy.html
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2019-11-05 11:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07 15:31 [alsa-devel] tegra30 tdm support Ben Dooks
2019-10-07 15:31 ` [alsa-devel] [PATCH v4 1/7] ASoC: tegra: add a TDM configuration callback Ben Dooks
2019-10-07 15:31 ` [alsa-devel] [PATCH v4 2/7] ASoC: tegra: Allow 24bit and 32bit samples Ben Dooks
2019-10-07 15:31 ` [alsa-devel] [PATCH v4 3/7] ASoC: tegra: i2s: Add support for more than 2 channels Ben Dooks
2019-10-08 15:29   ` Dmitry Osipenko
2019-10-17 16:23     ` Ben Dooks
2019-10-17 17:38       ` Dmitry Osipenko
2019-10-24 16:11         ` Jon Hunter
2019-11-05 11:58           ` Ben Dooks [this message]
2019-10-07 15:31 ` [alsa-devel] [PATCH v4 4/7] ASoC: tegra: disable rx_fifo after disable stream Ben Dooks
2019-10-07 15:31 ` [alsa-devel] [PATCH v4 5/7] ASoC: tegra: set i2s_offset to 0 for tdm Ben Dooks
2019-10-07 15:31 ` [alsa-devel] [PATCH v4 6/7] ASoC: tegra: config fifos on hw_param changes Ben Dooks
2019-10-07 15:31 ` [alsa-devel] [PATCH v4 7/7] ASoC: tegra: take packing settings from the audio cif_config Ben Dooks

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=5d069991-f5c3-ae14-da9c-9b20555be4f6@codethink.co.uk \
    --to=ben.dooks@codethink.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=digetx@gmail.com \
    --cc=edward.cragg@codethink.co.uk \
    --cc=jonathanh@nvidia.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@lists.codethink.co.uk \
    --cc=linux-tegra@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=thierry.reding@gmail.com \
    --cc=tiwai@suse.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 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).