From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: Query on pinctrl usage for DT nodes
Date: Mon, 15 Apr 2013 10:40:20 -0600 [thread overview]
Message-ID: <516C2D74.2090106@wwwdotorg.org> (raw)
In-Reply-To: <516BB818.3060603@ti.com>
On 04/15/2013 02:19 AM, Peter Ujfalusi wrote:
> Hi,
>
> On 04/03/2013 08:42 PM, Tony Lindgren wrote:
>> Oh it's already using pinctrl-single,bits option. Maybe there's a
>> bug, adding Peter to cc.
>
> I think all boils down to the fact that in pinctrl (single only?) _one_
> register can be only associated with _one_ driver. Even through ,bit type
> would allow us to only change parts of the same register, another device can
> not take the same register with different mask.
pinctrl itself certainly imposes no such restriction that I'm aware of.
pinctrl is only concerned with the ownership of *pins* (or perhaps
groups). The mapping of pins to registers is something entirely internal
to individual pinctrl drivers.
So, the solution here is for pinctrl-single to create a separate
pin/group object for each separately controllable entity, and that may
be each bit in a register rather than each register, depending on HW.
next prev parent reply other threads:[~2013-04-15 16:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 9:16 Query on pinctrl usage for DT nodes Prabhakar Lad
2013-04-03 16:44 ` Stephen Warren
2013-04-03 18:38 ` Tony Lindgren
2013-04-03 18:42 ` Tony Lindgren
2013-04-15 8:19 ` Peter Ujfalusi
2013-04-15 16:40 ` Stephen Warren [this message]
2013-04-16 7:18 ` Peter Ujfalusi
2013-04-08 13:12 ` Prabhakar Lad
2013-04-08 17:24 ` Stephen Warren
2013-04-10 8:12 ` Prabhakar Lad
2013-04-10 17:32 ` Stephen Warren
2013-04-10 20:34 ` Tony Lindgren
2013-04-15 5:09 ` Prabhakar Lad
2013-04-15 6:42 ` Prabhakar Lad
2013-04-15 8:26 ` Peter Ujfalusi
2013-04-16 21:32 ` Tony Lindgren
2013-04-23 7:42 ` Peter Ujfalusi
2013-04-23 18:17 ` Tony Lindgren
2013-05-21 14:16 ` Manjunathappa, Prakash
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=516C2D74.2090106@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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