public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: boris.brezillon@free-electrons.com (Boris BREZILLON)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/6] Per-user clock constraints
Date: Wed, 13 Aug 2014 11:46:18 +0200	[thread overview]
Message-ID: <20140813114618.2466ade6@bbrezillon> (raw)
In-Reply-To: <1407333368-31979-1-git-send-email-tomeu.vizoso@collabora.com>

Hi Tomeu,

Sorry for the late reply.

On Wed,  6 Aug 2014 15:56:03 +0200
Tomeu Vizoso <tomeu.vizoso@collabora.com> wrote:

> Hi,
> 
> in this v5 of the patchset I have just moved the storage of the clock constraints to the struct clk, as suggested by Stephen. Follows the original cover letter blurb:
> 
> I'm retaking Rabin's patches [0] for splitting the clk API in two: one API for
> clk consumers and another for providers. The consumer API uses a clk structure
> that just keeps track of the consumer and has a reference to the actual
> clk_core struct, which is used internally.
> 
> I have kept a patch from Rabin that aims to aid in debugging nested
> enable/disable calls, though my personal aim is to allow more than one consumer
> to influence the final, effective frequency rate. For now this is limited to
> setting floor and ceiling constraints, with the short-term aim of allowing
> devfreq and thermal drivers to set floor and ceiling frequencies on the memory
> clock, respectively.
> 
> For those functions in the consumer clk API that were called from providers, I
> have added variants to clk-provider.h that are the same only that accept a
> clk_core instead. These functions are prefixed with clk_provider_.
> 
> Patch 1/6 just adds a bunch of defines with the goal of having all the renames
> in their own commit while preserving git-bisectability, with patch 3/6
> containing the rename itself as generated by the Coccinelle script in [1].
> Patch 2/6 is needed because sound/soc/mxs/mxs-saif.c calls both the consumer
> and the provider API. The actual implementation of the API split comes in patch
> 4/6. I will be happy to organize the refactoring differently if anybody has a
> better idea.
> 
> Patch 5/6 warns when there's an unbalanced usage of the enable and disable
> APIs, and patch 6/6 adds the API for setting floor and ceiling frequencies, per
> consumer.

I tested your patch series on an at91 platform (sama5d3), and it works
as expected, but I had to fix some conflicts when applying your patches
on clk-next, and then got a few errors at compile time.

Anyway here is my branch with all those conflicts resolved: [1]. The
last commit [2] fixes the build errors (I'll let you squash/split the
changes as you wish).

Best Regards,

Boris

[1]https://github.com/bbrezillon/linux-at91/tree/per-clk-contraints
[2]https://github.com/bbrezillon/linux-at91/commit/d366c37dcfa5f06de3e27fc3c2807017bece9a2f

-- 
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2014-08-13  9:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06 13:56 [PATCH v5 0/6] Per-user clock constraints Tomeu Vizoso
2014-08-06 13:56 ` [PATCH v5 1/6] clk: Add temporary mapping to the existing API Tomeu Vizoso
2014-08-06 13:56 ` [PATCH v5 2/6] ASoC: mxs-saif: fix mixed use of public and provider clk API Tomeu Vizoso
2014-08-06 13:56 ` [PATCH v5 4/6] clk: use struct clk only for external API Tomeu Vizoso
2014-08-06 13:56 ` [PATCH v5 5/6] clk: per-user clock accounting for debug Tomeu Vizoso
2014-08-06 13:56 ` [PATCH v5 6/6] clk: Add floor and ceiling constraints to clock rates Tomeu Vizoso
2014-08-07 17:27   ` Stephen Warren
2014-08-13  9:46 ` Boris BREZILLON [this message]
2014-08-14 12:07   ` [PATCH v5 0/6] Per-user clock constraints Tomeu Vizoso
2014-08-14 15:54     ` Mike Turquette

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=20140813114618.2466ade6@bbrezillon \
    --to=boris.brezillon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox