greybus: arche-ctrl: Don't expose driver internals to arche-platform driver

Browse source

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>

...

This commit is contained in:

Viresh Kumar 2016-04-20 11:48:37 +05:30 • committed by Greg Kroah-Hartman

parent f2bf63a365

commit 7b62b61c75

3 changed files with 33 additions and 27 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

34

drivers/staging/greybus/arche-apb-ctrl.c

View file

19

drivers/staging/greybus/arche-platform.c

View file

7

drivers/staging/greybus/arche_platform.h

View file