From: Jon Hunter <jonathanh@nvidia.com>
To: linux-gpio@vger.kernel.org, linus.walleij@linaro.org,
antoine.tenart@free-electrons.com
Subject: [RFI] pinmux: pin group ownership
Date: Fri, 8 May 2015 16:01:37 +0100 [thread overview]
Message-ID: <554CCFD1.5050907@nvidia.com> (raw)
Hello,
I have been reviewing the pinmux driver code and I stumbled upon the
following change.
e5b3b2d9ed202697a937c282f9c4d93b1e3e0848 (pinctrl: allows not to define
the get_group_pins operation)
Looking at this change, if pinmux_enable_setting() is called but
.get_group_pins() is not defined, then num_pins will be 0. If this is
the case then pin_request() is not called to allocate the pins in the
group (because no pins are defined for the group). So that makes sense.
However, I am trying to understand then, if the pinmux driver will
protect against another device attempting to use the same group for a
different function when already in-use?
For example, if you have the two functions i2c0 and uart0 mapped to pin
group A, but no pins are defined for group A, will pinmux prevent
someone attempting to configure both functions on the same group at the
same time?
I did not see anywhere that sets a usecount for a group (ie. allocates
the group) but only for a pin.
Cheers
Jon
next reply other threads:[~2015-05-08 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 15:01 Jon Hunter [this message]
2015-05-12 11:30 ` [RFI] pinmux: pin group ownership Linus Walleij
2015-05-12 11:53 ` Jon Hunter
2015-05-12 12:10 ` Linus Walleij
2015-05-12 12:55 ` Jon Hunter
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=554CCFD1.5050907@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=antoine.tenart@free-electrons.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.