From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Philippe Reynes <tremyfr@gmail.com>
Cc: shawn.guo@linaro.org, kernel@pengutronix.de,
linux@arm.linux.org.uk, a.zummo@towertech.it, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
rtc-linux@googlegroups.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
fabio.estevam@freescale.com
Subject: Re: [PATCH 1/2] rtc: mxc: add a second clock
Date: Fri, 5 Jun 2015 00:17:56 +0200 [thread overview]
Message-ID: <20150604221756.GD713@piout.net> (raw)
In-Reply-To: <5570BE33.9080103@gmail.com>
On 04/06/2015 at 23:08:03 +0200, Philippe Reynes wrote :
> >You are getting the rate but don't you need to clk_prepare_enable()?
>
> This IP needs the clock reference rate for his configuration,
> so I think that I only need the rate.
>
I think we need to check whether we are guaranteed to get a result from
get_rate even if the clock is not enabled.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-04 22:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 22:35 [PATCH 0/2] add dt support for mxc rtc Philippe Reynes
2015-05-15 22:35 ` [PATCH 1/2] rtc: mxc: add a second clock Philippe Reynes
2015-05-18 11:27 ` Enrico Weigelt, metux IT consult
2015-05-18 21:57 ` Philippe Reynes
2015-05-19 5:27 ` Shawn Guo
2015-05-28 11:57 ` Alexandre Belloni
2015-06-04 21:08 ` Philippe Reynes
2015-06-04 22:17 ` Alexandre Belloni [this message]
2015-05-15 22:35 ` [PATCH 2/2] rtc: mxc: add support of device tree Philippe Reynes
2015-05-28 12:06 ` Alexandre Belloni
2015-06-04 21:26 ` Philippe Reynes
2015-06-04 22:22 ` Alexandre Belloni
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=20150604221756.GD713@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@freescale.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=shawn.guo@linaro.org \
--cc=tremyfr@gmail.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