All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@sirena.org.uk>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Medisetty, Naresh" <naresh@ti.com>,
	"davinci-linux-open-source@linux.davincidsp.com"
	<davinci-linux-open-source@linux.davincidsp.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 6/9] ARM: DaVinci: ASoC: Adds McASP clock	support for TI DM646X processor
Date: Thu, 19 Mar 2009 19:09:43 +0000	[thread overview]
Message-ID: <20090319190942.GA8966@sirena.org.uk> (raw)
In-Reply-To: <87ljr1l8g4.fsf@deeprootsystems.com>

On Thu, Mar 19, 2009 at 10:38:03AM -0700, Kevin Hilman wrote:

>     CLK(NULL, "mcasp0" &mcasp0_clk),
>     CLK(NULL, "mcasp1", &mcasp1_clk),

Exactly.

> The platform code can do a clk_get(<physcial name>) and pass that
> clk in with the platform data.

There should be no need to do this - the McASP DAI driver can just be a
regular platform device, probe as normal and register the DAI with the
ASoC core once it has done so.  This is, in fact, the preferred method
for doing this though support for htis is recent so only one CPU DAI
driver does it so far.

  reply	other threads:[~2009-03-19 19:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 12:11 [PATCH 6/9] ARM: DaVinci: ASoC: Adds McASP clock support for TI DM646X processor Medisetty, Naresh
2009-03-19 17:38 ` Kevin Hilman
2009-03-19 19:09   ` Mark Brown [this message]
2009-03-19 21:14     ` Kevin Hilman
2009-03-19 21:28       ` David Brownell
  -- strict thread matches above, loose matches on Subject: below --
2009-03-16 12:05 Naresh Medisetty
2009-03-16 15: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=20090319190942.GA8966@sirena.org.uk \
    --to=broonie@sirena.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=khilman@deeprootsystems.com \
    --cc=naresh@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.