On 1/15/2018 7:32 PM, Thomas Monjalon wrote:
15/01/2018 11:55, Guo, Jia:
On 1/15/2018 7:16 AM, Thomas Monjalon wrote:
Hi,
11/01/2018 15:05, Jeff Guo:
+/* A genaral callback for all registerd devices */
Typos: genaral, registerd
So the callback is only for registered devices?
What about ho
15/01/2018 11:55, Guo, Jia:
> On 1/15/2018 7:16 AM, Thomas Monjalon wrote:
> > Hi,
> >
> > 11/01/2018 15:05, Jeff Guo:
> >> +/* A genaral callback for all registerd devices */
> > Typos: genaral, registerd
> >
> > So the callback is only for registered devices?
> > What about hotplugged devices?
>
On 1/15/2018 7:16 AM, Thomas Monjalon wrote:
Hi,
11/01/2018 15:05, Jeff Guo:
+/* A genaral callback for all registerd devices */
Typos: genaral, registerd
So the callback is only for registered devices?
What about hotplugged devices?
the hotplugged devices is managed by the application, if
Hi,
11/01/2018 15:05, Jeff Guo:
> +/* A genaral callback for all registerd devices */
Typos: genaral, registerd
So the callback is only for registered devices?
What about hotplugged devices?
> +/**
> + * It registers the callback for the specific event. Multiple
> + * callbacks cal be registere
This patch aim to add a general uevent mechanism in eal device layer,
to enable all linux kernel object uevent monitoring, user could use these
APIs to monitor and read out the device status info that sent from the
kernel side, then corresponding to handle it, such as when detect hotplug
uevent typ
5 matches
Mail list logo