devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Rob Herring <robh@kernel.org>
Cc: Akinobu Mita <akinobu.mita@gmail.com>,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	Michael Turquette <mturquette@baylibre.com>
Subject: Re: [PATCH v2] clk: add userspace clock consumer
Date: Wed, 24 Feb 2016 14:08:19 -0800	[thread overview]
Message-ID: <20160224220819.GF4847@codeaurora.org> (raw)
In-Reply-To: <20160223214944.GA20852@rob-hp-laptop>

On 02/23, Rob Herring wrote:
> On Mon, Feb 22, 2016 at 08:48:39PM +0900, Akinobu Mita wrote:
> > This adds userspace consumer for common clock.
> > 
> > This driver is inspired from Userspace regulator consumer
> > (REGULATOR_USERSPACE_CONSUMER) and it is useful for test purposes and
> > some classes of devices that are controlled entirely from user space.
> 
> Whether the kernel handles a clock or userspace does should have nothing 
> to do with DT. Plus DT does not expose many of the clocks, so any 
> debug feature needs to expose all clocks and be independent of DT.
> 
> Beyond debug, I don't think we should be exposing clock control to 
> userspace.

Agreed. Plus, the userspace regulator consumer doesn't have any
DT binding for it, so I don't see why we would have a DT binding
for the clk one.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2016-02-24 22:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 11:48 [PATCH v2] clk: add userspace clock consumer Akinobu Mita
2016-02-23 21:49 ` Rob Herring
2016-02-24 22:08   ` Stephen Boyd [this message]
2016-02-25 14:40     ` Akinobu Mita
     [not found]       ` <CAC5umyjs_Q_G4jpcmPWk4Ug16tdwq+7c3UH1kwastj2P1UenqA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-25 23:01         ` Stephen Boyd

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=20160224220819.GF4847@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=akinobu.mita@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).