[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54B574CD.9020905@ti.com>
Date: Tue, 13 Jan 2015 21:41:01 +0200
From: Jyri Sarha <jsarha@...com>
To: Russell King - ARM Linux <linux@....linux.org.uk>,
Jean-Francois Moine <moinejf@...e.fr>
CC: Philipp Zabel <p.zabel@...gutronix.de>,
Andrew Jackson <Andrew.Jackson@....com>,
Mark Brown <broonie@...nel.org>,
Dave Airlie <airlied@...il.com>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v9 1/4] drm/i2c: tda998x: Add DT support for audio
On 01/13/2015 09:26 PM, Russell King - ARM Linux wrote:
> SCLK: _~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_
> WS: __~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~________________________________~
> I2S1: llmm............................llmm............................llm
> I2S2: llmm............................llmm............................llm
> I2S3: llmm............................llmm............................llm
> I2S4: llmm............................llmm............................llm
>
> So, what I'm saying is that it is_impossible_ to drive the TDA998x using
> multiple I2S streams which are not produced by the same I2S block.
This is besides the point, but it is possible that one of the multiple
I2S blocks is the bit-clock and frame-clock master to the i2s bus and
the others are slaves to it (banging their bits according to SCLK and WS
of the I2S master). However, in this situation there really is only one
i2s bus with multiple data pins.
Just my 0.02€ to this discussion.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists