From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 3/3] ARM: dts: igep00x0: add wl18xx bindings
Date: Wed, 11 Mar 2015 08:11:38 -0700 [thread overview]
Message-ID: <20150311151138.GU5264@atomide.com> (raw)
In-Reply-To: <CAB3XZEfi49qMsB7A3p4Y7r9emzSbeyUGVy4-njzey1UnJU0qzA@mail.gmail.com>
* Eliad Peller <eliad@wizery.com> [150311 06:39]:
> On Wed, Mar 11, 2015 at 3:21 PM, Javier Martinez Canillas
> <javier@dowhile0.org> wrote:
> > On Wed, Mar 11, 2015 at 2:17 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> >> On Wednesday 11 March 2015 14:07:11 Javier Martinez Canillas wrote:
> >>>
> >>> Right now it seems that all boards in mainline with a WiLink6 part are
> >>> using internal clocks. So as a first step I think that adding an
> >>> optional refclock-frequency and tcxoclock-frequency properties should
> >>> be enough.
> >>>
> >>> It would be good if the driver supports getting the refclock and
> >>> tcxoclock from an external provider in case a board gets these from
> >>> external clocks but that can be done as a followup if there are boards
> >>> in the future using that design.
> >>>
> >>> But please bear in mind that I'm not familiar with the clock handling
> >>> in WiLink6 since the WiLink8 part used in the IGEP boards does not
> >>> need these clocks and I only looked at Luciano's previous patches and
> >>> the WiLink today driver today. So it would be good if Eliad can double
> >>> check my assumptions to see if those are correct.
> >>
> sounds right. that's what i know as well.
>
> >> Sounds good. I'd also be fine with not implementing the case for
> >> external clocks in the code until we need (and can test) it, but
> >> I think it should be specified in the binding from the start.
> >>
> > Agreed.
> >
> great. so i'll implement the internal clocks case only.
OK great sounds good to me also.
Regards,
Tony
next prev parent reply other threads:[~2015-03-11 15:11 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 15:36 [PATCH v5 1/3] dt: bindings: add wl18xx wireless device Eliad Peller
2015-03-09 15:36 ` [PATCH v5 2/3] wl18xx: add basic device-tree support Eliad Peller
2015-03-09 19:47 ` Arnd Bergmann
2015-03-11 0:34 ` Javier Martinez Canillas
2015-03-11 9:51 ` Arnd Bergmann
2015-03-11 10:05 ` Javier Martinez Canillas
2015-03-11 10:32 ` Arnd Bergmann
2015-03-11 11:50 ` Eliad Peller
2015-03-09 15:36 ` [PATCH v5 3/3] ARM: dts: igep00x0: add wl18xx bindings Eliad Peller
2015-03-09 19:50 ` Arnd Bergmann
2015-03-09 21:03 ` Eliad Peller
2015-03-09 22:49 ` Tony Lindgren
2015-03-10 11:00 ` Eliad Peller
2015-03-10 14:11 ` Arnd Bergmann
2015-03-10 14:28 ` Tony Lindgren
2015-03-10 15:48 ` Arnd Bergmann
2015-03-10 15:55 ` Tony Lindgren
2015-03-10 14:31 ` Eliad Peller
2015-03-10 15:52 ` Arnd Bergmann
2015-03-10 16:11 ` Eliad Peller
2015-03-10 16:18 ` Tony Lindgren
2015-03-10 17:01 ` Eliad Peller
2015-03-10 17:35 ` Tony Lindgren
2015-03-10 19:49 ` Arnd Bergmann
2015-03-11 1:00 ` Javier Martinez Canillas
2015-03-11 9:53 ` Arnd Bergmann
2015-03-11 11:34 ` Javier Martinez Canillas
2015-03-11 12:12 ` Eliad Peller
2015-03-11 13:13 ` Arnd Bergmann
2015-03-11 12:40 ` Arnd Bergmann
2015-03-11 13:07 ` Javier Martinez Canillas
2015-03-11 13:17 ` Arnd Bergmann
2015-03-11 13:21 ` Javier Martinez Canillas
2015-03-11 13:38 ` Eliad Peller
2015-03-11 15:11 ` Tony Lindgren [this message]
2015-03-10 14:34 ` Sekhar Nori
2015-03-10 15:54 ` Arnd Bergmann
2015-03-11 0:28 ` Javier Martinez Canillas
2015-03-11 1:19 ` Javier Martinez Canillas
2015-03-11 11:59 ` Eliad Peller
2015-03-11 12:07 ` Javier Martinez Canillas
2015-03-11 11:54 ` Eliad Peller
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=20150311151138.GU5264@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).