On Fri, 2014-02-28 at 08:26 +0100, Yegor Yefremov wrote: > On Tue, Jul 30, 2013 at 3:04 PM, Luciano Coelho <coelho@xxxxxx> 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@xxxxxx > > [2] http://news.gmane.org/find-root.php?message_id=1375109728-5931-1-git-send-email-coelho@xxxxxx > > > > 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. -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
