From: Mark Brown <broonie@kernel.org>
To: Tushar Behera <tushar.behera@linaro.org>
Cc: alsa-devel@alsa-project.org, linux-samsung-soc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
devicetree@vger.kernel.org, lgirdwood@gmail.com,
robh+dt@kernel.org, sbkim73@samsung.com, rdunlap@infradead.org,
dianders@chromium.org
Subject: Re: [PATCH V2] ASoC: SAMSUNG: Add sound card driver for Snow board
Date: Wed, 30 Apr 2014 11:03:14 -0700 [thread overview]
Message-ID: <20140430180314.GA3245@sirena.org.uk> (raw)
In-Reply-To: <5360E5E7.8090807@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
On Wed, Apr 30, 2014 at 05:30:39PM +0530, Tushar Behera wrote:
> XCLKOUT mux register (0x10040a00) is not part of core clock SFR range,
> rather it is part of pmu-system-controller node.
> One option would be to add a clock provider for XCLKOUT. That would
> require me to extend current clock driver to get the
> pmu-system-controller phandle which in turn is dependent on the patch to
> early initialize syscon driver.[1]
> Will it be okay to configure XCLKOUT in snow sound-card driver by taking
> the phandle of pmu-system-controller from device tree? The
> implementation is provided below.
I can't think of any reason why we'd not want to have this visible as a
clock? Ideally we don't want to have any ASoC specific clock APIs when
we're done, the reason we do at the minute is that the clock API isn't
available as standard.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-04-30 18:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 9:01 [PATCH V2] ASoC: SAMSUNG: Add sound card driver for Snow board Tushar Behera
2014-04-24 13:39 ` Mark Brown
2014-04-25 4:16 ` Tushar Behera
2014-04-29 22:29 ` Mark Brown
2014-04-30 12:00 ` Tushar Behera
2014-04-30 18:03 ` Mark Brown [this message]
2014-05-01 11:29 ` Tushar Behera
2014-05-01 14:15 ` Mark Brown
2014-05-01 15:54 ` Doug Anderson
2014-05-01 16:40 ` Mark Brown
2014-05-02 4:56 ` Tushar Behera
2014-05-02 16:56 ` Mark Brown
2014-05-19 12:06 ` Tushar Behera
2014-05-19 12:34 ` Mark Brown
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=20140430180314.GA3245@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=sbkim73@samsung.com \
--cc=tushar.behera@linaro.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).