mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* GPIO: Performance sensitive applications, gpiochip-level locking
@ 2013-09-30 17:29 Darren Hart
  2013-10-04 15:09 ` Mark Brown
  2013-10-11 14:02 ` Linus Walleij
  0 siblings, 2 replies; 6+ messages in thread
From: Darren Hart @ 2013-09-30 17:29 UTC (permalink / raw)
  To: LKML; +Cc: Grant Likely, Linus Walleij

I'm currently working with a graphics driver that makes use of 2 GPIO
pins for EDID communication (clock and data). In order to coexist
peacefully with the driver for the GPIO chip, it must use gpiolib to
request the lines, set direction, and set values. This results in a
spinlock/unlock for every operation with this particular gpio driver.

It would be preferable to lock the resources once, perform the EDID
communication, then unlock the resources. The resources in this case are
the value and direction registers off the PCI GPIO base address register
which is shared with the other lines provided by the GPIO chip.

Is there a best practice for dealing with this kind of configuration?

If not, would it make sense to add optional gpiochip-level lock/unlock
and lockless direction and value operations to the gpiochip function
block?

Thanks,

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel



^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2013-10-15 22:10 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-09-30 17:29 GPIO: Performance sensitive applications, gpiochip-level locking Darren Hart
2013-10-04 15:09 ` Mark Brown
2013-10-11 14:02 ` Linus Walleij
2013-10-14 17:29   ` Darren Hart
2013-10-15 22:02     ` Linus Walleij
2013-10-15 22:10       ` Darren Hart

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®