From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Nicolin Chen <nicoleotsuka@gmail.com>,
lgirdwood@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com,
bardliao@realtek.com, oder_chiou@realtek.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org, Darren Hart <dvhart@linux.intel.com>
Subject: Re: [PATCH] ASoC: rt5659: Add mclk controls
Date: Fri, 29 Jul 2016 21:45:21 +0530 [thread overview]
Message-ID: <20160729161521.GL9681@localhost> (raw)
In-Reply-To: <20160728185510.GK11806@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
On Thu, Jul 28, 2016 at 07:55:10PM +0100, Mark Brown wrote:
> On Thu, Jul 28, 2016 at 11:14:20AM -0700, Nicolin Chen wrote:
> > On Thu, Jul 28, 2016 at 04:57:32PM +0100, Mark Brown wrote:
>
> > > This device seems to be used on x86 systems so we'll need to ensure that
> > > they register clocks for this. They really should set this up using
> > > quirks keyed off DMI information or similar so it's hidden from other
> > > systems.
>
> > Hmm..the change defines this mclk as a optional property so I'm
> > not sure how it would affect x86 systems. (Would love to refine
>
> Ah, clk_prepare_enable() silently ignores NULL as an argument? It is a
> bit messy to do things that way but might be the most practical thing.
>
> > it to make it impactless.) Since it's literally hidden, any way
> > that I can manually ensure it? Or just wait for an ack from x86
> > developers?
>
> Hopefully they'll speak up - we're in the merge window anyway so it'll
> be just over a week before this can go into -next.
Yeah I am not aware of any plan to have clks on x86. For audio we are not
going to use much. ACPI and controller w/ firmware does the job.
I have added Darren, he oversee platform things so might know if clocks
would be there in future..
Thanks
--
~Vinod
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-29 16:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 23:02 [PATCH] ASoC: rt5659: Add mclk controls Nicolin Chen
[not found] ` <1469660568-3511-1-git-send-email-nicoleotsuka-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-07-28 15:57 ` Mark Brown
[not found] ` <20160728155732.GG11806-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-07-28 18:14 ` Nicolin Chen
2016-07-28 18:55 ` Mark Brown
2016-07-28 19:03 ` Nicolin Chen
2016-07-29 16:15 ` Vinod Koul [this message]
2016-07-29 16:39 ` Mark Brown
[not found] ` <20160729163933.GJ10376-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-07-29 16:55 ` [alsa-devel] " Vinod Koul
2016-08-10 13:57 ` Pierre-Louis Bossart
2016-08-10 17:06 ` Mark Brown
2016-08-10 17:31 ` Pierre-Louis Bossart
2016-08-10 17:52 ` Mark Brown
2016-08-10 21:59 ` [alsa-devel] " Pierre-Louis Bossart
[not found] ` <ff13c01a-a3f5-b11f-c342-926e98f64be3-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-08-11 11:34 ` Mark Brown
2016-07-28 20:40 ` Lars-Peter Clausen
[not found] ` <579A6DCC.6060401-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
2016-07-28 20:51 ` Nicolin Chen
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=20160729161521.GL9681@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dvhart@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nicoleotsuka@gmail.com \
--cc=oder_chiou@realtek.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).