[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171023082114.qxngdzkm42v7dzzi@sirena.org.uk>
Date: Mon, 23 Oct 2017 09:21:14 +0100
From: Mark Brown <broonie@...nel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
Cc: Vinod Koul <vinod.koul@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>,
ALSA <alsa-devel@...a-project.org>, Takashi <tiwai@...e.de>,
Sanyog Kale <sanyog.r.kale@...el.com>,
Shreyas NC <shreyas.nc@...el.com>, patches.audio@...el.com,
alan@...ux.intel.com,
Charles Keepax <ckeepax@...nsource.cirrus.com>,
Sagar Dharia <sdharia@...eaurora.org>,
srinivas.kandagatla@...aro.org, plai@...eaurora.org,
Sudheer Papothi <spapothi@...eaurora.org>, mark.rutland@....com
Subject: Re: [alsa-devel] [PATCH 01/14] Documentation: Add SoundWire summary
On Sun, Oct 22, 2017 at 03:36:32PM +0530, Pierre-Louis Bossart wrote:
> On 10/21/17 4:58 PM, Vinod Koul wrote:
> > On Sat, Oct 21, 2017 at 09:57:44AM +0100, Mark Brown wrote:
> > > There's lots of perfectly normal nouns in this document like Slave here
> > > which are randomly capitalized. Is there some great reason for this?
> > > It makes the document pretty distracting to read.
> > Slave, SoundWire etc are MIPI definitions hence capitalized.
> I insisted to follow the conventions in the specification, it's not random
> at all.
It's making it pretty painful to read as kernel documentation.
> We can put together a DT binding document that follows the Disco spec but
> it'd be a bad idea to change the definitions or come up with new ones...
Given that there's a goal to do this via the device property stuff with
the apparent goal that we also use this stuff for DT it should at least
be run past some DT people. It may be that everything is totally fine as
is but we should at least check.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists