Public bug reported:
Hello Ubuntu Team,
I notice today using default iot and proposed iot kernel, missing TGPIO
and GPIO support.
IOT: 5.15.0-1040-intel-iotg
Proposed IOT: 5.15.0-1042-intel-iotg
With TGPIO support in kernel, i have this in dmesg:
dmesg | grep -i gpio
[ 1.954807] acpi MSFT0101:00: GPIO: looking up 0 in _CRS
[ 2.153305] i2c_designware i2c_designware.0: GPIO lookup for consumer scl
[ 2.153307] i2c_designware i2c_designware.0: using ACPI for GPIO lookup
[ 2.153309] acpi device:6b: GPIO: looking up scl-gpios
[ 2.153310] acpi device:6b: GPIO: looking up scl-gpio
[ 2.153312] i2c_designware i2c_designware.0: using lookup tables for GPIO
lookup
[ 2.153313] i2c_designware i2c_designware.0: No GPIO consumer scl found
[ 2.189085] i2c_designware i2c_designware.1: GPIO lookup for consumer scl
[ 2.189087] i2c_designware i2c_designware.1: using ACPI for GPIO lookup
[ 2.189088] acpi device:6c: GPIO: looking up scl-gpios
[ 2.189090] acpi device:6c: GPIO: looking up scl-gpio
[ 2.189091] i2c_designware i2c_designware.1: using lookup tables for GPIO
lookup
[ 2.189092] i2c_designware i2c_designware.1: No GPIO consumer scl found
[ 2.197541] mdio_bus fixed-0: GPIO lookup for consumer reset
[ 2.197542] mdio_bus fixed-0: using lookup tables for GPIO lookup
[ 2.197543] mdio_bus fixed-0: No GPIO consumer reset found
[ 2.209058] rtc_cmos rtc_cmos: GPIO lookup for consumer wp
[ 2.209059] rtc_cmos rtc_cmos: using lookup tables for GPIO lookup
[ 2.209060] rtc_cmos rtc_cmos: No GPIO consumer wp found
[ 2.626844] gpiochip_find_base: found new base at 664
[ 2.633323] gpio gpiochip0: (INTC1055:00): created GPIO range 0->25 ==>
INTC1055:00 PIN 0->25
[ 2.633327] gpio gpiochip0: (INTC1055:00): created GPIO range 32->47 ==>
INTC1055:00 PIN 26->41
[ 2.633328] gpio gpiochip0: (INTC1055:00): created GPIO range 64->88 ==>
INTC1055:00 PIN 42->66
[ 2.633329] gpio gpiochip0: (INTC1055:00): created GPIO range 96->103 ==>
INTC1055:00 PIN 67->74
[ 2.633331] gpio gpiochip0: (INTC1055:00): created GPIO range 128->151 ==>
INTC1055:00 PIN 75->98
[ 2.633332] gpio gpiochip0: (INTC1055:00): created GPIO range 160->180 ==>
INTC1055:00 PIN 99->119
[ 2.633333] gpio gpiochip0: (INTC1055:00): created GPIO range 192->215 ==>
INTC1055:00 PIN 120->143
[ 2.633334] gpio gpiochip0: (INTC1055:00): created GPIO range 224->252 ==>
INTC1055:00 PIN 144->172
[ 2.633335] gpio gpiochip0: (INTC1055:00): created GPIO range 256->279 ==>
INTC1055:00 PIN 173->196
[ 2.633337] gpio gpiochip0: (INTC1055:00): created GPIO range 288->312 ==>
INTC1055:00 PIN 197->221
[ 2.633338] gpio gpiochip0: (INTC1055:00): created GPIO range 320->344 ==>
INTC1055:00 PIN 228->252
[ 2.633339] gpio gpiochip0: (INTC1055:00): created GPIO range 352->359 ==>
INTC1055:00 PIN 262->269
[ 2.633397] gpio gpiochip0: (INTC1055:00): added GPIO chardev (254:0)
[ 2.633412] gpio gpiochip0: registered GPIOs 664 to 1023 on INTC1055:00
[ 4.144080] usb 3-10: GPIO lookup for consumer reset
[ 4.144084] usb 3-10: using ACPI for GPIO lookup
[ 4.144086] acpi device:5f: GPIO: looking up reset-gpios
[ 4.144088] acpi device:5f: GPIO: looking up reset-gpio
[ 4.144089] usb 3-10: using lookup tables for GPIO lookup
[ 4.144090] usb 3-10: No GPIO consumer reset found
[ 4.184939] usb 4-1: GPIO lookup for consumer privacy
[ 4.184941] usb 4-1: using ACPI for GPIO lookup
[ 4.184943] acpi device:62: GPIO: looking up privacy-gpios
[ 4.184945] acpi device:62: GPIO: looking up privacy-gpio
[ 4.184945] usb 4-1: using lookup tables for GPIO lookup
[ 4.184946] usb 4-1: No GPIO consumer privacy found
[ 4.186515] usb 4-1: GPIO lookup for consumer privacy
[ 4.186516] usb 4-1: using ACPI for GPIO lookup
[ 4.186517] acpi device:62: GPIO: looking up privacy-gpios
[ 4.186518] acpi device:62: GPIO: looking up privacy-gpio
[ 4.186519] usb 4-1: using lookup tables for GPIO lookup
[ 4.186519] usb 4-1: No GPIO consumer privacy found
But the support in the IOT kernel does not exist.
# dmesg | grep -i gpio
# uname -a
Linux 5.15.0-1042-intel-iotg #48-Ubuntu SMP Wed Sep 20 15:09:23 UTC 2023 x86_64
x86_64 x86_64 GNU/Linux
Is it possible that in the next version we will have support for GPIO
and TGPIO?
** Affects: linux-intel-iotg (Ubuntu)
Importance: Undecided
Status: New
** Tags: gpio
** Description changed:
Hello Ubuntu Team,
I notice today using default iot and proposed iot kernel, missing TGPIO
and GPIO support.
IOT: 5.15.0-1040-intel-iotg
Proposed IOT: 5.15.0-1042-intel-iotg
-
With TGPIO support in kernel, i have this in dmesg:
dmesg | grep -i gpio
[ 1.954807] acpi MSFT0101:00: GPIO: looking up 0 in _CRS
[ 2.153305] i2c_designware i2c_designware.0: GPIO lookup for consumer scl
[ 2.153307] i2c_designware i2c_designware.0: using ACPI for GPIO lookup
[ 2.153309] acpi device:6b: GPIO: looking up scl-gpios
[ 2.153310] acpi device:6b: GPIO: looking up scl-gpio
[ 2.153312] i2c_designware i2c_designware.0: using lookup tables for GPIO
lookup
[ 2.153313] i2c_designware i2c_designware.0: No GPIO consumer scl found
[ 2.189085] i2c_designware i2c_designware.1: GPIO lookup for consumer scl
[ 2.189087] i2c_designware i2c_designware.1: using ACPI for GPIO lookup
[ 2.189088] acpi device:6c: GPIO: looking up scl-gpios
[ 2.189090] acpi device:6c: GPIO: looking up scl-gpio
[ 2.189091] i2c_designware i2c_designware.1: using lookup tables for GPIO
lookup
[ 2.189092] i2c_designware i2c_designware.1: No GPIO consumer scl found
[ 2.197541] mdio_bus fixed-0: GPIO lookup for consumer reset
[ 2.197542] mdio_bus fixed-0: using lookup tables for GPIO lookup
[ 2.197543] mdio_bus fixed-0: No GPIO consumer reset found
[ 2.209058] rtc_cmos rtc_cmos: GPIO lookup for consumer wp
[ 2.209059] rtc_cmos rtc_cmos: using lookup tables for GPIO lookup
[ 2.209060] rtc_cmos rtc_cmos: No GPIO consumer wp found
[ 2.626844] gpiochip_find_base: found new base at 664
[ 2.633323] gpio gpiochip0: (INTC1055:00): created GPIO range 0->25 ==>
INTC1055:00 PIN 0->25
[ 2.633327] gpio gpiochip0: (INTC1055:00): created GPIO range 32->47 ==>
INTC1055:00 PIN 26->41
[ 2.633328] gpio gpiochip0: (INTC1055:00): created GPIO range 64->88 ==>
INTC1055:00 PIN 42->66
[ 2.633329] gpio gpiochip0: (INTC1055:00): created GPIO range 96->103 ==>
INTC1055:00 PIN 67->74
[ 2.633331] gpio gpiochip0: (INTC1055:00): created GPIO range 128->151 ==>
INTC1055:00 PIN 75->98
[ 2.633332] gpio gpiochip0: (INTC1055:00): created GPIO range 160->180 ==>
INTC1055:00 PIN 99->119
[ 2.633333] gpio gpiochip0: (INTC1055:00): created GPIO range 192->215 ==>
INTC1055:00 PIN 120->143
[ 2.633334] gpio gpiochip0: (INTC1055:00): created GPIO range 224->252 ==>
INTC1055:00 PIN 144->172
[ 2.633335] gpio gpiochip0: (INTC1055:00): created GPIO range 256->279 ==>
INTC1055:00 PIN 173->196
[ 2.633337] gpio gpiochip0: (INTC1055:00): created GPIO range 288->312 ==>
INTC1055:00 PIN 197->221
[ 2.633338] gpio gpiochip0: (INTC1055:00): created GPIO range 320->344 ==>
INTC1055:00 PIN 228->252
[ 2.633339] gpio gpiochip0: (INTC1055:00): created GPIO range 352->359 ==>
INTC1055:00 PIN 262->269
[ 2.633397] gpio gpiochip0: (INTC1055:00): added GPIO chardev (254:0)
[ 2.633412] gpio gpiochip0: registered GPIOs 664 to 1023 on INTC1055:00
[ 4.144080] usb 3-10: GPIO lookup for consumer reset
[ 4.144084] usb 3-10: using ACPI for GPIO lookup
[ 4.144086] acpi device:5f: GPIO: looking up reset-gpios
[ 4.144088] acpi device:5f: GPIO: looking up reset-gpio
[ 4.144089] usb 3-10: using lookup tables for GPIO lookup
[ 4.144090] usb 3-10: No GPIO consumer reset found
[ 4.184939] usb 4-1: GPIO lookup for consumer privacy
[ 4.184941] usb 4-1: using ACPI for GPIO lookup
[ 4.184943] acpi device:62: GPIO: looking up privacy-gpios
[ 4.184945] acpi device:62: GPIO: looking up privacy-gpio
[ 4.184945] usb 4-1: using lookup tables for GPIO lookup
[ 4.184946] usb 4-1: No GPIO consumer privacy found
[ 4.186515] usb 4-1: GPIO lookup for consumer privacy
[ 4.186516] usb 4-1: using ACPI for GPIO lookup
[ 4.186517] acpi device:62: GPIO: looking up privacy-gpios
[ 4.186518] acpi device:62: GPIO: looking up privacy-gpio
[ 4.186519] usb 4-1: using lookup tables for GPIO lookup
[ 4.186519] usb 4-1: No GPIO consumer privacy found
-
But the support in the IOT kernel does not exist.
- # dmesg | grep -i gpio
- # uname -a
- Linux glaic3n170 5.15.0-1042-intel-iotg #48-Ubuntu SMP Wed Sep 20 15:09:23
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
+ # dmesg | grep -i gpio
+ # uname -a
+ Linux 5.15.0-1042-intel-iotg #48-Ubuntu SMP Wed Sep 20 15:09:23 UTC 2023
x86_64 x86_64 x86_64 GNU/Linux
Is it possible that in the next version we will have support for GPIO
and TGPIO?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/2039802
Title:
[IOTG][ADL-P] TGPIO enabling
Status in linux-intel-iotg package in Ubuntu:
New
Bug description:
Hello Ubuntu Team,
I notice today using default iot and proposed iot kernel, missing
TGPIO and GPIO support.
IOT: 5.15.0-1040-intel-iotg
Proposed IOT: 5.15.0-1042-intel-iotg
With TGPIO support in kernel, i have this in dmesg:
dmesg | grep -i gpio
[ 1.954807] acpi MSFT0101:00: GPIO: looking up 0 in _CRS
[ 2.153305] i2c_designware i2c_designware.0: GPIO lookup for consumer scl
[ 2.153307] i2c_designware i2c_designware.0: using ACPI for GPIO lookup
[ 2.153309] acpi device:6b: GPIO: looking up scl-gpios
[ 2.153310] acpi device:6b: GPIO: looking up scl-gpio
[ 2.153312] i2c_designware i2c_designware.0: using lookup tables for GPIO
lookup
[ 2.153313] i2c_designware i2c_designware.0: No GPIO consumer scl found
[ 2.189085] i2c_designware i2c_designware.1: GPIO lookup for consumer scl
[ 2.189087] i2c_designware i2c_designware.1: using ACPI for GPIO lookup
[ 2.189088] acpi device:6c: GPIO: looking up scl-gpios
[ 2.189090] acpi device:6c: GPIO: looking up scl-gpio
[ 2.189091] i2c_designware i2c_designware.1: using lookup tables for GPIO
lookup
[ 2.189092] i2c_designware i2c_designware.1: No GPIO consumer scl found
[ 2.197541] mdio_bus fixed-0: GPIO lookup for consumer reset
[ 2.197542] mdio_bus fixed-0: using lookup tables for GPIO lookup
[ 2.197543] mdio_bus fixed-0: No GPIO consumer reset found
[ 2.209058] rtc_cmos rtc_cmos: GPIO lookup for consumer wp
[ 2.209059] rtc_cmos rtc_cmos: using lookup tables for GPIO lookup
[ 2.209060] rtc_cmos rtc_cmos: No GPIO consumer wp found
[ 2.626844] gpiochip_find_base: found new base at 664
[ 2.633323] gpio gpiochip0: (INTC1055:00): created GPIO range 0->25 ==>
INTC1055:00 PIN 0->25
[ 2.633327] gpio gpiochip0: (INTC1055:00): created GPIO range 32->47 ==>
INTC1055:00 PIN 26->41
[ 2.633328] gpio gpiochip0: (INTC1055:00): created GPIO range 64->88 ==>
INTC1055:00 PIN 42->66
[ 2.633329] gpio gpiochip0: (INTC1055:00): created GPIO range 96->103 ==>
INTC1055:00 PIN 67->74
[ 2.633331] gpio gpiochip0: (INTC1055:00): created GPIO range 128->151 ==>
INTC1055:00 PIN 75->98
[ 2.633332] gpio gpiochip0: (INTC1055:00): created GPIO range 160->180 ==>
INTC1055:00 PIN 99->119
[ 2.633333] gpio gpiochip0: (INTC1055:00): created GPIO range 192->215 ==>
INTC1055:00 PIN 120->143
[ 2.633334] gpio gpiochip0: (INTC1055:00): created GPIO range 224->252 ==>
INTC1055:00 PIN 144->172
[ 2.633335] gpio gpiochip0: (INTC1055:00): created GPIO range 256->279 ==>
INTC1055:00 PIN 173->196
[ 2.633337] gpio gpiochip0: (INTC1055:00): created GPIO range 288->312 ==>
INTC1055:00 PIN 197->221
[ 2.633338] gpio gpiochip0: (INTC1055:00): created GPIO range 320->344 ==>
INTC1055:00 PIN 228->252
[ 2.633339] gpio gpiochip0: (INTC1055:00): created GPIO range 352->359 ==>
INTC1055:00 PIN 262->269
[ 2.633397] gpio gpiochip0: (INTC1055:00): added GPIO chardev (254:0)
[ 2.633412] gpio gpiochip0: registered GPIOs 664 to 1023 on INTC1055:00
[ 4.144080] usb 3-10: GPIO lookup for consumer reset
[ 4.144084] usb 3-10: using ACPI for GPIO lookup
[ 4.144086] acpi device:5f: GPIO: looking up reset-gpios
[ 4.144088] acpi device:5f: GPIO: looking up reset-gpio
[ 4.144089] usb 3-10: using lookup tables for GPIO lookup
[ 4.144090] usb 3-10: No GPIO consumer reset found
[ 4.184939] usb 4-1: GPIO lookup for consumer privacy
[ 4.184941] usb 4-1: using ACPI for GPIO lookup
[ 4.184943] acpi device:62: GPIO: looking up privacy-gpios
[ 4.184945] acpi device:62: GPIO: looking up privacy-gpio
[ 4.184945] usb 4-1: using lookup tables for GPIO lookup
[ 4.184946] usb 4-1: No GPIO consumer privacy found
[ 4.186515] usb 4-1: GPIO lookup for consumer privacy
[ 4.186516] usb 4-1: using ACPI for GPIO lookup
[ 4.186517] acpi device:62: GPIO: looking up privacy-gpios
[ 4.186518] acpi device:62: GPIO: looking up privacy-gpio
[ 4.186519] usb 4-1: using lookup tables for GPIO lookup
[ 4.186519] usb 4-1: No GPIO consumer privacy found
But the support in the IOT kernel does not exist.
# dmesg | grep -i gpio
# uname -a
Linux 5.15.0-1042-intel-iotg #48-Ubuntu SMP Wed Sep 20 15:09:23 UTC 2023
x86_64 x86_64 x86_64 GNU/Linux
Is it possible that in the next version we will have support for GPIO
and TGPIO?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2039802/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
