Page MenuHomeFreeBSD

regulator: don't use internal gpiobus function
AcceptedPublic

Authored by vexeduxr on Mon, Jun 16, 7:51 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Jun 30, 3:42 PM
Unknown Object (File)
Sun, Jun 29, 6:13 PM
Unknown Object (File)
Fri, Jun 27, 2:01 AM
Unknown Object (File)
Wed, Jun 25, 11:23 AM
Unknown Object (File)
Tue, Jun 24, 1:56 PM
Unknown Object (File)
Thu, Jun 19, 4:35 AM
Unknown Object (File)
Thu, Jun 19, 4:23 AM
Unknown Object (File)
Wed, Jun 18, 8:58 PM
Subscribers

Details

Reviewers
imp
wulf
manu
mmel
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 Skipped
Unit
Tests Skipped
Build Status
Buildable 64946
Build 61829: arc lint + arc unit

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.Tue, Jun 17, 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.Tue, Jun 17, 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.Tue, Jun 17, 6:21 PM