From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Fabio Estevam <festevam@gmail.com>
Cc: Olof Johansson <olof@lixom.net>,
linux-mmc@vger.kernel.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
robh+dt@kernel.org, Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <pawel.moll@arm.com>,
ijc+devicetree@hellion.org.ok, galak@codeaurora.org,
chris@printf.net
Subject: Re: [PATCH 1/3] mmc: add support for power-on sequencing through DT
Date: Mon, 20 Jan 2014 17:16:21 +0000 [thread overview]
Message-ID: <20140120171621.GG15937@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOMZO5AfSe_c7gfee0BcZso8ZYg=PaTDwfsXwzpEcM1554VQ6Q@mail.gmail.com>
On Mon, Jan 20, 2014 at 03:03:50PM -0200, Fabio Estevam wrote:
> On Mon, Jan 20, 2014 at 2:48 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
>
> > So far so good. Now, what about this external oscillator which has its
> > own separate power control. My immediate thought is that this can be
> > specified via card_ext_clock - I would simply need to declare a fixed-rate
> > clock with either a regulator (power switch) controlled via a gpio (which
> > would probably be closer to the hardware) or a gpio as an enable... ah,
> > that requires me to write a common clock driver for that bit since this
> > is currently not modelled by CCF...
>
> Isn't this covered by the gpios property of fixed-clock?
>
> We do the following to enable the 26MHz codec clock in
> imx51-babbage.dts via GPIO4_26:
>
> clk_26M: codec_clock {
> compatible = "fixed-clock";
> reg=<0>;
> #clock-cells = <0>;
> clock-frequency = <26000000>;
> gpios = <&gpio4 26 GPIO_ACTIVE_LOW>;
> };
Not as far as I can see. fixed-clock appears to have two properies:
clock-frequency
clock-output-names
and nothing else. See of_fixed_clk_setup in drivers/clk/clk-fixed-rate.c.
You'll also find that the documentation in this file says this about it:
* DOC: basic fixed-rate clock that cannot gate
*
* Traits of this clock:
* prepare - clk_(un)prepare only ensures parents are prepared
* enable - clk_enable only ensures parents are enabled
* rate - rate is always a fixed value. No clk_set_rate support
* parent - fixed parent. No clk_set_parent support
So, I think the bit which you quote from imx51-babbage.dts is wishful
thinking on the part of the author of the DT file, rather than actually
being implemented in any way by the kernel DT support.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
next prev parent reply other threads:[~2014-01-20 17:16 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 3:56 [PATCH 0/3] RFC/RFT: Powering on MMC Wifi/BT modules in MMC core Olof Johansson
2014-01-20 3:56 ` [PATCH 1/3] mmc: add support for power-on sequencing through DT Olof Johansson
2014-01-20 8:44 ` Ulf Hansson
2014-01-20 19:13 ` Olof Johansson
2014-01-21 8:55 ` Ulf Hansson
2014-01-21 18:14 ` Olof Johansson
2014-01-22 11:30 ` Mark Brown
2014-01-20 16:36 ` Mark Brown
2014-01-20 16:48 ` Russell King - ARM Linux
2014-01-20 17:03 ` Fabio Estevam
2014-01-20 17:16 ` Russell King - ARM Linux [this message]
2014-01-20 18:47 ` Fabio Estevam
2014-01-21 19:19 ` Russell King - ARM Linux
2014-01-24 17:35 ` Fabio Estevam
2014-01-27 8:43 ` Jyri Sarha
2014-01-27 8:54 ` Chen-Yu Tsai
2014-01-27 9:48 ` Jyri Sarha
2014-01-20 18:58 ` Arnd Bergmann
[not found] ` <201401201958.57997.arnd-r2nGTMty4D4@public.gmane.org>
2014-01-20 19:04 ` Olof Johansson
2014-01-20 19:12 ` Arnd Bergmann
2014-01-20 19:14 ` Fabio Estevam
2014-01-20 19:14 ` Olof Johansson
2014-01-21 7:24 ` Sascha Hauer
2014-01-21 7:25 ` Sascha Hauer
2014-01-21 18:34 ` Tomasz Figa
2014-01-21 21:30 ` Olof Johansson
2014-01-21 21:39 ` Tomasz Figa
2014-01-26 17:26 ` Tomasz Figa
2014-01-27 10:19 ` Ulf Hansson
2014-01-28 0:59 ` Tomasz Figa
2014-01-28 1:08 ` Chris Ball
2014-01-28 10:06 ` Ulf Hansson
2014-01-28 10:48 ` Arnd Bergmann
2014-02-12 18:33 ` Mark Brown
2014-02-13 8:56 ` Ulf Hansson
2014-02-13 9:01 ` Tomasz Figa
2014-02-13 10:42 ` Russell King - ARM Linux
2014-02-13 12:48 ` Arnd Bergmann
2014-02-13 14:41 ` Russell King - ARM Linux
2014-02-13 16:13 ` Arnd Bergmann
2014-02-13 17:31 ` Olof Johansson
2014-02-15 12:18 ` Arnd Bergmann
2014-02-15 12:27 ` Russell King - ARM Linux
2014-02-15 13:09 ` Arnd Bergmann
2014-02-15 13:22 ` Tomasz Figa
2014-02-15 16:21 ` Arnd Bergmann
2014-02-15 20:52 ` Russell King - ARM Linux
2014-02-15 21:35 ` Tomasz Figa
2014-02-15 22:03 ` Russell King - ARM Linux
2014-02-17 13:00 ` Arnd Bergmann
2014-02-17 23:25 ` Mark Brown
2014-01-20 3:56 ` [PATCH 2/3] mmc: dw_mmc: call mmc_of_parse to fill in common options Olof Johansson
2014-01-20 4:53 ` Jaehoon Chung
2014-01-20 3:56 ` [PATCH 3/3] ARM: dts: exynos5250-snow: Enable wifi power-on Olof Johansson
2014-01-30 21:49 ` [PATCH 0/3] RFC/RFT: Powering on MMC Wifi/BT modules in MMC core Russell King - ARM Linux
2014-02-01 16:14 ` Russell King - ARM Linux
2014-02-13 10:36 ` Russell King - ARM Linux
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=20140120171621.GG15937@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=chris@printf.net \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.ok \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).