Messages in this thread | | | Date | Thu, 20 Nov 2014 13:26:00 +0000 | From | Lee Jones <> | Subject | Re: [PATCH 1/3] mfd: cros_ec: Add Chrome OS EC userspace device interface |
| |
> > I know how the device driver model works. I'm asking where the > > 'device' is registered from, not the 'driver' i.e. platform data, DT, > > ACPI? > > > > Right, sorry for misunderstanding your question and the silly comment then. > > $Subject adds a "cros-ec-dev" mfd cell to the cros ec mfd driver. > So the device is registered from DT when the cros ec device node is > matched (e.g: "google,cros-ec-spi" or "google,cros-ec-i2c") and the > cros ec mfd driver probe function calls mfd_add_devices().
Ah, so it's registered from another MFD device. That's okay then. That answers my question. FWIW I was going to ask about the missing match table, but that's not required in this case.
-- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog
| |