On Sun, Mar 22, 2020 at 05:17:21PM +0100, Tomek The Messenger wrote:
> What is the use case of using:
> MODULE_SOFTDEP("pre: another-external-kernel-module...");
> because I completely don't understand.
> If I have phandle to another-external-kernel-module in dts which is
> mandatory in my kernel
On Sun, Mar 22, 2020 at 05:08:15PM +0100, Tomek The Messenger wrote:
> Hi
> I am writing some framework for my kernel drivers. I delegated to framework
> the code which is common amongs all kernel drivers. So my framework module
> core.c has none probe, remove functions. It has also none
On Sun, Mar 22, 2020 at 05:26:09PM +0100, Tomek The Messenger wrote:
> I suppose the response is yes but I would like to make sure:
> Is below acceptable:
> some_module_name.c:
> #define DRIVER_NAME "some-driver-name"
> ...
> static struct platform_driver some_driver = {
> .driver = {
I suppose the response is yes but I would like to make sure:
Is below acceptable:
some_module_name.c:
#define DRIVER_NAME "some-driver-name"
...
static struct platform_driver some_driver = {
.driver = {
.name = DRIVER_NAME,
.of_match_table =
What is the use case of using:
MODULE_SOFTDEP("pre: another-external-kernel-module...");
because I completely don't understand.
If I have phandle to another-external-kernel-module in dts which is
mandatory in my kernel driver then should I put this line in my kernel
driver code?
If I use function
Hi
I am writing some framework for my kernel drivers. I delegated to framework
the code which is common amongs all kernel drivers. So my framework module
core.c has none probe, remove functions. It has also none module_init,
module_exit functions at those are not needed.
1.) When I do modprobe of
