From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Florian Eckert <fe@dev.tdt.de>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Enrico Weigelt <info@metux.net>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jean Delvare <jdelvare@suse.com>,
Wolfram Sang <wsa@the-dreams.de>,
Eckert.Florian@googlemail.com, linux-gpio@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: Add a SSDT ACPI description to recognize my I2C device connected via SMBus
Date: Thu, 30 Sep 2021 09:19:14 +0300 [thread overview]
Message-ID: <CAHp75Ve4HeJNP3oZB-UMQ7HjGBJcxX=1zF0-ijaWr_Tj2KestQ@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VdALPTzQE-tKj40Ft2b+13AyQKh-Scia_EjYyp54mJtPA@mail.gmail.com>
On Thu, Sep 30, 2021 at 9:15 AM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
> On Thu, Sep 30, 2021 at 1:40 AM Florian Eckert <fe@dev.tdt.de> wrote:
...
> > > 5) as Mika suggested, have you checked the kernel configuration?
> >
> > I have now switched on the suggested option
> > CONFIG_ACPI_CUSTOM_METHOD=y
> > CONFIG_ACPI_TABLE_UPGRADE=y
> > CONFIG_CONFIGFS_FS=y
> > CONFIG_ACPI_CONFIGFS=y
> > CONFIG_ACPI_DEBUG=y
> >
> > But this did not solved my issue loading ssdt during runtime.
>
> It won't as explained in 4) above.
It won't _alone_ solve it, i.o.w. it's required but not sufficient.
Means you have to keep these configuration options enabled.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2021-09-30 6:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200407173849.43628-1-andriy.shevchenko@linux.intel.com>
[not found] ` <290741faab199d3e43b6255bf2282075@dev.tdt.de>
[not found] ` <YUrO5ajlS9wS6xYU@smile.fi.intel.com>
[not found] ` <YUrg6TfVhk+TIxDz@smile.fi.intel.com>
2021-09-23 14:17 ` Add a SSDT ACPI description to recognize my I2C device connected via SMBus Florian Eckert
2021-09-23 16:24 ` Mika Westerberg
2021-09-23 20:26 ` Andy Shevchenko
2021-09-23 20:29 ` Andy Shevchenko
2021-09-29 22:40 ` Florian Eckert
2021-09-30 6:15 ` Andy Shevchenko
2021-09-30 6:19 ` Andy Shevchenko [this message]
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='CAHp75Ve4HeJNP3oZB-UMQ7HjGBJcxX=1zF0-ijaWr_Tj2KestQ@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=Eckert.Florian@googlemail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fe@dev.tdt.de \
--cc=info@metux.net \
--cc=jdelvare@suse.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=wsa@the-dreams.de \
/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).