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>,
"Jean Delvare" <jdelvare@suse.de>, "Bjørn Mork" <bjorn@mork.no>,
kernelnewbies@kernelnewbies.org
Subject: Re: GPIO Driver for Skylake-Y PCH
Date: Tue, 18 Jun 2019 11:40:34 +0300 [thread overview]
Message-ID: <20190618084034.GI9224@smile.fi.intel.com> (raw)
In-Reply-To: <61e483bc-6bf9-4438-87de-7a01fac1ae5b@www.fastmail.com>
On Mon, Jun 17, 2019 at 05:00:54PM -0700, Alexander Ivanov wrote:
> On Mon, 17 Jun 2019 09:39 -07:00, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> >
> > How come that this device is GPIO?
> > I mean what makes you, guys, to come to this conclusion?
> >
>
> Intel document 332996-002EN [1] chapter 28 says GPP_* groups are accessible through the PCH Sideband Interface, while 332690-004EN [2] defines P2SB at d31.f1
>
> Obviously, I am wrong here. However, the question stands, is there linux kernel support for Intel PCH GPIO?
Yes. Most of the SoCs from Intel use GPIO IP based on Chassis specification,
the drivers for which are available under drivers/pinctrl/intel. What you are
looking for is located under PINCTRL_SUNRISEPOINT configuration option.
> [1] http://www.intel.cn/content/dam/www/public/us/en/documents/datasheets/6th-gen-core-pch-u-y-io-datasheet-vol-2.pdf
> [2] https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/100-series-chipset-datasheet-vol-1.pdf
--
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-18 8:41 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 [this message]
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=20190618084034.GI9224@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).