From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Alexander Ivanov" <amivanov@fastmail.com>,
"Bjørn Mork" <bjorn@mork.no>, "Jean Delvare" <jdelvare@suse.de>,
kernelnewbies@kernelnewbies.org
Subject: Re: GPIO Driver for Skylake-Y PCH
Date: Mon, 17 Jun 2019 11:06:14 +0300 [thread overview]
Message-ID: <20190617080614.GX9224@smile.fi.intel.com> (raw)
In-Reply-To: <15515.1560627024@turing-police>
On Sat, Jun 15, 2019 at 03:30:24PM -0400, Valdis Klētnieks wrote:
> On Fri, 14 Jun 2019 15:40:59 -0700, "Alexander Ivanov" said:
>
> (Adding likely knowledgeable people to the recipients)
>
> Jean, Andy, Linus: The situation thus far: Alexander has a system with this GPIO on it:
How come that this device is GPIO?
I mean what makes you, guys, to come to this conclusion?
> > lspci -vvvnns 1f.1
> > 00:1f.1 Memory controller [0580]: Intel Corporation Device [8086:9d20] (rev 21)
> > Subsystem: Gigabyte Technology Co., Ltd Device [1458:1000]
> > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
> > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> > Latency: 0
> > Region 0: Memory at 7d000000 (64-bit, non-prefetchable) [size=16M]
> The obvious first thing to try was:
...which is obviously wrong. See above.
P.S. Agree with Greg that one must update kernel either to LTS or to latest
supported one.
--
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-17 16:39 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 [this message]
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
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=20190617080614.GX9224@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 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).