Date: Sat, 12 Nov 2011 10:33:42 +0200 From: JD Louw <jdl.ntq@gmail.com> To: Hans Petter Selasky <hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: [uslcom][patch] Add GPIO support Message-ID: <CAB-7mS5JqszhkGKet%2BQpOCvHqSrVpj7m4dtS3MrmMsGYtQxQcg@mail.gmail.com> In-Reply-To: <201111120839.41108.hselasky@c2i.net> References: <CAB-7mS6-kZk_Vxyd%2BQ-cGBEdAzqw=-QAh4GnH2OPVYC1fE5hqA@mail.gmail.com> <201111120839.41108.hselasky@c2i.net>
index | next in thread | previous in thread | raw e-mail
On Sat, Nov 12, 2011 at 9:39 AM, Hans Petter Selasky <hselasky@c2i.net> wrote: > On Friday 11 November 2011 22:06:19 JD Louw wrote: >> This patch adds custom IOCTLs to read and write the 4 GPIO pins on the >> cp2103 usb-to-serial chip. Time from IOCTL to actual pin change is >> pretty slow though. > > Hi, > > How slow is it? > > Have you tried reducing the interval of the intervalled control request and > see if there are any changes? Maybe the intervalled control request should be > started from a timer/callout instead. > > --HPS > Testing with my running lights app I would guess about 150ms. Reducing the control interval to 100ms does cause a corresponding IOCTL time drop. It won't be usable for bit banging, but that's probably not what the GPIOs were intended for. For my purposes 150 ms is fine. Is there an example of starting control requests from a timer/callout? If you want I can have a look, but as it stands I'm happy with it.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAB-7mS5JqszhkGKet%2BQpOCvHqSrVpj7m4dtS3MrmMsGYtQxQcg>