From: "Hiremath, Vaibhav" <hvaibhav@ti.com> To: Richard Cochran <richardcochran@gmail.com> Cc: Paul Walmsley <paul@pwsan.com>, Tony Lindgren <tony@atomide.com>, "N, Mugunthan V" <mugunthanvnm@ti.com>, "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: RE: Fwd: [PATCH 2/5] ARM: OMAP3+: hwmod: Add AM33XX HWMOD data for davinci_mdio Date: Tue, 23 Oct 2012 10:12:29 +0000 [thread overview] Message-ID: <79CD15C6BA57404B839C016229A409A83EB48592@DBDE01.ent.ti.com> (raw) In-Reply-To: <20121019061630.GB2983@netboy.at.omicron.at> On Fri, Oct 19, 2012 at 11:46:30, Richard Cochran wrote: > On Fri, Oct 19, 2012 at 02:18:29AM +0530, Vaibhav Hiremath wrote: > > > > Another important point is, this driver is also required and used for > > Davinci family of devices (arch/mach/mach-davinci/). > > That is really beside the point. If the code isn't ready yet, then > don't merge it. > With respect to AM33xx the driver may not be ready, but that doesn't mean driver itself is not ready. As I mentioned before, driver is used on davinci platform and it could be functional there. In case of AM33xx, where DT only boot mode is supported, you are forced to migrate driver to DT, which is addition to the driver. Note that, all the patches you have posted recently are AM33xx SoC integration specific patches. > When I asked about the beaglebone, I was given the impression that it > will be ready for v3.7-rc1. But, as I know realize, at the current > rate, it might not even be ready for v3.8. > I understand, and as you mentioned we are not fully there at v3.7-rc1 with all the drivers/module support, due to all known reasons. Its good that with v3.7-rc2, Beaglebone boots up out of box from mainline. Thanks, Vaibhav > I don't mind waiting, but please make sure that whatever lands into a > release is really, truly working. > > Thanks, > Richard > > >
WARNING: multiple messages have this Message-ID (diff)
From: hvaibhav@ti.com (Hiremath, Vaibhav) To: linux-arm-kernel@lists.infradead.org Subject: Fwd: [PATCH 2/5] ARM: OMAP3+: hwmod: Add AM33XX HWMOD data for davinci_mdio Date: Tue, 23 Oct 2012 10:12:29 +0000 [thread overview] Message-ID: <79CD15C6BA57404B839C016229A409A83EB48592@DBDE01.ent.ti.com> (raw) In-Reply-To: <20121019061630.GB2983@netboy.at.omicron.at> On Fri, Oct 19, 2012 at 11:46:30, Richard Cochran wrote: > On Fri, Oct 19, 2012 at 02:18:29AM +0530, Vaibhav Hiremath wrote: > > > > Another important point is, this driver is also required and used for > > Davinci family of devices (arch/mach/mach-davinci/). > > That is really beside the point. If the code isn't ready yet, then > don't merge it. > With respect to AM33xx the driver may not be ready, but that doesn't mean driver itself is not ready. As I mentioned before, driver is used on davinci platform and it could be functional there. In case of AM33xx, where DT only boot mode is supported, you are forced to migrate driver to DT, which is addition to the driver. Note that, all the patches you have posted recently are AM33xx SoC integration specific patches. > When I asked about the beaglebone, I was given the impression that it > will be ready for v3.7-rc1. But, as I know realize, at the current > rate, it might not even be ready for v3.8. > I understand, and as you mentioned we are not fully there at v3.7-rc1 with all the drivers/module support, due to all known reasons. Its good that with v3.7-rc2, Beaglebone boots up out of box from mainline. Thanks, Vaibhav > I don't mind waiting, but please make sure that whatever lands into a > release is really, truly working. > > Thanks, > Richard > > >
next prev parent reply other threads:[~2012-10-23 10:12 UTC|newest] Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-17 18:13 Fwd: [PATCH 2/5] ARM: OMAP3+: hwmod: Add AM33XX HWMOD data for davinci_mdio Richard Cochran 2012-10-17 18:13 ` Richard Cochran 2012-10-17 23:38 ` Paul Walmsley 2012-10-17 23:38 ` Paul Walmsley 2012-10-17 23:50 ` Tony Lindgren 2012-10-17 23:50 ` Tony Lindgren 2012-10-18 3:06 ` Richard Cochran 2012-10-18 3:06 ` Richard Cochran 2012-10-18 3:46 ` Paul Walmsley 2012-10-18 3:46 ` Paul Walmsley 2012-10-18 18:27 ` Richard Cochran 2012-10-18 18:27 ` Richard Cochran 2012-10-18 18:42 ` Paul Walmsley 2012-10-18 18:42 ` Paul Walmsley 2012-10-18 18:44 ` Richard Cochran 2012-10-18 18:44 ` Richard Cochran 2012-10-18 19:27 ` Paul Walmsley 2012-10-18 19:27 ` Paul Walmsley 2012-10-19 6:08 ` Richard Cochran 2012-10-19 6:08 ` Richard Cochran 2012-10-18 20:48 ` Vaibhav Hiremath 2012-10-18 20:48 ` Vaibhav Hiremath 2012-10-19 6:16 ` Richard Cochran 2012-10-19 6:16 ` Richard Cochran 2012-10-19 16:00 ` Tony Lindgren 2012-10-19 16:00 ` Tony Lindgren 2012-10-19 16:32 ` Matt Porter 2012-10-19 16:32 ` Matt Porter 2012-10-26 8:23 ` Hiremath, Vaibhav 2012-10-26 8:23 ` Hiremath, Vaibhav 2012-10-26 18:06 ` Tony Lindgren 2012-10-26 18:06 ` Tony Lindgren 2012-10-29 4:58 ` Hiremath, Vaibhav 2012-10-29 4:58 ` Hiremath, Vaibhav 2012-10-29 7:50 ` Richard Cochran 2012-10-29 7:50 ` Richard Cochran 2012-10-29 8:27 ` Hiremath, Vaibhav 2012-10-29 8:27 ` Hiremath, Vaibhav 2012-10-23 10:12 ` Hiremath, Vaibhav [this message] 2012-10-23 10:12 ` Hiremath, Vaibhav 2012-10-24 5:08 ` Richard Cochran 2012-10-24 5:08 ` Richard Cochran 2012-10-26 8:23 ` Hiremath, Vaibhav 2012-10-26 8:23 ` Hiremath, Vaibhav 2012-10-18 8:30 ` Koen Kooi 2012-10-18 8:30 ` Koen Kooi 2012-10-18 20:48 ` Fwd: " Vaibhav Hiremath 2012-10-18 20:48 ` Vaibhav Hiremath 2012-10-18 22:49 ` Paul Walmsley 2012-10-18 22:49 ` Paul Walmsley 2012-10-29 5:19 ` Paul Walmsley 2012-10-29 5:19 ` Paul Walmsley 2012-10-29 5:22 ` Hiremath, Vaibhav 2012-10-29 5:22 ` Hiremath, Vaibhav
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=79CD15C6BA57404B839C016229A409A83EB48592@DBDE01.ent.ti.com \ --to=hvaibhav@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=mugunthanvnm@ti.com \ --cc=paul@pwsan.com \ --cc=richardcochran@gmail.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: 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.