From: Darren Hart <dvhart@linux.intel.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Grant Likely <grant.likely@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: GPIO: Performance sensitive applications, gpiochip-level locking
Date: Mon, 30 Sep 2013 10:29:26 -0700 [thread overview]
Message-ID: <1380562166.32071.172.camel@dvhart-mobl4.amr.corp.intel.com> (raw)
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
next reply other threads:[~2013-09-30 17:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 17:29 Darren Hart [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1380562166.32071.172.camel@dvhart-mobl4.amr.corp.intel.com \
--to=dvhart@linux.intel.com \
--cc=grant.likely@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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®