All of lore.kernel.org
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: topology: Allow to set the frequency through a clock
Date: Tue, 10 Jun 2014 13:47:52 +0200	[thread overview]
Message-ID: <20140610114752.GL9791@lukather> (raw)
In-Reply-To: <1400700796-5763-1-git-send-email-maxime.ripard@free-electrons.com>

On Wed, May 21, 2014 at 09:33:14PM +0200, Maxime Ripard wrote:
> Hi,
> 
> This patch series add the possibility for the topology code to get the
> CPU frequency through a DT clock handle instead of needing a
> clock-frequency property.
> 
> Indeed, this information can be quite redundant if the clock tree
> defined in the DT is already describing the CPU parent clock.

Ping?

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140610/ef04c7d7/attachment.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Russell King <linux@arm.linux.org.uk>, Arnd Bergmann <arnd@arndb.de>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>, Nicolas Pitre <nico@linaro.org>
Subject: Re: [PATCH 0/2] ARM: topology: Allow to set the frequency through a clock
Date: Tue, 10 Jun 2014 13:47:52 +0200	[thread overview]
Message-ID: <20140610114752.GL9791@lukather> (raw)
In-Reply-To: <1400700796-5763-1-git-send-email-maxime.ripard@free-electrons.com>

[-- Attachment #1: Type: text/plain, Size: 502 bytes --]

On Wed, May 21, 2014 at 09:33:14PM +0200, Maxime Ripard wrote:
> Hi,
> 
> This patch series add the possibility for the topology code to get the
> CPU frequency through a DT clock handle instead of needing a
> clock-frequency property.
> 
> Indeed, this information can be quite redundant if the clock tree
> defined in the DT is already describing the CPU parent clock.

Ping?

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2014-06-10 11:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 19:33 [PATCH 0/2] ARM: topology: Allow to set the frequency through a clock Maxime Ripard
2014-05-21 19:33 ` Maxime Ripard
2014-05-21 19:33 ` [PATCH 1/2] ARM: topology: Use a clock if possible to get the CPU frequency Maxime Ripard
2014-05-21 19:33   ` Maxime Ripard
2014-05-21 19:33   ` Maxime Ripard
2014-05-21 19:33 ` [PATCH 2/2] ARM: sunxi: Add clocks node to the CPU nodes Maxime Ripard
2014-05-21 19:33   ` Maxime Ripard
2014-05-21 19:33   ` Maxime Ripard
2014-06-10 11:47 ` Maxime Ripard [this message]
2014-06-10 11:47   ` [PATCH 0/2] ARM: topology: Allow to set the frequency through a clock Maxime Ripard

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=20140610114752.GL9791@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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.