public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
	linux-clk@vger.kernel.org,
	"open list:OPEN FIRMWARE AND..." <devicetree@vger.kernel.org>,
	Michael Turquette <mturquette@baylibre.com>
Subject: Re: [PATCH v2] clk: add userspace clock consumer
Date: Thu, 25 Feb 2016 15:01:12 -0800	[thread overview]
Message-ID: <20160225230112.GA28849@codeaurora.org> (raw)
In-Reply-To: <CAC5umyjs_Q_G4jpcmPWk4Ug16tdwq+7c3UH1kwastj2P1UenqA@mail.gmail.com>

On 02/25, Akinobu Mita wrote:
> 2016-02-25 7:08 GMT+09:00 Stephen Boyd <sboyd@codeaurora.org>:
> > 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.
> 
> OK.  I'll drop a DT binding part of this driver.
> 
> I'll still try to expose this feature by platform device instead of
> exposing under clk debugfs.  Because we don't want to allow controlling
> all clock devices (which may result abuse of the feature).  Instead,
> this userspace consumer only allows explicitly specified devices to
> control.

I'm pretty lost on this whole patch. Is it for debug? Or is it to
put clk control into userspace? If it's for debug, why not just
keep this patch around locally and use it for debugging? If it's
for userspace clk control we need to have a larger discussion
around the concept of that (since Rob doesn't think it should be
done at all) and ABI (sysfs or ioctl?) before moving forward.

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

      reply	other threads:[~2016-02-25 23:01 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
2016-02-25 14:40     ` Akinobu Mita
2016-02-25 23:01       ` Stephen Boyd [this message]

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=20160225230112.GA28849@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