src/sys/dev/gpio, branch stable/14 FreeBSD source tree gpioc: allocate new fifo size 2025-10-01T09:08:55+00:00 Ahmad Khalifa vexeduxr@FreeBSD.org 2025-09-30T11:55:34+00:00 80ef1216d773b09a6905dbb7cfdeac9844e2a084 This slipped through after I resolved some merge conflicts. Fixes: d000adfe MFC after: 1 day (cherry picked from commit 2679636b4412927242e46d3806fbb58e2702eddb) 
This slipped through after I resolved some merge conflicts.

Fixes:		d000adfe
MFC after:	1 day

(cherry picked from commit 2679636b4412927242e46d3806fbb58e2702eddb)
gpioc: fix race in ioctl(GPIOCONFIGEVENTS) 2025-10-01T09:08:55+00:00 Ahmad Khalifa vexeduxr@FreeBSD.org 2025-09-30T11:09:50+00:00 6163ced966b4e37a987e514aa2d2a61781c98fa5 A race can occur in gpioc_ioctl when it is called with GPIOCONFIGEVENTS closely followed by GPIOSETCONFIG. GPIOSETCONFIG can alter the priv->pins list, making it no longer empty and opening the door for access to priv->events while we are reallocating it. Fix this by holding priv->mtx while handling GPIOCONFIGEVENTS. Reported by: Qiu-ji Chen PR: 289120 Reviewed by: mmel MFC after: 1 day Differential Revision: https://reviews.freebsd.org/D52783 (cherry picked from commit d000adfe41e6f2fe8f3dbe92d8fc2d34ae882086) 
A race can occur in gpioc_ioctl when it is called with GPIOCONFIGEVENTS
closely followed by GPIOSETCONFIG. GPIOSETCONFIG can alter the
priv->pins list, making it no longer empty and opening the door for
access to priv->events while we are reallocating it. Fix this by holding
priv->mtx while handling GPIOCONFIGEVENTS.

Reported by:	Qiu-ji Chen
PR:		289120
Reviewed by:	mmel
MFC after:	1 day
Differential Revision:	https://reviews.freebsd.org/D52783

(cherry picked from commit d000adfe41e6f2fe8f3dbe92d8fc2d34ae882086)
gpioc: allocate priv->events with the correct size 2025-10-01T09:08:55+00:00 Ahmad Khalifa vexeduxr@FreeBSD.org 2025-09-30T11:09:28+00:00 39139fec932edc313e891b0a49db61ad2c64b1fe MFC after: 1 day (cherry picked from commit fa26e445544eb88f05779258e2ab9c96384fe74d) 
MFC after:	1 day

(cherry picked from commit fa26e445544eb88f05779258e2ab9c96384fe74d)
gpio: attach gpiobus when the controller is ready 2025-07-07T18:51:47+00:00 Ahmad Khalifa vexeduxr@FreeBSD.org 2025-07-04T13:52:00+00:00 cdba3a8f9fce453774833f2f1123536cd17003b8 Only attach gpiobus when the controller is fully initialized. Children of gpiobus expect this to be the case. Reviewed by: mmel, imp, andrew Approved by: imp (mentor) MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D51088 (cherry picked from commit 4695e3aa7c685c092cb4b2662bee16c31be790f8) 
Only attach gpiobus when the controller is fully initialized. Children
of gpiobus expect this to be the case.

Reviewed by:	mmel, imp, andrew
Approved by:	imp (mentor)
MFC after:	3 days
Differential Revision:	https://reviews.freebsd.org/D51088

(cherry picked from commit 4695e3aa7c685c092cb4b2662bee16c31be790f8)
gpiobus: add a gpiobus_add_bus function 2025-07-07T18:48:59+00:00 Ahmad Khalifa vexeduxr@FreeBSD.org 2025-07-04T13:51:25+00:00 c6a6b94b661378961179d832be6f1eceef91f953 Some drivers need to postpone the attachment of gpiobus until hardware init is done. Add a new gpiobus_add_bus function to accommodate this case. Suggested by: mmel, andrew Reviewed by: mmel, imp, andrew Approved by: imp (mentor) MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D51133 (cherry picked from commit 2c356c8b8f79c08d42b23a72b7a320b59d955a3f) 
Some drivers need to postpone the attachment of gpiobus until hardware
init is done. Add a new gpiobus_add_bus function to accommodate this
case.

Suggested by:	mmel, andrew
Reviewed by:	mmel, imp, andrew
Approved by:	imp (mentor)
MFC after:	3 days
Differential Revision:	https://reviews.freebsd.org/D51133

(cherry picked from commit 2c356c8b8f79c08d42b23a72b7a320b59d955a3f)
bytgpio: expose PNP info 2025-03-26T01:28:38+00:00 Ahmad Khalifa ahmadkhalifa570@gmail.com 2024-07-26T08:21:44+00:00 7d042b0af1dc0f1c7f4979507aec9681d42ee616 Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/1349 (cherry picked from commit 969484b53217cee65d6802f1954f0431cbfc6b45) 
Reviewed by: imp
Pull Request: https://github.com/freebsd/freebsd-src/pull/1349

(cherry picked from commit 969484b53217cee65d6802f1954f0431cbfc6b45)
gpioaei: Add support for ACPI _EVT method 2025-03-09T20:42:35+00:00 Vladimir Kondratyev wulf@FreeBSD.org 2025-03-07T15:59:12+00:00 e7d1f208fde82c85b061ce792f20a4aa178ec82f This method is often used to process GPIO "Power on" button press on modern x86 laptops with S0ix sleep mode. Tested with patch from https://reviews.freebsd.org/D26407 Sponsored by: Future Crew LLC MFC after: 2 month (cherry picked from commit adc2c156acb50bac6e8ec66b72cadc8910ce4975) 
This method is often used to process GPIO "Power on" button press on
modern x86 laptops with S0ix sleep mode.

Tested with patch from https://reviews.freebsd.org/D26407

Sponsored by:	Future Crew LLC
MFC after:	2 month

(cherry picked from commit adc2c156acb50bac6e8ec66b72cadc8910ce4975)
acpi_gpiobus: assume GPIO_PIN_INPUT for interrupt pins 2025-03-09T20:42:13+00:00 Ahmad Khalifa ahmadkhalifa570@gmail.com 2025-03-07T15:59:11+00:00 f05f6d93732e7d58464352e97e2dcafbab94adc4 Different drivers respond differently to having neither GPIO_PIN_INPUT or GPIO_PIN_OUTPUT set, this stops the unpredictable results. (cherry picked from commit 6aab381a498f1a43ba372f4ae9f57ef88b4767b5) 
Different drivers respond differently to having neither GPIO_PIN_INPUT
or GPIO_PIN_OUTPUT set, this stops the unpredictable results.

(cherry picked from commit 6aab381a498f1a43ba372f4ae9f57ef88b4767b5)
acpi_gpiobus: Fix cleanup on set flags failure 2025-02-27T15:10:09+00:00 Andrew Turner andrew@FreeBSD.org 2024-12-09T15:14:13+00:00 32de28db2327014b320d2f3b29b5438dcdfd928c When GPIOBUS_PIN_SETFLAGS fails we called gpiobus_free_ivars to clean up the contents of the ivar, then would free the ivar. This lead to a use-after-free as the ivar had already been set on the child so gpiobus_child_deleted would try to free it again. Fix this by removing the early cleanup and letting gpiobus_child_deleted handle it. Fixes: c9e880c0ceef ("gpiobus: Use a bus_child_deleted method to free ivars for children") Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D47670 (cherry picked from commit bb8c68b25333638a20838500ccffee23b4291427) 
When GPIOBUS_PIN_SETFLAGS fails we called gpiobus_free_ivars to clean
up the contents of the ivar, then would free the ivar. This lead to a
use-after-free as the ivar had already been set on the child so
gpiobus_child_deleted would try to free it again.

Fix this by removing the early cleanup and letting
gpiobus_child_deleted handle it.

Fixes:	c9e880c0ceef ("gpiobus: Use a bus_child_deleted method to free ivars for children")
Sponsored by:	Arm Ltd
Differential Revision:	https://reviews.freebsd.org/D47670
(cherry picked from commit bb8c68b25333638a20838500ccffee23b4291427)
gpiobus: Add missing DEVMETHOD for bus_get_rman 2025-02-27T13:09:22+00:00 John Baldwin jhb@FreeBSD.org 2024-02-23T00:14:58+00:00 b53a0db0cb41678330685c620facb828941ed237 Reported by: andrew Fixes: 5bda26333a8e gpiobus: Use bus_generic_rman_* (cherry picked from commit 04eca69323111986b262eef3135d804361b60d17) 
Reported by:	andrew
Fixes:		5bda26333a8e gpiobus: Use bus_generic_rman_*
(cherry picked from commit 04eca69323111986b262eef3135d804361b60d17)