From: Mark Brown <broonie@kernel.org>
To: Xiubo Li <Li.Xiubo@freescale.com>
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.de,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: soc-core: add snd_soc_of_parse_sysclk_id() for dt
Date: Tue, 7 Jan 2014 16:24:47 +0000 [thread overview]
Message-ID: <20140107162447.GX31886@sirena.org.uk> (raw)
In-Reply-To: <1388648057-28373-1-git-send-email-Li.Xiubo@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
On Thu, Jan 02, 2014 at 03:34:17PM +0800, Xiubo Li wrote:
> This patch adds snd_soc_of_parse_sysclk_id() and supports below
> style on dt:
>
> sysclk-id = <XXX>;
>
> It's an optional property, If this property is absent the defualt
> vaule 0 will be returned.
The trick with this is defining what the clock should be. Drivers would
have to start defining their clock IDs and then at some point we end up
reinventing the common clock API and bindings. We really ought to be
moving ASoC's clock handling over towards clk but there's issues with
that given that the clock API is not available at all on some platforms
and the common clock API isn't common. This is rather a larger bit of
work than I expect you want to do right now though...
What's your use case for this - is it possible to make the driver you're
looking at default to a clock that'll work for most systems? That'd
sidestep the need to say which clock. Alternatively is the CODEC only
likely to be used with systems supporting common clk in which case doing
the sysclk configuration via the clk API might be the way forwards?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-01-07 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 7:34 Xiubo Li
2014-01-07 16:24 ` Mark Brown [this message]
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=20140107162447.GX31886@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Li.Xiubo@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®