linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 3/3] wlcore/wl12xx: spi: add wifi support to cm-t335
Date: Wed, 27 Jan 2016 10:40:44 -0800	[thread overview]
Message-ID: <20160127184044.GT19432@atomide.com> (raw)
In-Reply-To: <20160113172712.GI12777@atomide.com>

* Tony Lindgren <tony@atomide.com> [160113 09:28]:
> * Igor Grinberg <grinberg@compulab.co.il> [160112 22:01]:
> > Hi Kalle Valo,
> > 
> > On 01/07/16 11:02, Kalle Valo wrote:
> > > Uri Mashiach <uri.mashiach@compulab.co.il> writes:
> > > 
> > >> Device tree modifications:
> > >> - Pinmux for SPI0 and WiFi GPIOs.
> > >> - SPI0 node with wlcore as a child node.
> > >>
> > >> Cc: Tony Lindgren <tony@atomide.com>
> > >> Signed-off-by: Uri Mashiach <uri.mashiach@compulab.co.il>
> > >> ---
> > 
> > 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.

Applying patch 3/3 into omap-for-v4.6/dt thanks.

Tony

  parent reply	other threads:[~2016-01-27 18:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 13:35 [PATCH v4 0/3] wlcore/wl12xx: spi: add wifi support to cm-t335 Uri Mashiach
2015-12-30 13:35 ` [PATCH v4 1/3] wlcore/wl12xx: spi: add power operation function Uri Mashiach
2016-01-09  2:53   ` Sebastian Reichel
2016-01-12 11:21     ` Grygorii Strashko
2016-01-13  6:03   ` Igor Grinberg
2016-01-29  9:11   ` [v4,1/3] " Kalle Valo
2015-12-30 13:35 ` [PATCH v4 2/3] wlcore/wl12xx: spi: add device tree support Uri Mashiach
2016-01-09  2:56   ` Sebastian Reichel
2016-01-12 11:24     ` Grygorii Strashko
2016-01-13  6:05   ` Igor Grinberg
2015-12-30 13:35 ` [PATCH v4 3/3] wlcore/wl12xx: spi: add wifi support to cm-t335 Uri Mashiach
2016-01-07  9:02   ` Kalle Valo
2016-01-07 11:20     ` Uri Mashiach
2016-01-13  6:00     ` Igor Grinberg
2016-01-13 17:27       ` Tony Lindgren
2016-01-14  7:05         ` Kalle Valo
2016-01-14  9:08           ` Arend van Spriel
2016-01-14  9:11             ` Kalle Valo
2016-01-27 18:40         ` Tony Lindgren [this message]
2016-01-13  6:09   ` Igor Grinberg
2016-01-27 18:41     ` Tony Lindgren

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=20160127184044.GT19432@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).