All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <egtvedt@samfundet.no>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Russell King <linux@arm.linux.org.uk>,
	Haavard Skinnemoen <hskinnemoen@gmail.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Guan Xuetao <gxt@mprc.pku.edu.cn>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-mips@linux-mips.org,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] clk: Make the generic clock API available by default
Date: Wed, 29 Aug 2012 07:56:25 +0200	[thread overview]
Message-ID: <20120829055625.GA17753@samfundet.no> (raw)
In-Reply-To: <1346186104-4083-1-git-send-email-broonie@opensource.wolfsonmicro.com>

Around Tue 28 Aug 2012 13:35:04 -0700 or thereabout, Mark Brown wrote:
> Rather than requiring platforms to select the generic clock API to make
> it available make the API available as a user selectable option unless the
> user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
> or selects COMMON_CLK (if they depend on the generic implementation).
> 
> All current architectures that HAVE_CLK but don't use the common clock
> framework have selects of HAVE_CUSTOM_CLK added.
> 
> This allows drivers to use the generic API on platforms which have no need
> for the clock API at platform level.
> 
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> 
> This depends on having one of the patches I've sent adding a generic
> clkdev.h added merged - Arnd was expecting to merge one of those, there
> was just the lack of clarity about the most practical Kbuild hookup.
> 
>  arch/arm/Kconfig            |   12 ++++++++++++
>  arch/avr32/Kconfig          |    1 +

For the AVR32 related changes

Acked-by: Hans-Christian Egtvedt <egtvedt@samfundet.no>

<snipp>

-- 
mvh
Hans-Christian Egtvedt

WARNING: multiple messages have this Message-ID (diff)
From: Hans-Christian Egtvedt <egtvedt@samfundet.no>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-mips@linux-mips.org, Russell King <linux@arm.linux.org.uk>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
	Paul Mackerras <paulus@samba.org>,
	Guan Xuetao <gxt@mprc.pku.edu.cn>,
	linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org,
	Haavard Skinnemoen <hskinnemoen@gmail.com>
Subject: Re: [PATCH] clk: Make the generic clock API available by default
Date: Wed, 29 Aug 2012 07:56:25 +0200	[thread overview]
Message-ID: <20120829055625.GA17753@samfundet.no> (raw)
In-Reply-To: <1346186104-4083-1-git-send-email-broonie@opensource.wolfsonmicro.com>

Around Tue 28 Aug 2012 13:35:04 -0700 or thereabout, Mark Brown wrote:
> Rather than requiring platforms to select the generic clock API to make
> it available make the API available as a user selectable option unless the
> user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
> or selects COMMON_CLK (if they depend on the generic implementation).
> 
> All current architectures that HAVE_CLK but don't use the common clock
> framework have selects of HAVE_CUSTOM_CLK added.
> 
> This allows drivers to use the generic API on platforms which have no need
> for the clock API at platform level.
> 
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> 
> This depends on having one of the patches I've sent adding a generic
> clkdev.h added merged - Arnd was expecting to merge one of those, there
> was just the lack of clarity about the most practical Kbuild hookup.
> 
>  arch/arm/Kconfig            |   12 ++++++++++++
>  arch/avr32/Kconfig          |    1 +

For the AVR32 related changes

Acked-by: Hans-Christian Egtvedt <egtvedt@samfundet.no>

<snipp>

-- 
mvh
Hans-Christian Egtvedt

WARNING: multiple messages have this Message-ID (diff)
From: egtvedt@samfundet.no (Hans-Christian Egtvedt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: Make the generic clock API available by default
Date: Wed, 29 Aug 2012 07:56:25 +0200	[thread overview]
Message-ID: <20120829055625.GA17753@samfundet.no> (raw)
In-Reply-To: <1346186104-4083-1-git-send-email-broonie@opensource.wolfsonmicro.com>

Around Tue 28 Aug 2012 13:35:04 -0700 or thereabout, Mark Brown wrote:
> Rather than requiring platforms to select the generic clock API to make
> it available make the API available as a user selectable option unless the
> user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
> or selects COMMON_CLK (if they depend on the generic implementation).
> 
> All current architectures that HAVE_CLK but don't use the common clock
> framework have selects of HAVE_CUSTOM_CLK added.
> 
> This allows drivers to use the generic API on platforms which have no need
> for the clock API at platform level.
> 
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> 
> This depends on having one of the patches I've sent adding a generic
> clkdev.h added merged - Arnd was expecting to merge one of those, there
> was just the lack of clarity about the most practical Kbuild hookup.
> 
>  arch/arm/Kconfig            |   12 ++++++++++++
>  arch/avr32/Kconfig          |    1 +

For the AVR32 related changes

Acked-by: Hans-Christian Egtvedt <egtvedt@samfundet.no>

<snipp>

-- 
mvh
Hans-Christian Egtvedt

  reply	other threads:[~2012-08-29  6:01 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-28 20:35 [PATCH] clk: Make the generic clock API available by default Mark Brown
2012-08-28 20:35 ` Mark Brown
2012-08-28 20:35 ` Mark Brown
2012-08-29  5:56 ` Hans-Christian Egtvedt [this message]
2012-08-29  5:56   ` Hans-Christian Egtvedt
2012-08-29  5:56   ` Hans-Christian Egtvedt
2012-08-29 21:49 ` Stephen Warren
2012-08-29 21:49   ` Stephen Warren
2012-08-29 21:49   ` Stephen Warren
2012-08-30 17:19   ` Mark Brown
2012-08-30 17:19     ` Mark Brown
2012-08-30 17:19     ` Mark Brown
2012-08-30 23:40     ` Stephen Warren
2012-08-30 23:40       ` Stephen Warren
2012-08-30 23:40       ` Stephen Warren
2012-09-05  2:03 ` Benjamin Herrenschmidt
2012-09-05  2:03   ` Benjamin Herrenschmidt
2012-09-05  2:03   ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2012-10-22 13:02 Mark Brown
2012-10-22 13:02 ` Mark Brown
2012-10-22 13:05 ` Russell King - ARM Linux
2012-10-22 13:05   ` Russell King - ARM Linux
2012-10-22 13:27   ` Mark Brown
2012-10-22 13:27     ` Mark Brown
2012-10-22 13:50     ` Russell King - ARM Linux
2012-10-22 13:50       ` Russell King - ARM Linux
2012-10-22 13:54       ` Mark Brown
2012-10-22 13:54         ` Mark Brown
2012-10-22 15:56 ` Stephen Warren
2012-10-22 15:56   ` Stephen Warren
2012-10-23  9:47   ` Mark Brown
2012-10-23  9:47     ` Mark Brown
2012-10-23  2:10 ` Kelvin Cheung
2012-10-23  9:22   ` Mark Brown
2012-10-23  9:22     ` Mark Brown
2012-10-23  9:54 Mark Brown
2012-10-23  9:54 ` Mark Brown
2012-11-26 21:39 ` Grant Likely
2012-11-26 21:39   ` Grant Likely
2012-11-26 21:39   ` Grant Likely

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=20120829055625.GA17753@samfundet.no \
    --to=egtvedt@samfundet.no \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=hskinnemoen@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux@arm.linux.org.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    --cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.