From: Lukas Wunner <lukas@wunner.de>
To: Sinan Kaya <okaya@codeaurora.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: Tue, 25 Apr 2017 09:01:54 +0200 [thread overview]
Message-ID: <20170425070154.GC9999@wunner.de> (raw)
In-Reply-To: <3f0f2853-d2e5-be32-2bde-47e72c51a0a6@codeaurora.org>
On Sat, Apr 22, 2017 at 12:48 AM, Sinan Kaya <okaya@codeaurora.org> 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.
Would it be possible to solve this by just returning -EPROBE_DEFER from the
->probe hook if the devices you depend on are not bound yet?
Alternatively, would it be possible to solve it with a struct device_link?
Thanks,
Lukas
next prev parent reply other threads:[~2017-04-25 7:01 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
2017-04-24 23:01 ` Rafael J. Wysocki
2017-04-24 23:33 ` Sinan Kaya
2017-04-25 7:01 ` Lukas Wunner [this message]
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=20170425070154.GC9999@wunner.de \
--to=lukas@wunner.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okaya@codeaurora.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).