From: "Alexander Ivanov" <amivanov@fastmail.com>
To: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bj?rn Mork <bjorn@mork.no>, Jean Delvare <jdelvare@suse.de>,
kernelnewbies@kernelnewbies.org
Subject: Re: GPIO Driver for Skylake-Y PCH
Date: Tue, 18 Jun 2019 09:17:03 -0700 [thread overview]
Message-ID: <41071619-fa33-4745-9149-f87255120d30@www.fastmail.com> (raw)
In-Reply-To: <20190618155737.GU9224@smile.fi.intel.com>
On Tue, 18 Jun 2019 08:58 -07:00, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> On Tue, Jun 18, 2019 at 10:48:45AM -0400, Valdis Klētnieks wrote:
> > On Tue, 18 Jun 2019 11:40:34 +0300, Andy Shevchenko said:
> >
> > > 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.
> >
> > Thanks for the info, it's often unclear where to look - when the hardware has
> > a PCH and documentation that says it has GPIO, and there's an in-tree driver
> > called gpio_pch, it's easy to fail to look in the right place :)
>
Thank you for the info, indeed. I'm going to give it a try.
> Citing in-kernel documentation:
>
> --- 8< --- 8< ---- 8< ---
>
> Electrical properties of the pin such as biasing and drive strength
> may be placed at some pin-specific register in all cases or as part
> of the GPIO register in case (B) especially. This doesn't mean that such
> properties necessarily pertain to what the Linux kernel calls "GPIO".
>
Given the amount of related (and not so much) documentation, it's hard to miss.
That's what this newsgroup for :)
Thank you for helping!
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-06-18 16:16 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 [this message]
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=41071619-fa33-4745-9149-f87255120d30@www.fastmail.com \
--to=amivanov@fastmail.com \
--cc=andriy.shevchenko@linux.intel.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).