mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Luciano Coelho <coelho@ti.com>,
	"Cousson, Benoit" <b-cousson@ti.com>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>, <balbi@ti.com>,
	<linux-omap@vger.kernel.org>, <linux@arm.linux.org.uk>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [[PATCH v2]] OMAP: omap4-panda: add WiLink shared transport power functions
Date: Fri, 18 Jan 2013 19:54:08 +0200	[thread overview]
Message-ID: <20130118175408.GC1035@arwen.pp.htv.fi> (raw)
In-Reply-To: <20130118173635.GE15361@atomide.com>

[-- Attachment #1: Type: text/plain, Size: 2099 bytes --]

Hi,

On Fri, Jan 18, 2013 at 09:36:35AM -0800, Tony Lindgren wrote:
> * Luciano Coelho <coelho@ti.com> [130118 01:03]:
> > On Thu, 2013-01-17 at 15:16 -0800, Tony Lindgren wrote:
> > > * Luciano Coelho <coelho@ti.com> [130117 10:04]:
> > > > But this patch is pretty small and simple, so why not include it to at
> > > > least fix the breakage in 3.7 and 3.8? Whether you take it or not now
> > > > won't make any difference in the 5k LOC in these kernel versions.
> > > 
> > > Well we are planning to drop the non-DT support for omap4 as soon as it's
> > > usable with DT. For omap4 we are only carrying SDP and panda support to
> > > make this transition easier. The only bindings missing AFAIK are wl12xx and
> > > USB.
> > 
> > In my view this is a regression and it should be fixed with as simple a
> > patch as possible.  The alternative to my solution is to revert the
> > patch that removed the enable/disable from the ti-st driver *and* fix
> > u-boot, because if it doesn't mux the UART2 pins properly (and it
> > doesn't) the shared transport still won't work.
> 
> Fixing the muxing here makes sense naturally as we cannot do that in the driver
> until we've flipped things over to use DT.
> 
> But I don't think we should fix the driver regression by adding more platform
> callbacks as we are getting rid of them anyways.

it's not adding more callbacks, solely implementing them as it should
have been done on Pavan's original patch.

> > > What's your estimate of having minimal wl12xx WLAN DT binding available?
> > 
> > To tell you the truth, I haven't even started looking into DT for wl12xx
> > myself.  So I have no idea when it will be ready.  Benoit has been
> > looking into it, but I don't know how far he is.
> 
> If it's going to take long we should just init the platform data for
> it temporarily even in the DT boot case until the binding is available.

which will boil down to having those platform_data callbacks to have it
at least functional. How will Luca test DT conversion if ti-st isn't
even functional ?

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-01-18 17:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 21:45 Luciano Coelho
2013-01-17  9:30 ` Peter Ujfalusi
2013-01-17  9:34   ` Felipe Balbi
2013-01-17  9:55     ` Peter Ujfalusi
2013-01-17 10:05       ` Felipe Balbi
2013-01-17 10:09         ` Felipe Balbi
2013-01-17 10:35           ` Luciano Coelho
2013-01-17 10:40             ` Peter Ujfalusi
2013-01-17 17:31               ` Tony Lindgren
2013-01-17 17:57                 ` Luciano Coelho
2013-01-17 23:16                   ` Tony Lindgren
2013-01-18  8:58                     ` Luciano Coelho
2013-01-18 17:36                       ` Tony Lindgren
2013-01-18 17:54                         ` Felipe Balbi [this message]
2013-01-18 18:05                           ` Tony Lindgren
2013-01-18 19:08                         ` Luciano Coelho
2013-01-18 19:22                           ` Tony Lindgren
2013-01-18 10:11                     ` Peter Ujfalusi
2013-01-18 17:49                       ` Tony Lindgren
2013-01-23  8:55                         ` Peter Ujfalusi
2013-01-17  9:35   ` Luciano Coelho
2013-01-17  9:59     ` Peter Ujfalusi

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=20130118175408.GC1035@arwen.pp.htv.fi \
    --to=balbi@ti.com \
    --cc=b-cousson@ti.com \
    --cc=coelho@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=peter.ujfalusi@ti.com \
    --cc=tony@atomide.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

all inboxes | Powered by JetHome®