greybus: arche-ctrl: Don't expose driver internals to arche-platform driver
authorViresh Kumar <viresh.kumar@linaro.org>
Wed, 20 Apr 2016 06:18:37 +0000 (11:48 +0530)
committerGreg Kroah-Hartman <gregkh@google.com>
Sat, 23 Apr 2016 00:37:21 +0000 (09:37 +0900)
commit7b62b61c752a4700ecf11d63a7ec40aeb3cee66c
treefd61c48dd760bf5fe4b3ecccb71eaef78dbe3709
parentf2bf63a365425fa7df56c4e1dbe5a6bb29680324
greybus: arche-ctrl: Don't expose driver internals to arche-platform driver

We have chosen the *ugly* way of registering two platform drivers from
the module_init() of only one of them, so that we can avoid having two
separate modules for them.

But we should still be doing this in a sane way. There is no need to
expose internals of arche-ctrl to arche-platform, like PM-ops, probe,
resume, id-table, etc. Just expose an init and a exit callback.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Reviewed-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
drivers/staging/greybus/arche-apb-ctrl.c
drivers/staging/greybus/arche-platform.c
drivers/staging/greybus/arche_platform.h