lkml.org 
[lkml]   [2023]   [Apr]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH v11 02/14] HP BIOSCFG driver - biosattr-interface
HI Thomas,

Sorry for asking again. I just want to be understand exactly what I must do.


> > > >
> > > > > + args->command = command;
> > > > > + args->commandtype = query;
> > > > > + args->datasize = insize;
> > > > > + memcpy(args->data, buffer, flex_array_size(args, data, insize));
> > > > > +
> > > > > + ret = wmi_evaluate_method(HP_WMI_BIOS_GUID, 0, mid, &input, &output);
> > > >
> > > > The driver is mixing calls to the UUID based APIs and the wmi_device
> > > > ones.
> > > > wmi_devices is newer and preferred.
> > >
> > > The driver calls wmi_evaluate_method when initiating an WMI call.
> > > Where is the driver mixing calls to the UUID based APIs and the
> > > wmi_device one?
> > > WMI calls are made by calling hp_wmi_perform_query() which invokes
> > > wmi_evaluate_method().
> > > Did I miss something?
> >
> > wmi_evaluate_method() is UUID-based.
> > struct wmi_driver is wmi_device based.
> >
> > The wmi_driver/wmi_device code essentially does nothing and is only used
> > to validate that a device is present.
> > The same can be done more easily wmi_has_guid().
> >
>

Are you asking to replace all calls to wmi_evaluate_method() which is
UUID based API with calls to wmidev_evaluate_method() which is
wmi_device based? Correct?

\
 
 \ /
  Last update: 2023-04-25 00:16    [W:0.135 / U:0.540 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site