From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Alexander Ivanov <amivanov@fastmail.com>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
"Bjørn Mork" <bjorn@mork.no>, "Jean Delvare" <jdelvare@suse.de>,
kernelnewbies@kernelnewbies.org
Subject: Re: GPIO Driver for Skylake-Y PCH
Date: Tue, 25 Jun 2019 14:08:15 +0300 [thread overview]
Message-ID: <20190625110815.GU9224@smile.fi.intel.com> (raw)
In-Reply-To: <3442d71f-1621-48b8-bbd7-7031d8a25653@www.fastmail.com>
On Mon, Jun 24, 2019 at 11:39:42AM -0700, Alexander Ivanov wrote:
> On Fri, 21 Jun 2019 10:39 -07:00, Alexander Ivanov <amivanov@fastmail.com> wrote:
> >
> > On Fri, 21 Jun 2019 03:12 -07:00, Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > >
> > > Usually to check this is better to run
> > > grep -H 15 /sys/bus/acpi/devices/*/status
> > > which return you the list of *present and available* ACPI devices.
> >
> >
> > It looks like INT344B device is neither present nor available. This
> > device isn't in the list returned by above grep.
> > Its status actually returns 0. What could be reasons for that?
> >
>
> Any idea why would otherwise 'visible' [1] device appear unavailable and not present [2]?
> I cannot see anything obviously wrong in kernel traces either.
>
>
> [1] # tree /sys/bus/acpi/devices/INT344B\:00/
> /sys/bus/acpi/devices/INT344B:00/
> ├── hid
> ├── modalias
> ├── path
> ├── power
> │ ├── autosuspend_delay_ms
> │ ├── control
> │ ├── runtime_active_time
> │ ├── runtime_status
> │ └── runtime_suspended_time
> ├── status
> ├── subsystem -> ../../../../../bus/acpi
> └── uevent
>
> [2] # cat /sys/bus/acpi/devices/INT344B\:00/status
> 0
There is no issue with kernel. ACPI tables provided by firmware, so,
vendor of your firmware decided to turn off this device.
--
With Best Regards,
Andy Shevchenko
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-06-25 11:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 17:58 GPIO Driver for Skylake-Y PCH Alexander Ivanov
2019-06-14 18:46 ` Valdis Klētnieks
2019-06-14 19:01 ` Alexander Ivanov
2019-06-14 19:09 ` Valdis Klētnieks
2019-06-14 20:25 ` Alexander Ivanov
2019-06-14 22:40 ` Alexander Ivanov
2019-06-15 8:53 ` Bjørn Mork
2019-06-15 19:30 ` Valdis Klētnieks
2019-06-15 19:38 ` Alexander Ivanov
2019-06-15 19:56 ` Greg KH
2019-06-16 1:50 ` Valdis Klētnieks
2019-06-16 2:45 ` Alexander Ivanov
2019-06-16 8:54 ` Bjørn Mork
2019-06-17 8:06 ` Andy Shevchenko
2019-06-18 0:00 ` Alexander Ivanov
2019-06-18 8:40 ` Andy Shevchenko
2019-06-18 14:48 ` Valdis Klētnieks
2019-06-18 15:57 ` Andy Shevchenko
2019-06-18 16:17 ` Alexander Ivanov
2019-06-20 21:02 ` Alexander Ivanov
2019-06-21 10:12 ` Andy Shevchenko
2019-06-21 17:39 ` Alexander Ivanov
2019-06-24 18:39 ` Alexander Ivanov
2019-06-25 11:08 ` Andy Shevchenko [this message]
2019-06-25 14:10 ` Linus Walleij
2019-07-10 16:04 ` Andy Shevchenko
2019-08-28 21:04 ` Alexander Ivanov
2019-08-29 7:47 ` Valentin Vidić
2019-08-29 10:49 ` Andy Shevchenko
2019-08-29 11:49 ` Valentin Vidić
2019-08-29 14:59 ` Andy Shevchenko
2019-08-29 17:17 ` Valentin Vidić
2019-08-29 15:59 ` Alexander Ivanov
2019-06-14 19:12 ` Bjørn Mork
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=20190625110815.GU9224@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=amivanov@fastmail.com \
--cc=bjorn@mork.no \
--cc=jdelvare@suse.de \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linus.walleij@linaro.org \
--cc=valdis.kletnieks@vt.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.