On Mon, Jul 30, 2012 at 09:40:27AM +0200, Shilimkar, Santosh wrote: > On Mon, Jul 30, 2012 at 7:51 AM, S, Venkatraman <svenkatr@xxxxxx> wrote: > > On Sat, Jul 28, 2012 at 1:40 PM, Shilimkar, Santosh > > <santosh.shilimkar@xxxxxx> wrote: > >> On Fri, Jul 27, 2012 at 6:50 PM, Russell King - ARM Linux > >> <linux@xxxxxxxxxxxxxxxx> wrote: > >>> On Fri, Jul 27, 2012 at 06:08:13PM +0200, Shilimkar, Santosh wrote: > >>>> On Fri, Jul 27, 2012 at 3:42 PM, Russell King - ARM Linux > >>>> <linux@xxxxxxxxxxxxxxxx> wrote: > >>>> > On Wed, Jul 25, 2012 at 03:12:22PM +0100, Russell King - ARM Linux wrote: > >>>> >> Just a quick reminder that I'm still on holiday, and at this point there > >>>> >> are over 2500 messages from the mailing lists which are sitting unread > >>>> >> since I left the UK. As I mentioned before I left the UK, it is my > >>>> >> intention *not* to go back and read all those outstanding messages - > >>>> >> there's too many of them to do that. > >>>> >> > >>>> >> So, if you want me to react to any email message you've sent, you'd > >>>> >> *better* send it again next week unless I've already responded. > >>>> >> > >>>> >> Meanwhile, I see v3.5 has been released; I have a couple of things I > >>>> >> need to do with my tree before I can push the changes, and I'll > >>>> >> probably see about sorting those out over the weekend. I also see > >>>> >> that 14 new patches have landed in the patch system. > >>>> >> > >>>> >> However, the timing of my holiday vs the merge window means that I > >>>> >> can't take anything new, unless they're fixes, so don't be surprised > >>>> >> if some stuff gets missed this merge window. > >>>> > > >>>> > Right. I'm not fully recovered from the jet lag (I'm still rather tired > >>>> > - I hate travelling back from the North American continent because it > >>>> > takes days to recover.) > >>>> > > >>>> > I have now archived off *all* email sent to me during July - which means > >>>> > that I will *NOT* be responding to anything sent during the last 17 days. > >>>> > If anyone has sent me anything important, it *MUST* be resent now. > >>>> > > >>>> > I am aware of an issue concerning the OMAP DMA patches. I'm not sure > >>>> > exactly what is required there, so I've dropped them from my planned pull > >>>> > request in the interests of getting everything else I have to Linus. I > >>>> > may plan to send a pull request this evening. > >>>> > > >>>> Well the only pending discussion was enabling the CONFIG option for > >>>> DMA at driver level SOC config level. Not sure if there was anything else > >>>> on this really. > >>> > >>> Why? The DMA driver itself is optional. > >> That was Tony's point too. Unfortunately MMC and SPI driver don't work > >> today without DMA. Some works needs to be done to support polling > >> mode and am bit skeptical if it is really worth it. Same case be with other > >> SDMA supported drivers mostly. > >> > > Russell, Tony, > > Can I request to include the DMA & MMC changes into this merge window ? > > We have many cleanups and new patches waiting to be queued up for next (3.7) > > merge window, and it'd be easier if they are implemented on top of the > > DMA changes, > > so that it gets tested together, and don't create merge conflicts. > > I am looking into implementing polling mode, which might take some time. > > Thanks Venkat. For the SPI driver as well I heard from Shubro (in cc) that > he is looking into polling mode. > > IMHO, we should merge the OMAP DMA engine support which is now sufficiently > tested and has been in linux-next for some time. Polling mode and ASOC > related issues can be then debugged directly on mainline. > For the time being, the SOC patch which Tony merged in linux-omap > master can be included along with rest of the OMAP DMA engine patches > to have working kernel. So I take that as you wanting exactly what is in linux-next merged without any further changes? -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
