From: Timur Tabi <timur@freescale.com>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: fsl: enable ssi clock in probe function
Date: Thu, 29 Mar 2012 11:23:42 -0500 [thread overview]
Message-ID: <4F748C8E.1010702@freescale.com> (raw)
In-Reply-To: <20120329160916.GG19506@S2101-09.ap.freescale.net>
Shawn Guo wrote:
> d18b63ab0b04af1bad01e59a96b88fc8cda08752
> ASoC: core: Use driver core probe deferral
That fixed it, but the SHA in my repository is
97883ef0a8f61fbd5fb8242980f6998290d1dd95
Anyway, I just want to say that for-3.5 still works on PowerPC.
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?
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: timur@freescale.com (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: fsl: enable ssi clock in probe function
Date: Thu, 29 Mar 2012 11:23:42 -0500 [thread overview]
Message-ID: <4F748C8E.1010702@freescale.com> (raw)
In-Reply-To: <20120329160916.GG19506@S2101-09.ap.freescale.net>
Shawn Guo wrote:
> d18b63ab0b04af1bad01e59a96b88fc8cda08752
> ASoC: core: Use driver core probe deferral
That fixed it, but the SHA in my repository is
97883ef0a8f61fbd5fb8242980f6998290d1dd95
Anyway, I just want to say that for-3.5 still works on PowerPC.
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?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-03-29 16:24 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 [this message]
2012-03-29 16:23 ` Timur Tabi
2012-03-29 16:30 ` Mark Brown
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=4F748C8E.1010702@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=shawn.guo@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.