From: Luca Coelho <luca@coelho.fi>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: linux-wireless@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
"Nori, Sekhar" <nsekhar@ti.com>,
mturquette@linaro.org, mark.rutland@arm.com, balbi@ti.com,
grant.likely@linaro.org, rob.herring@calxeda.com,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
linux-omap@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
nm@ti.com, martinez.javier@gmail.com
Subject: Re: [PATCH v4 0/8] wilink: add device tree support
Date: Fri, 28 Feb 2014 14:29:51 +0200 [thread overview]
Message-ID: <1393590591.13669.36.camel@dubbel> (raw)
In-Reply-To: <CAGm1_kvdzkvzEEymQ+H0XiKugifHF27KDz3jwX5Frg_U=S7KgA@mail.gmail.com>
On Fri, 2014-02-28 at 08:26 +0100, Yegor Yefremov wrote:
> On Tue, Jul 30, 2013 at 3:04 PM, Luciano Coelho <coelho@ti.com> wrote:
> > Hi,
> >
> > This patch series adds device tree support to the wlcore_sdio driver,
> > which is used by WiLink6, WiLink7 and WiLink8.
> >
> > The first patches do some clean-up to make the data needed in the
> > wilink device tree node smaller. The remaining patches implement the
> > actual device tree node parsing in wlcore_sdio.
> >
> > Regarding the XTAL clock issues, for now we don't support XTAL mode
> > with DT, but I have sent a proposal for a small change in the clock
> > framework to support this, but it's still under discussions [1].
> >
> > The DTS file changes will be sent separately, since they need to go
> > via different trees.
> >
> > A new version of the bindings documentation has been sent [2] and, if
> > no more comments are given to it, I'll apply it via my tree.
> >
> > [1] http://news.gmane.org/find-root.php?message_id=1372971912-10877-1-git-send-email-coelho@ti.com
> > [2] http://news.gmane.org/find-root.php?message_id=1375109728-5931-1-git-send-email-coelho@ti.com
> >
> > Changes in v4:
> >
> > * Rebased on top of 3.11-rc3 (eg. no more changes on the board files
> > that were removed);
> >
> > * Use the new irq_get_trigger_type() instead of
> > irqd_get_trigger_type() (thanks Javier);
> >
> > * Added some missing const's (thanks Felipe);
> >
> > * Reverted Tony's workaround to get WiLink to work on Panda while DT
> > was not supported yet.
> >
> >
> > Please review.
>
> What is the state of the series? Who is now responsible for the
> patches? What issues were still not handled?
There were some comments about this series (or more precisely, the one
that added the bindings documentation[1]). Unfortunately, I have left
TI since and have no time to handle them. Feel free to pick it up and
continue from there.
[1] https://lkml.org/lkml/2013/7/30/712
--
Cheers,
Luca.
next prev parent reply other threads:[~2014-02-28 12:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 13:04 [PATCH v4 0/8] wilink: add device tree support Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 1/8] wl1251: split wl251 platform data to a separate structure Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 2/8] wlcore: set irq_flags in the board files instead of hiding behind a quirk Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 3/8] wlcore: remove pwr_in_suspend from platform data Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 4/8] wl12xx: use frequency instead of enumerations for pdata clocks Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 5/8] wlcore: add initial device tree support to the sdio module Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 6/8] wlcore: sdio: add wilink clock providers Luciano Coelho
2013-07-30 22:35 ` Mike Turquette
2013-07-30 23:04 ` Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 7/8] wlcore: sdio: get clocks from device tree Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 8/8] wlcore/wl12xx: check if we got correct clock data from DT Luciano Coelho
2014-02-28 7:26 ` [PATCH v4 0/8] wilink: add device tree support Yegor Yefremov
2014-02-28 9:22 ` Alexandre Belloni
2014-03-06 10:51 ` Yegor Yefremov
2014-02-28 12:29 ` Luca Coelho [this message]
2014-02-28 14:12 ` Luca Coelho
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=1393590591.13669.36.camel@dubbel \
--to=luca@coelho.fi \
--cc=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martinez.javier@gmail.com \
--cc=mturquette@linaro.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=rob.herring@calxeda.com \
--cc=tony@atomide.com \
--cc=yegorslists@googlemail.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;
as well as URLs for NNTP newsgroup(s).