From: skannan@codeaurora.org (Saravana Kannan)
To: linux-arm-kernel@lists.infradead.org
Subject: [ARM ATTEND] Clock DT bindings
Date: Thu, 15 Aug 2013 20:07:52 -0700 [thread overview]
Message-ID: <520D9788.5080805@codeaurora.org> (raw)
You asked for specific topics. So, here's one:
Clock DT bindings discussion on:
* Allowing producers to export clocks by names.
* Allowing consumers to list clocks by "producer phandle, clock name".
* Should we allow for -clock magic similar to regulators?
* Should the entire clock tree be represented in DT.
I would like to attend the ARM summit to represent the needs of SoCs
with complicated clocking HW. I have worked on clocks for about 5 years
(since MSM started running Linux) and would like to throw in my opinion
on what clock DT bindings would work well, why and help come up with a
solution that works well for everyone.
Thanks,
Saravana
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next reply other threads:[~2013-08-16 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 3:07 Saravana Kannan [this message]
2013-08-16 4:07 ` [ARM ATTEND] Clock DT bindings Mike Turquette
2013-08-16 12:41 ` [Ksummit-2013-discuss] " James Hogan
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=520D9788.5080805@codeaurora.org \
--to=skannan@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).