<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/usb/dwc3, branch v3.6</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/usb/dwc3?h=v3.6</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/usb/dwc3?h=v3.6'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2012-09-06T16:52:30Z</updated>
<entry>
<title>usb: dwc3: gadget: fix pending isoc handling</title>
<updated>2012-09-06T16:52:30Z</updated>
<author>
<name>Pratyush Anand</name>
<email>pratyush.anand@st.com</email>
</author>
<published>2012-08-30T06:51:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f4a53c55117b82e895ec98b1765c9d66940377fc'/>
<id>urn:sha1:f4a53c55117b82e895ec98b1765c9d66940377fc</id>
<content type='text'>
If xfernotready is received and there is no request in request_list then
REQUEST_PENDING flag must be set, so that next request in ep queue is executed.

In case of isoc transfer, if xfernotready is already elapsed and even first
request has not been queued to request_list, then issue END TRANSFER, so that
you can receive xfernotready again and can have notion of current microframe.

Signed-off-by: Pratyush Anand &lt;pratyush.anand@st.com&gt;
Signed-off-by: Felipe Balbi &lt;balbi@ti.com&gt;
</content>
</entry>
<entry>
<title>usb: dwc3: core: fix incorrect usage of resource pointer</title>
<updated>2012-09-06T16:52:28Z</updated>
<author>
<name>Kishon Vijay Abraham I</name>
<email>kishon@ti.com</email>
</author>
<published>2012-08-21T09:26:16Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=066618bc350cc6035c3a0fc559a8ac02f55785a9'/>
<id>urn:sha1:066618bc350cc6035c3a0fc559a8ac02f55785a9</id>
<content type='text'>
Populate the resources for xhci afresh instead of directly using the
*struct resource* of core. *resource* structure has parent, sibling,
child pointers which should be filled only by resource API's. By
directly using the *resource* pointer of core in xhci, these parent,
sibling, child pointers are already populated even before
*platform_device_add* causing side effects.

Cc: stable@vger.kernel.org # v3.4, v3.5
Reported-by: Ruchika Kharwar &lt;ruchika@ti.com&gt;
Tested-by: Moiz Sonasath &lt;m-sonasath@ti.com&gt;
Signed-off-by: Kishon Vijay Abraham I &lt;kishon@ti.com&gt;
Signed-off-by: Felipe Balbi &lt;balbi@ti.com&gt;
</content>
</entry>
<entry>
<title>usb: dwc3: ep0: correct cache sync issue in case of ep0_bounced</title>
<updated>2012-09-06T16:52:24Z</updated>
<author>
<name>Pratyush Anand</name>
<email>pratyush.anand@st.com</email>
</author>
<published>2012-08-10T08:12:16Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0416e494ce7dc84e2719bc9fb7daecb330476074'/>
<id>urn:sha1:0416e494ce7dc84e2719bc9fb7daecb330476074</id>
<content type='text'>
In case of ep0 out, if length is not aligned to maxpacket size then we use
dwc-&gt;ep_bounce_addr for dma transfer and not request-&gt;dma. Since, we have
alreday done memcpy from dwc-&gt;ep0_bounce to request-&gt;buf, so we do not need to
issue cache sync function. In fact, cache sync function will bring wrong data
in request-&gt;buf from request-&gt;dma in this scenario.

So, cache sync function must not be executed in case of ep0 bounced.

Cc: &lt;stable@vger.kernel.org&gt; # v3.4 v3.5
Signed-off-by: Pratyush Anand &lt;pratyush.anand@st.com&gt;
Signed-off-by: Felipe Balbi &lt;balbi@ti.com&gt;
</content>
</entry>
<entry>
<title>Merge tag 'dwc3-for-v3.6' of git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-next</title>
<updated>2012-07-05T22:15:38Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2012-07-05T22:15:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=933141509cefd64102a943d61d154c5c53bad889'/>
<id>urn:sha1:933141509cefd64102a943d61d154c5c53bad889</id>
<content type='text'>
usb: dwc3: patches for v3.6 merge window

lots of changes for the dwc3 driver which will make
the driver a lot more stable and some changes which
are just cosmetic.

The bulk of changes is related to mis-defined macros
which were never used before, some fixes to error path
which e.g. prevent the driver from initiating two
transfer on ep0out in case of stall, some fixes to
request dequeueing and the End Transfer Command.

We have some changes to U1/U2 handling where we were
enabling those transtions at the wrong spot (though
we haven't seen a problem from that as of today).

A few patches will make it easier to add support for
newer releases of the core by adding definitions for
new registers and changing the code to act accordingly
when certain revisions are detected.

There's also the usual comestic changes to make the
driver easier to maintain and make it easier for new-
comers to understand the driver. Also one patch fixing
a double inclusion of a header.
</content>
</entry>
<entry>
<title>Merge tag 'gadget-for-v3.6' of git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-next</title>
<updated>2012-07-05T22:10:09Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2012-07-05T22:10:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=94ff447cf275170042a7a05b972b6da8b94754ca'/>
<id>urn:sha1:94ff447cf275170042a7a05b972b6da8b94754ca</id>
<content type='text'>
usb: gadget: patches for v3.6 merge window

This is quite a big pull request and contains patches
all over the place.

omap_udc is now a bit cleaner after removing omap2 support,
fixing some checkpatch.pl warnings and errors, switching over
to generic map/unmap routines and preventing a NULL pointer
de-reference.

s3c-hsotg has been switched over to devm_* API, got some
locking fixes and improvements and it also got an implementation
for the pullup() method.

the mass storage gadgets changed default value of the removable
parameter, dropped some unused options and made "file" and "ro"
module_parameters read-only in some cases.

ffs function got support for HID descriptor.

Some UDCs have been converted to clk_prepare_enable() and
clk_disable_unprepare().

Marvell now got support for its USB3 controller in mainline
after introducing its mv_u3d_core.c driver.
</content>
</entry>
<entry>
<title>usb: dwc3: return error in case of run/stop timeout</title>
<updated>2012-07-02T07:04:02Z</updated>
<author>
<name>Pratyush Anand</name>
<email>pratyush.anand@st.com</email>
</author>
<published>2012-07-02T04:51:55Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6f17f74b3d8345663f5fcfd834145685110075bd'/>
<id>urn:sha1:6f17f74b3d8345663f5fcfd834145685110075bd</id>
<content type='text'>
Although timeout has never been experienced, still to make it
meaningful, its better to return error if it ever occurs.

Signed-off-by: Pratyush Anand &lt;pratyush.anand@st.com&gt;
Signed-off-by: Felipe Balbi &lt;balbi@ti.com&gt;
</content>
</entry>
<entry>
<title>usb: dwc3: enable ACCEPT{U1,U2}ENA when SetConfiguration received</title>
<updated>2012-07-02T07:03:55Z</updated>
<author>
<name>Pratyush Anand</name>
<email>pratyush.anand@st.com</email>
</author>
<published>2012-07-02T04:51:54Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e274a31e29b6a097c32f526493f4ebce10856dcb'/>
<id>urn:sha1:e274a31e29b6a097c32f526493f4ebce10856dcb</id>
<content type='text'>
As per databook, ACCEPT{U1,U2}ENA bits should be set after receiving
SetConfiguration Command.

Signed-off-by: Pratyush Anand &lt;pratyush.anand@st.com&gt;
Signed-off-by: Felipe Balbi &lt;balbi@ti.com&gt;
</content>
</entry>
<entry>
<title>usb: dwc3: no need to clear INIT{U1,U2}ENA bits</title>
<updated>2012-07-02T07:03:15Z</updated>
<author>
<name>Pratyush Anand</name>
<email>pratyush.anand@st.com</email>
</author>
<published>2012-07-02T04:51:53Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dd864f20b382b131bfe10c87c5c81985f5bafa54'/>
<id>urn:sha1:dd864f20b382b131bfe10c87c5c81985f5bafa54</id>
<content type='text'>
as per databook, these bits are cleared by hardware on each USB reset,
so no need to clear it explicitly by software in reset ISR.

Signed-off-by: Pratyush Anand &lt;pratyush.anand@st.com&gt;
Signed-off-by: Felipe Balbi &lt;balbi@ti.com&gt;
</content>
</entry>
<entry>
<title>usb: dwc3: keep default hird threshold value as 4b1100</title>
<updated>2012-07-02T07:02:34Z</updated>
<author>
<name>Pratyush Anand</name>
<email>pratyush.anand@st.com</email>
</author>
<published>2012-07-02T04:51:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cbc725b371f80710c5c611db78a501a6cd314ec3'/>
<id>urn:sha1:cbc725b371f80710c5c611db78a501a6cd314ec3</id>
<content type='text'>
as per data book any HIRD threshold value greater than 4b1100 is
invalid. So set the maximum valid value as default values.

Signed-off-by: Pratyush Anand &lt;pratyush.anand@st.com&gt;
Signed-off-by: Felipe Balbi &lt;balbi@ti.com&gt;
</content>
</entry>
<entry>
<title>usb: dwc3: correct set_halt implementation for ep0</title>
<updated>2012-07-02T07:02:07Z</updated>
<author>
<name>Pratyush Anand</name>
<email>pratyush.anand@st.com</email>
</author>
<published>2012-06-25T17:10:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=08f0d96670c53898b4154e7945e77cdd966003f7'/>
<id>urn:sha1:08f0d96670c53898b4154e7945e77cdd966003f7</id>
<content type='text'>
set_halt for ep0 is called to stall a deferred control responses by the
gadget.  We already have a function to stall default control endpoint.
This patch points set_halt for ep0 to the already available function.

Signed-off-by: Pratyush Anand &lt;pratyush.anand@st.com&gt;
Signed-off-by: Michel Sanches &lt;michel.sanches@st.com&gt;
Signed-off-by: Felipe Balbi &lt;balbi@ti.com&gt;
</content>
</entry>
</feed>
