On Sat, Apr 29, 2017 at 08:30:41AM -0700, Jerry Snitselaar wrote: > On Sat Apr 29 17, Jarkko Sakkinen wrote: > > On Fri, Apr 28, 2017 at 09:27:48AM -0600, Jason Gunthorpe wrote: > > > On Fri, Apr 28, 2017 at 03:12:26PM +0300, Jarkko Sakkinen wrote: > > > > > > > I guess we have a problem in tis such that some of the devices in some > > > > environments are not available through ACPI. There's also of_match_table > > > > but I'm wondering if ACPI and OF would cover everything we are using > > > > pnp_driver for. > > > > > > How do you recover the acpi handle like pnp_acpi_device does from a > > > platform_device? > > > > > > If you know how to do that then we should use acpi_match_table and > > > merge the platform and acpi devices.. > > > > > > Does the acpi_match_table encompass all of the pnp subsystem as well, > > > or do we still need to have pnp_driver to handle legacy pre-acpi PNP > > > systems? > > > > > > Jason > > > > AFAIK with ACPI_COMPANION as in > > > > http://lxr.free-electrons.com/source/net/rfkill/rfkill-gpio.c > > > > /Jarkko > > What about ACPI_HANDLE like is done in thie bit of sdhci_acpi_probe()? > > static int sdhci_acpi_probe(struct platform_device *pdev) > { > struct device *dev = &pdev->dev; > acpi_handle handle = ACPI_HANDLE(dev);
Yes. That can be used for getting the handle. ACPI_HANDLE just wraps ACPI_COMPANION in a way that it extracts the handle from struct acpi_device. /Jarkko ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ tpmdd-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
