Re: Thread in driver

winstonhyypia@xxxxxxxxx wrote in
news:12efb42e-b16b-4920-a82b-a87763e0298a@xxxxxxxxxxxxxxxxxxxxxxxxxxx
:

Actually I would like to create a driver which I can pass a
function pointer in. And the driver is able to do the callback
whenever there is an interrupt. Here is my program...

This kind of solution will work only if your callback is inside
another driver (and in CE 6.0 both driver must be kernel mode drivers
or user mode driver of the same "group" and so running inside the same
process).
If you do that calling your driver from an application the callback
code will not be mapped inside the context of the caller (unless you
are in CE 5.0 and the code is inside a DLL that is shared by the
driver and the process) and, anyway, it will run in the context of the
caller process (device.exe in CE 5, the kernel or user-mode device
process in CE 6) and so it won't be able to access your process
memory.

If you need to implement such a mechanism, use a named event and set
it inside the IST. The app will spin a thread that will wait on the
same event and perform the operations that the callback was supposed
to perform when the event is set (you can call your current callback
inside the thread to reduce code changes).
If you need to way for the callback completition before you can accept
a new interrupt you can use another named event that the app will set
and the driver will wait on.
If you need to exchange data between the IST and your app you have a
wide choice of solutions: shared memory block, a IOCTL implemented by
the driver to return information stored inside the IST, a point-to-
point message queue (in this case you won't need the named event
because the queue can be use to synchronize the IST thread and the
application thread.



--
Valter Minute
www.fortechembeddedlabs.it
Training, support and development for Windows CE
(the reply address of this message is invalid)
.

Relevant Pages

  • RE: PROBLEM: kernel oops with g_serial USB gadget on 2.6.30
    ... as the S3C OTG UDC driver does all its job in interrupts. ... way also a packet_done callback is done from an interrupt. ...
    (Linux-Kernel)
  • Re: Thread in driver
    ... And the driver is able to do the callback ... whenever there is an interrupt. ... This kind of solution will work only if your callback is inside ... If you need to implement such a mechanism, use a named event and set ...
    (microsoft.public.windowsce.platbuilder)
  • [PATCH 1/5] call i2c_probe from i2c core
    ... If you want to write a `sensors' driver, ... Whenever a new adapter is inserted, or for all adapters if the driver is ... the callback attach_adapteris called. ... -contains -1 for a probed detection, 0 for a forced detection, or a positive ...
    (Linux-Kernel)
  • Re: V4L2: switch to register_chrdev_region: needs testing/review of release() handling
    ... In addition it allows us to intercept the release callback when the ... drivers do the refcounting in varying degrees of competency (from 'not' ... closes as well will the release be called and the driver can do the ... reconnect the webcam even while some application is still using the old ...
    (Linux-Kernel)
  • Re: Cross Process Callbacks
    ... If you have the help of a wrapper API in the application space, ... application calls a function, CallMeBackWithData(Callback fcn, DWORD ... DeviceIoControl(driver, set up callback, event) ... Driver -> handles buffer cleanup and continues in device.exe context ...
    (microsoft.public.windowsce.platbuilder)
Quantcast