public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: Mark Rutland <mark.rutland@arm•com>
Cc: "devicetree@vger•kernel.org" <devicetree@vger•kernel.org>,
	"alsa-devel@alsa-project•org" <alsa-devel@alsa-project•org>,
	"lars@metafoo•de" <lars@metafoo•de>,
	"swarren@wwwdotorg•org" <swarren@wwwdotorg•org>,
	"festevam@gmail•com" <festevam@gmail•com>,
	"s.hauer@pengutronix•de" <s.hauer@pengutronix•de>,
	Nicolin Chen <b42378@freescale•com>,
	"timur@tabi•org" <timur@tabi•org>,
	"rob.herring@calxeda•com" <rob.herring@calxeda•com>,
	"tomasz.figa@gmail•com" <tomasz.figa@gmail•com>,
	"p.zabel@pengutronix•de" <p.zabel@pengutronix•de>,
	"R65777@freescale•com" <R65777@freescale•com>,
	"shawn.guo@linaro•org" <shawn.guo@linaro•org>,
	"linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>
Subject: Re: [PATCH v7 2/2] ASoC: fsl: Add S/PDIF machine driver
Date: Mon, 19 Aug 2013 12:45:22 +0100	[thread overview]
Message-ID: <20130819114522.GC30073@sirena.org.uk> (raw)
In-Reply-To: <20130819113121.GL3719@e106331-lin.cambridge.arm.com>

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

On Mon, Aug 19, 2013 at 12:31:21PM +0100, Mark Rutland wrote:
> On Mon, Aug 19, 2013 at 11:52:01AM +0100, Mark Brown wrote:

> > This is intended to allow userspace to distinguish between systems that
> > are electrically identical but physically distinct, for example when
> > multiple systems are derived from the same reference design.

> I see. Surely if there's some meaning imparted to userspace by the model
> name, there's a contract there that we should document (the set of valid
> model names and what they correspond to)?

In theory I guess.  In practice I doubt many people will bother and I'd
expect zero productive result from those that do.

> I'm not sure I understand why userspace needs to know what the system is
> if we've adequately described how it's wired and what its capabilities
> are. However, I'm not at all familiar with the way we handle audio, so
> please forgive my naivety there :)

The physical form of the system can have a substantial impact on how
people want to configure it at runtime even if there is no software
visible difference.  Coefficients can be chosen to work with plastics,
or volumes adjusted for expected user positioning with respect to the
hardware for example.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-08-19 11:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19  8:35 [PATCH v7 0/2] Add freescale S/PDIF CPU DAI and machine drivers Nicolin Chen
2013-08-19  8:35 ` [PATCH v7 1/2] ASoC: fsl: Add S/PDIF CPU DAI driver Nicolin Chen
2013-08-19  9:18   ` Mark Rutland
2013-08-19  9:34     ` Nicolin Chen
2013-08-19  9:54       ` Mark Rutland
2013-08-19 10:13         ` Nicolin Chen
2013-08-19 11:13           ` Mark Rutland
2013-08-19 11:34             ` Nicolin Chen
2013-08-20  8:47               ` Mark Rutland
2013-08-20  5:19         ` Shawn Guo
2013-08-20  8:54           ` Mark Rutland
2013-08-20 16:28           ` Stephen Warren
2013-08-19  8:35 ` [PATCH v7 2/2] ASoC: fsl: Add S/PDIF machine driver Nicolin Chen
2013-08-19  9:24   ` Mark Rutland
2013-08-19  9:50     ` Nicolin Chen
2013-08-19 10:01       ` Mark Rutland
2013-08-19 10:21         ` Nicolin Chen
2013-08-19 11:15           ` Mark Rutland
2013-08-19 10:27         ` Philipp Zabel
2013-08-19 10:52         ` Mark Brown
2013-08-19 11:31           ` Mark Rutland
2013-08-19 11:45             ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130819114522.GC30073@sirena.org.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=R65777@freescale$(echo .)com \
    --cc=alsa-devel@alsa-project$(echo .)org \
    --cc=b42378@freescale$(echo .)com \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=festevam@gmail$(echo .)com \
    --cc=lars@metafoo$(echo .)de \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mark.rutland@arm$(echo .)com \
    --cc=p.zabel@pengutronix$(echo .)de \
    --cc=rob.herring@calxeda$(echo .)com \
    --cc=s.hauer@pengutronix$(echo .)de \
    --cc=shawn.guo@linaro$(echo .)org \
    --cc=swarren@wwwdotorg$(echo .)org \
    --cc=timur@tabi$(echo .)org \
    --cc=tomasz.figa@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox