On Fri, 17 Oct 2014, Bjorn Andersson wrote:
> On Wed 08 Oct 01:40 PDT 2014, Lee Jones wrote:
[...]
> > > +static struct qcom_smd_driver qcom_smd_rpm_driver = {
> > > + .probe = qcom_smd_rpm_probe,
> > > + .remove = qcom_smd_rpm_remove,
> > > + .callback = qcom_smd_rpm_callback,
> > > + .driver = {
> > > + .name = "qcom_smd_rpm",
> > > + .owner = THIS_MODULE,
> > > + .of_match_table = qcom_smd_rpm_of_match,
> > > + },
> > > +};
> > > +
> > > +module_qcom_smd_driver(qcom_smd_rpm_driver);
> >
> > I don't like this. What's wrong with the existing platform driver
> > code?
> >
>
> I started off with having smd child devices as platform drivers and had some
> accessor functions to find the open handles that triggered the probe() and
> register the callback with those. But this didn't feel very sane, so I did
> implemented a custom driver struct and probe prototype to simplify writing
> drivers.
>
> May I ask why you dislike this? This is how it's done in so many other places
> in the kernel...
I don't believe that's the case. All owners of their own
module_*_driver() registration calls are busses (see below), whereas
'qcom_smd' is just a driver. Things would soon get out of control if
we allowed every driver in the kernel to supply their own driver
registration information variants.
$ git grep "^module_.*_driver(" | \
cut -d: -f2 | cut -d'(' -f1 | sort | uniq
module_acpi_driver
module_amba_driver
module_comedi_driver
module_comedi_pci_driver
module_comedi_pcmcia_driver
module_comedi_usb_driver
module_gameport_driver
module_hid_driver
module_i2c_driver
module_mcb_driver
module_mipi_dsi_driver
module_pci_driver
module_pcmcia_driver
module_platform_driver
module_serio_driver
module_spi_driver
module_spmi_driver
module_usb_composite_driver
module_usb_driver
module_usb_serial_driver
module_virtio_driver
--
Lee Jones
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 devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
