Kernel Newbies archive on lore.kernel.org
 help / color / Atom feed
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: Fri, 21 Jun 2019 13:12:06 +0300
Message-ID: <20190621101206.GI9224@smile.fi.intel.com> (raw)
In-Reply-To: <fda9c935-47ff-4607-b9dd-941f95c220b0@www.fastmail.com>

On Thu, Jun 20, 2019 at 02:02:11PM -0700, Alexander Ivanov wrote:
> On Tue, 18 Jun 2019 01:41 -07:00, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> > > 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.

> My box is updated with current Fedora distro and now running 5.0.9-301.fc30.x86_64. It's also said that the box has Sunrisepoint chipset. For this chipset, 5.0.9 kernel support following devices:
> 
> static const struct acpi_device_id spt_pinctrl_acpi_match[] = {
> 	{ "INT344B", (kernel_ulong_t)&sptlp_soc_data },
> 	{ "INT345D", (kernel_ulong_t)&spth_soc_data },
> 	{ }
> };
> 
> [ https://elixir.bootlin.com/linux/v5.0.9/source/drivers/pinctrl/intel/pinctrl-sunrisepoint.c#L587 ]
> 
> I believe the box has INT344B device attached to acpi bus proper:
> 
> $ sudo ls -la /sys/bus/acpi/devices/INT344*
> ...
> lrwxrwxrwx. 1 root root 0 Jun 20 11:47 /sys/bus/acpi/devices/INT344B:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT344B:00

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.

> Drivers seem loaded:
> 
> $ lsmod | grep pin
> pinctrl_sunrisepoint    28672  0
> pinctrl_intel          28672  1 pinctrl_sunrisepoint
> 
> However, I don't see any gpio devices.
> 
> $ ls /dev/gpio*
> ls: cannot access '/dev/gpio*': No such file or directory
> $ ls /sys/bus/gpio/devices/
> $
> 
> What am I still missing?

Two items:
- CONFIG_GPIO_SYSFS (deprecated!)
- that this is an old way to access to GPIO chips, the correct one is
  to use character device; libgpiod tools will help you with that

-- 
With Best Regards,
Andy Shevchenko



_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply index

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 17:58 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 [this message]
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-06-14 19:12   ` Bjørn Mork

Reply instructions:

You may reply publically 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=20190621101206.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

Kernel Newbies archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kernelnewbies/0 kernelnewbies/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernelnewbies kernelnewbies/ https://lore.kernel.org/kernelnewbies \
		kernelnewbies@kernelnewbies.org kernelnewbies@archiver.kernel.org
	public-inbox-index kernelnewbies


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernelnewbies.kernelnewbies


AGPL code for this site: git clone https://public-inbox.org/ public-inbox