From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Timur Tabi <timur@freescale.com>
Cc: alsa-devel@alsa-project.org, Shawn Guo <shawn.guo@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: fsl: enable ssi clock in probe function
Date: Thu, 29 Mar 2012 17:30:59 +0100 [thread overview]
Message-ID: <20120329163059.GW3668@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F748C8E.1010702@freescale.com>
[-- Attachment #1.1: Type: text/plain, Size: 379 bytes --]
On Thu, Mar 29, 2012 at 11:23:42AM -0500, Timur Tabi wrote:
> I do have one question though. I don't know much about the clock layer.
> When you do this:
> ssi_private->clk = clk_get(&pdev->dev, NULL);
> What clock are you getting?
The default clock - personally I much prefer always naming the clocks
even if there's one of them but more people seem to prefer this style.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: fsl: enable ssi clock in probe function
Date: Thu, 29 Mar 2012 17:30:59 +0100 [thread overview]
Message-ID: <20120329163059.GW3668@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F748C8E.1010702@freescale.com>
On Thu, Mar 29, 2012 at 11:23:42AM -0500, Timur Tabi wrote:
> I do have one question though. I don't know much about the clock layer.
> When you do this:
> ssi_private->clk = clk_get(&pdev->dev, NULL);
> What clock are you getting?
The default clock - personally I much prefer always naming the clocks
even if there's one of them but more people seem to prefer this style.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120329/ffaf352d/attachment.sig>
next prev parent reply other threads:[~2012-03-29 16:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 2:53 [PATCH] ASoC: fsl: enable ssi clock in probe function Shawn Guo
2012-03-29 2:53 ` Shawn Guo
2012-03-29 11:29 ` Mark Brown
2012-03-29 11:29 ` Mark Brown
2012-03-29 16:01 ` Timur Tabi
2012-03-29 16:01 ` Timur Tabi
2012-03-29 16:09 ` Shawn Guo
2012-03-29 16:09 ` Shawn Guo
2012-03-29 16:23 ` Timur Tabi
2012-03-29 16:23 ` Timur Tabi
2012-03-29 16:30 ` Mark Brown [this message]
2012-03-29 16:30 ` Mark Brown
2012-03-30 5:55 ` Shawn Guo
2012-03-30 5:55 ` Shawn Guo
2012-03-30 13:03 ` Timur Tabi
2012-03-30 13:03 ` Timur Tabi
2012-03-30 13:16 ` Shawn Guo
2012-03-30 13:16 ` Shawn Guo
2012-03-30 13:19 ` Timur Tabi
2012-03-30 13:19 ` Timur Tabi
2012-03-29 16:30 ` Mark Brown
2012-03-29 16:30 ` 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=20120329163059.GW3668@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=shawn.guo@linaro.org \
--cc=timur@freescale.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.