I did: acpidump > acpi.dat acpixtract.pmtools -sDSDT acpi.dat cat DSDT | grep INT33 and got: INT33BDHID INT33BD
..so I guess the BIOS is to blame - we use a LEC-BT SMARC module from ADLINK. I tried to look around in the BIOS but could not find any “pinctrl” options. We did not have this problem using the Jethro branch with this BIOS. Can I “fake” the required ACPI ID’s by patching the ACPI/pinctrl drivers? Regards, Henrik From: Tan, Jui Nee <[email protected]> Sent: Thursday, 18 October 2018 11.41 To: Henrik Haugaard Jensen <[email protected]>; [email protected] Subject: RE: [meta-intel] GPIO functionality for Intel E3845 CPU (valley-island, bay-trail) Could you please try to dump ACPI DSDT table and check if the following strings exist: * INT33B2 * INT33FC These are the ACPI ID required to load BYT pinctrl driver. Thanks, Juinee From: Henrik Haugaard Jensen [mailto:[email protected]] Sent: Wednesday, October 17, 2018 7:04 PM To: Tan, Jui Nee <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: RE: [meta-intel] GPIO functionality for Intel E3845 CPU (valley-island, bay-trail) Thanks, I tried the PINCTRL configs, but /sys/class/gpio/ and /sys/kernel/debug/gpio does still not get populated. A bit of printk debugging show that ”byt_gpio_init” is called but “byt_pinctrl_probe” is not. Any ideas? Regards, Henrik From: Tan, Jui Nee <[email protected]<mailto:[email protected]>> Sent: Wednesday, 17 October 2018 03.11 To: Henrik Haugaard Jensen <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: RE: [meta-intel] GPIO functionality for Intel E3845 CPU (valley-island, bay-trail) You should be able to see the gpiochips available in /sys/class/gpio/gpiochip* and “byt_gpio_init” is also being called with the following kernel configurations enabled: CONFIG_PINCTRL=y CONFIG_PINCTRL_BAYTRAIL=y CONFIG_PINCTRL_INTEL=y Thanks, Juinee From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Henrik Haugaard Jensen Sent: Wednesday, October 10, 2018 10:28 PM To: [email protected]<mailto:[email protected]> Subject: [meta-intel] GPIO functionality for Intel E3845 CPU (valley-island, bay-trail) We have successfully used meta-intel jethro branch for our device based on an intel E3845 CPU. Now we need to upgrade to a newer Linux kernel to get full camera/video/media support. But when building new BSP with sumo or rocko branches it turn out that pinctrl/GPIO system is not working neither with linux-intel 4.9 or 4.14. Baytrail pin-controller support and GPIO support seems to be configured for the kernel out of the box, but after booting “/sys/kernel/debug/gpio” is empty and the pin-controller gpio-chip’s is not showing in “/sys/class/gpio”. Doing initcall debugging shows that “bxt_pinctrl_init” (Broxton ) is called and not “byt_gpio_init” (Baytrail) - I have tried, but not been able, to find out why. I have tried both vanilla meta-intel sumo BSP and “ROCKO 2.4 – BAY TRAIL BSP” (meta-intel branch 8.1-rocko-2.4.2) – what is going wrong? Also I have the impression that since linux 4.8 the “/sys/class/gpio” user interface is obsolete and apparently replaced by /dev/gpioxxx pin devices and a new gpiolib userspace tool for this has been provided. Has this new GPIO interface made its way into meta-intel? Regards, Henrik Haugaard Jensen TrackMan
-- _______________________________________________ meta-intel mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-intel
