From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: Luciano Coelho <coelho-l0cyMroinI0@public.gmane.org>
Cc: "linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
"linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org"
<rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
"linux-arm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-arm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
mturquette-l0cyMroinI0@public.gmane.org
Subject: Re: [PATCH] Documentation: dt: bindings: TI WiLink modules
Date: Fri, 28 Jun 2013 11:21:45 +0100 [thread overview]
Message-ID: <20130628102145.GB2139@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <1372413215.21065.41.camel-eHkr6bJ9aPyyenC2BZ5AVw@public.gmane.org>
On Fri, Jun 28, 2013 at 10:53:35AM +0100, Luciano Coelho wrote:
> On Fri, 2013-06-28 at 10:38 +0100, Mark Rutland wrote:
> > On Tue, Jun 25, 2013 at 09:35:30AM +0100, Luciano Coelho wrote:
> > > +Optional properties:
> > > +--------------------
> > > +
> > > +- refclock: the internal WLAN reference clock frequency (required for
> > > + WiLink6 and WiLink7; not used for WiLink8). Must be one of the
> > > + following:
> > > + 0 = 19.2 MHz
> > > + 1 = 26.0 MHz
> > > + 2 = 38.4 MHz
> > > + 3 = 52.0 MHz
> > > + 4 = 38.4 MHz, XTAL
> > > + 5 = 26.0 MHz, XTAL
> > > +
> > > +- tcxoclock: the internal WLAN TCXO clock frequency (required for
> > > + WiLink7 not used for WiLink6 and WiLink8). Must be one of the
> > > + following:
> > > + 0 = 19.200 MHz
> > > + 1 = 26.000 MHz
> > > + 2 = 38.400 MHz
> > > + 3 = 52.000 MHz
> > > + 4 = 16.368 MHz
> > > + 5 = 32.736 MHz
> > > + 6 = 16.800 MHz
> > > + 7 = 33.600 MHz
> >
> > This looks suspiciously like what we have the common clock bindings for:
> >
> > refclk {
> > compatible = "fixed-clock";
> > #clock-cells = <0>;
> > clock-frequency = <19200000>;
> > }
> >
> > wilink {
> > compatible = "ti,wilink7";
> > interrupt-parent = <&some_interrupt_controller>;
> > interrupts = <0 1 1>;
> > clocks = <&refclk>, <&refclk>;
> > clock-names = "refclk", "txoclk";
> > };
> >
> > Could you not use them?
>
> Hmmm... this actually does look good. But these are internal clocks in
> the modules, they cannot be accessed from outside. Does it make sense
> to register them with the clock framework?
Given we already have a common way of describing clocks, I think it
makes sense to use it -- people already understand the common bindings,
and it's less code to add add to the kernel. I don't think the fact
these clocks are internal should prevent us from describing them as we
would an external clock.
Perhaps Mike Turquette [Cc'd] has an opinion on the matter.
Thanks,
Mark.
next prev parent reply other threads:[~2013-06-28 10:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 8:35 [PATCH] Documentation: dt: bindings: TI WiLink modules Luciano Coelho
2013-06-25 11:12 ` Felipe Balbi
2013-06-25 11:56 ` Luciano Coelho
2013-06-25 13:07 ` Felipe Balbi
2013-06-25 19:35 ` Luciano Coelho
2013-06-25 19:37 ` Luciano Coelho
2013-06-26 6:24 ` Tony Lindgren
2013-06-26 8:13 ` Luciano Coelho
2013-06-26 8:22 ` Tony Lindgren
[not found] ` <51CBC1C8.1040301@gmail.com>
2013-06-27 8:47 ` Luciano Coelho
2013-06-27 12:51 ` Nishanth Menon
2013-06-27 12:58 ` Luciano Coelho
2013-06-27 13:15 ` Nishanth Menon
2013-06-27 13:19 ` Luciano Coelho
2013-06-27 13:23 ` Nishanth Menon
[not found] ` <51CC3CEE.3050004-l0cyMroinI0@public.gmane.org>
2013-06-27 13:30 ` Luciano Coelho
2013-06-27 13:39 ` Nishanth Menon
2013-06-27 18:51 ` Luciano Coelho
2013-06-27 19:12 ` Nishanth Menon
2013-06-27 19:46 ` Luciano Coelho
2013-06-27 19:56 ` Nishanth Menon
2013-06-28 9:38 ` Mark Rutland
2013-06-28 9:53 ` Luciano Coelho
[not found] ` <1372413215.21065.41.camel-eHkr6bJ9aPyyenC2BZ5AVw@public.gmane.org>
2013-06-28 10:21 ` Mark Rutland [this message]
2013-06-28 10:31 ` Luciano Coelho
2013-06-28 11:22 ` Luciano Coelho
2013-06-28 11:41 ` Felipe Balbi
2013-06-28 12:13 ` Luciano Coelho
2013-06-28 12:18 ` Felipe Balbi
[not found] ` <20130628121859.GP11297-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-06-28 13:21 ` Luciano Coelho
2013-07-01 12:39 ` Luciano Coelho
2013-07-17 23:58 ` Laurent Pinchart
2013-07-20 7:48 ` Luciano Coelho
2013-06-28 10:39 ` Mark Rutland
2013-06-28 10:33 ` Mark Rutland
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=20130628102145.GB2139@e106331-lin.cambridge.arm.com \
--to=mark.rutland-5wv7dgnigg8@public.gmane.org \
--cc=coelho-l0cyMroinI0@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mturquette-l0cyMroinI0@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.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).