Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1620012
| From | Lee Jones <lee.jones@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v3] mfd:rtsx: do retry when dma transfer error |
| Date | 2017-04-10 17:10 +0200 |
| Message-ID | <tuJ74-2kr-33@gated-at.bofh.it> (permalink) |
| References | <sWcdA-Is-45@gated-at.bofh.it> <ttxAZ-4Hw-3@gated-at.bofh.it> <ttA5P-6lG-7@gated-at.bofh.it> <tuDO1-7gt-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, 10 Apr 2017, 冯伟linux wrote:
> > --- a/drivers/mfd/rtsx_pcr.c
> > +++ b/drivers/mfd/rtsx_pcr.c
> > @@ -30,6 +30,7 @@
> > #include <linux/platform_device.h>
> > #include <linux/mfd/core.h>
> > #include <linux/mfd/rtsx_pci.h>
> > +#include <linux/mmc/card.h>
> > Why is this required?
> >
> The UHS_SER104_MAX_DTR which is in "card_clock = UHS_SER104_MAX_DTR
> - (pcr->dma_error_count *20000000)" is defined in linux/mmc/card.h, so
> it is required.
Okay.
> > spin_lock_irqsave(&pcr->lock, flags);
> > - if (pcr->trans_result == TRANS_RESULT_FAIL)
> > - err = -EINVAL;
> > + if (pcr->trans_result == TRANS_RESULT_FAIL) {
> > + err = -EILSEQ;
> > "Illegal byte sequence", really?
> >
> This errno need to be -EILSEQ.
You need to explain why.
> >>> + if (card_clock == UHS_SDR104_MAX_DTR &&
> >>> + pcr->dma_error_count &&
> >>> + PCI_PID(pcr) == RTS5227_DEVICE_ID)
> >>> + card_clock = (UHS_SDR104_MAX_DTR -
> >>> + pcr->dma_error_count * 20000000);
> > ... but won't this only reduce the clock frequency just once?
> >
> > There is no point bracketing the whole statement.
> >
> > But you do need to bracket one (the second) section of it.
> >
> The times of DMA transfer error occurrs recorded in dma_error_count,
> When DMA transfer error occurrs, the card_clock is reduced by 20MHz.
I think you'll find this logic will only reduce the clock frequency by
20MHz once and only once.
After the first:
card_clock = (UHS_SDR104_MAX_DTR - pcr->dma_error_count * 20000000)
... happens, the first comparison:
card_clock == UHS_SDR104_MAX_DTR
... will fail on subsequent attempts and will not allow it to be
reduced any further. Did you test it?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH v3] mfd:rtsx: do retry when dma transfer error 冯伟linux <steven_feng@realsil.com.cn> - 2017-04-07 10:40 +0200
Re: [PATCH v3] mfd:rtsx: do retry when dma transfer error Lee Jones <lee.jones@linaro.org> - 2017-04-07 13:20 +0200
Re: [PATCH v3] mfd:rtsx: do retry when dma transfer error 冯伟linux <steven_feng@realsil.com.cn> - 2017-04-10 11:30 +0200
Re: [PATCH v3] mfd:rtsx: do retry when dma transfer error Lee Jones <lee.jones@linaro.org> - 2017-04-10 17:10 +0200
Re: [PATCH v3] mfd:rtsx: do retry when dma transfer error 冯伟linux <steven_feng@realsil.com.cn> - 2017-04-11 05:50 +0200
csiph-web