From: Jyri Sarha <jsarha@TI.COM>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, bcousson@baylibre.com,
peter.ujfalusi@TI.COM, liam.r.girdwood@linux.intel.com,
detheridge@TI.COM
Subject: Re: [PATCH 3/3] ASoC: simple-card: Add system-clock-id DT parameter to dai nodes
Date: Tue, 24 Jun 2014 12:59:20 +0300 [thread overview]
Message-ID: <53A94BF8.4090808@ti.com> (raw)
In-Reply-To: <20140621100959.GC5099@sirena.org.uk>
On 06/21/2014 01:09 PM, Mark Brown wrote:
> On Fri, Jun 13, 2014 at 01:04:38PM +0300, Jyri Sarha wrote:
>> Select clk_id parameters for set_sysclk calls in the card init phase.
>
> This is making the ID defined by the drivers into ABI. It's not clear
> that this is something we want to do, and we certainly don't want to do
> it without updating the driver bindings. In principle what we want to
> do here is have our clocks handled by the clock API, though that's not
> trivial work.
>
I see, actually this is not something I would need anytime soon, but
how about the previous "Add system-clock-direction DT parameter to dai
nodes" patch?
There is a clear common definitions for clock direction, so this should
be ok, right?
If the clock direction patch would go in I would not need to add more
stuff to already quite messy davinci-evm driver.
Best regards,
Jyri
next prev parent reply other threads:[~2014-06-24 9:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 10:04 [PATCH 0/3] More simple-card dai node clock parameters Jyri Sarha
2014-06-13 10:04 ` [PATCH 1/3] ASoC: simple-card: Make u32 DT parameter handling 64-bit proof Jyri Sarha
2014-06-21 10:07 ` Mark Brown
2014-06-13 10:04 ` [PATCH 2/3] ASoC: simple-card: Add system-clock-direction DT parameter to dai nodes Jyri Sarha
2014-06-13 10:04 ` [PATCH 3/3] ASoC: simple-card: Add system-clock-id " Jyri Sarha
2014-06-13 12:24 ` satish kumar
2014-06-21 10:09 ` Mark Brown
2014-06-24 9:59 ` Jyri Sarha [this message]
2014-06-24 10:20 ` 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=53A94BF8.4090808@ti.com \
--to=jsarha@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=bcousson@baylibre.com \
--cc=broonie@kernel.org \
--cc=detheridge@TI.COM \
--cc=devicetree@vger.kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@TI.COM \
/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.