From: Mark Brown <broonie@kernel•org>
To: Fabio Estevam <festevam@gmail•com>
Cc: devicetree@vger•kernel.org, alsa-devel@alsa-project•org,
lars@metafoo•de, Nicolin Chen <b42378@freescale•com>,
timur@tabi•org, rob.herring@calxeda•com, p.zabel@pengutronix•de,
Shawn Guo <shawn.guo@linaro•org>,
linuxppc-dev@lists•ozlabs.org
Subject: Re: [alsa-devel] [PATCH v4 1/2] ASoC: fsl: Add S/PDIF CPU DAI driver
Date: Tue, 13 Aug 2013 20:02:55 +0100 [thread overview]
Message-ID: <20130813190255.GF6427@sirena.org.uk> (raw)
In-Reply-To: <CAOMZO5A7noEb98yuCPY6o2mf-FikFcMYiDLpg3huPKHMO7Fwdw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 400 bytes --]
On Tue, Aug 13, 2013 at 02:58:26PM -0300, Fabio Estevam wrote:
> On Mon, Aug 12, 2013 at 9:01 AM, Nicolin Chen <b42378@freescale•com> wrote:
> > +Required properties:
> > + - compatible : Compatible list, contains "fsl,<chip>-spdif". Using general
> Can't we just use "fsl,fsl-spdif" instead?
It's better to list the specific chips in the DT so that we can quirk if
we need to later.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-13 19:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 12:01 [PATCH v4 0/2] Add freescale S/PDIF CPU DAI and machine drivers Nicolin Chen
2013-08-12 12:01 ` [PATCH v4 1/2] ASoC: fsl: Add S/PDIF CPU DAI driver Nicolin Chen
2013-08-13 17:58 ` [alsa-devel] " Fabio Estevam
2013-08-13 19:01 ` Fabio Estevam
2013-08-13 19:02 ` Mark Brown [this message]
2013-08-14 2:09 ` Nicolin Chen
2013-08-14 3:27 ` Shawn Guo
2013-08-14 5:30 ` Nicolin Chen
2013-08-14 6:39 ` Shawn Guo
2013-08-14 6:34 ` Nicolin Chen
2013-08-14 8:14 ` Shawn Guo
2013-08-14 15:47 ` Stephen Warren
2013-08-15 2:18 ` Nicolin Chen
2013-08-15 9:24 ` Shawn Guo
2013-08-16 22:49 ` Stephen Warren
2013-08-12 12:01 ` [PATCH v4 2/2] ASoC: fsl: Add S/PDIF machine driver Nicolin Chen
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=20130813190255.GF6427@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--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=p.zabel@pengutronix$(echo .)de \
--cc=rob.herring@calxeda$(echo .)com \
--cc=shawn.guo@linaro$(echo .)org \
--cc=timur@tabi$(echo .)org \
/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