linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Turquette <mturquette@baylibre.com>
To: Mason <slash.tmp@free.fr>, "clk" <linux-clk@vger.kernel.org>
Cc: "Stephen Boyd" <sboyd@codeaurora.org>
Subject: Re: Two-output clk provider with standard clk consumer
Date: Thu, 15 Oct 2015 05:09:56 -0700	[thread overview]
Message-ID: <20151015120956.7777.63740@quantum> (raw)
In-Reply-To: <561CF3CD.8060508@free.fr>

Quoting Mason (2015-10-13 05:06:37)
> On 13/10/2015 10:59, Mason asked: [noob clk questions]
> =

> Hmmm, I'm thinking there might be a better place to ask beginner question.
> Some subsystems have a dedicated IRC channel. Does clk have one? :-)
> Or perhaps kernelnewbies? (I'll check the archive.)

Hi Mason,

Please join us in #linux-clk on freenode. And sorry for not responding
sooner. I've been traveling on business for more than one month and
Stephen has been bearing 100% of the load while I'm away.

Regarding the reliance on string names when clock-output-names is not
used, that is an on-going discussion[0] affecting multiple drivers right
now. We're trying to find a long-term solution that moves away from
string names and uses the DT hierarchy to establish parent-child
relationships.

[0] http://lkml.kernel.org/r/<20151015104326.6f7e907c@free-electrons.com>

Regards,
Mike

> =

> Regards.
>=20

  reply	other threads:[~2015-10-15 12:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13  8:59 Two-output clk provider with standard clk consumer Mason
2015-10-13 12:06 ` Mason
2015-10-15 12:09   ` Michael Turquette [this message]
2015-10-15 14:37     ` Mason

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=20151015120956.7777.63740@quantum \
    --to=mturquette@baylibre.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=slash.tmp@free.fr \
    /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).