From: Stephen Boyd <sboyd@codeaurora.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
linux-clk@vger.kernel.org, x86@kernel.org,
platform-driver-x86@vger.kernel.org,
Darren Hart <dvhart@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
alsa-devel@alsa-project.org,
Irina Tirdea <irina.tirdea@intel.com>,
Michael Turquette <mturquette@baylibre.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>, Mark Brown <broonie@kernel.org>,
"H . Peter Anvin" <hpa@zytor.com>, Len Brown <lenb@kernel.org>,
Vinod Koul <vinod.koul@intel.com>
Subject: Re: [PATCH v7 0/5] Add platform clock for BayTrail platforms
Date: Fri, 20 Jan 2017 16:00:28 -0800 [thread overview]
Message-ID: <20170121000028.GG20800@codeaurora.org> (raw)
In-Reply-To: <1484736630.2133.184.camel@linux.intel.com>
On 01/18, Andy Shevchenko wrote:
> On Tue, 2017-01-17 at 15:57 -0600, Pierre-Louis Bossart wrote:
> > These patches specifically enable the audio MCLK required by Baytrail
> > CR devices. It is the remaining part of a bigger set of patches
> > (already merged in Mark Brown's tree) that enable sound for Baytrail
> > CR
> > devices (especially Asus T100TAF) [1]. They include the clock driver
> > and clock enabling in the pmc_atom code (along with moving of the
> > non-architectural pmc_atom driver code into drivers/platform/x86 as
> > suggested by Thomas Gleixner [2]). This move includes a new header in
> > include/linux/platform_data/x86/. While there is an agreement that the
> > definitions for PMC clocks are not really platform data this location
> > is seen as a good-enough compromise with an agreement between Darren
> > Hart and Andy Shevchenko [3]
> >
> > [1] http://mailman.alsa-project.org/pipermail/alsa-devel/2016-August/1
> > 11704.html
> > [2] http://mailman.alsa-project.org/pipermail/alsa-devel/2016-October/
> > 113936.html
> > [3] http://mailman.alsa-project.org/pipermail/alsa-devel/2016-December
> > /115892.html
> >
>
> Stephen, I see no issues with the patches. If you want to push them
> through your tree, take a tag from PDx86 subsystem point of view:
Does PDx86 == platform device x86? I can provide a stable branch
in clk tree for platform tree, or platform x86 maintainer can ack
the platform/x86 patches and I can take the whole batch through
clk tree.
>
> Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-01-21 0:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 21:57 [PATCH v7 0/5] Add platform clock for BayTrail platforms Pierre-Louis Bossart
2017-01-17 21:57 ` [PATCH v7 1/5] clk: Make x86/ conditional on CONFIG_COMMON_CLK Pierre-Louis Bossart
2017-01-17 21:57 ` [PATCH v7 2/5] clk: x86: Add Atom PMC platform clocks Pierre-Louis Bossart
2017-01-20 23:58 ` Stephen Boyd
2017-01-21 13:56 ` Andy Shevchenko
2017-01-21 16:28 ` [alsa-devel] " Pierre-Louis Bossart
2017-01-17 21:57 ` [PATCH v7 3/5] arch/x86/platform/atom: Move pmc_atom to drivers/platform/x86 Pierre-Louis Bossart
2017-01-18 9:28 ` Thomas Gleixner
2017-01-17 21:57 ` [PATCH v7 4/5] platform/x86: Enable Atom PMC platform clocks Pierre-Louis Bossart
2017-01-17 21:57 ` [PATCH v7 5/5] platform/x86: fix typo in comment Pierre-Louis Bossart
2017-01-18 10:50 ` [PATCH v7 0/5] Add platform clock for BayTrail platforms Andy Shevchenko
2017-01-21 0:00 ` Stephen Boyd [this message]
2017-01-21 10:53 ` Andy Shevchenko
2017-01-27 0:17 ` Stephen Boyd
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=20170121000028.GG20800@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=dvhart@infradead.org \
--cc=hpa@zytor.com \
--cc=irina.tirdea@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mturquette@baylibre.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.com \
--cc=vinod.koul@intel.com \
--cc=x86@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).