From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org, linux-clk <linux-clk@vger.kernel.org>
Subject: Re: [RFC 4/5] WIP: clk: shmobile: r8a7795: add R clk
Date: Tue, 22 Mar 2016 17:27:10 +0100 [thread overview]
Message-ID: <20160322162707.GB14057@katana> (raw)
In-Reply-To: <CAMuHMdW0o9Po8pmJx8=xDi5VQc6ToqrENOHCOr64RffcUNPdSQ@mail.gmail.com>
> > + if (0) { /* FIXME: how to check if EXTALR rate is > 0? */
>
> Can't you just get its rate?
> Please cc linux-clk for questions like this.
I wondered if a clock provider has an easier method than simply becoming
a clock consumer of its own clock. I thought some of you might know
something. I'll have a second look. If that fails, I'll ask the clk
list, of course.
prev parent reply other threads:[~2016-03-22 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1458587984-6313-1-git-send-email-wsa@the-dreams.de>
[not found] ` <1458587984-6313-5-git-send-email-wsa@the-dreams.de>
2016-03-22 9:32 ` [RFC 4/5] WIP: clk: shmobile: r8a7795: add R clk Geert Uytterhoeven
2016-03-22 16:27 ` Wolfram Sang [this message]
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=20160322162707.GB14057@katana \
--to=wsa@the-dreams.de \
--cc=geert@linux-m68k.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.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