From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932680AbcLMBQO (ORCPT ); Mon, 12 Dec 2016 20:16:14 -0500 Received: from mail-oi0-f68.google.com ([209.85.218.68]:33565 "EHLO mail-oi0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932595AbcLMBQH (ORCPT ); Mon, 12 Dec 2016 20:16:07 -0500 MIME-Version: 1.0 In-Reply-To: <1a98dcda-a662-958e-307f-5fe3f281ed9f@linux.intel.com> References: <1481306510-7471-1-git-send-email-irina.tirdea@intel.com> <1481306510-7471-2-git-send-email-irina.tirdea@intel.com> <1a98dcda-a662-958e-307f-5fe3f281ed9f@linux.intel.com> From: Andy Shevchenko Date: Tue, 13 Dec 2016 03:16:05 +0200 Message-ID: Subject: Re: [PATCH v6 1/3] clk: x86: Add Atom PMC platform clocks To: Pierre-Louis Bossart Cc: Irina Tirdea , linux-clk@vger.kernel.org, "x86@kernel.org" , platform-driver-x86@vger.kernel.org, Stephen Boyd , Darren Hart , Thomas Gleixner , Michael Turquette , Ingo Molnar , "H. Peter Anvin" , ALSA Development Mailing List , Mark Brown , Takashi Iwai , Pierre-Louis Bossart , "Rafael J. Wysocki" , Len Brown , "linux-acpi@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Dec 13, 2016 at 2:15 AM, Pierre-Louis Bossart wrote: > >>> +#include > > > This was a suggestion of Darren Hart in agreement with Thomas Gleixner. > see > http://mailman.alsa-project.org/pipermail/alsa-devel/2016-October/113936.html > > Darren, did we get your proposal right? > >> Is it indeed platform data? I would not create platform_data/x86 >> without strong argument. >> Perhaps include/linux/clk/x86_pmc.h? (Yes, I know about clk-lpss.h >> which is old enough and was basically first try of clk stuff on x86) Looking more into the patch I got another question. Do we really need a platform driver for that? That's what I think motivated me for the header location. And that's why I asked about use of the driver/clock provider in the latter patch. If the answer is yes, then I doubt which location is preferable, otherwise include/clk/x86_*.h looks appropriate. Sorry if I wasn't clear in the first place. -- With Best Regards, Andy Shevchenko