tinyusb.git/src/portable/dialog, branch 0.15.0 Unnamed repository; edit this file 'description' to name the repository. http://cgit.235523.xyz/tinyusb.git/atom/src/portable/dialog?h=0.15.0 2022-12-04T12:44:01Z more typos 2022-12-04T12:44:01Z hathach thach@tinyusb.org 2022-12-04T11:51:52Z urn:sha1:43b255f413e08b9e567a23b24701efbdaebcb824 added dcd_sof_enable() stubs for all other ports 2022-03-07T16:05:05Z hathach thach@tinyusb.org 2022-03-07T16:05:05Z urn:sha1:606f932d92322a71960f51148ecc91eaf29bf507 rename TUSB_OPT_DEVICE_ENABLED to CFG_TUD_ENABLED 2022-02-25T11:35:21Z hathach thach@tinyusb.org 2022-02-23T14:46:40Z urn:sha1:d10326cb4e0f48a05bc39c6f51b7b0fb29427cc9 TUSB_OPT_DEVICE_ENABLED still usable for backward compatible dcd_da1469x: Re-enable RX after resume 2022-01-20T15:28:09Z Jerzy Kasenberg jerzy.kasenberg@codecoup.pl 2022-01-20T08:58:40Z urn:sha1:7b078367e82fae8ef4ec094f6db9e584db82f06a 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. dcd_da1469x: Fix over-run/under-run mask 2022-01-20T09:01:18Z Jerzy Kasenberg jerzy.kasenberg@codecoup.pl 2022-01-20T08:55:25Z urn:sha1:ae4d901d8351437c499cecef349b84af4bb6c239 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. more wMaxPacketSize 2021-10-24T07:39:02Z hathach thach@tinyusb.org 2021-10-24T07:39:02Z urn:sha1:109b7a666155eb1b59bf946be7319ac11bc625ea remove ep descriptor wMaxPacketSize bitfield due to endian issue 2021-10-24T06:11:21Z hathach thach@tinyusb.org 2021-10-24T06:11:21Z urn:sha1:5af989384bd95dbf16f824bcc48e56f3ea283080 Merge branch 'master' into fix-warnings 2021-10-23T14:23:56Z Ha Thach thach@tinyusb.org 2021-10-23T14:23:56Z urn:sha1:311c05b401591507cbc4977926bcc878d3f119aa add volatile to EPx_REGS for -Wcast-qual 2021-10-17T10:33:14Z hathach thach@tinyusb.org 2021-10-17T10:33:14Z urn:sha1:099d3b377fd619e664e60c948e6f73d7276dd81d since gcc does difference between volatile struct and member when casting pointer dcd_da146xx: Drop unexpected data 2021-10-15T10:02:15Z Jerzy Kasenberg jerzy.kasenberg@codecoup.pl 2021-10-15T09:57:52Z urn:sha1:bf4b133084585d302691e53faf868c0c37b9eaf0 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.