[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150107173351.GB2634@sirena.org.uk>
Date: Wed, 7 Jan 2015 17:33:51 +0000
From: Mark Brown <broonie@...nel.org>
To: Andrew Jackson <Andrew.Jackson@....com>
Cc: Jean-Francois Moine <moinejf@...e.fr>,
Russell King - ARM Linux <linux@....linux.org.uk>,
Dave Airlie <airlied@...il.com>, Jyri Sarha <jsarha@...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 Wed, Jan 07, 2015 at 05:18:20PM +0000, Andrew Jackson wrote:
> I understand your difficulty! I was just wanting something to clarify the
> meaning of the value without reference to the driver source.
> You could add something like this to your existing explanation: "The value
> describes which audio input pins are selected; this varies depending
> on chip type so consult the section on audio port configuration in the
> relevant datasheet.".
This is commonly done by just saying that the value will be written into
a given bitfield for such and such a purpose and then relying on the
chip documentation for that; it's a more direct way of saying the above.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists