[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150113122715.GP12302@n2100.arm.linux.org.uk>
Date: Tue, 13 Jan 2015 12:27:15 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Philipp Zabel <p.zabel@...gutronix.de>
Cc: Jean-Francois Moine <moinejf@...e.fr>,
Andrew Jackson <Andrew.Jackson@....com>,
Jyri Sarha <jsarha@...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 Tue, Jan 13, 2015 at 01:21:58PM +0100, Philipp Zabel wrote:
> I wonder if it wouldn't be nicer to have the AP# and type in the device
> tree and then calculate the register value from that in the driver.
>
> port@1 {
> reg = <1>; /* AP1 */
> nxp,audio-port = "i2s";
> tda998x_i2s: endpoint {
> remote-endpoint = <&audio1_i2s>;
> };
> };
What about the case where we have 4 I2S streams being supplied to the
device on four separate AP inputs?
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
--
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