Page MenuHomeFreeBSD

regulator: don't use internal gpiobus function
ClosedPublic

Authored by vexeduxr on Jun 16 2025, 7:51 AM.
Tags
None
Referenced Files
F171483837: D50870.id157091.diff
Fri, Sep 11, 9:39 AM
Unknown Object (File)
Wed, Sep 9, 8:25 PM
Unknown Object (File)
Sun, Sep 6, 7:08 PM
Unknown Object (File)
Sat, Sep 5, 2:48 AM
Unknown Object (File)
Fri, Sep 4, 10:34 AM
Unknown Object (File)
Fri, Sep 4, 9:36 AM
Unknown Object (File)
Fri, Sep 4, 9:34 AM
Unknown Object (File)
Fri, Aug 28, 1:59 PM
Subscribers

Details

Summary

gpiobus_acquire_pin is only meant to be used internally by gpiobus. Use
gpio_pin_acquire instead.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

manu added a reviewer: mmel.

I think that it should be ok but let's wait for @mmel

This revision is now accepted and ready to land.Jun 17 2025, 7:59 AM

Why did you remove the comment? IMHO it is still a bit problematic (or not well defined) to hold the mutex across the GPIO infrastructure call.

I don't really see why it would cause problems. With the current implementation at least.
Thinking about this some more, it's very possible that a future change to gpiobus_acquire_pin or gpio_pin_acquire can break this though...

This revision now requires review to proceed.Jun 17 2025, 5:09 PM

Thanks.
The most problematic variant is GPIO over I2C bus (or other serial bus), where sleepable(SX) locks are required for basic operation. So I just was to be very careful and warn others of the problematic place.

This revision is now accepted and ready to land.Jun 17 2025, 6:21 PM

Looks good, but this is more 'permission to commit' rather than 'the change is good'. I trust the people that reviewed it and didn't see anything insane.