[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151121125252.GD26072@sirena.org.uk>
Date: Sat, 21 Nov 2015 12:52:52 +0000
From: Mark Brown <broonie@...nel.org>
To: Rob Herring <robh@...nel.org>
Cc: Adam Thomson <Adam.Thomson.Opensource@...semi.com>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>, alsa-devel@...a-project.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Support Opensource <support.opensource@...semi.com>
Subject: Re: [PATCH v3 1/2] ASoC: da7218: Add bindings documentation for
DA7218 audio codec
On Fri, Nov 20, 2015 at 09:53:51AM -0600, Rob Herring wrote:
> On Thu, Nov 19, 2015 at 01:59:34PM +0000, Adam Thomson wrote:
> > +- VDD-supply: VDD power supply for the device
> > +- VDDMIC-supply: VDDMIC power supply for the device
> > +- VDDIO-supply: VDDIO power supply for the device
> These should be lower case (that is documented in ePAPR BTW :)).
Does that actually make a meaningful difference to anything? Things end
up this way because the strings we use to request the supplies end up in
the property names, we've also got a few other things like representing
microvolts as uV which just look very wrong when written all lowercase.
We could work around it for the supply names by force lowercasing the
name if we don't find the property with the passed name (to avoid
breaking existing users) though.
There's a bunch of stuff in ePAPR that we're ignoring, and a bunch of
other stuff that has no real value like the class naming stuff.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists