Hi Arnd
> dmaengine: shdma: use normal interface for passing slave id
>
> The shmobile platform is one of only two users of the slave_id field
> in dma_slave_config, which is incompatible with the way that the
> dmaengine API normally works.
>
> I've had a closer look at the existing code now a
Hi Arnd, Ulf
> > > > > The alignment_shift and dma_rx_offset values seem to always be
> > > > > the same for all users (at least the remaining ones, possibly there
> > > > > were others originally), so you could hardcode those in tmio_mmc_dma.c
> > > > > and remove the tmio_mmc_dma structure enti
Hi Arnd
Thank you for your DMAEngine fixup patch.
I tried this patch, and have comment.
> dmaengine: shdma: use normal interface for passing slave id
>
> The shmobile platform is one of only two users of the slave_id field
> in dma_slave_config, which is incompatible with the way that the
> dma
Hi Arnd, Ulf
Thank you for your feedback
> > Then, I want to try "dmaengine cleanup" patch-set as 2nd step if possible.
> > I guess [8/9] and [9/9] are not good for "header cleanup" (?) I don't know.
> > Arnd, Ulf, what is your opinion ?
>
> Patch 8 looks great to me.
>
> Patch 9 as I mentione
Hi, I have a Lenovo Yoga 13 laptop with a Realtek RTS5129 card reader
(0bda:0129)
It used to work fine with the RTS5139 kernel driver, but apparently that
driver was removed since kernel 3.16 and replaced with MFD_RTSX_USB /
MMC_REALTEK_USB.
I upgraded to kernel 3.18.1 and compiled those drivers
On Tuesday 06 January 2015 17:10:29 Suman Tripathi wrote:
> Hi Arnd,
> > On Monday 15 December 2014 22:31:06 Suman Tripathi wrote:
> > > @@ -162,6 +206,16 @@ static int sdhci_arasan_probe(struct
> > > platform_device *pdev)> > >
> > > goto clk_dis_ahb;
> > >
> > >
On Tuesday 06 January 2015 11:45:58 Lars-Peter Clausen wrote:
> On 01/05/2015 11:39 PM, Arnd Bergmann wrote:
> > As discussed on the topic of shmobile DMA today, jz4740 is the only
> > user of the slave_id field in dma_slave_config besides shmobile. This
> > use is really incompatible with the way
On Tuesday 06 January 2015 00:20:59 Kuninori Morimoto wrote:
>
> Hi Arnd, Ulf
>
> Thank you for your feedback
>
> > > > The slave_id/chan_priv values are now passed three times into the
> > > > driver, and one should really be enough. I'd suggest removing the
> > > > integer fields from both tmi
On Tuesday 06 January 2015 02:38:53 Kuninori Morimoto wrote:
> Hi Arnd again
>
> > > > The alignment_shift and dma_rx_offset values seem to always be
> > > > the same for all users (at least the remaining ones, possibly there
> > > > were others originally), so you could hardcode those in tmio_mmc
On 01/06/2015 01:47 PM, Måns Rullgård wrote:
Lars-Peter Clausen writes:
On 01/05/2015 11:39 PM, Arnd Bergmann wrote:
As discussed on the topic of shmobile DMA today, jz4740 is the only
user of the slave_id field in dma_slave_config besides shmobile. This
use is really incompatible with the wa
Lars-Peter Clausen writes:
> On 01/05/2015 11:39 PM, Arnd Bergmann wrote:
>> As discussed on the topic of shmobile DMA today, jz4740 is the only
>> user of the slave_id field in dma_slave_config besides shmobile. This
>> use is really incompatible with the way that other drivers use the
>> dmaeng
Hi Arnd,
On Monday 15 December 2014 22:31:06 Suman Tripathi wrote:
> @@ -162,6 +206,16 @@ static int sdhci_arasan_probe(struct platform_device
> *pdev)
> goto clk_dis_ahb;
> }
>
> +#if defined(CONFIG_IOMMU_SUPPORT)
> + sdhci_arasan->domain = iommu_domain_alloc(&amba_
On 01/05/2015 11:39 PM, Arnd Bergmann wrote:
As discussed on the topic of shmobile DMA today, jz4740 is the only
user of the slave_id field in dma_slave_config besides shmobile. This
use is really incompatible with the way that other drivers use the
dmaengine API, so we should get rid of it.
Do
13 matches
Mail list logo
