[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 2/2] RFC: Xen pad logic



On Mon, Mar 26, 2012 at 07:29:09AM +0000, Liu, Jinsong wrote:
> Konrad Rzeszutek Wilk wrote:
> >> +static struct acpi_driver xen_acpi_pad_driver = {
> >> +  .name = "processor_aggregator",
> >> +  .class = ACPI_PROCESSOR_AGGREGATOR_CLASS,
> >> +  .ids = xen_pad_device_ids,
> >> +  .ops = {
> >> +          .add = xen_acpi_pad_add,
> >> +          .remove = xen_acpi_pad_remove,
> >> +  },
> >> +};
> >> +
> >> +static int __init xen_acpi_pad_init(void)
> >> +{
> >> +  return acpi_bus_register_driver(&xen_acpi_pad_driver);
> > 
> > If the acpi_bus_register_driver function could work with multiple
> > acpi_drivers that define the same class (and have some priority) would
> > this be easier?
> 
> Not quite clear your point, could you elaborate more?

I was thinking it could do multiple registration of a driver servicing the
same PNPxxx.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.