rt-thread.git/components/drivers/src, branch v2.0.0_beta Unnamed repository; edit this file 'description' to name the repository. http://cgit.235523.xyz/rt-thread.git/atom/components/drivers/src?h=v2.0.0_beta 2014-07-12T23:27:57Z [Drivers] Add workqueue implementation. 2014-07-12T23:27:57Z bernard bernard.xiong@gmail.com 2014-07-12T23:27:57Z urn:sha1:005014e7d0026249078b37e718200da55990928e device/pipe: add a control cmd to get the space left in pipe 2013-10-22T17:43:18Z Grissiom chaos.proton@gmail.com 2013-10-22T17:43:18Z urn:sha1:0feefc03b6008301a19a430427390cc9c44decf8 dev/portal: fix bug in portal callback forwarding 2013-08-22T08:43:06Z Grissiom chaos.proton@gmail.com 2013-08-22T08:43:06Z urn:sha1:246bdde8de4167065b4a52530a9c7be85c189dd8 When forwarding rx/tx callback from the underlaying device(pipe), the "dev" argument should be the portal. So the portal callback could think itself as called. dev/portal: add checks on oflag 2013-08-22T07:12:00Z Grissiom chaos.proton@gmail.com 2013-08-22T07:12:00Z urn:sha1:824261d3bc8467f6220061f43d22321f1ce50bc3 It does not make sense to open portal without a flag. One should open a portal with RT_DEVICE_OFLAG_RDWR in most cases. dev/portal: implement portal device 2013-08-20T04:54:43Z Grissiom chaos.proton@gmail.com 2013-08-20T02:48:15Z urn:sha1:6e676e7754e9042c333ff7f3826766c6462f92be Portal is a device that connect devices. Currently, you can only connect pipes in portal. Pipes are unidirectional. But with portal, you can construct a bidirectional device with two pipes. dev/pipe: make pipe a type of device 2013-08-20T02:16:55Z Grissiom chaos.proton@gmail.com 2013-08-20T02:16:55Z urn:sha1:7e68096a88aaa9279507df54da191893be99f7df Pipe have many differences with char device. The main difference is altough pipe have both read and write, it is unidirectional in nature. dev/pipe: cleanup 2013-08-19T08:25:17Z Grissiom chaos.proton@gmail.com 2013-08-19T08:25:17Z urn:sha1:0340300f89a924b30fd8042b76686a236720d3d7 dev/pipe: call rx_indicate the time we resume reader 2013-08-19T07:57:59Z Grissiom chaos.proton@gmail.com 2013-08-19T07:57:59Z urn:sha1:e8cca2315a790d61c743a71e1a682e6ace7866fd Some reader(FinSh again) would like to block on a semaphore which is released in rx_indicate. So we should invoke rx_indicate in _rt_pipe_resume_reader. device/pipe: add nonblocking read/write and force write mode 2013-08-19T07:35:56Z Grissiom chaos.proton@gmail.com 2013-08-19T07:35:56Z urn:sha1:d683d32bd5502c15be600145966400a41710a7f4 The previous implementation will always blocks the reader/writer. However, at least FinSh would expect the device to be nonblocking --- read should return 0 when there is no data in it. ringbuffer: add put_force and putchar_force API 2013-08-19T07:32:42Z Grissiom chaos.proton@gmail.com 2013-08-19T03:52:04Z urn:sha1:4919d29d693491e8eae9697deed7b808c7bcbb93 Add the APIs that will discard the old data when rb is full.