public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: dts: mx28: Provide a codec clock
Date: Tue, 25 Jun 2013 10:27:59 -0700	[thread overview]
Message-ID: <20130625172759.23972.34839@quantum> (raw)
In-Reply-To: <20130625142257.GE12178@S2101-09.ap.freescale.net>

Quoting Shawn Guo (2013-06-25 07:22:58)
> On Tue, Jun 25, 2013 at 11:00:00AM -0300, Fabio Estevam wrote:
> > Since commit 9e13f345887 (ASoC: sgtl5000: Let the codec acquire its clock) it is 
> > necessary to pass a codec clock to the sgtl5000 driver.
> > 
> > Since the saif mclk cannot be passed as a real clock within the clock framework,
> > let's pass a dummy one to the codec driver.
> > 
> Why can not saif driver register the mclk to clock framework?

There are a growing number of drivers which define their own clocks. One
example can be found in drivers/media/platform/omap3isp/isp.c.

Regards,
Mike

> 
> Shawn
> 
> > The mxs-saif driver will activate the codec clock.
> > 
> > Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2013-06-25 17:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25 13:59 [PATCH 1/3] clk: mxs: clk-imx28: Provide a dummy clock Fabio Estevam
2013-06-25 14:00 ` [PATCH 2/3] ARM: dts: mx28: Provide a codec clock Fabio Estevam
2013-06-25 14:22   ` Shawn Guo
2013-06-25 17:27     ` Mike Turquette [this message]
2013-06-25 14:00 ` [PATCH 3/3] ASoC: sgtl5000: Defer probe in case of I2C error Fabio Estevam
2013-06-26  8:33   ` 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=20130625172759.23972.34839@quantum \
    --to=mturquette@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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