Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1281881
| From | Tony Lindgren <tony@atomide.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC v02 03/15] dmaengine: core: Introduce new, universal API to request a channel |
| Date | 2015-12-02 16:10 +0100 |
| Message-ID | <qBhcB-nj-7@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <qAx9L-4lF-1@gated-at.bofh.it> <qAz1U-5xV-11@gated-at.bofh.it> <qAOkh-76n-3@gated-at.bofh.it> <qAWBc-42t-5@gated-at.bofh.it> <qBcwi-5Mp-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
* Peter Ujfalusi <peter.ujfalusi@ti.com> [151202 02:01]: > On 12/01/2015 07:00 PM, Tony Lindgren wrote: > >> I see. The dm81xx basically am33xx/am43xx? > > > > Yeah similar to am33xx with different clocks and with a bunch of accelerators. > > > >> Actually I would prefer to use the dmaengine's event router framework and we > >> do have support for the am33xx/am43xx type of crossbar already implemented. > >> I'm going to resend the DTS series for am33xx/am43xx to convert them to use > >> the new DT bindings along with the dma event router support: > >> https://www.mail-archive.com/linux-omap%40vger.kernel.org/msg120828.html > > > > OK yes a dmaengine event router works too when available. Good to see > > them as separate driver instances now :) Are only the dts changes missing > > now? > > > > FYI, when we have separate interconnect driver instances, we don't want to > > and cannot tweak registers outside the interconnect instance because of them > > being in separate clock and/or power domains :p > > What does this mean in practice? We can not touch these registers? The DMA > crossbar is a separate driver from the eDMA driver. Seem like it should not affect DMA crossbar as it's a separate driver. What I meant is we need a separate driver for clocks, pinctrl, regulators, PHY, crossbar or syscon to use the SCM registers from drivers sitting on a L4 interonnect. > > In any case, it seems there's no harm using pinctrl for evtmux on dm81xx > > until the event router is available. It's currently only needed on the > > t410 emmc that I'm aware of :) > > The AM33xx/AM43xx DMA crossbar support is in 4.4 already: > 42dbdcc6bf96 dmaengine: ti-dma-crossbar: Add support for crossbar on AM33xx/AM43xx OK great. Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [RFC v02 03/15] dmaengine: core: Introduce new, universal API to request a channel Tony Lindgren <tony@atomide.com> - 2015-11-30 17:00 +0100
Re: [RFC v02 03/15] dmaengine: core: Introduce new, universal API to request a channel Peter Ujfalusi <peter.ujfalusi@ti.com> - 2015-12-01 09:20 +0100
Re: [RFC v02 03/15] dmaengine: core: Introduce new, universal API to request a channel Tony Lindgren <tony@atomide.com> - 2015-12-01 18:10 +0100
Re: [RFC v02 03/15] dmaengine: core: Introduce new, universal API to request a channel Peter Ujfalusi <peter.ujfalusi@ti.com> - 2015-12-02 11:10 +0100
Re: [RFC v02 03/15] dmaengine: core: Introduce new, universal API to request a channel Tony Lindgren <tony@atomide.com> - 2015-12-02 16:10 +0100
csiph-web