Return-path: Received: from muru.com ([72.249.23.125]:55089 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753767AbcAMR1R (ORCPT ); Wed, 13 Jan 2016 12:27:17 -0500 Date: Wed, 13 Jan 2016 09:27:12 -0800 From: Tony Lindgren To: Igor Grinberg Cc: Kalle Valo , Uri Mashiach , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , bcousson@baylibre.com, Eliad Peller , devicetree@vger.kernel.org, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-wireless@vger.kernel.org Subject: Re: [PATCH v4 3/3] wlcore/wl12xx: spi: add wifi support to cm-t335 Message-ID: <20160113172712.GI12777@atomide.com> (sfid-20160113_182725_596941_A402261F) References: <1451482533-8624-1-git-send-email-uri.mashiach@compulab.co.il> <1451482533-8624-4-git-send-email-uri.mashiach@compulab.co.il> <87io35lq2p.fsf@kamboji.qca.qualcomm.com> <5695E802.7050909@compulab.co.il> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <5695E802.7050909@compulab.co.il> Sender: linux-wireless-owner@vger.kernel.org List-ID: * Igor Grinberg [160112 22:01]: > Hi Kalle Valo, > > On 01/07/16 11:02, Kalle Valo wrote: > > Uri Mashiach writes: > > > >> Device tree modifications: > >> - Pinmux for SPI0 and WiFi GPIOs. > >> - SPI0 node with wlcore as a child node. > >> > >> Cc: Tony Lindgren > >> Signed-off-by: Uri Mashiach > >> --- > > Uri, please document the dependencies next time. Thanks! > > >> v1 -> v2: Replace interrupts and interrupt-parent with interrupts-extended. > >> v2 -> v3: Move the pinctrl-0 = <&wifi_pins> to the wlcore node. > >> v3 -> v4: replace interrupts-extended with interrupts and interrupt-parent. (revert v2 modification). > >> According to Rob Herring and Documentation/devicetree/bindings/interrupt-controller/interrupts.txt, > >> interrupts-extended should only be used when a device has multiple interrupt parents. > >> > >> arch/arm/boot/dts/am335x-cm-t335.dts | 55 ++++++++++++++++++++++++++++++++++++ > >> 1 file changed, 55 insertions(+) > > > > To what tree should this patch go? My wireless-drivers-next tree doesn't > > even have this file. > > Right. It will hit the mainline during this merge window through Tony's and > arm-soc trees. > > Do you think it will be sensible if you take 1/3 and 2/3 patches and Tony > will take the 3/3 (there is no code dependency between first two and the last one), > or we can just wait till arm-soc hits the mainline, so you will have the > needed code? Yeah I'll pick the dts changes separately after the merge window as there is no dependency to the driver changes. Regards, Tony