From: Tony Lindgren <tony@atomide.com> To: Peter Ujfalusi <peter.ujfalusi@ti.com> Cc: Luciano Coelho <coelho@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 09:49:10 -0800 [thread overview] Message-ID: <20130118174910.GF15361@atomide.com> (raw) In-Reply-To: <50F91FE2.3020402@ti.com> * Peter Ujfalusi <peter.ujfalusi@ti.com> [130118 02:15]: > Hi Tony, > > On 01/18/2013 12:16 AM, Tony Lindgren wrote: > > Well we are planning to drop the non-DT support for omap4 as soon as it's > > usable with DT. > > Exactly, but right now we do have legacy and legacy should work in order to > help for example Luca to make the final push which allows us to move to DT > only for OMAP4. Yeah I'm suggesting we should do the muxing in the platform code and fix the regression in the driver. But not add the new platform callbacks. > > For omap4 we are only carrying SDP and panda support to > > make this transition easier. The only bindings missing AFAIK are wl12xx and > > USB. > > > > If we add this, then it implies we're somehow supporting it, which is not > > the way to go IMHO as we need to get rid of these platform callbacks instead. > > IMHO we should keep these boards working as long as we have the legacy board > support for them. Naturally. We cannot flip over to DT only boot until we have usable system :) And to me "usable system" means being able to use my pandaboard es with a lapdock for work things. Currently it seems that we need the following working with DT to have panda and blaze usable: 1. MMC (done) 2. USB (patches pending for EHCI and MUSB) 3. Ethernet (done for blaze, needs USB for panda) 4. DSS (various drivers pending, probably still needs some platform init code) 5. WLAN (no binding, needs platform init until done) 6. Audio (done?) The DMA binding is still pending, but these devices should also work without it until we have the binding. And various miscellaneous drivers we can init with the platform code until the bindings are done. > So what is the policy now regarding to 'old' legacy but still used OMAP4 board > files? I think we should still maintain them, but the effort to get rid of > them should be the highest priority. Yes only minimal fixes. We should not add any new features to them as that will just complicate the conversion to DT. Once we have a usable system booting with DT, we can ust drop the old omap4 board-*.c files. Regards, Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren) To: linux-arm-kernel@lists.infradead.org Subject: [[PATCH v2]] OMAP: omap4-panda: add WiLink shared transport power functions Date: Fri, 18 Jan 2013 09:49:10 -0800 [thread overview] Message-ID: <20130118174910.GF15361@atomide.com> (raw) In-Reply-To: <50F91FE2.3020402@ti.com> * Peter Ujfalusi <peter.ujfalusi@ti.com> [130118 02:15]: > Hi Tony, > > On 01/18/2013 12:16 AM, Tony Lindgren wrote: > > Well we are planning to drop the non-DT support for omap4 as soon as it's > > usable with DT. > > Exactly, but right now we do have legacy and legacy should work in order to > help for example Luca to make the final push which allows us to move to DT > only for OMAP4. Yeah I'm suggesting we should do the muxing in the platform code and fix the regression in the driver. But not add the new platform callbacks. > > For omap4 we are only carrying SDP and panda support to > > make this transition easier. The only bindings missing AFAIK are wl12xx and > > USB. > > > > If we add this, then it implies we're somehow supporting it, which is not > > the way to go IMHO as we need to get rid of these platform callbacks instead. > > IMHO we should keep these boards working as long as we have the legacy board > support for them. Naturally. We cannot flip over to DT only boot until we have usable system :) And to me "usable system" means being able to use my pandaboard es with a lapdock for work things. Currently it seems that we need the following working with DT to have panda and blaze usable: 1. MMC (done) 2. USB (patches pending for EHCI and MUSB) 3. Ethernet (done for blaze, needs USB for panda) 4. DSS (various drivers pending, probably still needs some platform init code) 5. WLAN (no binding, needs platform init until done) 6. Audio (done?) The DMA binding is still pending, but these devices should also work without it until we have the binding. And various miscellaneous drivers we can init with the platform code until the bindings are done. > So what is the policy now regarding to 'old' legacy but still used OMAP4 board > files? I think we should still maintain them, but the effort to get rid of > them should be the highest priority. Yes only minimal fixes. We should not add any new features to them as that will just complicate the conversion to DT. Once we have a usable system booting with DT, we can ust drop the old omap4 board-*.c files. Regards, Tony
next prev parent reply other threads:[~2013-01-18 17:49 UTC|newest] Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-16 21:45 [[PATCH v2]] OMAP: omap4-panda: add WiLink shared transport power functions Luciano Coelho 2013-01-16 21:45 ` Luciano Coelho 2013-01-16 21:45 ` Luciano Coelho 2013-01-17 9:30 ` Peter Ujfalusi 2013-01-17 9:30 ` Peter Ujfalusi 2013-01-17 9:30 ` Peter Ujfalusi 2013-01-17 9:34 ` Felipe Balbi 2013-01-17 9:34 ` Felipe Balbi 2013-01-17 9:34 ` Felipe Balbi 2013-01-17 9:55 ` Peter Ujfalusi 2013-01-17 9:55 ` Peter Ujfalusi 2013-01-17 9:55 ` Peter Ujfalusi 2013-01-17 10:05 ` Felipe Balbi 2013-01-17 10:05 ` Felipe Balbi 2013-01-17 10:05 ` Felipe Balbi 2013-01-17 10:09 ` Felipe Balbi 2013-01-17 10:09 ` Felipe Balbi 2013-01-17 10:09 ` Felipe Balbi 2013-01-17 10:35 ` Luciano Coelho 2013-01-17 10:35 ` Luciano Coelho 2013-01-17 10:35 ` Luciano Coelho 2013-01-17 10:40 ` Peter Ujfalusi 2013-01-17 10:40 ` Peter Ujfalusi 2013-01-17 10:40 ` Peter Ujfalusi 2013-01-17 17:31 ` Tony Lindgren 2013-01-17 17:31 ` Tony Lindgren 2013-01-17 17:57 ` Luciano Coelho 2013-01-17 17:57 ` Luciano Coelho 2013-01-17 17:57 ` Luciano Coelho 2013-01-17 23:16 ` Tony Lindgren 2013-01-17 23:16 ` Tony Lindgren 2013-01-18 8:58 ` Luciano Coelho 2013-01-18 8:58 ` Luciano Coelho 2013-01-18 8:58 ` Luciano Coelho 2013-01-18 17:36 ` Tony Lindgren 2013-01-18 17:36 ` Tony Lindgren 2013-01-18 17:54 ` Felipe Balbi 2013-01-18 17:54 ` Felipe Balbi 2013-01-18 17:54 ` Felipe Balbi 2013-01-18 18:05 ` Tony Lindgren 2013-01-18 18:05 ` Tony Lindgren 2013-01-18 19:08 ` Luciano Coelho 2013-01-18 19:08 ` Luciano Coelho 2013-01-18 19:08 ` Luciano Coelho 2013-01-18 19:22 ` Tony Lindgren 2013-01-18 19:22 ` Tony Lindgren 2013-01-18 10:11 ` Peter Ujfalusi 2013-01-18 10:11 ` Peter Ujfalusi 2013-01-18 10:11 ` Peter Ujfalusi 2013-01-18 17:49 ` Tony Lindgren [this message] 2013-01-18 17:49 ` Tony Lindgren 2013-01-23 8:55 ` Peter Ujfalusi 2013-01-23 8:55 ` Peter Ujfalusi 2013-01-23 8:55 ` Peter Ujfalusi 2013-01-17 9:35 ` Luciano Coelho 2013-01-17 9:35 ` Luciano Coelho 2013-01-17 9:35 ` Luciano Coelho 2013-01-17 9:59 ` Peter Ujfalusi 2013-01-17 9:59 ` Peter Ujfalusi 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=20130118174910.GF15361@atomide.com \ --to=tony@atomide.com \ --cc=balbi@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 \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.