From: Mike Turquette <mturquette@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Heiko St??bner <heiko@sntech.de>,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, Tero Kristo <t-kristo@ti.com>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
Matt Sealey <neko@bakuhatsu.net>,
Grant Likely <grant.likely@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/5] clk: dt: bindings for mux, divider & gate clocks
Date: Thu, 22 Aug 2013 23:54:17 -0700 [thread overview]
Message-ID: <20130823065417.8231.67103@quantum> (raw)
In-Reply-To: <20130823043248.GF23960@codeaurora.org>
Quoting Stephen Boyd (2013-08-22 21:32:48)
> On 08/21, Mike Turquette wrote:
> >
> > I just happened across a to-do list note telling me to respond to this
> > email. Better late than never.
> >
> [snip]
> >
> > This is a way to establish initial configuration from the consumer's
> > perspective. Similarly something can be done for the clock rate with
> > assigned-clock-rate.
>
> Ok. Thanks for the information. Unfortunately it isn't what I
> thought it was.
>
> >
> > With all of that said this is consumer-level stuff. We'll definitely
> > talk about the clock provider DT bindings at the ARM Summit, which is
> > what you discuss above.
>
> I can't wait another 2 months to start discussing the clock
> provider DT bindings. We need to discuss it on the list.
You asked what was discussed at a conference. I told you what was
discussed at that conference. As an aside I also told you what would be
discussed at an upcoming conference. At no point did I say the
discussion was tabled until then.
Regards,
Mike
>
> --
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
> hosted by The Linux Foundation
next prev parent reply other threads:[~2013-08-23 6:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 6:14 [PATCH v3 0/5] clk: dt: bindings for mux, divider & gate clocks Mike Turquette
2013-06-21 6:14 ` [PATCH v3 1/5] clk: divider: replace bitfield width with mask Mike Turquette
[not found] ` <1371795256-16703-1-git-send-email-mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-06-21 6:14 ` [PATCH v3 2/5] clk: of: helper for determining number of parent clocks Mike Turquette
2013-06-22 17:04 ` [PATCH v3 0/5] clk: dt: bindings for mux, divider & gate clocks Heiko Stübner
2013-07-18 21:04 ` Stephen Boyd
2013-08-22 4:14 ` Mike Turquette
2013-08-23 4:32 ` Stephen Boyd
2013-08-23 6:54 ` Mike Turquette [this message]
2013-06-21 6:14 ` [PATCH v3 3/5] clk: dt: binding for basic multiplexer clock Mike Turquette
2013-06-25 8:27 ` Haojian Zhuang
2013-06-25 17:40 ` Mike Turquette
2013-06-26 8:40 ` Mark Rutland
[not found] ` <20130626084058.GA10833-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-07-09 13:58 ` Mike Turquette
2013-06-21 6:14 ` [PATCH v3 4/5] clk: dt: binding for basic divider clock Mike Turquette
2013-06-21 6:14 ` [PATCH v3 5/5] clk: dt: binding for basic gate clock 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=20130823065417.8231.67103@quantum \
--to=mturquette@linaro.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=haojian.zhuang@linaro.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neko@bakuhatsu.net \
--cc=sboyd@codeaurora.org \
--cc=t-kristo@ti.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;
as well as URLs for NNTP newsgroup(s).