From: Mark Brown <broonie@kernel.org>
To: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
Cc: Philip Balister <philip@balister.org>,
Saravana Kannan <skannan@codeaurora.org>,
linux-arm-kernel@lists.infradead.org,
Mike Turquette <mturquette@linaro.org>,
linux-kernel@vger.kernel.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH RFC] clk: Introduce userspace clock driver
Date: Fri, 17 May 2013 12:02:41 +0100 [thread overview]
Message-ID: <20130517110241.GI1627@sirena.org.uk> (raw)
In-Reply-To: <1b69c011-cab5-4fde-a61d-7e2536208920@CH1EHSMHS003.ehs.local>
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
On Thu, May 16, 2013 at 11:55:45AM -0700, Sören Brinkmann wrote:
> On Thu, May 16, 2013 at 06:26:05PM +0100, Mark Brown wrote:
> > The binding should obviously be defined as a set of clocks rather than a
> > single clock - something like how we specify regulators on PMICs
> > probably makes sense. Each clock can have its own properties.
> For a device driver as clock consumer, the bindings etc. are well
> defined. Just add the 'clocks' and 'clock-names' props and use the CCF.
That's not really intended to be used for enumeration by the child,
though - you'd at least need to define that the child looks through
the same binding to figure out what clocks to request.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-05-17 11:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 17:31 [PATCH RFC] User space " Soren Brinkmann
2013-05-10 17:31 ` [PATCH RFC] clk: Introduce userspace " Soren Brinkmann
2013-05-10 17:44 ` Emilio López
2013-05-10 18:15 ` Sören Brinkmann
2013-05-10 18:49 ` Emilio López
2013-05-10 22:18 ` Mike Turquette
2013-05-10 23:01 ` Saravana Kannan
2013-05-10 23:06 ` Sören Brinkmann
2013-05-10 23:25 ` Saravana Kannan
2013-05-10 23:36 ` Sören Brinkmann
2013-05-11 14:21 ` Mark Brown
2013-05-16 4:23 ` Saravana Kannan
2013-05-16 18:21 ` Mark Brown
2013-05-10 23:08 ` Sören Brinkmann
2013-05-13 8:31 ` Peter De Schrijver
[not found] ` <CAHp75Vcr10d=XesGQvrC_v+ijdp3nK+m=w5E7d6GCo1Z9ogWnw@mail.gmail.com>
2013-05-10 18:03 ` Sören Brinkmann
2013-05-10 21:24 ` Mark Brown
2013-05-11 16:54 ` Sören Brinkmann
2013-05-12 14:33 ` Mark Brown
2013-05-12 19:05 ` Sören Brinkmann
2013-05-13 5:21 ` Mark Brown
2013-05-13 16:09 ` Sören Brinkmann
2013-05-13 16:21 ` Sebastian Hesselbarth
2013-05-13 17:24 ` Sören Brinkmann
2013-05-13 17:37 ` Sebastian Hesselbarth
2013-05-13 17:58 ` Sören Brinkmann
2013-05-13 18:18 ` Sebastian Hesselbarth
2013-05-14 16:46 ` Mike Turquette
2013-05-14 18:09 ` Philip Balister
2013-05-15 4:46 ` Mark Brown
2013-05-16 4:28 ` Saravana Kannan
2013-05-16 14:44 ` Philip Balister
2013-05-16 17:26 ` Mark Brown
2013-05-16 18:55 ` Sören Brinkmann
2013-05-17 11:02 ` Mark Brown [this message]
2013-05-13 18:16 ` Mark Brown
2013-05-13 18:20 ` Sebastian Hesselbarth
2013-05-13 18:44 ` Mark Brown
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=20130517110241.GI1627@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=philip@balister.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=skannan@codeaurora.org \
--cc=soren.brinkmann@xilinx.com \
/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
all inboxes | Powered by JetHome®