Re: [PATCH 1/3] mfd: cros_ec: Add Chrome OS EC userspace device interface
From: Lee Jones
Date: Thu Nov 20 2014 - 08:26:36 EST
> > 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.
Linaro STMicroelectronics Landing Team Lead
Linaro.org â Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/