Re: [PATCHv2 0/5] wl1251 device tree support
On Fri, Jan 24, 2014 at 10:53:22PM +0100, Sebastian Reichel wrote: On Sat, Jan 18, 2014 at 09:47:06AM -0800, Tony Lindgren wrote: [...] The reason was for keeping things building and git bisect working. I do have wl1251-pdata-signed as the base for branch omap-for-v3.14/omap3-board-removal. However the board removal was considered too early for v3.14, so that's been postponed. This is because people are still updating their systems to device tree based booting. So I can redo my omap-for-v3.14/omap3-board-removal against v3.14. So if you want to, feel free to pick all the wl12xx patches to your wireless tree. AFAIK my omap-for-v3.14/omap3-board-removal is the only other user for those patches, and that I can redo that on v3.14. So for the arch/arm/*omap* touching patches, feel free to add: Acked-by: Tony Lindgren t...@atomide.com Another ping. If this does not go into 3.14 via wireless tree it will become complicated for 3.15 again. It's too late for new networking features in 3.14. Why wouldn't Tony send it via his tree? At any rate, I don't have the patches. If you still want them through the wireless tree (for 3.15) then you'll need to resend them. John -- John W. LinvilleSomeday the world will need a hero, and you linvi...@tuxdriver.com might be all we have. Be ready. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCHv2 0/5] wl1251 device tree support
On Fri, Jan 17, 2014 at 02:45:15AM +0100, Sebastian Reichel wrote: On Mon, Jan 06, 2014 at 11:57:09PM +0100, Sebastian Reichel wrote: Hi John, The following patchset adds device tree support to the spi variant of the wl1251 driver. Luciano Coelho (1): wl1251: split wl251 platform data to a separate structure Sebastian Reichel (4): wl1251: move power GPIO handling into the driver wl1251: spi: add vio regulator support wl1251: spi: add device tree support Documentation: dt: wireless: Add wl1251 What's the status of this patchset? Tony prepared an immutable branch for patches 1+2 [0]. I think the other patches are also ok (at least there were no more complains from the DT binding maintainers). It would be nice to have wl1251 DT support in 3.14. [0] http://www.spinics.net/lists/linux-omap/msg101165.html -- Sebastian ping? I can't see it on wireless-next. I can't pull it because the branch is based on a later source than that of wireless-next. -- John W. LinvilleSomeday the world will need a hero, and you linvi...@tuxdriver.com might be all we have. Be ready. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCHv2 0/5] wl1251 device tree support
On Fri, Jan 17, 2014 at 09:44:16AM -0800, Tony Lindgren wrote: * John W. Linville linvi...@tuxdriver.com [140117 07:17]: On Fri, Jan 17, 2014 at 02:45:15AM +0100, Sebastian Reichel wrote: On Mon, Jan 06, 2014 at 11:57:09PM +0100, Sebastian Reichel wrote: Hi John, The following patchset adds device tree support to the spi variant of the wl1251 driver. Luciano Coelho (1): wl1251: split wl251 platform data to a separate structure Sebastian Reichel (4): wl1251: move power GPIO handling into the driver wl1251: spi: add vio regulator support wl1251: spi: add device tree support Documentation: dt: wireless: Add wl1251 What's the status of this patchset? Tony prepared an immutable branch for patches 1+2 [0]. I think the other patches are also ok (at least there were no more complains from the DT binding maintainers). It would be nice to have wl1251 DT support in 3.14. [0] http://www.spinics.net/lists/linux-omap/msg101165.html -- Sebastian ping? I can't see it on wireless-next. I can't pull it because the branch is based on a later source than that of wireless-next. Hmm I thought v3.13-rc1 was the base we agreed on the immutable branch. Care to explain what the issue is merging it in? I think I was clear -- the branch is based on a later source than that of wireless-next. AFAIK merging it fast forwards your branch to v3.13-rc1 and then you just need to do the pull request against v3.13-rc1. It's not a forward, it's a merge. And I don't want to do that in the wireless-next tree right now. Are you sending that branch for 3.14? Is there some reason that I have to have it in wireless-next? John -- John W. LinvilleSomeday the world will need a hero, and you linvi...@tuxdriver.com might be all we have. Be ready. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/4] wl1251: split wl251 platform data to a separate structure
On Thu, Nov 14, 2013 at 03:22:18PM -0800, Tony Lindgren wrote: * Sebastian Reichel s...@debian.org [131114 15:04]: On Thu, Nov 14, 2013 at 10:51:33AM -0800, Tony Lindgren wrote: [...] If this is not going into v3.13, these will cause conflicts with the mach-omap2/board-*.c files for v3.14. So it might be best to do a minimal header patch first that can be merged in by both linux-omap and wireless trees. I guess this patch is pretty minimal. It also seems to be acked by the involved Maintainers, so maybe just merge Patch 1 without the other patches? This does not solve the problem with the struct modification from the second patch, but I guess it's the more intrusive patch. Once at least the first two patches are ready, how about I queue them after -rc1 and set up an immutable branch that can be merged in by linux-omap tree and the wireless tree? That sounds reasonable to me. -- John W. LinvilleSomeday the world will need a hero, and you linvi...@tuxdriver.com might be all we have. Be ready. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] omap: zoom2/3: fix build caused by wl1271 support
On Tue, Oct 05, 2010 at 11:39:47PM +0300, Luciano Coelho wrote: On Tue, 2010-10-05 at 15:19 +0200, ext Luciano Coelho wrote: On Tue, 2010-10-05 at 14:07 +0200, ext Luciano Coelho wrote: On Tue, 2010-10-05 at 13:53 +0200, ext Luciano Coelho wrote: On Sat, 2010-10-02 at 01:10 +0200, ext Tony Lindgren wrote: * Anand Gadiyar gadi...@ti.com [101001 13:25]: Patch omap: zoom: add mmc3/wl1271 device support in the wireless tree still uses .wires in struct omap2_hsmmc_info. .wires has now been replaced with .caps in patch omap: mmc: extended to pass host capabilities from board file in the OMAP tree. This causes linux-next as of 20101001 build to break as below. Fix this. CC arch/arm/mach-omap2/board-zoom-peripherals.o arch/arm/mach-omap2/board-zoom-peripherals.c:217: error: unknown field 'wires' specified in initializer make[1]: *** [arch/arm/mach-omap2/board-zoom-peripherals.o] Error 1 make: *** [arch/arm/mach-omap2] Error 2 Can you guys please queue this via the wireless tree along with the other wl1271 patches? Acked-by: Tony Lindgren t...@atomide.com I can apply this to the wl12xx tree. I just need John's confirmation. The pull request I sent to John last week is still pending. I don't know if it is possible to substitute it for a newer one with more patches (and still try to make it to 2.6.37). What do you think, John? Damn, for some reason I had a bug in John's email in my contact book. Now sending to the correct email address. Applied to the wl12xx tree. I'll send a new replacement pull to John today, including this patch. Thanks. Hmmm... We got a problem here. This patch breaks builds when we *don't* have omap: mmc extended to pass host capabilities from board file. We don't have that on wireless-next yet, so builds with zoom boards selected are broken. Any ideas on how to solve this dilemma? I guess the proper way to handle this would be to make the changes proposed in this patch when merging instead of having a normal commit for it, wouldn't it? Just cherry-pick that change into the branch of your tree that I do _not_ pull from. I presume that it is already available in linux-next? John -- John W. LinvilleSomeday the world will need a hero, and you linvi...@tuxdriver.com might be all we have. Be ready. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] omap: zoom2/3: fix build caused by wl1271 support
On Wed, Oct 06, 2010 at 06:27:49PM +0300, Luciano Coelho wrote: On Wed, 2010-10-06 at 16:01 +0200, ext Gadiyar, Anand wrote: Hmmm... We got a problem here. This patch breaks builds when we *don't* have omap: mmc extended to pass host capabilities from board file. We don't have that on wireless-next yet, so builds with zoom boards selected are broken. Any ideas on how to solve this dilemma? I guess the proper way to handle this would be to make the changes proposed in this patch when merging instead of having a normal commit for it, wouldn't it? Just cherry-pick that change into the branch of your tree that I do _not_ pull from. I presume that it is already available in linux-next? Yup - both patches are in linux-next; that's where we noticed the build break. Ok, I hope the patch applies cleanly in our trees. John, don't you want to do the cherry-pick on your wireless-testing then? If you do it, I can inherit that, because I pull from it into my testing branch (wl12xx/master). At the moment, w-t is broken too. OK, that's fine -- do you have the commit ID and the tree that has it? John -- John W. LinvilleSomeday the world will need a hero, and you linvi...@tuxdriver.com might be all we have. Be ready. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v3] omap: beagle: add support for wl1271 on the board file
On Thu, Sep 23, 2010 at 01:03:35PM +0300, Luciano Coelho wrote: Add board configuration for the wl1271 daughter board. This patch is based on Ohad Ben-Cohen's patches for Zoom boards. Cc: Ohad Ben-Cohen o...@wizery.com Signed-off-by: Luciano Coelho luciano.coe...@nokia.com --- from v2 to v3: removed accidental change to wl1271.h I presume that this should come through my tree as well (since it contains the move of wl12xx.h)? John -- John W. LinvilleSomeday the world will need a hero, and you linvi...@tuxdriver.com might be all we have. Be ready. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 0/7] native wl1271 support on ZOOM
On Wed, Sep 15, 2010 at 01:08:18PM +0200, Vitaly Wool wrote: On Wed, Sep 15, 2010 at 11:21 AM, Ohad Ben-Cohen o...@wizery.com wrote: On Wed, Sep 1, 2010 at 11:26 PM, Ohad Ben-Cohen o...@wizery.com wrote: This patchset adds wl1271 support on ZOOM2/3 boards. Tony, John, let me please suggest merging this through the wireless tree. wl1271 is a moving target - it keeps changing in the wireless tree and merging this patchset there will allow wl1271 developers to have everything in a single tree (and prevent merge conflicts in linux-next). Thanks Ohad, that's what I was about to suggest as well. :) OK, that is fine with me if the omap folks agree? John -- John W. LinvilleSomeday the world will need a hero, and you linvi...@tuxdriver.com might be all we have. Be ready. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 00/20] native support for wl1271 on ZOOM
On Wed, Jul 21, 2010 at 08:33:34PM +0300, Ohad Ben-Cohen wrote: This patch series adds native support for wl1271 on ZOOM. Just for the record, I'm fine with the wl1271 bits here going through the omap tree with the rest of the series. John -- John W. LinvilleSomeday the world will need a hero, and you linvi...@tuxdriver.com might be all we have. Be ready. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
