On Thu, Sep 26, 2013 at 2:55 PM, Joel Fernandes <joelf@xxxxxx> wrote: > HWMOD removal for MMC is breaking edma_start as the events are being manually > triggered due to unused channel list not being clear. > > The above issue is fixed by reading the "dmas" property from the DT node if it > exists and clearing the bits in the unused channel list if the dma controller > used by any device is EDMA. For this purpose we use the of_* helpers to parse > the arguments in the dmas phandle list. > > Also introduced is a minor clean up of a checkpatch error in old code. > > Reviewed-by: Sekhar Nori <nsekhar@xxxxxx> > Reported-by: Balaji T K <balajitk@xxxxxx> > Cc: Sekhar Nori <nsekhar@xxxxxx> > Cc: Tony Lindgren <tony@xxxxxxxxxxx> > Cc: Olof Johansson <olof@xxxxxxxxx> > Cc: Nishanth Menon <nm@xxxxxx> > Cc: Pantel Antoniou <panto@xxxxxxxxxxxxxxxxxxxxxxx> > Cc: Jason Kridner <jkridner@xxxxxxxxxxxxxxx> > Cc: Koen Kooi <koen@xxxxxxxxxxxxxxxxxxxxx> > Signed-off-by: Joel Fernandes <joelf@xxxxxx> > --- > Just resending this patch after discussing with Sekhar and Olof. Actually, the patch you talked to me about was v3 of this. It seems that you have reposted v6 but labelled it v3. This is very confusing. > AM335x is being booted by many users such as the beaglebone community. DT is > the only boot method available for all these users. EDMA is required for the > operation for many common peripherals in AM335x SoC such as McASP, MMC and > Crypto. > > Although EDMA DT nodes are going in only for 3.13, in reality the kernel has > been used for more than a year with EDMA code and out of tree EDMA DTS patches. > Hence though the DT nodes are still not in mainline, this patch can be still be > considered a critical fix as such and it would be great if it could be included > in 3.12-rc release. Thanks. This is really the root of this problem. If you sit on code out of tree for a year, and something breaks that we couldn't even have detected since we didn't have the out-of-tree pieces. We'll help you the first few times (such as now) but we will eventually stop caring. If I was in a worse mood, then I'd just say that since your users already has to have out-of-tree code to even use this functionality, they could just add this fix on top of that stack of patches. But I'm in a slightly better mood than that and I'll pick it up this time. :) > More details about why this broke an existing feature folks were using: > Previously the DMA resources for platform devices were being populated through > HWMOD, however with the recent clean ups with HWMOD, this data has been moved > to Device tree. The EDMA code though is not aware of this so it fails to fetch > the DMA resources correctly which it needs to prepare the unused channel list > (basically doesn't properly clear the channels that are in use, in the unused > list). So that we can learn for next time: What should we (as in us maintainers and you TI) have done differently to avoid this? -Olof -- 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
