Prev: Confirmation needed, DIFx + Sensor type = No go.
Next: Can the IFS kit be used freely?
From: Doron Holan [MSFT] on 3 Mar 2010 18:20
what do you mean by managed by the framework? UMDF will not present IO
requests to you on that thread, but you can certainly use valid UMDF object
interface pointers in that thread

d

--

This posting is provided "AS IS" with no warranties, and confers no rights.


"gti4ever" <gti4ever(a)discussions.microsoft.com> wrote in message
news:EB9DC71D-537F-499B-930B-4CF100DEDEEC(a)microsoft.com...
> Sorry, what I meant is: if I create a worker thread in my UMDF driver,
> will
> the queues/requests that are used in that thread be managed by the
> framework?
>
> G.
>
>
> "Doron Holan [MSFT]" wrote:
>
>> you want to call IWDFDeviceInitialize::SetFilter to make sure UMDF does
>> not
>> think it is the PPO
>>
>> > Also, can WDF framewrok controls (from Pnp and Power management point
>> > of
>> > view) a worker thread created by UMDF?
>> I don't understand the question
>>
>> d
>>
>> --
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "gti4ever" <gti4ever(a)discussions.microsoft.com> wrote in message
>> news:C62F869F-37C5-4B14-A294-1CD3D3F5B51D(a)microsoft.com...
>> > Thanks Doron,
>> >
>> > In my case, I need that UMDF on top of the PDO always because of some
>> > of
>> > the
>> > user mode post processing needs.
>> >
>> > If I understand your reply correctly, I should not set anything special
>> > in
>> > my raw PDO + UMDF and simply let my HID mini driver and framework
>> > handle
>> > the
>> > power management. Is this correct?
>> >
>> > Also, can WDF framewrok controls (from Pnp and Power management point
>> > of
>> > view) a worker thread created by UMDF?
>> >
>> >
>> > G.
>> >
>> >
>> > "Doron Holan [MSFT]" wrote:
>> >
>> >> power policy ownership (PPO) is a per pnp stack property, not a
>> >> property
>> >> that applies to the entire driver. the hid minidriver cannot be the
>> >> power
>> >> policy owner for minidriver stack, but can certainly be the PPO for
>> >> the
>> >> raw
>> >> PDO it creates. the bigger concern is that there can only be one PPO
>> >> for
>> >> the raw PDO. if you install a UMDF drver on top of the PDO you should
>> >> tell
>> >> UMDF not to be the power policy owner .... BUT if you are always going
>> >> to
>> >> install the UMDF driver on the raw PDO, do not mark it raw b/c it will
>> >> not
>> >> run on its own with out the UMDF FDO. if you stop marking the PDO as
>> >> raw,
>> >> then UMDF should be the PPO
>> >>
>> >> d
>> >>
>> >> --
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >>
>> >> "gti4ever" <gti4ever(a)discussions.microsoft.com> wrote in message
>> >> news:2EF50846-417C-466C-9CD7-6FDBF808EE70(a)microsoft.com...
>> >> > Hi,
>> >> >
>> >> > I created a raw PDO from my KMDF HID mini driver for doing sideband
>> >> > communication. I have also installed a UMDF driver on top of that
>> >> > raw
>> >> > PDO.
>> >> >
>> >> > In this case, what kind of power policy should I apply to that raw
>> >> > PDO?
>> >> > Will
>> >> > it affect the HID mini driver that creates it since HID mini driver
>> >> > can't
>> >> > be
>> >> > a power policy owner.
>> >> >
>> >> > Thanks.
>> >> >
>> >> > G.
>> >> >
>> >> >
>> >> .
>> >>
>> .
>>
First  |  Prev  | 
Pages: 1 2
Prev: Confirmation needed, DIFx + Sensor type = No go.
Next: Can the IFS kit be used freely?