linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [ARM ATTEND] Clock DT bindings
Date: Thu, 15 Aug 2013 21:07:08 -0700	[thread overview]
Message-ID: <20130816040708.4443.26655@quantum> (raw)
In-Reply-To: <520D9788.5080805@codeaurora.org>

Quoting Saravana Kannan (2013-08-15 20:07:52)
> 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.

+1

Would be nice to have you in attendance Saravana. Some of these issues
also cross over into the "kernel data bloat" topic that was posted to
the list earlier.

Regards,
Mike

> 
> Thanks,
> Saravana
> 
> -- 
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> hosted by The Linux Foundation

  reply	other threads:[~2013-08-16  4:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16  3:07 [ARM ATTEND] Clock DT bindings Saravana Kannan
2013-08-16  4:07 ` Mike Turquette [this message]
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=20130816040708.4443.26655@quantum \
    --to=mturquette@linaro.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).