From: Darren Hart <dvhart@infradead.org>
To: Mario.Limonciello@dell.com
Cc: linux@dominikbrodowski.net, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Dell Inc. XPS 13 9343/0TM99H fails to boot v4.16-rc5
Date: Tue, 13 Mar 2018 14:42:59 -0700 [thread overview]
Message-ID: <20180313214259.GA9260@localhost.localdomain> (raw)
In-Reply-To: <bddaade724054711ba4682f73ec54264@ausx13mpc120.AMER.DELL.COM>
On Tue, Mar 13, 2018 at 07:07:26AM +0000, Mario.Limonciello@dell.com wrote:
> > -----Original Message-----
> > From: Dominik Brodowski [mailto:linux@dominikbrodowski.net]
> > Sent: Tuesday, March 13, 2018 2:44 PM
> > To: Limonciello, Mario <Mario_Limonciello@Dell.com>; Darren Hart
> > <dvhart@infradead.org>
> > Cc: platform-driver-x86@vger.kernel.org; linux-kernel@vger.kernel.org
> > Subject: Re: Dell Inc. XPS 13 9343/0TM99H fails to boot v4.16-rc5
> >
> > On Tue, Mar 13, 2018 at 06:12:04AM +0000, Mario.Limonciello@dell.com wrote:
> > > As long as they're ready before dell-laptop's initialization which uses
> > > late_initcall that should be fine.
> > >
> > > Am I correct to presume you're going to propose a patch you can test and
> > > confirm your hypothesis rather than Darren reverting my patch to bring
> > > them together?
> >
> > Thanks for the input; a draft patch (which works fine on my system) is
> > attached below.
> >
> > On Mon, Mar 12, 2018 at 11:32:13PM -0700, Darren Hart wrote:
> > > There is one other caveat, which you'll find documented in
> > > dell-laptop.c, namely that dell-laptop needs to init after dell-rbtn
> > > (I'm starting to appreciate the monolithic thinkpad-acpi driver).
> > >
> > > We need things to init in this order (items on the same line have no
> > > dependency):
> > >
> > > 1. DCDBAS, ACPI_WMI
> > > 2. DELL_SMBIOS, DELL_RBTN
> > > 3. DELL_LAPTOP, DELL_WMI
> > >
> > > Currently:
> > > subsys_initcall: ACPI_WMI, DELL_SMBIOS
> > > module_init: DCDBAS, DELL_WMI
> > > late_initcall: DELL_LAPTOP
> > >
> > > From a quick naive glance, it appears as though we might be able to
> > > address this as follows:
> > >
> > > subsys_initcall: DCDBAS, ACPI_WMI
> > > module_init: DELL_SMBIOS, DELL_RBTN
> > > late_initcall: DELL_LAPTOP, DELL_WMI
> >
> > Hmmm. I do not yet understand why you propose to
> >
> > a) advance the DCDBAS initialization to subsys_initcall, as only DELL_LAPTOP
> > (running as a late_initcall) requires it to be up and running, and
>
> Actually dell-smbios itself should require this too. The SMM backend will use
> it during initialization to determine if WSMT is enabled. If it's not operational
> yet then we may get invalid results.
>
Exactly.
> So considering this I think Darren's proposal is good to move DCDBAS to earlier.
>
> >
> > b) delay DELL_WMI to late_initcall, as it can safely be initialized as long
> > as ACPI_WMI is ready.
>
> Maybe Darren meant dell-wmi-descriptor not dell-wmi?
> Otherwise I would agree that part isn't needed.
Like DELL_LAPTOP, DELL_WMI depends on smbios being ready, so needs to
init after DELL_SMBIOS as well.
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2018-03-13 21:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 18:53 Dell Inc. XPS 13 9343/0TM99H fails to boot v4.16-rc5 Dominik Brodowski
2018-03-12 20:23 ` Darren Hart
2018-03-12 22:07 ` Dominik Brodowski
2018-03-12 22:17 ` Linus Torvalds
2018-03-12 23:33 ` Darren Hart
2018-03-14 3:34 ` Darren Hart
2018-03-14 17:23 ` Linus Torvalds
2018-03-14 18:27 ` Darren Hart
2018-03-12 22:42 ` Mario.Limonciello
2018-03-13 5:51 ` Dominik Brodowski
2018-03-13 6:12 ` Mario.Limonciello
2018-03-13 6:43 ` Dominik Brodowski
2018-03-13 7:07 ` Mario.Limonciello
2018-03-13 21:42 ` Darren Hart [this message]
2018-03-14 1:28 ` Mario.Limonciello
2018-03-14 6:25 ` Dominik Brodowski
2018-03-13 6:32 ` Darren Hart
-- strict thread matches above, loose matches on Subject: below --
2018-03-12 20:36 [PATCH v2] platform/x86: dell-smbios: Resolve dependency error on ACPI_WMI Darren Hart
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=20180313214259.GA9260@localhost.localdomain \
--to=dvhart@infradead.org \
--cc=Mario.Limonciello@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=platform-driver-x86@vger.kernel.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