From: Sinan Kaya <okaya@codeaurora.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Timur Tabi <timur@codeaurora.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI / GED: use late init to allow other drivers init
Date: Fri, 21 Apr 2017 18:48:55 -0400 [thread overview]
Message-ID: <f352be8c-fc38-4b56-5932-e82f112b86d3@codeaurora.org> (raw)
In-Reply-To: <bf1ce91f-b232-4dce-5ed7-597b0ef46f92@codeaurora.org>
On 4/21/2017 6:48 PM, Sinan Kaya wrote:
> On 4/21/2017 6:43 PM, Rafael J. Wysocki wrote:
>>> +late_initcall(ged_init);
>> Does this fix the problem?
>>
>> What about if the module in question is loaded after running late_initcalls?
>
> This fixed the issue for me where I had dependencies for QUP I2C driver and GHES
> drivers. Both of them are modules and get probed via normal module execution path.
>
> However, I'm open to improvements. Do you have a better suggestion? I can try
> to add some _DEP stuff if it is present, but I remember Linux doesn't like _DEP
> stuff too much.
>
I forgot to mention that GED driver is a built-in module.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-04-21 22:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 22:28 [PATCH] ACPI / GED: use late init to allow other drivers init Sinan Kaya
2017-04-21 22:43 ` Rafael J. Wysocki
2017-04-21 22:48 ` Sinan Kaya
2017-04-21 22:48 ` Sinan Kaya [this message]
2017-04-24 23:01 ` Rafael J. Wysocki
2017-04-24 23:33 ` Sinan Kaya
2017-04-25 7:01 ` Lukas Wunner
2017-04-25 16:24 ` Sinan Kaya
2017-04-28 2:32 ` Sinan Kaya
2017-05-11 0:58 ` Rafael J. Wysocki
2017-05-11 1:38 ` Sinan Kaya
2017-05-11 0:46 ` Rafael J. Wysocki
2017-05-11 13:43 ` Sinan Kaya
2017-05-11 14:52 ` Rafael J. Wysocki
2017-05-15 2:36 ` Sinan Kaya
2017-05-15 10:59 ` Rafael J. Wysocki
2017-05-21 15:51 ` Sinan Kaya
2017-04-25 1:43 ` Sinan Kaya
2017-04-25 11:03 ` Rafael J. Wysocki
2017-04-25 16:25 ` Sinan Kaya
2017-04-24 22:49 ` Baicar, Tyler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f352be8c-fc38-4b56-5932-e82f112b86d3@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=timur@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).