diff options
author | Abhishek Sahu <absahu@codeaurora.org> | 2018-03-12 18:44:54 +0530 |
---|---|---|
committer | Wolfram Sang <wsa@the-dreams.de> | 2018-03-24 13:19:38 +0100 |
commit | c5adc0fa63a930e3313c74bb7c1d4d158130eb41 (patch) | |
tree | 2a10dda89d6e7688e1387dd6d2ad70e2ce968525 /drivers/leds | |
parent | 6d5f37f166bb07b04b4d42e9d1f5427b7931cd3c (diff) | |
download | linux-c5adc0fa63a930e3313c74bb7c1d4d158130eb41.tar.bz2 |
i2c: qup: schedule EOT and FLUSH tags at the end of transfer
The role of FLUSH and EOT tag is to flush already scheduled
descriptors in BAM HW in case of error. EOT is required only
when descriptors are scheduled in RX FIFO. If all the messages
are WRITE, then only FLUSH tag will be used.
A single BAM transfer can have multiple read and write messages.
The EOT and FLUSH tags should be scheduled at the end of BAM HW
descriptors. Since the READ and WRITE can be present in any order
so for some of the cases, these tags are not being written
correctly.
Following is one of the example
READ, READ, READ, READ
Currently EOT and FLUSH tags are being written after each READ.
If QUP gets NACK for first READ itself, then flush will be
triggered. It will look for first FLUSH tag in TX FIFO and will
stop there so only descriptors for first READ descriptors be
flushed. All the scheduled descriptors should be cleared to
generate BAM DMA completion.
Now this patch is scheduling FLUSH and EOT only once after all the
descriptors. So, flush will clear all the scheduled descriptors and
BAM will generate the completion interrupt.
Signed-off-by: Abhishek Sahu <absahu@codeaurora.org>
Reviewed-by: Sricharan R <sricharan@codeaurora.org>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Diffstat (limited to 'drivers/leds')
0 files changed, 0 insertions, 0 deletions