All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: <vinod.koul@intel.com>, <arnd@arndb.de>,
	<andy.shevchenko@gmail.com>, <linux-mmc@vger.kernel.org>,
	<nsekhar@ti.com>, <linux-kernel@vger.kernel.org>,
	<linux-spi@vger.kernel.org>, <dmaengine@vger.kernel.org>,
	<linux-omap@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC v02 03/15] dmaengine: core: Introduce new, universal API to request a channel
Date: Tue, 1 Dec 2015 10:13:20 +0200	[thread overview]
Message-ID: <565D56A0.2090204@ti.com> (raw)
In-Reply-To: <20151130155142.GZ2517@atomide.com>

On 11/30/2015 05:51 PM, Tony Lindgren wrote:
> Hi,
> 
> * Peter Ujfalusi <peter.ujfalusi@ti.com> [151130 05:49]:
>>
>> For each dmaengine driver an array of DMA device, slave and the parameter
>> for the filter function needs to be added:
>>
>> static struct dma_filter_map da830_edma_map[] = {
>> 	DMA_FILTER_ENTRY("davinci-mcasp.0", "rx", EDMA_CTLR_CHAN(0, 0)),
>> 	DMA_FILTER_ENTRY("davinci-mcasp.0", "tx", EDMA_CTLR_CHAN(0, 1)),
>> 	DMA_FILTER_ENTRY("davinci-mcasp.1", "rx", EDMA_CTLR_CHAN(0, 2)),
>> 	DMA_FILTER_ENTRY("davinci-mcasp.1", "tx", EDMA_CTLR_CHAN(0, 3)),
>> 	DMA_FILTER_ENTRY("davinci-mcasp.2", "rx", EDMA_CTLR_CHAN(0, 4)),
>> 	DMA_FILTER_ENTRY("davinci-mcasp.2", "tx", EDMA_CTLR_CHAN(0, 5)),
>> 	DMA_FILTER_ENTRY("spi_davinci.0", "rx", EDMA_CTLR_CHAN(0, 14)),
>> 	DMA_FILTER_ENTRY("spi_davinci.0", "tx", EDMA_CTLR_CHAN(0, 15)),
>> 	DMA_FILTER_ENTRY("da830-mmc.0", "rx", EDMA_CTLR_CHAN(0, 16)),
>> 	DMA_FILTER_ENTRY("da830-mmc.0", "tx", EDMA_CTLR_CHAN(0, 17)),
>> 	DMA_FILTER_ENTRY("spi_davinci.1", "rx", EDMA_CTLR_CHAN(0, 18)),
>> 	DMA_FILTER_ENTRY("spi_davinci.1", "tx", EDMA_CTLR_CHAN(0, 19)),
>> };
> 
> FYI, if the EDMA_CTRL_CHAN above is just the evtmux registers

No, they are not. They are the eDMA event numbers. I used the EDMA_CTRL_CHAN()
macro for all board files to have uniform look for the data. The first
parameter means the eDMA instance number while the second is the event number
on that eDMA. Since most devices have only one eDMA, we have 0 as eDMA id in
most cases.
The eventmux, or crossbar is different thing and we have several versions of
the event crossbar or mux used.

> those
> can be handled with the pinctrl framework. It seems that would allow
> leaving out some of the built-in look up data, and have the mux parts
> handled by a proper device driver. Below is a sample from the dm81xx
> platform for reference.
> 
> SoC dtsi file:
> 
> evtmux: pinmux@f90 {
> 	compatible = "pinctrl-single";
> 	reg = <0xf90 0x40>;
> 	#address-cells = <1>;
> 	#size-cells = <0>;
> 	pinctrl-single,register-width = <8>;
> 	pinctrl-single,function-mask = <0x1f>;
> };
> 
> Board specific dts file:
> 
> &evtmux {
> 	sd2_edma_pins: pinmux_sd2_edma_pins {
> 	pinctrl-single,pins = <
> 		8 1     /* use SDTXEVT1 for EDMA instead of MCASP0TX */
> 		9 2     /* use SDRXEVT1 for EDMA instead of MCASP0RX */
> 		>;
> 	};
> };

I see. The dm81xx basically am33xx/am43xx?

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

> Dynamic muxing of these channels can be done too using the pinctrl
> framework named modes, but probably is not a good idea in the case of
> SD card and MaASP in case something goes wrong :)

In theory it can be done, but in practice it is not possible. It is up to the
board design decision to select which DMA event is not needed to be used in
default mode and that one can be used to route the crossbar hidden request to it.
Just imaging: playing audio from MMC (in the example you have), audio needs
constant DMA, so the MMC would never get DMA request, also the drivers tend to
request the DMA channel in their probe/init and hold to it as long as they are
loaded...

-- 
Péter

WARNING: multiple messages have this Message-ID (diff)
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: arnd@arndb.de, vinod.koul@intel.com, linux-mmc@vger.kernel.org,
	nsekhar@ti.com, linux-kernel@vger.kernel.org,
	linux-spi@vger.kernel.org, andy.shevchenko@gmail.com,
	dmaengine@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC v02 03/15] dmaengine: core: Introduce new, universal API to request a channel
Date: Tue, 1 Dec 2015 10:13:20 +0200	[thread overview]
Message-ID: <565D56A0.2090204@ti.com> (raw)
In-Reply-To: <20151130155142.GZ2517@atomide.com>

On 11/30/2015 05:51 PM, Tony Lindgren wrote:
> Hi,
> 
> * Peter Ujfalusi <peter.ujfalusi@ti.com> [151130 05:49]:
>>
>> For each dmaengine driver an array of DMA device, slave and the parameter
>> for the filter function needs to be added:
>>
>> static struct dma_filter_map da830_edma_map[] = {
>> 	DMA_FILTER_ENTRY("davinci-mcasp.0", "rx", EDMA_CTLR_CHAN(0, 0)),
>> 	DMA_FILTER_ENTRY("davinci-mcasp.0", "tx", EDMA_CTLR_CHAN(0, 1)),
>> 	DMA_FILTER_ENTRY("davinci-mcasp.1", "rx", EDMA_CTLR_CHAN(0, 2)),
>> 	DMA_FILTER_ENTRY("davinci-mcasp.1", "tx", EDMA_CTLR_CHAN(0, 3)),
>> 	DMA_FILTER_ENTRY("davinci-mcasp.2", "rx", EDMA_CTLR_CHAN(0, 4)),
>> 	DMA_FILTER_ENTRY("davinci-mcasp.2", "tx", EDMA_CTLR_CHAN(0, 5)),
>> 	DMA_FILTER_ENTRY("spi_davinci.0", "rx", EDMA_CTLR_CHAN(0, 14)),
>> 	DMA_FILTER_ENTRY("spi_davinci.0", "tx", EDMA_CTLR_CHAN(0, 15)),
>> 	DMA_FILTER_ENTRY("da830-mmc.0", "rx", EDMA_CTLR_CHAN(0, 16)),
>> 	DMA_FILTER_ENTRY("da830-mmc.0", "tx", EDMA_CTLR_CHAN(0, 17)),
>> 	DMA_FILTER_ENTRY("spi_davinci.1", "rx", EDMA_CTLR_CHAN(0, 18)),
>> 	DMA_FILTER_ENTRY("spi_davinci.1", "tx", EDMA_CTLR_CHAN(0, 19)),
>> };
> 
> FYI, if the EDMA_CTRL_CHAN above is just the evtmux registers

No, they are not. They are the eDMA event numbers. I used the EDMA_CTRL_CHAN()
macro for all board files to have uniform look for the data. The first
parameter means the eDMA instance number while the second is the event number
on that eDMA. Since most devices have only one eDMA, we have 0 as eDMA id in
most cases.
The eventmux, or crossbar is different thing and we have several versions of
the event crossbar or mux used.

> those
> can be handled with the pinctrl framework. It seems that would allow
> leaving out some of the built-in look up data, and have the mux parts
> handled by a proper device driver. Below is a sample from the dm81xx
> platform for reference.
> 
> SoC dtsi file:
> 
> evtmux: pinmux@f90 {
> 	compatible = "pinctrl-single";
> 	reg = <0xf90 0x40>;
> 	#address-cells = <1>;
> 	#size-cells = <0>;
> 	pinctrl-single,register-width = <8>;
> 	pinctrl-single,function-mask = <0x1f>;
> };
> 
> Board specific dts file:
> 
> &evtmux {
> 	sd2_edma_pins: pinmux_sd2_edma_pins {
> 	pinctrl-single,pins = <
> 		8 1     /* use SDTXEVT1 for EDMA instead of MCASP0TX */
> 		9 2     /* use SDRXEVT1 for EDMA instead of MCASP0RX */
> 		>;
> 	};
> };

I see. The dm81xx basically am33xx/am43xx?

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

> Dynamic muxing of these channels can be done too using the pinctrl
> framework named modes, but probably is not a good idea in the case of
> SD card and MaASP in case something goes wrong :)

In theory it can be done, but in practice it is not possible. It is up to the
board design decision to select which DMA event is not needed to be used in
default mode and that one can be used to route the crossbar hidden request to it.
Just imaging: playing audio from MMC (in the example you have), audio needs
constant DMA, so the MMC would never get DMA request, also the drivers tend to
request the DMA channel in their probe/init and hold to it as long as they are
loaded...

-- 
Péter

WARNING: multiple messages have this Message-ID (diff)
From: peter.ujfalusi@ti.com (Peter Ujfalusi)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v02 03/15] dmaengine: core: Introduce new, universal API to request a channel
Date: Tue, 1 Dec 2015 10:13:20 +0200	[thread overview]
Message-ID: <565D56A0.2090204@ti.com> (raw)
In-Reply-To: <20151130155142.GZ2517@atomide.com>

On 11/30/2015 05:51 PM, Tony Lindgren wrote:
> Hi,
> 
> * Peter Ujfalusi <peter.ujfalusi@ti.com> [151130 05:49]:
>>
>> For each dmaengine driver an array of DMA device, slave and the parameter
>> for the filter function needs to be added:
>>
>> static struct dma_filter_map da830_edma_map[] = {
>> 	DMA_FILTER_ENTRY("davinci-mcasp.0", "rx", EDMA_CTLR_CHAN(0, 0)),
>> 	DMA_FILTER_ENTRY("davinci-mcasp.0", "tx", EDMA_CTLR_CHAN(0, 1)),
>> 	DMA_FILTER_ENTRY("davinci-mcasp.1", "rx", EDMA_CTLR_CHAN(0, 2)),
>> 	DMA_FILTER_ENTRY("davinci-mcasp.1", "tx", EDMA_CTLR_CHAN(0, 3)),
>> 	DMA_FILTER_ENTRY("davinci-mcasp.2", "rx", EDMA_CTLR_CHAN(0, 4)),
>> 	DMA_FILTER_ENTRY("davinci-mcasp.2", "tx", EDMA_CTLR_CHAN(0, 5)),
>> 	DMA_FILTER_ENTRY("spi_davinci.0", "rx", EDMA_CTLR_CHAN(0, 14)),
>> 	DMA_FILTER_ENTRY("spi_davinci.0", "tx", EDMA_CTLR_CHAN(0, 15)),
>> 	DMA_FILTER_ENTRY("da830-mmc.0", "rx", EDMA_CTLR_CHAN(0, 16)),
>> 	DMA_FILTER_ENTRY("da830-mmc.0", "tx", EDMA_CTLR_CHAN(0, 17)),
>> 	DMA_FILTER_ENTRY("spi_davinci.1", "rx", EDMA_CTLR_CHAN(0, 18)),
>> 	DMA_FILTER_ENTRY("spi_davinci.1", "tx", EDMA_CTLR_CHAN(0, 19)),
>> };
> 
> FYI, if the EDMA_CTRL_CHAN above is just the evtmux registers

No, they are not. They are the eDMA event numbers. I used the EDMA_CTRL_CHAN()
macro for all board files to have uniform look for the data. The first
parameter means the eDMA instance number while the second is the event number
on that eDMA. Since most devices have only one eDMA, we have 0 as eDMA id in
most cases.
The eventmux, or crossbar is different thing and we have several versions of
the event crossbar or mux used.

> those
> can be handled with the pinctrl framework. It seems that would allow
> leaving out some of the built-in look up data, and have the mux parts
> handled by a proper device driver. Below is a sample from the dm81xx
> platform for reference.
> 
> SoC dtsi file:
> 
> evtmux: pinmux at f90 {
> 	compatible = "pinctrl-single";
> 	reg = <0xf90 0x40>;
> 	#address-cells = <1>;
> 	#size-cells = <0>;
> 	pinctrl-single,register-width = <8>;
> 	pinctrl-single,function-mask = <0x1f>;
> };
> 
> Board specific dts file:
> 
> &evtmux {
> 	sd2_edma_pins: pinmux_sd2_edma_pins {
> 	pinctrl-single,pins = <
> 		8 1     /* use SDTXEVT1 for EDMA instead of MCASP0TX */
> 		9 2     /* use SDRXEVT1 for EDMA instead of MCASP0RX */
> 		>;
> 	};
> };

I see. The dm81xx basically am33xx/am43xx?

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

> Dynamic muxing of these channels can be done too using the pinctrl
> framework named modes, but probably is not a good idea in the case of
> SD card and MaASP in case something goes wrong :)

In theory it can be done, but in practice it is not possible. It is up to the
board design decision to select which DMA event is not needed to be used in
default mode and that one can be used to route the crossbar hidden request to it.
Just imaging: playing audio from MMC (in the example you have), audio needs
constant DMA, so the MMC would never get DMA request, also the drivers tend to
request the DMA channel in their probe/init and hold to it as long as they are
loaded...

-- 
P?ter

  reply	other threads:[~2015-12-01  8:13 UTC|newest]

Thread overview: 147+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 13:45 [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel Peter Ujfalusi
2015-11-30 13:45 ` Peter Ujfalusi
2015-11-30 13:45 ` Peter Ujfalusi
2015-11-30 13:45 ` Peter Ujfalusi
2015-11-30 13:45 ` [RFC v02 01/15] dmaengine: core: Allow NULL mask pointer in __dma_device_satisfies_mask() Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 14:35   ` Andy Shevchenko
2015-11-30 14:35     ` Andy Shevchenko
2015-11-30 14:35     ` Andy Shevchenko
2015-12-01  9:47     ` Peter Ujfalusi
2015-12-01  9:47       ` Peter Ujfalusi
2015-12-01 12:58       ` Andy Shevchenko
2015-12-01 12:58         ` Andy Shevchenko
2015-12-01 17:06         ` Vinod Koul
2015-12-01 17:06           ` Vinod Koul
2015-11-30 13:45 ` [RFC v02 02/15] dmaengine: core: Move and merge the code paths using private_candidate Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 14:42   ` Andy Shevchenko
2015-11-30 14:42     ` Andy Shevchenko
2015-12-01  8:41     ` Peter Ujfalusi
2015-12-01  8:41       ` Peter Ujfalusi
2015-11-30 13:45 ` [RFC v02 03/15] dmaengine: core: Introduce new, universal API to request a channel Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 14:09   ` Arnd Bergmann
2015-11-30 14:09     ` Arnd Bergmann
2015-11-30 14:09     ` Arnd Bergmann
2015-12-01  9:48     ` Peter Ujfalusi
2015-12-01  9:48       ` Peter Ujfalusi
2015-12-01  9:48       ` Peter Ujfalusi
2015-11-30 14:51   ` Andy Shevchenko
2015-11-30 14:51     ` Andy Shevchenko
2015-11-30 14:51     ` Andy Shevchenko
2015-12-01  9:56     ` Peter Ujfalusi
2015-12-01  9:56       ` Peter Ujfalusi
2015-12-01 10:07       ` Andy Shevchenko
2015-12-01 10:07         ` Andy Shevchenko
2015-11-30 15:51   ` Tony Lindgren
2015-11-30 15:51     ` Tony Lindgren
2015-11-30 15:51     ` Tony Lindgren
2015-12-01  8:13     ` Peter Ujfalusi [this message]
2015-12-01  8:13       ` Peter Ujfalusi
2015-12-01  8:13       ` Peter Ujfalusi
2015-12-01 17:00       ` Tony Lindgren
2015-12-01 17:00         ` Tony Lindgren
2015-12-02 10:00         ` Peter Ujfalusi
2015-12-02 10:00           ` Peter Ujfalusi
2015-12-02 10:00           ` Peter Ujfalusi
2015-12-02 10:00           ` Peter Ujfalusi
2015-12-02 15:00           ` Tony Lindgren
2015-12-02 15:00             ` Tony Lindgren
2015-12-02 15:00             ` Tony Lindgren
2015-11-30 13:45 ` [RFC v02 04/15] dmaengine: edma: Add support for DMA filter mapping to slave devices Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 14:11   ` Arnd Bergmann
2015-11-30 14:11     ` Arnd Bergmann
2015-12-01  9:58     ` Peter Ujfalusi
2015-12-01  9:58       ` Peter Ujfalusi
2015-12-01  9:58       ` Peter Ujfalusi
2015-12-01 10:14       ` Arnd Bergmann
2015-12-01 10:14         ` Arnd Bergmann
2015-12-01 17:22   ` Vinod Koul
2015-12-01 17:22     ` Vinod Koul
2015-12-01 20:20     ` Arnd Bergmann
2015-12-01 20:20       ` Arnd Bergmann
2015-12-01 20:20       ` Arnd Bergmann
2015-12-02  4:37       ` Vinod Koul
2015-12-02  4:37         ` Vinod Koul
2015-12-02  4:37         ` Vinod Koul
2015-12-02 10:02         ` Peter Ujfalusi
2015-12-02 10:02           ` Peter Ujfalusi
2015-12-02 10:02           ` Peter Ujfalusi
2015-11-30 13:45 ` [RFC v02 05/15] ARM: davinci: devices-da8xx: Add dma_filter_map to edma Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45 ` [RFC v02 06/15] ARM: davinci: dm355: " Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45 ` [RFC v02 07/15] ARM: davinci: dm365: " Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45 ` [RFC v02 08/15] ARM: davinci: dm644x: " Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45 ` [RFC v02 09/15] ARM: davinci: dm646x: " Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45 ` [RFC v02 10/15] mmc: davinci_mmc: Use dma_request_chan() to requesting DMA channel Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45 ` [RFC v02 11/15] spi: davinci: " Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2016-05-02 11:04   ` Applied "spi: davinci: Use dma_request_chan() for requesting DMA channel" to the spi tree Mark Brown
2016-05-02 11:04     ` Mark Brown
2015-11-30 13:45 ` [RFC v02 12/15] ARM: davinci: devices-da8xx: Remove DMA resources for MMC and SPI Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45 ` [RFC v02 13/15] ARM: davinci: devices: Remove DMA resources for MMC Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45 ` [RFC v02 14/15] ARM: davinci: dm355: Remove DMA resources for SPI Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45 ` [RFC v02 15/15] ARM: davinci: dm365: " Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 13:45   ` Peter Ujfalusi
2015-11-30 14:18 ` [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel Arnd Bergmann
2015-11-30 14:18   ` Arnd Bergmann
2015-12-01 10:12   ` Peter Ujfalusi
2015-12-01 10:12     ` Peter Ujfalusi
2015-12-01 10:12     ` Peter Ujfalusi
2015-12-01 10:12     ` Peter Ujfalusi
2015-12-01 10:15     ` Arnd Bergmann
2015-12-01 10:15       ` Arnd Bergmann
2015-12-01 10:15       ` Arnd Bergmann
2015-11-30 14:32 ` Andy Shevchenko
2015-11-30 14:32   ` Andy Shevchenko
2015-12-01 13:45   ` Peter Ujfalusi
2015-12-01 13:45     ` Peter Ujfalusi
2015-12-01 14:24     ` Arnd Bergmann
2015-12-01 14:24       ` Arnd Bergmann
2015-12-02 10:51       ` Peter Ujfalusi
2015-12-02 10:51         ` Peter Ujfalusi
2015-12-02 13:38         ` Arnd Bergmann
2015-12-02 13:38           ` Arnd Bergmann
2015-12-02 13:38           ` Arnd Bergmann
2015-12-01 16:59 ` Vinod Koul
2015-12-01 16:59   ` Vinod Koul
2015-12-01 16:59   ` Vinod Koul
2015-12-01 20:17   ` Arnd Bergmann
2015-12-01 20:17     ` Arnd Bergmann
2015-12-01 20:17     ` Arnd Bergmann
2015-12-02  4:52     ` Vinod Koul
2015-12-02  4:52       ` Vinod Koul
2015-12-02  8:23       ` Arnd Bergmann
2015-12-02  8:23         ` Arnd Bergmann
2015-12-02 12:29     ` Peter Ujfalusi
2015-12-02 12:29       ` Peter Ujfalusi
2015-12-02 12:29       ` 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=565D56A0.2090204@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=arnd@arndb.de \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=tony@atomide.com \
    --cc=vinod.koul@intel.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: link
Be 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.