From: Alexandre Bailon <abailon-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
To: b-liu-l0cyMroinI0@public.gmane.org
Cc: linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
nsekhar-l0cyMroinI0@public.gmane.org,
ptitiano-rdvid1DuHRBWk0Htik3J/w@public.gmane.org,
sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Alexandre Bailon
<abailon-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
Subject: [PATCH 0/2] Update MUSB CPPI 4.1 driver to correctly manage the DA8xx
Date: Sun, 13 Aug 2017 14:04:21 +0200 [thread overview]
Message-ID: <20170813120423.16371-1-abailon@baylibre.com> (raw)
A couple of weeks ago, Sekhar reported a warning issue happening in
CPPI 4.1. The teardown sequence was not correctly programmed.
The caused was a couple of difference between the DSPS and the DA8xx.
These differences are the way to program the autoreq, the teardown and
the DMA mode.
This series intends to fix the teardown and to correctly program
the DMA mode.
This series has been roughly tested.
I have only tried it on the DA580 LCK and the BeagleBone Black.
Only the device mode (msc and ecm) have been tested.
Alexandre Bailon (2):
usb: musb: musb_cppi41: Fix the address of teardown and autoreq
registers
usb: musb: musb_cppi41: Fix cppi41_set_dma_mode() for DA8xx
drivers/usb/musb/musb_cppi41.c | 63 +++++++++++++++++++++++++++++++++++++-----
1 file changed, 56 insertions(+), 7 deletions(-)
--
2.13.0
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-08-13 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 12:04 Alexandre Bailon [this message]
[not found] ` <20170813120423.16371-1-abailon-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2017-08-13 12:04 ` [PATCH 1/2] usb: musb: musb_cppi41: Fix the address of teardown and autoreq registers Alexandre Bailon
[not found] ` <20170813120423.16371-2-abailon-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2017-08-14 13:31 ` Sekhar Nori
[not found] ` <7ee74cb1-19aa-5323-5325-ef9cc3410762-l0cyMroinI0@public.gmane.org>
2017-08-14 13:36 ` Sekhar Nori
[not found] ` <abce1d79-bc75-2018-2112-d701a8ca69d5-l0cyMroinI0@public.gmane.org>
2017-09-04 13:02 ` Sekhar Nori
[not found] ` <868405c0-0731-7546-509c-8270eb20f30e-l0cyMroinI0@public.gmane.org>
2017-09-07 17:16 ` Bin Liu
[not found] ` <20170907171602.GB21905-zlS79ln5qqxp6PWD+TyudpdHMjK6IpyN@public.gmane.org>
2017-09-12 6:42 ` Alexandre Bailon
2017-08-15 10:12 ` Sergei Shtylyov
[not found] ` <6e5b0e12-d298-b698-bc06-d9c3ae8fb5c3-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2017-09-12 6:49 ` Alexandre Bailon
2017-08-13 12:04 ` [PATCH 2/2] usb: musb: musb_cppi41: Fix cppi41_set_dma_mode() for DA8xx Alexandre Bailon
[not found] ` <20170813120423.16371-3-abailon-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2017-08-15 10:23 ` Sergei Shtylyov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170813120423.16371-1-abailon@baylibre.com \
--to=abailon-rdvid1duhrbwk0htik3j/w@public.gmane.org \
--cc=b-liu-l0cyMroinI0@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nsekhar-l0cyMroinI0@public.gmane.org \
--cc=ptitiano-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox