From: Nicolin Chen <b42378@freescale.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Shawn Guo <shawn.guo@linaro.org>,
Fabio Estevam <festevam@gmail.com>,
broonie@kernel.org, lars@metafoo.de, p.zabel@pengutronix.de,
devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
linuxppc-dev@lists.ozlabs.org, timur@tabi.org,
rob.herring@calxeda.com
Subject: Re: [alsa-devel] [PATCH v4 1/2] ASoC: fsl: Add S/PDIF CPU DAI driver
Date: Thu, 15 Aug 2013 10:18:23 +0800 [thread overview]
Message-ID: <20130815021823.GA1846@MrMyself> (raw)
In-Reply-To: <520BA687.4030905@wwwdotorg.org>
Hi Stephen,
On Wed, Aug 14, 2013 at 09:47:19AM -0600, Stephen Warren wrote:
> If the clock source name list is different, then it needs a different
> compatible value, so that each compatible value can specify which clock
> names are required.
>
> Also, the compatible value itself should always include the exact HW
> that's present (most specific HW version), as well as any other HW it's
> compatible with.
Thank you for the comments. Yes, I did so in v1-v3, but after rethinking
about the situation (Actually both the HW version and the clock mux itself
are same, just the clock sources connecting to the mux might be different),
so I decided to do this by abstracting the driver from those source info
and letting DT binding to pass such information. Because I think putting
the clock sources into the driver differed by compatible value would make
the driver more like SoC-specified, not the ideal way -- SoC-independent,
since the clock sources are based on SoC design, not on itself.
Thank you,
Nicolin Chen
next prev parent reply other threads:[~2013-08-15 2:27 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
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 [this message]
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=20130815021823.GA1846@MrMyself \
--to=b42378@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=lars@metafoo.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=p.zabel@pengutronix.de \
--cc=rob.herring@calxeda.com \
--cc=shawn.guo@linaro.org \
--cc=swarren@wwwdotorg.org \
--cc=timur@tabi.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).