<feed xmlns='http://www.w3.org/2005/Atom'>
<title>tinyusb.git/src/portable/dialog, branch 0.14.0</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/tinyusb.git/atom/src/portable/dialog?h=0.14.0</id>
<link rel='self' href='http://cgit.235523.xyz/tinyusb.git/atom/src/portable/dialog?h=0.14.0'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/tinyusb.git/'/>
<updated>2022-03-07T16:05:05Z</updated>
<entry>
<title>added dcd_sof_enable() stubs for all other ports</title>
<updated>2022-03-07T16:05:05Z</updated>
<author>
<name>hathach</name>
<email>thach@tinyusb.org</email>
</author>
<published>2022-03-07T16:05:05Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/tinyusb.git/commit/?id=606f932d92322a71960f51148ecc91eaf29bf507'/>
<id>urn:sha1:606f932d92322a71960f51148ecc91eaf29bf507</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rename TUSB_OPT_DEVICE_ENABLED to CFG_TUD_ENABLED</title>
<updated>2022-02-25T11:35:21Z</updated>
<author>
<name>hathach</name>
<email>thach@tinyusb.org</email>
</author>
<published>2022-02-23T14:46:40Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/tinyusb.git/commit/?id=d10326cb4e0f48a05bc39c6f51b7b0fb29427cc9'/>
<id>urn:sha1:d10326cb4e0f48a05bc39c6f51b7b0fb29427cc9</id>
<content type='text'>
TUSB_OPT_DEVICE_ENABLED still usable for backward compatible
</content>
</entry>
<entry>
<title>dcd_da1469x: Re-enable RX after resume</title>
<updated>2022-01-20T15:28:09Z</updated>
<author>
<name>Jerzy Kasenberg</name>
<email>jerzy.kasenberg@codecoup.pl</email>
</author>
<published>2022-01-20T08:58:40Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/tinyusb.git/commit/?id=7b078367e82fae8ef4ec094f6db9e584db82f06a'/>
<id>urn:sha1:7b078367e82fae8ef4ec094f6db9e584db82f06a</id>
<content type='text'>
Going to suspend states disable reception on non-0 RX endpoints.

Now when USB resume condition is detected, all RX endpoints
with pending transfers are resumed.
</content>
</entry>
<entry>
<title>dcd_da1469x: Fix over-run/under-run mask</title>
<updated>2022-01-20T09:01:18Z</updated>
<author>
<name>Jerzy Kasenberg</name>
<email>jerzy.kasenberg@codecoup.pl</email>
</author>
<published>2022-01-20T08:55:25Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/tinyusb.git/commit/?id=ae4d901d8351437c499cecef349b84af4bb6c239'/>
<id>urn:sha1:ae4d901d8351437c499cecef349b84af4bb6c239</id>
<content type='text'>
Bit mask enabling/disabling over-run/unde-run was shifted
by one nibble, so interrupt was never enabled.
It did not force any issue as this situation could only
happen on ISO endpoints without DMA.
</content>
</entry>
<entry>
<title>more wMaxPacketSize</title>
<updated>2021-10-24T07:39:02Z</updated>
<author>
<name>hathach</name>
<email>thach@tinyusb.org</email>
</author>
<published>2021-10-24T07:39:02Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/tinyusb.git/commit/?id=109b7a666155eb1b59bf946be7319ac11bc625ea'/>
<id>urn:sha1:109b7a666155eb1b59bf946be7319ac11bc625ea</id>
<content type='text'>
</content>
</entry>
<entry>
<title>remove ep descriptor wMaxPacketSize bitfield due to endian issue</title>
<updated>2021-10-24T06:11:21Z</updated>
<author>
<name>hathach</name>
<email>thach@tinyusb.org</email>
</author>
<published>2021-10-24T06:11:21Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/tinyusb.git/commit/?id=5af989384bd95dbf16f824bcc48e56f3ea283080'/>
<id>urn:sha1:5af989384bd95dbf16f824bcc48e56f3ea283080</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'master' into fix-warnings</title>
<updated>2021-10-23T14:23:56Z</updated>
<author>
<name>Ha Thach</name>
<email>thach@tinyusb.org</email>
</author>
<published>2021-10-23T14:23:56Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/tinyusb.git/commit/?id=311c05b401591507cbc4977926bcc878d3f119aa'/>
<id>urn:sha1:311c05b401591507cbc4977926bcc878d3f119aa</id>
<content type='text'>
</content>
</entry>
<entry>
<title>add volatile to EPx_REGS for -Wcast-qual</title>
<updated>2021-10-17T10:33:14Z</updated>
<author>
<name>hathach</name>
<email>thach@tinyusb.org</email>
</author>
<published>2021-10-17T10:33:14Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/tinyusb.git/commit/?id=099d3b377fd619e664e60c948e6f73d7276dd81d'/>
<id>urn:sha1:099d3b377fd619e664e60c948e6f73d7276dd81d</id>
<content type='text'>
since gcc does difference between volatile struct and member when
casting pointer
</content>
</entry>
<entry>
<title>dcd_da146xx: Drop unexpected data</title>
<updated>2021-10-15T10:02:15Z</updated>
<author>
<name>Jerzy Kasenberg</name>
<email>jerzy.kasenberg@codecoup.pl</email>
</author>
<published>2021-10-15T09:57:52Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/tinyusb.git/commit/?id=bf4b133084585d302691e53faf868c0c37b9eaf0'/>
<id>urn:sha1:bf4b133084585d302691e53faf868c0c37b9eaf0</id>
<content type='text'>
USB3CV tool verifies MSC device by sending too short or
too long packets.
In case of too long packets (msc_device requested 31 bytes
but incoming data had 32 bytes) extra byte(s) were left in
FIFO resulting in some data mismatch later on.

Now if more data is received in packet that expected extra
bytes are just dropped.
</content>
</entry>
<entry>
<title>dcd_da146xx: Fix EPIN stall notification handling</title>
<updated>2021-10-15T10:02:15Z</updated>
<author>
<name>Jerzy Kasenberg</name>
<email>jerzy.kasenberg@codecoup.pl</email>
</author>
<published>2021-10-15T09:34:26Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/tinyusb.git/commit/?id=49aa0b72a8301f21281fa6498af47ac26bcb1bea'/>
<id>urn:sha1:49aa0b72a8301f21281fa6498af47ac26bcb1bea</id>
<content type='text'>
Normal TX handler for IN non-0 endpoints is called during
outgoing transfer or just after it was finished.
It may need to fill TX fifo with same data if TX_DONE is present
but ACK_STAT is not.
It may need to fill more data when called during transfer.
But it may also be called when STALL was sent.
In this case TX_DONE is set ACK_STAT is not, just like for packets
that were sent but no ACK was received.
Code was trying to send something again. There was nothing to send
so empty ZLP was scheduled for stalled endpoint.
This ZLP was later send to host where valid response was required.

This change checks if notification was for STALL endpoint and
does not try to fill TX FIFO in that case.
</content>
</entry>
</feed>
