[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161219110404.cnk43zqenn2m7ib2@sirena.org.uk>
Date: Mon, 19 Dec 2016 11:04:04 +0000
From: Mark Brown <broonie@...nel.org>
To: Darren Hart <dvhart@...radead.org>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Irina Tirdea <irina.tirdea@...el.com>,
linux-clk@...r.kernel.org, "x86@...nel.org" <x86@...nel.org>,
platform-driver-x86@...r.kernel.org,
Stephen Boyd <sboyd@...eaurora.org>,
Thomas Gleixner <tglx@...utronix.de>,
Michael Turquette <mturquette@...libre.com>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
ALSA Development Mailing List <alsa-devel@...a-project.org>,
Takashi Iwai <tiwai@...e.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...el.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Len Brown <lenb@...nel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 1/3] clk: x86: Add Atom PMC platform clocks
On Fri, Dec 16, 2016 at 10:36:07AM -0800, Darren Hart wrote:
> My understanding is include/linux should be more generic, rather than platform
> specific headers. So while platform_data may refer specifically to the platform
> bus drivers, it's the closest thing we have to include/platform, which would be
> ideal. I would prefer to stick with include/platform_data because:
It's not specific to the platform bus, it's for use with the platform_data
pointer embedded in struct device that all buses can have - it's
extensively used for things like I2C and SPI for example. But really it
doesn't matter *that* much.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists