Re: [PATCH v6 0/3] solve SDHCI DWC MSHC 128MB DMA boundary limitation

2018-08-28 Thread Ulf Hansson
On 28 August 2018 at 11:45, Jisheng Zhang wrote: > When using DMA, if the DMA addr spans 128MB boundary, we have to split > the DMA transfer into two so that each one doesn't exceed the boundary. > > patch1 adds adma_table_cnt to struct sdhci_host so that driver can > control the ADMA table

Re: [PATCH v6 0/3] solve SDHCI DWC MSHC 128MB DMA boundary limitation

2018-08-28 Thread Ulf Hansson
On 28 August 2018 at 11:45, Jisheng Zhang wrote: > When using DMA, if the DMA addr spans 128MB boundary, we have to split > the DMA transfer into two so that each one doesn't exceed the boundary. > > patch1 adds adma_table_cnt to struct sdhci_host so that driver can > control the ADMA table

[PATCH v6 0/3] solve SDHCI DWC MSHC 128MB DMA boundary limitation

2018-08-28 Thread Jisheng Zhang
When using DMA, if the DMA addr spans 128MB boundary, we have to split the DMA transfer into two so that each one doesn't exceed the boundary. patch1 adds adma_table_cnt to struct sdhci_host so that driver can control the ADMA table count. patch2 introduces adma_write_desc() hook to struct

[PATCH v6 0/3] solve SDHCI DWC MSHC 128MB DMA boundary limitation

2018-08-28 Thread Jisheng Zhang
When using DMA, if the DMA addr spans 128MB boundary, we have to split the DMA transfer into two so that each one doesn't exceed the boundary. patch1 adds adma_table_cnt to struct sdhci_host so that driver can control the ADMA table count. patch2 introduces adma_write_desc() hook to struct