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: Thu, 1 May 2014 07:15:10 -0700 [thread overview]
Message-ID: <20140501141510.GW3245@sirena.org.uk> (raw)
In-Reply-To: <53623004.5010805@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On Thu, May 01, 2014 at 04:59:08PM +0530, Tushar Behera wrote:
> Okay, I will extend the existing clock driver to support XCLKOUT.
It may make more sense to add another clock driver for this clock
depending on how things are done, I don't know.
> Of the many parents of XCLKOUT, we need to set XXTI clock as the parent.
> Is it okay if we pass two clocks "mclk" (XCLKOUT) and "mclk_parent"
> (XXTI) to sound-card driver via DT and do the necessary reparenting
> during the sound-card driver probe call?
No, that's not OK at all, it won't allow for configuration of the
system. This is what I was talking about when I was talking the clock
framework extensions to allow the clock tree to be configured using DT,
that would allow the settings to be put in DT.
> Else, we can push that change to bootloader (to set the XCLKOUT mux
> register) and only enable/disable the clock in sound-card driver.
That's not going to work given that the existing bootloaders don't do
this.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-01 14:15 UTC|newest]
Thread overview: 15+ 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-23 9:01 ` 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
2014-05-01 11:29 ` Tushar Behera
2014-05-01 14:15 ` Mark Brown [this message]
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=20140501141510.GW3245@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.