On 2018-05-18 06:03, Vinod wrote:
> On 17-05-18, 12:20, Frank Mori Hess wrote:
>> Sorry to keep coming back to this, but I'm experiencing a bit of
>> incredulity that you are saying what you seem to be saying. You seem
>> to be saying dmaengine provides no way to permanently stop a transfer
>> safely other than transferring the full number of bytes initially
>> requested. So the proper resolution is the 8250 serial driver needs
>> to remove rx dma support, because they are just trying to do something
>> that is not supported.
>> I see two ways of interpreting what you are saying. First, from the
>> point of view of the user of the dmaengine api. From this point of
>> view it is impossible for data loss to occur during pause or reading
>> the residue, so saying they cause no data loss during
>> pause/residue/terminate is meaningless. This is because the user
>> can't confirm any data loss until after they have read the residue and
>> the transfer is terminated, since optimistically the data may still be
>> available if only the user would resume and allow the transfer to
>> Second there is the interpretation I want to believe. This is "no
>> data loss on pause" means that after the pause, no data has been
>> discarded by the dma controller hardware, in fact all the data it has
>> read before being paused has been fully transferred to its
>> destination. Reading the residue while paused gives you an accurate,
>> up-to-date state of the paused transfer. Then finally, although in
>> general dma terminate causes data loss, it does not in this case since
>> we terminated while we were paused and read the up-to-date residue.
>> This is the interpretation implicit in the 8250 serial driver.
> You are simply mixing things up! On Pause we don't expect data loss, as user
> resume the transfer. This means as you rightly guessed, the DMA HW should not
> any data, nor should SW.
> Now if you want to read residue at this point it is perfectly valid. But if
> decide to terminate the channel (yes it is terminate_all API), we abort and
> have context to report back!
> As Lars rightly pointed out, residue calculation are very tricky, DMA fifo may
> have data, some data may be in device FIFO, so residue is always from DMA
> of view and may differ from device view (more or less depending upon
> Now if you require to add more features for your usecase, please do feel free
> send a patch. The framework can always be improved, we haven't solved world
> hunger yet!
Okay, I see that in theory, there are some tricky bits in implementing DMA
support in UART drivers. On the other hand there are already drivers
to be working fine. This discussion is about revert of the feature
pl330 driver, which is required by other in-kernel driver without proper
Can we drop it for now and discuss what and how should be implemented to
everyone happy, without any regressions?
Marek Szyprowski, PhD
Samsung R&D Institute Poland